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 551371 - crash in File Browser: Estaba intentando visual...
crash in File Browser: Estaba intentando visual...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-08 13:31 UTC by oticojimenez
Modified: 2008-09-09 12:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description oticojimenez 2008-09-08 13:31:23 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Estaba intentando visualizar una carpeta compartida de Windows... no se pudo conectar!


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

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 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: 83931136 vsize: 83931136 resident: 29343744 share: 16191488 rss: 29343744 rss_rlim: 4294967295
CPU usage: start_time: 1220880460 rtime: 652 utime: 602 stime: 50 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 0xb6bb9720 (LWP 4946)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 206495

Thread 1 (Thread 0xb6bb9720 (LWP 4946))

  • #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 ---------------------
** Message: Hit unexpected error "El directorio no está vacío" while doing a file operation.
** Message: Hit unexpected error "El directorio no está vacío" while doing a file operation.
** Message: Hit unexpected error "El directorio no está vacío" while doing a file operation.
** Message: Hit unexpected error "El directorio no está vacío" while doing a file operation.
** Message: Hit unexpected error "El directorio no está vacío" while doing a file operation.
** (nautilus:4946): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Bodega»), avise a la lista de correo de gnome-vfs.
warning: .dynamic section for "/usr/lib/libgnutls.so.26" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libstdc++.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-09-09 12:17:39 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 ***