GNOME Bugzilla – Bug 573940
Rhythmbox crashes with segfault
Last modified: 2009-03-05 01:32:10 UTC
Please describe the problem: Rhythmbox crashes unexpectedly due to some sort of glib issue. Steps to reproduce: Running rhythmbox from the command line to see error messages. Actual results: This msg is output repeatedly: (rhythmbox:12467): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed And finally: (rhythmbox:12467): GStreamer-CRITICAL **: gst_element_post_message: assertion `GST_IS_ELEMENT (element)' failed Segmentation fault This is when the program quits. Expected results: It would not output these messages and especially wouldn't crash. Does this happen every time? Yes. Other information:
I should also mention that this only occurs during playback.
seems to be a problem when crossfading is enabled.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Update: I did a reinstall of rhythmbox (via synaptic). Also I should mention that I'm using the latest git checkouts of all the gstreamer modules. After the reinstall, the original crasher is gone and I don't get those messages anymore, but when I do a seek (while crossfading is enabled) the window becomes unresponsive and playback stops. Here's the stacktrace from bugbuddy: Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.3 2008-07-09 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-23-rt #1 SMP PREEMPT RT Mon Jan 26 02:29:24 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 143548416 vsize: 143548416 resident: 40849408 share: 19742720 rss: 40849408 rss_rlim: 4294967295 CPU usage: start_time: 1236112451 rtime: 252 utime: 192 stime: 60 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/local/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0xb662d740 (LWP 19054)] [New Thread 0xb03fab90 (LWP 19082)] [New Thread 0xb0bfbb90 (LWP 19081)] [New Thread 0xb13fcb90 (LWP 19079)] [New Thread 0xb3f55b90 (LWP 19078)] [New Thread 0xb23feb90 (LWP 19077)] [New Thread 0xb2bffb90 (LWP 19076)] [New Thread 0xb3754b90 (LWP 19075)] [New Thread 0xb1bfdb90 (LWP 19074)] [New Thread 0xb4a5fb90 (LWP 19058)] 0xb7fe3410 in __kernel_vsyscall ()
+ Trace 213127
Thread 1 (Thread 0xb662d740 (LWP 19054))
----------- .xsession-errors (69 sec old) --------------------- Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600025 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600025 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
That appears to be a stack trace from a completely different problem. What version of rhythmbox are you using?
0.11.5-0ubuntu8 on Ubuntu hardy heron.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 553230 ***