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 114569 - Startup error
Startup error
Status: RESOLVED DUPLICATE of bug 106758
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-05-25 10:10 UTC by mck
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Crash when running 'nautilus -c' (3.21 KB, text/plain)
2003-06-11 11:17 UTC, mck
Details
40 backtraces caused from command 'nautilus' (37.70 KB, application/octet-stream)
2003-06-11 16:31 UTC, mck
Details

Description mck 2003-06-06 14:37:19 UTC
Package: nautilus
Severity: critical
Version: 2.2.1
Synopsis: Startup error
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
nautilus crashes during startup

Steps to reproduce the problem:
1.  start nautlius (either by logging into gnome session, or by typing
'nautilus' at the command line.


Actual Results:
error dialog

Expected Results:
nautlius window, (or nautilus drawn desktop incase of starting gnome
session).

How often does this happen?
everytime.




Debugging Information:

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

(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)...[New
Thread 1088000320 (LWP 1767)]
[New Thread 1116949808 (LWP 1771)]
[New Thread 1105935664 (LWP 1770)]
[New Thread 1097542960 (LWP 1769)]
0xffffe002 in ??
    ()

Thread 1 (Thread 1088000320 (LWP 1767))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 FAMPending
    at fam.c++ line 274
  • #4 fam_do_iter_unlocked
    at file-method.c line 2066
  • #5 fam_callback
    at file-method.c line 2148
  • #6 g_vsnprintf
    from /usr/lib/libglib-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-06 10:37 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-06-10 05:38:42 UTC
This looks like a duplicate of bug 106758, which was supposed to have
been fixed in February.  If you can still get this problem with a
newer version of nautilus, feel free to add a comment to that bug so
that it can be looked at again.

*** This bug has been marked as a duplicate of 106758 ***
Comment 2 mck 2003-06-11 09:43:13 UTC
I'm using gnome-vfs2-2.2.2-4.1 which is definitely newer than february.
And I'm using nautilus 2.2.1-5
Comment 3 mck 2003-06-11 09:58:36 UTC
I upgraded to nautilus-2.2.3 
And I still get the problem. (Note is works for all users on my pc
except for one).
Comment 4 mck 2003-06-11 11:17:32 UTC
Created attachment 17439 [details]
Crash when running 'nautilus -c'
Comment 5 mck 2003-06-11 11:18:22 UTC
Output from above process (nautilus -c); 
 
[mick@butterfly earth]$ nautilus -c 
running nautilus_self_check_search_uri 
running nautilus_self_check_file_utilities 
running nautilus_self_check_file_operations 
running nautilus_self_check_directory 
wrote 3757 bytes, (total: 3757  left: 0) 
 
Comment 6 mck 2003-06-11 16:31:14 UTC
Created attachment 17458 [details]
40 backtraces caused from command 'nautilus'
Comment 7 mck 2003-06-11 16:36:54 UTC
Every time I start I get 40+ error dialogs popping up. 
This is incredibly annoying, especially since it is not always me that starts 
nautilus, eg when gnome starts nautilus is started too. 
I really would like nautilus to work again for this particular user, but at the least 
only have to deal with one error dialog for essentially one process.