GNOME Bugzilla – Bug 547235
crash in Rhythmbox Music Player: music player
Last modified: 2008-08-11 20:10:08 UTC
Version: 0.11.5 What were you doing when the application crashed? music player Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: SphereCrystal Memory status: size: 60719104 vsize: 60719104 resident: 31268864 share: 16912384 rss: 31268864 rss_rlim: 4294967295 CPU usage: start_time: 1218423907 rtime: 126 utime: 106 stime: 20 cutime:1 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb655d740 (LWP 17452)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 204967
Thread 1 (Thread 0xb655d740 (LWP 17452))
----------- .xsession-errors (32986 sec old) --------------------- ** (gnome-cups-icon:3308): WARNING **: IPP request failed with status 1280 ** (nm-applet:3307): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.16" is not allowed to own the service "org.freedesktop.Networ ** (gnome-cups-icon:3308): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3308): WARNING **: IPP request failed with status 1280 ** (nm-applet:3307): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.16" is not allowed to own the service "org.freedesktop.Networ ** (gnome-cups-icon:3308): WARNING **: IPP request failed with status 1280 ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 524985 ***