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 511620 - crash in File Browser: trying to check properit...
crash in File Browser: trying to check properit...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-23 20:05 UTC by iwua
Modified: 2008-01-24 23:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description iwua 2008-01-23 20:05:06 UTC
Version: 2.18.3

What were you doing when the application crashed?
trying to check properities of directory


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 80547840 vsize: 80547840 resident: 24064000 share: 13754368 rss: 24064000 rss_rlim: 4294967295
CPU usage: start_time: 1201085163 rtime: 1172 utime: 948 stime: 224 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 0xb6e0e6b0 (LWP 2717)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6e0e6b0 (LWP 2717))

  • #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 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (59 sec old) ---------------------
** Message: volume = 0
Ostrzeżenie menedżera okien: last_user_time (3076232240) is greater than comparison timestamp (2822644429).  This most likely represents a buggy client sending inaccurate timestamps in messages such
Ostrzeżenie menedżera okien: 0x2c00003 (Share Fold) appears to be one of the offending windows with a timestamp of 3076232240.  Working around...
Ostrzeżenie menedżera okien: last_user_time (3076125744) is greater than comparison timestamp (2822644618).  This most likely represents a buggy client sending inaccurate timestamps in messages such
Ostrzeżenie menedżera okien: 0x3000003 (Share Fold) appears to be one of the offending windows with a timestamp of 3076125744.  Working around...

(nautilus:17167): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Initializing nautilus-open-terminal extension
Initializing nautilus-image-converter extension
Initializing gnome-mount extension
Ostrzeżenie menedżera okien: last_user_time (3076645936) is greater than comparison timestamp (2822725815).  This most likely represents a buggy client sending inaccurate timestamps in messages such
Ostrzeżenie menedżera okien: 0x2c00003 (PAKIET BIU) appears to be one of the offending windows with a timestamp of 3076645936.  Working around...
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-24 23:12:40 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 355018 ***