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 145872 - Nautilus doesn't launch in ANY circumstance under FC2 x86_64
Nautilus doesn't launch in ANY circumstance under FC2 x86_64
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-19 19:01 UTC by egheury
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description egheury 2004-07-08 20:43:12 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: nautilus
Severity: normal
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Nautilus doesn't launch in ANY circumstance under FC2 x86_64
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:


HARD SEVERITY - NO NAUTILUS BROWSER AT ALL (sorry I'm not used to Bugzilla)


Nautilus doesn't launch in ANY circumstances I've tested under FC2
x86_64.

After signing up in the blue graphical login screen of Fedora Core 2
x86_64, the desktop appears and I get the following error message:

The Application "nautilus" has quit unexpectedly.
You can inform the developers of what happened to help them fix it.  Or
you can restart the application right now.

When I try to launch nautilus from a terminal, as a standard user (not
root) I get the same error message. 
When I try to launch nautilus from a terminal with ' su -c "nautilus" '
I get the same messagebox as above + the following string to the shell
(not as a messagebox) :

(nautilus:9022): GnomeUI-WARNING **: While connecting to session
manager:
Authentication Rejected, reason : None of the authentication protocols
specified are supported and host-based authentication failed.




Steps to reproduce the crash:

SEE ABOVE





Expected Results:

SEE ABOVE




How often does this happen?

Everytime I want Nautilus to launch !!!!!!!!!!!!!!!


Additional Information:

please...............help


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

  • #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 16:43 -------


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 egheury@ulb.ac.be.
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 Martin Wehner 2004-07-09 00:40:49 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 ***