GNOME Bugzilla – Bug 454822
crash in Rhythmbox Music Player: Starting up listening to...
Last modified: 2007-07-08 12:25:57 UTC
What were you doing when the application crashed? Starting up listening to a streaming session, probably with non-functional sound set up. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 135323648 vsize: 135323648 resident: 38326272 share: 24043520 rss: 38326272 rss_rlim: 4294967295 CPU usage: start_time: 1183895800 rtime: 545 utime: 302 stime: 243 cutime:2 cstime: 0 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 -1208792528 (LWP 12599)] [New Thread -1220498544 (LWP 12612)] [New Thread -1268474992 (LWP 12611)] [New Thread -1257985136 (LWP 12610)] [New Thread -1257718896 (LWP 12609)] [New Thread -1244284016 (LWP 12605)] (no debugging symbols found) 0x00b9f402 in __kernel_vsyscall ()
+ Trace 146491
Thread 3 (Thread -1268474992 (LWP 12611))
----------- .xsession-errors (35 sec old) --------------------- localuser:prop being added to access control list SESSION_MANAGER=local/telesfor.scotclimb.org.uk:/tmp/.ICE-unix/11829 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3c00021 (Music Play); these messages lack timestamps and therefore suck. Xlib: unexpected async reply (sequence 0xcc83)! --------------------------------------------------
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 436498 ***