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 541361 - crash in Open Folder: Connecting to a hidden s...
crash in Open Folder: Connecting to a hidden s...
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-03 09:04 UTC by Baatar
Modified: 2008-07-04 04:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Baatar 2008-07-03 09:04:40 UTC
Version: 2.20.0

What were you doing when the application crashed?
Connecting to a hidden share C$ on a Windows XP SP2 computer. Interesting thing is it does not crash if I connect to d$ share on the same computer.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 80637952 vsize: 80637952 resident: 27439104 share: 15618048 rss: 27439104 rss_rlim: 4294967295
CPU usage: start_time: 1215072983 rtime: 216 utime: 198 stime: 18 cutime:114 cstime: 3 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 0xb6b7a940 (LWP 2816)]
[New Thread 0xb5a83b90 (LWP 3349)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b7a940 (LWP 2816))

  • #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 (10 sec old) ---------------------
Initializing gnome-mount extension
seahorse nautilus module initialized
Window manager warning: last_focus_time (2801704) is greater than comparison timestamp (2801690).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACT
** (nautilus:2816): WARNING **: No description found for mime type "x-directory/smb-share" (file is "d%24"), please tell the gnome-vfs mailing list.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
--------------------------------------------------
Comment 1 A. Walton 2008-07-03 12:36:30 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 ***
Comment 2 Baatar 2008-07-04 03:36:34 UTC
Nautilus still crashes event though the bug is marked as resolved. My observation is that crash only happens if the connecting share is a Windows system volume (like C:).
Comment 3 A. Walton 2008-07-04 04:44:26 UTC
Please see the duplicate. The fix for this crash has been committed to the Nautilus 2.20 branch: http://svn.gnome.org/viewvc/nautilus?view=revision&revision=14097 . If your distribution has not updated its Nautilus 2.20 package, you should file a bug against your distribution. You should not be seeing this crash any longer. 

If you can still reproduce this crash after updating, please file another bug with full debug symbols for Nautilus and GnomeVFS. Thanks.