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 119522 - nautilus crashes 100% of the time at startup
nautilus crashes 100% of the time at startup
Status: RESOLVED DUPLICATE of bug 96915
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-08-10 02:06 UTC by Jon Nelson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jon Nelson 2003-08-10 02:24:57 UTC 
Distribution: Unknown
Package: nautilus
Severity: normal
Version: GNOME2.3.6 2.3.8
Gnome-Distributor: GNOME.Org
Synopsis: nautilus crashes 100% of the time at startup
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.3.8
BugBuddy-GnomeVersion: 2.0 (2.3.3.1)
Description:
Description of the crash:

nautilus crashes 100% of the time at startup.
invocations that start nautilus from the commandline do not appear to
crash.




Debugging Information:

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

[New Thread 16384 (LWP 3421)]
[New Thread 32769 (LWP 3422)]
[New Thread 16386 (LWP 3423)]
[New Thread 32771 (LWP 3424)]
[New Thread 49156 (LWP 3425)]
[New Thread 65541 (LWP 3426)]
0x40ae923a in __libc_waitpid (pid=3427, stat_loc=0xbfffea7c, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 39482

Thread 1 (Thread 16384 (LWP 3421))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 738
  • #2 __pthread_sighandler
    at sighandler.c line 38
  • #3 <signal handler called>
  • #4 g_logv
    at gmessages.c line 512
  • #5 g_log
    at gmessages.c line 527
  • #6 _gnome_vfs_async_job_map_get_job
    at gnome-vfs-async-job-map.c line 56
  • #7 gnome_vfs_async_cancel
    at gnome-vfs-async-ops.c line 49
  • #8 remove_trash_volume
    at nautilus-trash-directory.c line 250
  • #9 eel_g_hash_table_safe_for_each
    at eel-glib-extensions.c line 694
  • #10 trash_finalize
    at nautilus-trash-directory.c line 371
  • #11 g_object_last_unref
    at gobject.c line 442
  • #12 nautilus_directory_unref
    at nautilus-directory.c line 162
  • #13 destroy
    at nautilus-trash-monitor.c line 163
  • #14 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #15 g_type_class_meta_marshal
    at gclosure.c line 514
  • #16 g_closure_invoke
    at gclosure.c line 437
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2938
  • #18 g_signal_emit_valist
    at gsignal.c line 2554
  • #19 g_signal_emit
    at gsignal.c line 2612
  • #20 gtk_object_dispose
    at gtkobject.c line 376
  • #21 g_object_last_unref
    at gobject.c line 429
  • #22 unref_trash_monitor
    at nautilus-trash-monitor.c line 170
  • #23 eel_debug_shut_down
    at eel-debug.c line 177
  • #24 main
    at nautilus-main.c line 288
  • #25 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 152 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-09 22:24 -------

Unknown version 2.3.8 in product nautilus. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 John Fleck 2003-08-10 02:32:43 UTC 
This is a bug that was thought to have been slain, but is showing up
again. Could you look at bug #96915 and see if there's any further
diagnostic information the developers need that you might be able to
provide? Thanks.

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