GNOME Bugzilla – Bug 542901
crash in Rhythmbox Music Player: I connected My IPOD shuf...
Last modified: 2008-07-21 06:24:20 UTC
Version: 0.11.5 What were you doing when the application crashed? I connected My IPOD shuffle whith GNUpod. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 68878336 vsize: 68878336 resident: 29462528 share: 17731584 rss: 29462528 rss_rlim: 4294967295 CPU usage: start_time: 1216033049 rtime: 72 utime: 64 stime: 8 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb662e9c0 (LWP 24915)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 202773
Thread 1 (Thread 0xb662e9c0 (LWP 24915))
----------- .xsession-errors (6 sec old) --------------------- ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card (pidgin:32264): GStreamer-CRITICAL **: Trying to dispose element fakesink, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card ** (update-notifier:32255): WARNING **: no cdrom: disk Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400022 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 ***