Description of problem: When I try to play ogv video on freshly installed F18 Beta in KDE, Dragon Player crashes. How reproducible: Always Steps to Reproduce: 1. Try to open ogv video, for example this https://bugzilla.redhat.com/attachment.cgi?id=628062 Actual results: It crashes. When run from console, there is: QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::begin: Paint device returned engine == 0, type: 2 QSocketNotifier: Invalid socket 7 and type 'Read', disabling... dragon: Fatal IO error: client killed (dragon:14122): GStreamer-CRITICAL **: gstsystemclock: write control failed in wakeup_async: 9:Bad file descriptor (dragon:14122): GStreamer-CRITICAL **: gst_system_clock_remove_wakeup: assertion `sysclock->priv->wakeup_count > 0' failed Unable to start Dr. Konqi Expected results: It should run.
Hmmm, this sounds a lot like a hardware driver issue, what graphics driver are you using? If this is reproducible on other systems, it probably qualifies as a Final blocker because Dragon Player isn't withstanding a basic functionality test.
I have tried it in virt-manager - qemu and kvm. I'll try it on bare hardware.
It seems that it works on bare hardware...
This one also sounds like a driver issue.
Still relevant with F20 host and F20 guest
A backtrace would likely be helpful, either from drkonqi or abrt.
Created attachment 837774 [details] thread apply all bt Culprit: Thread 8 (Thread 0x7fffd551c700 (LWP 4390)): #0 0x0000003337293fe5 in __memcpy_sse2_unaligned () from /lib64/libc.so.6 #1 0x00007fffd4b13fee in theora_dec_decode_buffer () from /usr/lib64/gstreamer-0.10/libgsttheora.so #2 0x00007fffd4b151e2 in theora_dec_chain () from /usr/lib64/gstreamer-0.10/libgsttheora.so #3 0x00007fffeb5f44c1 in gst_pad_push () from /lib64/libgstreamer-0.10.so.0 #4 0x00007fffd8312081 in gst_multi_queue_loop () from /usr/lib64/gstreamer-0.10/libgstcoreelements.so #5 0x00007fffeb61a394 in gst_task_func () from /lib64/libgstreamer-0.10.so.0 #6 0x000000333966f406 in g_thread_pool_thread_proxy () from /lib64/libglib-2.0.so.0 #7 0x000000333966ea45 in g_thread_proxy () from /lib64/libglib-2.0.so.0 #8 0x0000003337a07f33 in start_thread () from /lib64/libpthread.so.0 #9 0x00000033372f4ead in clone () from /lib64/libc.so.6
Looks like Problem starts from gstreamer-0.10/libgsttheora.so , let's start there, then possibly drill down to glibc/qemu.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.