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 161999 - nautilus crashes when run
nautilus crashes when run
Status: RESOLVED DUPLICATE of bug 160818
Product: nautilus
Classification: Core
Component: general
2.8.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-22 16:27 UTC by Ed Davison
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Ed Davison 2004-12-22 16:27:26 UTC
Distribution: Gentoo Base System version 1.4.16
Package: nautilus
Severity: normal
Version: GNOME2.8.0 2.8.0
Gnome-Distributor: Gentoo Linux
Synopsis: nautilus crashes when run
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.8.0
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
WHen I start nautilus I get a gnome_segv and a dialog box informing me
that it has ended suddenly. This is immediately following an upgrade
from 2.6.3 to 2.8.0.

Steps to reproduce the crash:
1. start nautilus
2. crashes

Expected Results:
normal functionality

How often does this happen?
every time

Additional Information:
I use gnome linux and emerged nautilus yesterday from 2.6.3 to 2.8.0 and
today when I get in to work, nautilus crashes every time I try to use
it.



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 23139)]
[New Thread 32769 (LWP 23141)]
[New Thread 16386 (LWP 23142)]
0x40de65cb in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 23139))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 __JCR_LIST__
    from /usr/lib/libgnomeui-2.so.0
  • #2 ??
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 741
  • #4 __pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 _gnome_vfs_drive_from_corba
    at gnome-vfs-drive.c line 598
  • #7 read_drives_from_daemon
    at gnome-vfs-volume-monitor-client.c line 132
  • #8 gnome_vfs_volume_monitor_client_init
    at gnome-vfs-volume-monitor-client.c line 189
  • #9 g_type_create_instance
    at gtype.c line 1595
  • #10 g_object_constructor
    at gobject.c line 1044
  • #11 g_object_newv
    at gobject.c line 941
  • #12 g_object_new_valist
    at gobject.c line 984
  • #13 g_object_new
    at gobject.c line 822
  • #14 _gnome_vfs_get_volume_monitor_internal
    at gnome-vfs-volume-monitor.c line 249
  • #15 gnome_vfs_get_volume_monitor
    at gnome-vfs-volume-monitor.c line 276
  • #16 nautilus_application_instance_init
    at nautilus-application.c line 183
  • #17 g_type_create_instance
    at gtype.c line 1595
  • #18 g_object_constructor
    at gobject.c line 1044
  • #19 bonobo_object_constructor
    at bonobo-object.c line 819
  • #20 g_object_newv
    at gobject.c line 941
  • #21 g_object_new_valist
    at gobject.c line 984
  • #22 g_object_new
    at gobject.c line 822
  • #23 nautilus_application_new
    at nautilus-application.c line 115
  • #24 main
    at nautilus-main.c line 323
  • #0 waitpid
    from /lib/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-22 11:27 -------


Unknown version 2.8.0 in product nautilus.  Setting version to "2.8.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 bfdi533@cbacc-security3.mccombs.utexas.edu.
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 Elijah Newren 2004-12-22 17:01:32 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 160818 ***