GNOME Bugzilla – Bug 437180
crash in Rhythmbox Music Player: I was trying to access p...
Last modified: 2007-06-15 10:54:11 UTC
What were you doing when the application crashed? I was trying to access properties of a song from the waiting list, and at the same time, the song ended. Distribution: Debian lenny/sid Gnome Release: 2.18.1 2007-04-25 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 154673152 vsize: 154673152 resident: 37904384 share: 20217856 rss: 37904384 rss_rlim: 4294967295 CPU usage: start_time: 1178705820 rtime: 6334 utime: 5775 stime: 559 cutime:4 cstime: 3 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 -1229334832 (LWP 6332)] [New Thread -1334514800 (LWP 8233)] [New Thread -1267373168 (LWP 8230)] [New Thread -1326122096 (LWP 8227)] [New Thread -1250194544 (LWP 7946)] [New Thread -1292551280 (LWP 7945)] [New Thread -1359692912 (LWP 6952)] [New Thread -1284158576 (LWP 7705)] [New Thread -1275765872 (LWP 6381)] [New Thread -1258980464 (LWP 6341)] (no debugging symbols found) 0xb7fad410 in ?? ()
+ Trace 133277
----------- .xsession-errors (52843 sec old) --------------------- (evolution-2.10:10828): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:10828): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:10828): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:10828): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:10828): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:10828): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.10:10828): camel-WARNING **: camel_exception_get_id called with NULL parameter. ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hi ! About the way to reproduce the bug, you have to clic on properties *at the same time* the song ends (and remove itself from the waiting list). Here the trace I got after installing *-dbg packages I still have trace with "no debuggind symbol" Distribution: Debian lenny/sid Gnome Release: 2.18.1 2007-04-25 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 102182912 vsize: 102182912 resident: 37441536 share: 19255296 rss: 37441536 rss_rlim: 4294967295 CPU usage: start_time: 1179118971 rtime: 640 utime: 568 stime: 72 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1229453088 (LWP 7321)] [New Thread -1296020592 (LWP 7828)] [New Thread -1250952304 (LWP 7595)] 0xb7f76410 in ?? ()
+ Trace 134042
----------- .xsession-errors --------------------- (rhythmbox:7321): Rhythmbox-CRITICAL **: rb_song_info_constructor: assertion `selected_entries != NULL' failed Failed to read a valid object file image from memory. --------------------------------------------------
I think the window in which this condition could occur was closed by some of the work on bug 399012.
Taking another look, this appears to be impossible now, so I'm closing this bug. *** This bug has been marked as a duplicate of 399012 ***