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 541611 - crash in File Browser: Intentar abrir una carpe...
crash in File Browser: Intentar abrir una carpe...
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-07-04 22:20 UTC by alan.alvespi
Modified: 2008-07-04 23:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description alan.alvespi 2008-07-04 22:20:33 UTC
Version: 2.20.0

What were you doing when the application crashed?
Intentar abrir una carpeta en red


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

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 520548352 vsize: 520548352 resident: 35028992 share: 18874368 rss: 35028992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1215207915 rtime: 1871 utime: 1751 stime: 120 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b567e619240 (LWP 4520)]
(no debugging symbols found)
0x00002b5677b0fedf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b567e619240 (LWP 4520))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
QImage::smoothScale: Image is a null image
QImage::smoothScale: Image is a null image
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x3200003 especificada para 0x3200001 (Correduria).

(gnome-terminal:7317): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Advertencia del gestor de ventanas: last_user_time (1909936800) is greater than comparison timestamp (1279698).  This most likely represents a buggy client sending inaccurate timestamps in messages su
Advertencia del gestor de ventanas: 0x340001f (Terminal) appears to be one of the offending windows with a timestamp of 1909936800.  Working around...
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x3600003 especificada para 0x3600001 (Correduria).
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:4520): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Juego%20Cos»), avise a la lista de correo de gnome-vfs.
--------------------------------------------------
Comment 1 A. Walton 2008-07-04 23:38:05 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 522534 ***