GNOME Bugzilla – Bug 506525
crash in File Browser: abriendo propiedades de ...
Last modified: 2007-12-31 10:12:42 UTC
Version: 2.18.3 What were you doing when the application crashed? abriendo propiedades de pendrive Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77684736 vsize: 77684736 resident: 26177536 share: 16326656 rss: 26177536 rss_rlim: 4294967295 CPU usage: start_time: 1199071597 rtime: 146 utime: 137 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6d7a6b0 (LWP 28704)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 183600
Thread 1 (Thread 0xb6d7a6b0 (LWP 28704))
----------- .xsession-errors (13909 sec old) --------------------- ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave ...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 355018 ***