GNOME Bugzilla – Bug 506332
crash in Home Folder: Alterando o icone do dis...
Last modified: 2007-12-30 01:21:28 UTC
What were you doing when the application crashed? Alterando o icone do dispositivo. Tipo de dispositivo e seu ponto de montagem /dev/sdb1 vfat 19G 256K 19G 1% /media/SDB usb 5-4: new high speed USB device using ehci_hcd and address 4 usb 5-4: configuration #1 chosen from 1 choice scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 3:0:0:0: Direct-Access IBM-IC25 N020ATCS04-0 0000 PQ: 0 ANSI: 0 sd 3:0:0:0: [sdb] 39070080 512-byte hardware sectors (20004 MB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 27 00 00 00 sd 3:0:0:0: [sdb] Assuming drive cache: write through sd 3:0:0:0: [sdb] 39070080 512-byte hardware sectors (20004 MB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 27 00 00 00 sd 3:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 3:0:0:0: [sdb] Attached SCSI dis 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: TGT4-Chrome Icon Theme: micro Memory status: size: 78729216 vsize: 78729216 resident: 29507584 share: 16367616 rss: 29507584 rss_rlim: 4294967295 CPU usage: start_time: 1198965464 rtime: 933 utime: 893 stime: 40 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 0xb6e1f6b0 (LWP 9268)] [New Thread 0xb35a4b90 (LWP 9466)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 183491
Thread 1 (Thread 0xb6e1f6b0 (LWP 9268))
----------- .xsession-errors (11568 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 ***