GNOME Bugzilla – Bug 538121
crash in Rhythmbox Music Player:
Last modified: 2008-06-15 12:12:33 UTC
Version: 0.11.5 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23.12-dream #1 SMP PREEMPT Fri Jan 18 02:13:57 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Go-SX Icon Theme: Go_Dream Memory status: size: 67530752 vsize: 67530752 resident: 31543296 share: 18026496 rss: 31543296 rss_rlim: 4294967295 CPU usage: start_time: 1213350165 rtime: 164 utime: 133 stime: 31 cutime:0 cstime: 2 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 0xb65eca80 (LWP 16050)] (no debugging symbols found) 0xb7c84f91 in waitpid () from /lib/libpthread.so.0
+ Trace 200308
Thread 1 (Thread 0xb65eca80 (LWP 16050))
----------- .xsession-errors (640 sec old) --------------------- Sample Encoding: signed (2's complement) Channels : 2 Sample Rate : 44100 Time: 00:00.00 [00:00.81] of 00:00.81 (0.00%) Samples out: 0 Clips: 0 Time: 00:00.37 [00:00.44] of 00:00.81 (45.6%) Samples out: 16.4k Clips: 0 Time: 00:00.56 [00:00.26] of 00:00.81 (68.4 Done. Input File : '/usr/share/amsn/skins/default/sounds/online.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 2 Sample Rate : 44100 Time: 00:00.00 [00:00.81] of 00:00.81 (0.00%) Samples out: 0 Clips: 0 Time: 00:00.37 [00:00.44] of 00:00.81 (45.6%) Samples out: 16.4k Clips: 0 Time: 00:00.56 [00:00.26] of 00:00.81 (68.4 Done. --------------------------------------------------
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 ***