GNOME Bugzilla – Bug 506554
crash in Rhythmbox Music Player: Nothing. It just crashed...
Last modified: 2007-12-31 10:34:07 UTC
Version: 0.11.3 What were you doing when the application crashed? Nothing. It just crashed by itself, probably sending my iPod data to last.fm. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.21.4 2007-12-27 (GARNOME) BugBuddy Version: 2.20.1 System: Linux 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 126038016 vsize: 126038016 resident: 39759872 share: 21098496 rss: 39759872 rss_rlim: 4294967295 CPU usage: start_time: 1199096607 rtime: 156 utime: 150 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/pedro/garnome/bin/rhythmbox' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1231845696 (LWP 6126)] [New Thread -1255257200 (LWP 6131)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 183618
Thread 1 (Thread -1231845696 (LWP 6126))
----------- .xsession-errors (289260 sec old) --------------------- ** (gconftool-2:6262): WARNING **: FIXME: Need to shutdown linc connections ... ** (gconftool-2:6263): WARNING **: FIXME: Need to shutdown linc connections ... (nautilus:6255): Liboobs-WARNING **: Failed to connect to socket /home/pedro/garnome/var/run/dbus/system_bus_socket: Conexão recusada seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:6255): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.NoServer : Failed to connect to socket /home/pedro/garnome/var/run/dbus/system_bus_socket: Conexão recusada ** (nautilus:6255): WARNING **: Could not initialize hal context Shutting down gnome-mount extension ** (gnome-panel:6235): WARNING **: Failed to establish a connection with GDM: Arquivo ou diretório inexistente --------------------------------------------------
*** This bug has been marked as a duplicate of 324487 ***