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 529447 - crash in Open Folder: Connecting to a samba sh...
crash in Open Folder: Connecting to a samba sh...
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-04-22 22:07 UTC by scott.ashcroft
Modified: 2008-04-23 00:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description scott.ashcroft 2008-04-22 22:07:16 UTC
Version: 2.20.0

What were you doing when the application crashed?
Connecting to a samba share on a remote server.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25 #17 SMP Sat Apr 19 14:10:07 BST 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: 66473984 vsize: 66473984 resident: 28368896 share: 15224832 rss: 28368896 rss_rlim: 4294967295
CPU usage: start_time: 1208901815 rtime: 312 utime: 292 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6cfb720 (LWP 6026)]
0xffffe424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6cfb720 (LWP 6026))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 istr_hash
    at nautilus-directory-async.c line 170
  • #7 g_hash_table_insert_internal
    at /build/buildd/glib2.0-2.16.3/glib/ghash.c line 118
  • #8 istr_set_insert
    at nautilus-directory-async.c line 189
  • #9 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 848
  • #10 directory_load_callback
    at nautilus-directory-async.c line 1035
  • #11 dispatch_job_callback
    at gnome-vfs-job.c line 237
  • #12 g_idle_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 4087
  • #13 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #14 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #15 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #16 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 main
    at nautilus-main.c line 556
  • #0 __kernel_vsyscall


----------- .xsession-errors (34 sec old) ---------------------
CALLBACK: full-authentication!!!
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
(gnome-terminal:5892): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
--------------------------------------------------
Comment 1 André Klapper 2008-04-23 00:11:12 UTC
same trace as bug 522534 comment 201.

*** This bug has been marked as a duplicate of 522534 ***