GNOME Bugzilla – Bug 434299
crash in Rhythmbox Music Player: trying to play music in ...
Last modified: 2007-04-30 14:13:50 UTC
What were you doing when the application crashed? trying to play music in magnatune in a Fedora 7 Test 4 GNOME i386 live cd Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 251052032 vsize: 251052032 resident: 134512640 share: 18468864 rss: 134512640 rss_rlim: 4294967295 CPU usage: start_time: 1177877051 rtime: 3207 utime: 2625 stime: 582 cutime:179 cstime: 67 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 -1208227584 (LWP 2893)] [New Thread -1311716464 (LWP 2944)] [New Thread -1233740912 (LWP 2935)] [New Thread -1259676784 (LWP 2928)] [New Thread -1246762096 (LWP 2911)] (no debugging symbols found) 0x0029d402 in __kernel_vsyscall ()
+ Trace 131219
Thread 3 (Thread -1233740912 (LWP 2935))
----------- .xsession-errors (21 sec old) --------------------- ** 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 (rhythmbox:2840): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:2840): libgnomevfs-WARNING **: trying to read a non-existing handle sys:1: GtkWarning: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed Loading simple Config module ... Creating backend ... Loading socket FrontEnd module ... Starting SCIM as daemon ... Xlib: unexpected async reply (sequence 0x19577)! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 421671 ***