GNOME Bugzilla – Bug 460051
crash in Rhythmbox Music Player:
Last modified: 2007-08-23 12:35:13 UTC
Version: 0.10.1 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OSX Memory status: size: 50786304 vsize: 50786304 resident: 28028928 share: 16089088 rss: 28028928 rss_rlim: 4294967295 CPU usage: start_time: 1185316852 rtime: 84 utime: 76 stime: 8 cutime:3 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 -1229056320 (LWP 11310)] (no debugging symbols found) 0xb7f377f2 in ?? () from /lib/ld-linux.so.2
+ Trace 150328
Thread 1 (Thread -1229056320 (LWP 11310))
----------- .xsession-errors --------------------- [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left [msmpeg4 @ 0xb68a6b48]ext header missing, 16 left AFD changed from -2 to -1 ** (update-notifier:3111): WARNING **: no cdrom: disk Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
*** Bug 460053 has been marked as a duplicate of this bug. ***
*** Bug 460392 has been marked as a duplicate of this bug. ***
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 358855 ***