GNOME Bugzilla – Bug 495604
crash in Rhythmbox Music Player: just listening to musig ...
Last modified: 2007-11-15 09:19:27 UTC
Version: 0.10.1 What were you doing when the application crashed? just listening to musig ... white stripes Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 172298240 vsize: 172298240 resident: 57663488 share: 39096320 rss: 57663488 rss_rlim: 4294967295 CPU usage: start_time: 1194703806 rtime: 9061 utime: 8112 stime: 949 cutime:4 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208604112 (LWP 3904)] [New Thread -1299338352 (LWP 4911)] [New Thread -1288639600 (LWP 4910)] [New Thread -1277334640 (LWP 3911)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176807
Thread 3 (Thread -1288639600 (LWP 4910))
----------- .xsession-errors (207 sec old) --------------------- (gtk-window-decorator:3361): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed (gtk-window-decorator:3361): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] --------------------------------------------------
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 434996 ***