Description of problem: subtitlecomposer 0.6.4 has a ASS parsing bug that was fixed in version 0.6.5. I tripped on the ASS parsing bug but there are several other bug fixes in 0.6.5. This bug report is a request to update subtitlecomposer to version 0.6.5 (the most recent to date). Version-Release number of selected component (if applicable): $ rpm -q subtitlecomposer subtitlecomposer-0.6.4-4.mga6 How reproducible: Always. Steps to Reproduce: 1. Run subtitlecomposer; 2. Open a ASS file that triggers the bug.
Done! subtitlecomposer is now up-to-date for mga6.
Assignee: bugsquad => geiger.david68210CC: (none) => geiger.david68210
Again, many thanks David. Installed and tested without issues. This issue is resolved. The ASS files that were previously triggering this issue are loading correctly with the updated version. System: Mageia 6, Plasma DE, x86_64, Intel CPU, nVidia GPU using nvidia340 proprietary driver. $ uname -a Linux marte 4.14.13-desktop-1.mga6 #1 SMP Wed Jan 10 12:48:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ rpm -q subtitlecomposer subtitlecomposer-0.6.5-1.mga6
Assigning to QA now, Advisory: ======================== Some users reported that our current subtitlecomposer package has some bugs especially an ASS parsing bug. So this updates subtitlecomposer to a version which is supported and maintained upstream. And also it fixes some others upstream bugs. ======================== Packages in 6/core/updates_testing: ======================== subtitlecomposer-0.6.5-1.mga6.i586.rpm subtitlecomposer-0.6.5-1.mga6.x86_64.rpm Source RPM: ======================== subtitlecomposer-0.6.5-1.mga6.src.rpm
Assignee: geiger.david68210 => qa-bugs
Already tested so marking it as OK for x86_64.
Whiteboard: (none) => MGA6-64-OK
Advisory uploaded. Thanks PC_LX for your testing, which allows validating the update.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0021.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED