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 88137 - Nautilus crashes on startup
Nautilus crashes on startup
Status: RESOLVED DUPLICATE of bug 74189
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-07-14 12:37 UTC by rushuru
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rushuru 2002-07-14 12:36:35 UTC
Package: nautilus
Severity: major
Version: 2.0.0
Synopsis: Nautilus crashes on startup
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.1)

Description:
Description of Problem:
Nautilus crashes on startup

Steps to reproduce the problem:
1. click on Applications / Home folder
2.  or type nautilus in a xterm
3. 

Actual Results:
It doesn't start.
Same thing at gnome start (it leaves me with the greyish xfree
background and no icons)

Morever, I get like 5 or 10 bug buddy prompts in a row telling me
Nautilus had crashed and asking me whether I want to submit a bug report
(wasn't 1 enough?)

Heres the message I get hen typing nautilus in gnome-terminal:

** (nautilus:29081): WARNING **: Make registration id from
'OAFIID:Nautilus_Factory' ':0.0'
** Message: About to register ':0.0,OAFIID:Nautilus_Factory': 0x810a628

** (nautilus:29081): WARNING **: registration of
':0.0,OAFIID:Nautilus_Factory' returns 2
** Message: Successfully registered `:0.0,OAFIID:Nautilus_Factory'

However, nothing happens

Expected Results:

Nautilus starts

How often does this happen?

Everytime

Additional Information:
I'm using gentoo and nautilus used to work as expected (actually better
than I expected it has improved a lot, you did a great work). However I
'emerged -u world' yesterday and the breakage seems to have occured
since then: among the updates were a new version of the glibc (2.2.5-r5)
and gtk+ (2.0.5-r1)

I recompiled nautilus (2.0.0-r3) to make sure, but it still doesn't
start. Other gnome2 apps (panel, pan 0.12 etc.) work fine.



Debugging Information:

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

[New Thread 1024 (LWP 28776)]
[New Thread 2049 (LWP 28778)]
[New Thread 1026 (LWP 28779)]
[New Thread 2051 (LWP 28780)]
[New Thread 3076 (LWP 28781)]
[New Thread 4101 (LWP 28782)]
[New Thread 5126 (LWP 28783)]
0x1609a339 in wait4 () from /lib/libc.so.6

Thread 1 (Thread 1024 (LWP 28776))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 620
  • #4 pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_logv




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-07-14 08:36 -------

The original reporter (rushuru@hotmail.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 John Fleck 2002-07-14 17:41:45 UTC
Adding spider to cc list, in case he sees any other of these or
recognizes what the issue might be.
Comment 2 Luis Villa 2002-07-16 03:54:03 UTC
This is bug 74189; it is fixed in CVS and will be in the 2.0.1
tarball. Thanks, though.

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