Bug 29990 - obs-studio [UPDATE REQUEST]: 26.1.2 > 27.1.3
Summary: obs-studio [UPDATE REQUEST]: 26.1.2 > 27.1.3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 29982
  Show dependency treegraph
 
Reported: 2022-02-03 06:28 CET by Nikolay Sabelnikov
Modified: 2022-02-03 23:52 CET (History)
3 users (show)

See Also:
Source RPM: obs-studio
CVE:
Status comment:


Attachments

Description Nikolay Sabelnikov 2022-02-03 06:28:50 CET
A version update is required. Perhaps it will solve my bug.
Nikolay Sabelnikov 2022-02-03 06:29:53 CET

CC: (none) => 79625490833
Blocks: (none) => 29982

Nikolay Sabelnikov 2022-02-03 06:30:46 CET

Blocks: 29982 => (none)

Nikolay Sabelnikov 2022-02-03 06:31:07 CET

Blocks: (none) => 29982

Comment 1 Morgan Leijström 2022-02-03 09:50:59 CET
Thank you for the suggestion

Please, you need to make more clear summaries.
We should not need to open the bug to see what it is about.

Same goes for the summary.

(In reply to Nikolay Sabelnikov from comment #0)
> A version update is required.

Except nice to have, do it bring something specific?
We dont have manpower to update every package to latest, so we need information in order to prioritise.



> Perhaps it will solve my bug.

In bug 29982 sturmvogel replied:

> With the tainted package obs-studio-26.1.2-1.mga8.tainted.x86_64.rpm this problem don't occur.

Did you try the tainted version?
Maybe the nontainted per circumstances can not run that encoder.
Please reply in that bug.

CC: (none) => fri
Summary: [UPDATE REQUEST]: 26.1.2 > 27.1.3 => obs-studio [UPDATE REQUEST]: 26.1.2 > 27.1.3

Comment 2 Rémi Verschelde 2022-02-03 23:52:00 CET
This is not needed to "fix" bug 29982 but the update has been done in Cauldron anyone, it was on my backlog for a while.

CC: (none) => rverschelde
Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.