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 541066 - crash in Open Folder:
crash in Open Folder:
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-01 11:55 UTC by gpmulvey
Modified: 2008-07-01 18:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description gpmulvey 2008-07-01 11:55:29 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (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: Clearlooks
Icon Theme: gnome

Memory status: size: 440631296 vsize: 440631296 resident: 37646336 share: 16887808 rss: 37646336 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214912281 rtime: 381 utime: 337 stime: 44 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 0x2b876da5f220 (LWP 7024)]
(no debugging symbols found)
0x00002b8766a04edf in waitpid () from /lib/libpthread.so.0

+ Trace 201826

Thread 1 (Thread 0x2b876da5f220 (LWP 7024))

  • #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 (11 sec old) ---------------------
Window manager warning: last_user_time (1878603392) is greater than comparison timestamp (1145075).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_A
Window manager warning: 0x26003b9 (Quick Intr) appears to be one of the offending windows with a timestamp of 1878603392.  Working around...
(gnome-panel:3531): GLib-GIO-WARNING **: Missing callback called fullpath = /home/ger/.config/menus/gnome-settings.menu
(gnome-panel:3531): GLib-GIO-WARNING **: Missing callback called fullpath = /home/ger/.config/menus/gnome-applications.menu
Window manager warning: last_user_time (2042689152) is greater than comparison timestamp (1531748).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_A
Window manager warning: 0x2600003 (Network Se) appears to be one of the offending windows with a timestamp of 2042689152.  Working around...

(gnome-terminal:7218): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
** (nautilus:7024): WARNING **: No description found for mime type "x-directory/smb-share" (file is "MediaDrive"), please tell the gnome-vfs mailing list.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-07-01 18:02:17 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 ***