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 146541 - System will NOT open after updates!!!
System will NOT open after updates!!!
Status: RESOLVED DUPLICATE of bug 145864
Product: nautilus
Classification: Core
Component: File and Folder Operations
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-12 03:39 UTC by punchydrums
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description punchydrums 2004-07-09 06:33:16 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: nautilus
Severity: normal
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: System will NOT open after updates!!!
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:  Okay, my system CRASHED EACH time immediately
after login (Nautilus stopped running error), but was EXCITED to see
that a "patch" was available through Up2date ...... however, after a
successful installation, the system will no longer open after reboot of
the new smp-427 core (I think that's what it is called ... I updated
from the smp-358).   It also locks up when using the regular new core
(without the smp capabilities).   


Steps to reproduce the crash:
1. any boot or reboot when the new .427 core is selected!
2. 
3. 

Expected Results: 
System will NOT load (open) and just waits ...... giving a message that
it's "Searching for new hardware" ...... but NEVER comes out of the
search.   Therefore, the system NEVER loads ...... never!


How often does this happen? 
EVERY TIME!


Additional Information:
ACPI 1.0 Enabled
ACPI 2.0 Disabled
(I disabled the ACPI 2.0 after discovering that your Fedora-FC2-i386
wouldn't load with the "2.0" enabled, and left it disabled, assuming
Linux's x86_64 based products didn't like the "2.0" configuration).

SADLY, I CANNOT even use this software!

Simply CANNOT!

But would APPRECIATE ANY & ALL help that can be provided!







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 2931)]
[New Thread 1084225888 (LWP 2941)]
[Thread debugging using libthread_db enabled]
[New Thread 182987112864 (LWP 2931)]
[New Thread 1084225888 (LWP 2941)]
[Thread debugging using libthread_db enabled]
[New Thread 182987112864 (LWP 2931)]
[New Thread 1084225888 (LWP 2941)]
(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 2931))

  • #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-09 02:33 -------


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 punchydrums@yahoo.com.
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 Vincent Untz 2004-07-09 13:51:08 UTC

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