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 541626 - crash in Open Folder: Connecting to a Windows ...
crash in Open Folder: Connecting to a Windows ...
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-05 04:10 UTC by der.gruene.v0gel
Modified: 2008-07-05 18:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description der.gruene.v0gel 2008-07-05 04:10:24 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Connecting to a Windows XP shared folder over smb://


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: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 94740480 vsize: 94740480 resident: 23601152 share: 15241216 rss: 23601152 rss_rlim: 4294967295
CPU usage: start_time: 1215230850 rtime: 360 utime: 338 stime: 22 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 0xb6bc9940 (LWP 3108)]
[New Thread 0xb4087b90 (LWP 3395)]
[New Thread 0xb6383b90 (LWP 3394)]
[New Thread 0xb5b82b90 (LWP 3392)]
[New Thread 0xb5381b90 (LWP 3381)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 202088

Thread 1 (Thread 0xb6bc9940 (LWP 3108))

  • #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 (32 sec old) ---------------------
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
--------------------------------------------------
Comment 1 A. Walton 2008-07-05 18:25:22 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 ***