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 526692 - crash in Open Folder: opening a samba share
crash in Open Folder: opening a samba share
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-07 11:39 UTC by sp4mdis
Modified: 2008-04-08 08:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description sp4mdis 2008-04-07 11:39:32 UTC 
Version: 2.20.0

What were you doing when the application crashed?
opening a samba share


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 402350080 vsize: 402350080 resident: 37044224 share: 18038784 rss: 37044224 rss_rlim: 18446744073709551615
CPU usage: start_time: 1207559682 rtime: 175 utime: 157 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2ad64caf9b80 (LWP 3573)]
0x00002ad64660734f in waitpid () from /lib/libpthread.so.0

+ Trace 194479

Thread 1 (Thread 0x2ad64caf9b80 (LWP 3573))

  • #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 istr_hash
    at nautilus-directory-async.c line 170
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 848
  • #8 directory_load_callback
    at nautilus-directory-async.c line 1035
  • #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 main
    at nautilus-main.c line 556
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (8 sec old) ---------------------
LoadPlugin: failed to initialize shared library /usr/lib/jvm/jre1.6.0_03/plugin/i386/ns7/libjavaplugin_oji.so [/usr/lib/jvm/jre1.6.0_03/plugin/i386/ns7/libjavaplugin_oji.so: wrong ELF class: ELFCLASS3
LoadPlugin: failed to initialize shared library /usr/lib/jvm/jre1.6.0_03/plugin/i386/ns7/libjavaplugin_oji.so [/usr/lib/jvm/jre1.6.0_03/plugin/i386/ns7/libjavaplugin_oji.so: wrong ELF class: ELFCLASS3
LoadPlugin: failed to initialize shared library /usr/lib/jvm/jre1.6.0_03/plugin/i386/ns7/libjavaplugin_oji.so [/usr/lib/jvm/jre1.6.0_03/plugin/i386/ns7/libjavaplugin_oji.so: wrong ELF class: ELFCLASS3
(gnome-terminal:3597): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:3597): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
smbopen smb://st/charlie with gnome-open
** (nautilus:3573): WARNING **: No description found for mime type "x-directory/smb-share" (file is "charlie"), please tell the gnome-vfs mailing list.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-08 08:25:55 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 ***