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 546576 - crash in File Browser:
crash in File Browser:
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-08-06 12:35 UTC by gvizquel
Modified: 2008-08-06 15:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description gvizquel 2008-08-06 12:35:09 UTC
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 75894784 vsize: 75894784 resident: 26497024 share: 16003072 rss: 26497024 rss_rlim: 4294967295
CPU usage: start_time: 1218025163 rtime: 581 utime: 553 stime: 28 cutime:0 cstime: 0 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 0xb6b6e720 (LWP 3278)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b6e720 (LWP 3278))

  • #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 (238 sec old) ---------------------
Advertencia del gestor de ventanas: 0x2c00003 (Software U) appears to be one of the offending windows with a timestamp of 3076215856.  Working around...
Advertencia del gestor de ventanas: last_user_time (3076215856) is greater than comparison timestamp (2549451366).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x2c00aa5 () appears to be one of the offending windows with a timestamp of 3076215856.  Working around...
Advertencia del gestor de ventanas: last_user_time (3076387888) is greater than comparison timestamp (2549466858).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x2c00081 (Synaptic) appears to be one of the offending windows with a timestamp of 3076387888.  Working around...
Cutting log (size: 101040, max: 100000)Wine exited with a successful status

(gnome-terminal:3675): 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 (3076461616) is greater than comparison timestamp (2549767068).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x340001e (Terminal) appears to be one of the offending windows with a timestamp of 3076461616.  Working around...
** (nautilus:3278): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «UEAD»), avise a la lista de correo de gnome-vfs.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Gianluca Borello 2008-08-06 15:25:57 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 ***