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 544017 - 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-07-21 15:52 UTC by gvizquel
Modified: 2008-07-21 17:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description gvizquel 2008-07-21 15:52:44 UTC
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (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: 73719808 vsize: 73719808 resident: 32247808 share: 15892480 rss: 32247808 rss_rlim: 4294967295
CPU usage: start_time: 1216655541 rtime: 283 utime: 273 stime: 10 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 0xb6b56720 (LWP 9633)]
[New Thread 0xb6305b90 (LWP 9655)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b56720 (LWP 9633))

  • #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 (12 sec old) ---------------------
  warnings.warn("apt API not stable yet", FutureWarning)
Advertencia del gestor de ventanas: last_user_time (3075888176) is greater than comparison timestamp (1179566317).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x2c00003 (Software U) appears to be one of the offending windows with a timestamp of 3075888176.  Working around...
Advertencia del gestor de ventanas: last_user_time (3075888176) is greater than comparison timestamp (1179570485).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x2c00a35 () appears to be one of the offending windows with a timestamp of 3075888176.  Working around...
Advertencia del gestor de ventanas: last_user_time (3075617840) is greater than comparison timestamp (1179577043).  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 3075617840.  Working around...
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:9605): 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.
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:9633): 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.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-07-21 17:07:08 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 ***