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 145983 - nautilus crashes on fresh install of fedora core 2 for amd64
nautilus crashes on fresh install of fedora core 2 for amd64
Status: RESOLVED DUPLICATE of bug 138986
Product: nautilus
Classification: Core
Component: general
2.6.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-24 02:58 UTC by Navdeep Dhaliwal
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Navdeep Dhaliwal 2004-07-08 22:15:06 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: nautilus
Severity: major
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: nautilus crashes on fresh install of fedora core 2 for amd64
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
After installing fedora core 2 and rebooting the pc, the first dialog
window I saw when I got into my X session was that nautilus has quit
unexpectedly. I cannot launch anything that relates to the nautilus
(network server, etc)

Steps to reproduce the crash:
1. Login to a gnome session
2. Click on file broswe file system/network servers, etc

Expected Results: nautilus to launch

How often does this happen? All the time

Additional Information: The system has a 160 gig seagate serial ata
drive, motherboard is a kv8-max3, system has 1 gig of ram. The serial
ata chipset is a via one. Only 'tuning' i've done is set the kernel to
boot with pci=noacpi option.



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib64/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread 182987112864 (LWP 4461)]
[New Thread 1084225888 (LWP 4462)]
[Thread debugging using libthread_db enabled]
[New Thread 182987112864 (LWP 4461)]
[New Thread 1084225888 (LWP 4462)]
[Thread debugging using libthread_db enabled]
[New Thread 182987112864 (LWP 4461)]
[New Thread 1084225888 (LWP 4462)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x0000002a96ef7e74 in waitpid () from
/lib64/tls/libpthread.so.0

Thread 1 (Thread 182987112864 (LWP 4461))

  • #0 waitpid
    from /lib64/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 free
    from /lib64/tls/libc.so.6
  • #4 g_free
    from /usr/lib64/libglib-2.0.so.0
  • #5 ORBit_free_T
    from /usr/lib64/libORBit-2.so.0
  • #6 CORBA_wstring_len
    from /usr/lib64/libORBit-2.so.0
  • #7 CORBA_wstring_len
    from /usr/lib64/libORBit-2.so.0
  • #8 ORBit_free_T
    from /usr/lib64/libORBit-2.so.0
  • #9 CORBA_wstring_len
    from /usr/lib64/libORBit-2.so.0
  • #10 ORBit_free_T
    from /usr/lib64/libORBit-2.so.0
  • #11 ORBit_free
    from /usr/lib64/libORBit-2.so.0
  • #12 CORBA_free
    from /usr/lib64/libORBit-2.so.0
  • #13 gnome_vfs_volume_monitor_client_get_type
    from /usr/lib64/libgnomevfs-2.so.0
  • #14 gnome_vfs_volume_monitor_client_get_type
    from /usr/lib64/libgnomevfs-2.so.0
  • #15 g_type_create_instance
    from /usr/lib64/libgobject-2.0.so.0
  • #16 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #17 g_object_newv
    from /usr/lib64/libgobject-2.0.so.0
  • #18 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #19 g_object_new
    from /usr/lib64/libgobject-2.0.so.0
  • #20 _gnome_vfs_get_volume_monitor_internal
    from /usr/lib64/libgnomevfs-2.so.0
  • #21 gnome_vfs_get_volume_monitor
    from /usr/lib64/libgnomevfs-2.so.0
  • #22 nautilus_application_get_spatial_window_list
  • #23 g_type_create_instance
    from /usr/lib64/libgobject-2.0.so.0
  • #24 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #25 bonobo_object_query_local_interface
    from /usr/lib64/libbonobo-2.so.0
  • #26 g_object_newv
    from /usr/lib64/libgobject-2.0.so.0
  • #27 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #28 g_object_new
    from /usr/lib64/libgobject-2.0.so.0
  • #29 nautilus_application_new
  • #30 main
  • #0 waitpid
    from /lib64/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 18:15 -------


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 me@navdeep.ca.
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 Navdeep Dhaliwal 2004-07-08 23:32:29 UTC
This issue seems to be related to having too many devices in my /etc/fstab, if 
i comment out my floppy drive and try restarting nautilus everything begins to 
work. I have 2 cdroms and a floppy drive. 
Comment 2 Martin Wehner 2004-07-09 00:50:47 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 138986 ***