GNOME Bugzilla – Bug 420063
crash in Gimmie:
Last modified: 2007-03-19 21:29:07 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-11-386 #2 Thu Mar 15 07:58:11 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Silicon Icon Theme: Tango Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (224791 sec old) --------------------- ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card 'Headset' ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 119991
items.append(DriveItem(drive))
icon=drive.get_icon())
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 417988 ***