Bug 318009 – Crashed on startup

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 318009 - Crashed on startup


Summary:	Crashed on startup


Status:	RESOLVED DUPLICATE of bug 170947

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

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-10-05 11:49 UTC by Jeroen Asselman
Modified:	2005-10-05 16:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Jeroen Asselman 2005-10-05 11:49:57 UTC

Distribution: Gentoo Base System version 1.12.0_pre8
Package: nautilus
Severity: normal
Version: GNOME2.10.2 2.10.1
Gnome-Distributor: Gentoo
Synopsis: Crashed on startup
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.1
BugBuddy-GnomeVersion: 2.0 (2.10.1)
Description:
Description of the crash:
When startiing nautilus from an xterm, it gave a few warnings:
invalid length 10794
Failed to process 71 bytes from server
invalid length 10794
invalid length 10794
invalid length 10794

And then the "The application nautilus has quit unexpectedly"  dialog
box popped up.


Debugging Information:

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1230149408 (LWP 13353)]
[New Thread -1234097232 (LWP 13376)]
[New Thread -1233830992 (LWP 13375)]
[New Thread -1233564752 (LWP 13374)]
[New Thread -1233298512 (LWP 13373)]
[New Thread -1233032272 (LWP 13372)]
[New Thread -1232766032 (LWP 13368)]
[New Thread -1232499792 (LWP 13367)]
[New Thread -1230734416 (LWP 13358)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 63378

Thread 1 (Thread -1230149408 (LWP 13353))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#2 libgnomeui_segv_handle
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 _xdg_glob_hash_insert_text
from /usr/lib/libgnomevfs-2.so.0
#5 _gnome_vfs_xdg_hash_append_glob
from /usr/lib/libgnomevfs-2.so.0
#6 _gnome_vfs_xdg_glob_read_from_file
from /usr/lib/libgnomevfs-2.so.0
#7 xdg_mime_init_from_directory
from /usr/lib/libgnomevfs-2.so.0
#8 xdg_run_command_on_dirs
from /usr/lib/libgnomevfs-2.so.0
#9 xdg_mime_init
from /usr/lib/libgnomevfs-2.so.0
#10 _gnome_vfs_xdg_mime_type_equal
from /usr/lib/libgnomevfs-2.so.0
#11 gnome_vfs_mime_type_is_equal
from /usr/lib/libgnomevfs-2.so.0
#12 gnome_vfs_mime_type_get_equivalence
from /usr/lib/libgnomevfs-2.so.0
#13 nautilus_file_is_mime_type
from /usr/lib/libnautilus-private.so.2
#14 nautilus_file_is_nautilus_link
from /usr/lib/libnautilus-private.so.2
#15 lacks_link_info
from /usr/lib/libnautilus-private.so.2
#16 start_or_stop_io
from /usr/lib/libnautilus-private.so.2
#17 nautilus_directory_async_state_changed
from /usr/lib/libnautilus-private.so.2
#18 get_info_callback
from /usr/lib/libnautilus-private.so.2
#19 dispatch_job_callback
from /usr/lib/libgnomevfs-2.so.0
#20 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#22 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#23 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#24 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#25 main
#0 __kernel_vsyscall





------- Bug moved to this database by unknown@gnome.bugs 2005-10-05 11:49 UTC -------


Unknown version 2.10.1 in product nautilus.  Setting version to "2.10.x".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was jeroen@asselman.com.

Comment 1 Christian Neumair 2005-10-05 16:43:01 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 170947 ***