https://bugs.kde.org/show_bug.cgi?id=481318
Mladen Milinkovic, Max changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=481318
--- Comment #3 from Joe Breuer ---
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
https://bugs.kde.org/show_bug.cgi?id=481318
Mladen Milinkovic, Max changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=481315
https://bugs.kde.org/show_bug.cgi?id=481318
--- Comment #2 from Joe Breuer ---
(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, th
https://bugs.kde.org/show_bug.cgi?id=481318
Andreas Sturmlechner changed:
What|Removed |Added
CC||ast...@gentoo.org
See Also|
https://bugs.kde.org/show_bug.cgi?id=481318
--- Comment #1 from Mladen Milinkovic, Max ---
Thanks for the report.
This is probably fixed with commit 0f99f801e3a4bf779167e15e151b14e8ca962f87.
Can you try building/testing current master?
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=481318
Joe Breuer changed:
What|Removed |Added
Assignee|unassigned-b...@kde.org |max...@smoothware.net
Product|unknown
