GNOME Bugzilla – Bug 528771
crash in Evolution Mail: I was in the Evolution p...
Last modified: 2008-05-13 11:45:12 UTC
What were you doing when the application crashed? I was in the Evolution preferences, and I unselected an account name. Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: glass-icons Memory status: size: 630730752 vsize: 630730752 resident: 58806272 share: 25042944 rss: 58806272 rss_rlim: 18446744073709551615 CPU usage: start_time: 1208530974 rtime: 1726 utime: 1626 stime: 100 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 0x2b5d8a3f5ce0 (LWP 10302)] [New Thread 0x4604c950 (LWP 10333)] [New Thread 0x4600b950 (LWP 10331)] [New Thread 0x44808950 (LWP 10329)] [New Thread 0x4580a950 (LWP 10326)] [New Thread 0x45009950 (LWP 10325)] [New Thread 0x44007950 (LWP 10319)] [New Thread 0x43806950 (LWP 10318)] [New Thread 0x43005950 (LWP 10317)] [New Thread 0x42804950 (LWP 10316)] [New Thread 0x42003950 (LWP 10312)] [New Thread 0x41001950 (LWP 10308)] [New Thread 0x40800950 (LWP 10306)] (no debugging symbols found) 0x00002b5d7f9feedf in waitpid () from /lib/libpthread.so.0
+ Trace 195556
Thread 1 (Thread 0x2b5d8a3f5ce0 (LWP 10302))
----------- .xsession-errors (11301 sec old) --------------------- ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA lib ../../../src/pcm/pcm_dmix.c:996:(snd_pcm_dmix_open) ...Too much output, ignoring rest... --------------------------------------------------
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 324168 ***