After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 532952 - crash in Home Folder: Navegando nas pastas de ...
crash in Home Folder: Navegando nas pastas de ...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-13 13:04 UTC by iltonjunior
Modified: 2008-05-13 16:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description iltonjunior 2008-05-13 13:04:05 UTC 
What were you doing when the application crashed?
Navegando nas pastas de um servidor com fotos.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-486 #1 Fri Apr 18 23:53:06 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79626240 vsize: 79626240 resident: 24997888 share: 16441344 rss: 24997888 rss_rlim: 4294967295
CPU usage: start_time: 1210677095 rtime: 1433 utime: 1326 stime: 107 cutime:185 cstime: 21 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6baa720 (LWP 3080)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197623

Thread 1 (Thread 0xb6baa720 (LWP 3080))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (3946 sec old) ---------------------
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-13 16:07:16 UTC 
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 522534 ***