Summary: | subtitlecomposer crashes | ||
---|---|---|---|
Product: | [Applications] subtitlecomposer | Reporter: | Joe Breuer <kde> |
Component: | general | Assignee: | Mladen Milinkovic, Max <maxrd2> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | asturm |
Priority: | NOR | Keywords: | drkonqi |
Version: | 0.8.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Joe Breuer
2024-02-14 11:43:20 UTC
Thanks for the report. This is probably fixed with commit 0f99f801e3a4bf779167e15e151b14e8ca962f87. Can you try building/testing current master? (In reply to Mladen Milinkovic, Max from comment #1) > Thanks for the report. > This is probably fixed with commit 0f99f801e3a4bf779167e15e151b14e8ca962f87. > Can you try building/testing current master? Thank you, that's a great idea! Unfortunately, the master branch doesn't readily build on gentoo. The ebuild mentions some patches having to do with turning off unavailable tests - I'll have a deeper look tomorrow / "soon". On a fresh day, with sufficient coffee, I managed to pull in that "tests-optional" patchset. And I'm happy to report that the crash is gone; I can play and seek to and past the point that always was a problem in 0.8.0 without any issues now. How does KDE handle bug reports? Do you have/use a specific state for "it's fixed in git, but no release yet", or would this be just RESOLVED FIXED? (In reply to Joe Breuer from comment #3) > On a fresh day, with sufficient coffee, I managed to pull in that > "tests-optional" patchset. > > And I'm happy to report that the crash is gone; I can play and seek to and > past the point that always was a problem in 0.8.0 without any issues now. Great! Thank you for reporting it. > How does KDE handle bug reports? Do you have/use a specific state for "it's > fixed in git, but no release yet", or would this be just RESOLVED FIXED? Just flagged it as RESOLVED/FIXED... No need to worry about release here. |