GNOME Bugzilla – Bug 537630
crash in Rhythmbox Music Player: ho collegato un ipod nan...
Last modified: 2008-06-14 19:16:45 UTC
Version: 0.11.5 What were you doing when the application crashed? ho collegato un ipod nano da 8 gb Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 73330688 vsize: 73330688 resident: 29794304 share: 17723392 rss: 29794304 rss_rlim: 4294967295 CPU usage: start_time: 1213116678 rtime: 88 utime: 80 stime: 8 cutime:0 cstime: 1 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 0xb671b960 (LWP 5818)] [New Thread 0xb51b2b90 (LWP 5824)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200047
Thread 1 (Thread 0xb671b960 (LWP 5818))
----------- .xsession-errors --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (update-notifier:4413): WARNING **: no cdrom: disk (rhythmbox:5818): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed --------------------------------------------------
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. *** This bug has been marked as a duplicate of 524985 ***