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 537749 - crash in Open Folder: Tried to access a samba ...
crash in Open Folder: Tried to access a samba ...
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-06-11 09:07 UTC by Tero Laxström
Modified: 2008-06-11 11:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Tero Laxström 2008-06-11 09:07:48 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Tried to access a samba share with nautilus. Directory was smb://1.2.3.4/data/temp/


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

System: Linux 2.6.25-2-686 #1 SMP Tue May 27 15:38:35 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: DebianRed
Icon Theme: Mist

Memory status: size: 62533632 vsize: 62533632 resident: 28913664 share: 15667200 rss: 28913664 rss_rlim: 4294967295
CPU usage: start_time: 1213174751 rtime: 800 utime: 742 stime: 58 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 0xb6bd4720 (LWP 13216)]
0xb7fb3424 in __kernel_vsyscall ()

+ Trace 200113

Thread 1 (Thread 0xb6bd4720 (LWP 13216))

  • #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 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.12.10/gtk/gtkmain.c line 1163
  • #17 main
    at nautilus-main.c line 556
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Initializing gnome-mount extension
** (nautilus:13121): WARNING **: No description found for mime type "x-directory/smb-share" (file is "data"), please tell the gnome-vfs mailing list.
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Initializing gnome-mount extension
** (nautilus:13182): WARNING **: No description found for mime type "x-directory/smb-share" (file is "backup"), please tell the gnome-vfs mailing list.
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Initializing gnome-mount extension
** (nautilus:13216): WARNING **: No description found for mime type "x-directory/smb-share" (file is "data"), please tell the gnome-vfs mailing list.
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-11 11:13:31 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 ***