[Gstreamer-bugs] [Bug 113533] Changed - gst-player 0.5.x blocks hardware and gnome software

bugzilla-daemon at widget.gnome.org bugzilla-daemon at widget.gnome.org
Tue Aug 5 02:10:45 PDT 2003


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=113533

Changed by dh at onclick.org.

--- shadow/113533	Mon Aug  4 17:58:07 2003
+++ shadow/113533.tmp.28501	Tue Aug  5 05:10:44 2003
@@ -32,6 +32,28 @@
 fairly sure that something else is keeping the actual scheduler busy
 before it can do userspace jobs like killing other userspace apps or
 so. This might be a video driver bug (Xv!) or such a thing, but really
 doesn't sound like anything GStreamer related, unless you can provide
 a test case of some sort (please note that none of us could reproduce
 any of this)...
+
+------- Additional Comments From dh at onclick.org  2003-08-05 05:10 -------
+It is absolutely gst-player related. All the other apps do not start,
+go on or do not even close just because of gst-player. I just have to
+close gst-player and all other products behave normal!!! This
+behaviour isn't easy to reproduce because it happens quite suddenly
+and does not show a schema. But it happens several times a day.
+
+gst-player even prevents gnome-system-monitor from killing processes
+(it freezes while trying to) though ps still works fine. If I kill
+gst-player the gnome-system-monitor suddenly goes on. 
+
+I believe that this is related to bonobo-activation because all gnome
+apps rely on bonobo-activation-server. There must be some blocking or
+locking of bonobo activities through gst-player. This could even lock
+my cd-burner since it may just be locked by a bonobo-component that is
+not releasing grip. That the cd-burner does not loose grip after
+reboot may be a hardware problem. If I open the tray at start-up by
+pressing the button over a long period the burner behaves normal again.
+
+I used gst-player with all new 2.3.x releases and the problem is still
+the same.




More information about the Gstreamer-bugs mailing list