Bug 140348 – nautilus 2.6 segfaults on start

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 140348 - nautilus 2.6 segfaults on start


Summary:	nautilus 2.6 segfaults on start


Status:	RESOLVED DUPLICATE of bug 138986

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.6.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-04-18 07:17 UTC by Travis Tilley
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.5/2.6

Description Travis Tilley 2004-04-17 17:19:45 UTC

Distribution: Gentoo Base System version 1.4.8
Package: nautilus
Severity: normal
Version: GNOME2.6. 2.6.0
Gnome-Distributor: Gentoo Linux
Synopsis: nautilus 2.6 segfaults on start
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.6.0
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:

nautious segfaults on start

How often does this happen?

semi-often but not all the time



Debugging Information:

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 16384 (LWP 10972)]
[New Thread 32769 (LWP 10973)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 10972)]
[New Thread 32769 (LWP 10973)]
[New Thread 16386 (LWP 10974)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 10972)]
[New Thread 32769 (LWP 10973)]
0x0000002a9936d9c3 in waitpid () from /lib/libpthread.so.0

+ Trace 46127

Thread 1 (Thread 16384 (LWP 10972))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
from /usr/lib/libgnomeui-2.so.0
#2 __pthread_sighandler
from /lib/libpthread.so.0
#3 <signal handler called>
#4 ORBit_free_T
from /usr/lib/libORBit-2.so.0
#5 ORBit_freekids_via_TypeCode_T
from /usr/lib/libORBit-2.so.0
#6 ORBit_freekids_via_TypeCode_T
from /usr/lib/libORBit-2.so.0
#7 ORBit_free_T
from /usr/lib/libORBit-2.so.0
#8 ORBit_freekids_via_TypeCode_T
from /usr/lib/libORBit-2.so.0
#9 ORBit_free_T
from /usr/lib/libORBit-2.so.0
#10 ORBit_free
from /usr/lib/libORBit-2.so.0
#11 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#12 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#13 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#14 g_object_constructor
from /usr/lib/libgobject-2.0.so.0
#15 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#16 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_object_new
from /usr/lib/libgobject-2.0.so.0
#18 gnome_vfs_volume_monitor_unref
from /usr/lib/libgnomevfs-2.so.0
#19 nautilus_application_instance_init
#20 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#21 g_object_constructor
from /usr/lib/libgobject-2.0.so.0
#22 bonobo_object_constructor
from /usr/lib/libbonobo-2.so.0
#23 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#24 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_object_new
from /usr/lib/libgobject-2.0.so.0
#26 nautilus_application_new
#27 main
#0 waitpid
from /lib/libpthread.so.0





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-18 03:19 -------


Unknown version 2.6.0 in product nautilus. Setting version to "1.0.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was lv@gentoo.org.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Martin Wehner 2004-04-17 17:46:14 UTC

This looks like a duplicate of Bug 135417.
Can you confirm? Are you on AMD64?

Comment 2 Travis Tilley 2004-04-17 18:06:08 UTC

yes, i am on amd64. and unlike other reports, i'm not currently running a cvs 
snapshot of glibc. I'm running 2.3.2... which i thought should have eliminated 
this bug, since we're seeing a decent number of bugs related to 
http://bugs.gentoo.org/show_bug.cgi?id=46674 
 
"Without TLS, the thread descriptor is allocated from stack. If the thread 
stack is malloced and set by pthread_attr_setstack, it may be freed before the 
thread manager thread finishes processing the thread descriptor." 
http://sources.redhat.com/bugzilla/show_bug.cgi?id=110 
 
NPTL support enables TLS, which fixed things for me with the glibc 2.3.3 
snapshot. i am not currently using nptl.

Comment 3 Travis Tilley 2004-04-17 18:28:25 UTC

http://bugzilla.gnome.org/show_bug.cgi?id=138986 can also be marked a duplicate 
of Bug 135417, along with this one. sorry about that.

Comment 4 Martin Wehner 2004-04-18 13:37:33 UTC

Thanks for the feedback. I'm gonna mark this as duplicate of 138986; please add
any information that might be useful there.

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