GNOME Bugzilla – Bug 463586
crash in Rhythmbox Music Player: trying to play a simple ...
Last modified: 2007-08-07 13:25:40 UTC
What were you doing when the application crashed? trying to play a simple MP3 file! Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 110616576 vsize: 110616576 resident: 35995648 share: 24248320 rss: 35995648 rss_rlim: 4294967295 CPU usage: start_time: 1186296485 rtime: 194 utime: 178 stime: 16 cutime:2 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208137168 (LWP 4094)] [New Thread -1244804208 (LWP 4114)] [New Thread -1233425520 (LWP 4099)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 152902
Thread 1 (Thread -1208137168 (LWP 4094))
----------- .xsession-errors (59 sec old) --------------------- ** (gnome-control-center:4075): WARNING **: get_actions_list() - PROBLEM - Can't load gnome-cups-manager.desktop ** Message: Error: Could not open resource for writing. gstalsasink.c(625): gst_alsasink_open (): /autoaudiosink0-actual-sink-alsa: Playback open error on device 'default': No such device The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 44 error_code 11 request_code 140 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 413801 ***