GNOME Bugzilla – Bug 617842
crash in Rhythmbox: (rhythmbox-metadata:9092...
Last modified: 2010-09-04 05:45:41 UTC
Version: 0.12.8 What were you doing when the application crashed? (rhythmbox-metadata:9092): GStreamer-CRITICAL **: Trying to dispose object "id3v2mux0", but it still has a parent "pipeline". You need to let the parent manage the object instead of unreffing the object directly. Same thing of bug, https://bugzilla.gnome.org/show_bug.cgi?id=614483, but with traces (glib2 and rhythmbox) and newer packages. Distribution: Unknown Gnome Release: 2.30.0 2010-03-30 (Archlinux) BugBuddy Version: 2.30.0 System: Linux 2.6.33-ARCH #1 SMP PREEMPT Sun May 2 10:40:03 CEST 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10800901 Selinux: No Accessibility: Disabled GTK+ Theme: Radiance Icon Theme: ubuntu-mono-light GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 646279168 vsize: 646279168 resident: 69058560 share: 30470144 rss: 69058560 rss_rlim: 18446744073709551615 CPU usage: start_time: 1273114047 rtime: 1132 utime: 1061 stime: 71 cutime:0 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0x7f4a25288710 (LWP 9023)] [New Thread 0x7f4a37325710 (LWP 9020)] [New Thread 0x7f4a3b75c710 (LWP 9019)] 0x00007f4a45fcb803 in poll () from /lib/libc.so.6
+ Trace 221747
Inferior 1 [process 9015] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (111 sec old) --------------------- ** (gnome-power-manager:2446): WARNING **: proxy failed ** (gnome-power-manager:2446): WARNING **: failed to get Computer root object ** (gnome-power-manager:2446): WARNING **: proxy NULL!! ** Message: Initializing gksu extension... Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00057 (Reprodutor) Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00057 (Reprodutor) Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00057 (Reprodutor) Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000057 (Reprodutor) Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
Created attachment 160394 [details] The syslog Something appeared at my syslog when the crash happened.
Not sure quite what's happening here, but the stack traces you're providing aren't even from the right process. rhythmbox-metadata is the thing that's "crashing" (it's presumably only crashing because you have G_DEBUG=fatal-warnings or similar set somewhere), so you need to provide a stack trace from that, not rhythmbox itself.
I'm a newbie here, how can i get rhythmbox-metadata stack traces if it crashs?
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!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of bug 628254 ***