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 135417 - nautilus segfaults on amd64 with nfs
nautilus segfaults on amd64 with nfs
Status: RESOLVED DUPLICATE of bug 138986
Product: ORBit2
Classification: Deprecated
Component: general
2.5.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 137120 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-02-25 18:26 UTC by Max Nickel
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Max Nickel 2004-02-25 18:26:30 UTC 
When nfs mounts are autoloaded in /etc/fstab, nautilus segfaults right at
the  start on x86_64 platform. It doesn't matter if it is started as
desktop drawer or filemanager, it segfaults in both occassions.
Without nfs mounts nautilus is running fine
Comment 1 Max Nickel 2004-02-25 18:34:14 UTC 
forgot to say, i am currently using nautilus 2.5.7
Comment 2 Max Nickel 2004-02-26 01:07:46 UTC 
ok, i have some more information.
It's not about having the nfs partitions mounted, but about having
them in /etc/fstab.
If they are in there nautilus segfaults in browser view and as
desktop, but not as spatial !
If i comment them out, everything works fine
Comment 3 Philipp Frauenfelder 2004-02-26 16:25:07 UTC 
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.

Just for the completeness (as you are using Gentoo), what options did
you compile your nautilus with?
Comment 4 Philipp Frauenfelder 2004-02-26 16:28:22 UTC 
As a side note: I am using Debian's current unstable packages of Gnome
with Nautilus 2.4.2. I am having NFS mounts mounted and in my fstab (I
am using autofs4 too) without any problems. I am using this on a ia32
box with Nautilus as Desktop manager and file browser.
Comment 5 Luis Villa 2004-03-04 20:24:48 UTC 
Max, ping? Gentoo compile options and/or stack trace, please? Thanks!
Comment 6 Max Nickel 2004-03-04 20:47:44 UTC 
pong :) ok, here is the stacktrace:

(gdb) bt

+ Trace 44821

  • #0 ORBit_free_T
    at allocators.c line 167
  • #1 ORBit_freekids_via_TypeCode_T
    at allocators.c line 88
  • #2 ORBit_freekids_via_TypeCode_T
    at allocators.c line 65
  • #3 ORBit_free_T
    at allocators.c line 197
  • #4 ORBit_freekids_via_TypeCode_T
    at allocators.c line 96
  • #5 ORBit_free_T
    at allocators.c line 197
  • #6 ORBit_free
    at allocators.c line 213
  • #7 CORBA_free
    at allocators.c line 138
  • #8 read_drives_from_daemon
    at gnome-vfs-volume-monitor-client.c line 132
  • #9 gnome_vfs_volume_monitor_client_init
    at gnome-vfs-volume-monitor-client.c line 176
  • #10 g_type_create_instance
    at gtype.c line 1595
  • #11 g_object_constructor
    at gobject.c line 1044
  • #12 g_object_newv
    at gobject.c line 941
  • #13 g_object_new_valist
    at gobject.c line 984
  • #14 g_object_new
    at gobject.c line 822
  • #15 _gnome_vfs_get_volume_monitor_internal
    at gnome-vfs-volume-monitor.c line 224
  • #16 gnome_vfs_get_volume_monitor
    at gnome-vfs-volume-monitor.c line 238
  • #17 nautilus_application_instance_init
    at nautilus-application.c line 182
  • #18 g_type_create_instance
    at gtype.c line 1595
  • #19 g_object_constructor
    at gobject.c line 1044
  • #20 bonobo_object_constructor
    at bonobo-object.c line 813
  • #21 g_object_newv
    at gobject.c line 941
  • #22 g_object_new_valist
    at gobject.c line 984
  • #23 g_object_new
    at gobject.c line 822
  • #24 nautilus_application_new
    at nautilus-application.c line 199
  • #25 main
    at nautilus-main.c line 319 

i compiled it with -02, thats all
Comment 7 Max Nickel 2004-03-14 18:56:43 UTC 
As i have the feeling that this is more an ORBit issue, i'm moving it
there

I'm using ORBit 2.10.0 right now

Also i have spoken to different ppl, and this is not just happening
with nfs shares in /etc/fstab.
The backtrace though is the same. especially the mem=0x300000002
Comment 8 Max Nickel 2004-03-14 23:17:18 UTC 
And i have seen i forgot to add the errormsg gdb gives me :o
sorry for that, here it is:

(gdb) run
Starting program: /usr/bin/nautilus
setpgrp failed in child: No such process
 
Program received signal SIGSEGV, Segmentation fault.
ORBit_free_T (mem=0x6) at allocators.c:167
167     allocators.c: No such file or directory.
        in allocators.c

stacktrace is still the same.
Comment 9 Matthew Gatto 2004-03-15 11:00:53 UTC 
*** Bug 137120 has been marked as a duplicate of this bug. ***
Comment 10 borh 2004-03-20 13:54:17 UTC 
Another Gentoo/2.6.4kernel/udev/AMD64 user. I'd just like to report
that this is still not fixed in Gnome 2.6rc1 (ORBit2-2.10.0 ,
nautilus-2.5.91). I don't have any remote mounts in fstab, everything
is compiled with"-02" (everything tested with a clean install of gnome
/ all config files deleted, in fact everything but nautilus works). I
get the same error as Max Nickel above. I'd be happy to provide any
additional debug information, if requested.
Comment 11 Martin Wehner 2004-04-18 13:33:50 UTC 
I'm going to mark this as dup of 138986.
Please add further comments there.


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