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 86069 - Random Crashes (Mostly in StartHere:)
Random Crashes (Mostly in StartHere:)
Status: RESOLVED DUPLICATE of bug 84693
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-20 18:39 UTC by Carsten Menke
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Attachments
Crash when editing Preferences and hitting "UP" (6.25 KB, text/plain)
2002-06-21 02:35 UTC, Carsten Menke
Details
Doing Start Here:, Applications/Development hit "UP" (6.26 KB, text/plain)
2002-06-21 02:42 UTC, Carsten Menke
Details

Description Carsten Menke 2002-06-20 18:39:48 UTC
Package: nautilus
Severity: critical
Version: 2.0.0
Synopsis: Random Crashes (Mostly in StartHere:)
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.1)

Description:
Description of Problem:
Nautilus crashes randomly on different things, so far I have not been
able to get a definite reproduction
but in this state it could not go into Gnome2

Steps to reproduce the problem:
1. Open Start Here 
2. Try to configure some Settings (a good start is to use the Sawfish
settings)
3.  Wait that Nautilus crashes

Actual Results:
Nautilus crashes fairly often 

Expected Results:
Rock Solid Nautilus not crashing all over the time

How often does this happen?
every few minutes when working in Nautilus

Additional Information:
Pulled the Gnome2 Tree using cvsgnome 0.20
and made a world stable to get the latest tarballs

Also everybody warns about it, I see this behavior when running Gnome2
as root.
I have not added a user yet. Also, is it possible that this has something to
do with 
the fact that I have not set up my LOCALS ?



Debugging Information:

Backtrace was generated from 'nautilus'

(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 21666)]
[New Thread 2049 (LWP 21671)]
[New Thread 1026 (LWP 21672)]
[New Thread 2051 (LWP 21673)]
[New Thread 3076 (LWP 10250)]
[New Thread 4101 (LWP 10251)]
[New Thread 5126 (LWP 10252)]
0x40b086f9 in __wait4 () at __wait4:-1
	in __wait4

Thread 1 (Thread 1024 (LWP 21666))

  • #0 __wait4
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 gnome_scores_new
    from /opt/gnome2/lib/libgnomeui-2.so.0
  • #4 pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 gnome_vfs_monitor_do_cancel
    from /opt/gnome2/lib/libgnomevfs-2.so.0
  • #7 gnome_vfs_monitor_cancel
    from /opt/gnome2/lib/libgnomevfs-2.so.0
  • #8 do_monitor_cancel
    from /opt/gnome2/lib/gnome-vfs-2.0/modules/libvfolder-desktop.so
  • #9 gnome_vfs_monitor_do_cancel
    from /opt/gnome2/lib/libgnomevfs-2.so.0
  • #10 gnome_vfs_monitor_cancel
    from /opt/gnome2/lib/libgnomevfs-2.so.0
  • #11 nautilus_monitor_cancel
    from /opt/gnome2/lib/libnautilus-private.so.2
  • #12 nautilus_directory_monitor_remove_internal
    from /opt/gnome2/lib/libnautilus-private.so.2
  • #13 vfs_file_monitor_remove
    from /opt/gnome2/lib/libnautilus-private.so.2
  • #14 nautilus_file_monitor_remove
    from /opt/gnome2/lib/libnautilus-private.so.2
  • #15 monitor_file_for_open_with
  • #16 reset_bonobo_open_with_menu
  • #17 real_update_menus
  • #18 fm_icon_view_update_menus
  • #19 fm_directory_view_update_menus
  • #20 update_menus_timeout_callback
  • #21 g_timeout_dispatch
    from /opt/gnome2/lib/libglib-2.0.so.0
  • #22 g_main_dispatch
    from /opt/gnome2/lib/libglib-2.0.so.0
  • #23 g_main_context_iterate
    from /opt/gnome2/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /opt/gnome2/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /opt/gnome2/lib/libgtk-x11-2.0.so.0
  • #26 main
  • #27 __libc_start_main
    from /lib/libc.so.6
0x40b086f9	-1	in __wait4

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-20 14:39 -------

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

Comment 1 Luis Villa 2002-06-20 22:09:01 UTC
Damon: is this bug 84693?
Comment 2 Carsten Menke 2002-06-21 02:35:37 UTC
Created attachment 9368 [details]
Crash when editing Preferences and hitting "UP"
Comment 3 Carsten Menke 2002-06-21 02:42:33 UTC
Created attachment 9369 [details]
Doing Start Here:, Applications/Development hit "UP"
Comment 4 Carsten Menke 2002-06-21 02:45:01 UTC
According to the last Backtrace it's reproduceable:

Do this:

Open Nautilus

Choose "Start Here:"

Go to Applications
Go to Development
Open Glade and close it
Hit the "Go Up" Button

NOTE: If I do not open Glade, then Nautilus doesn't crash.
Comment 5 John Fleck 2002-06-21 03:22:33 UTC
The stack traces look identical to #84693 to me. I was all ready to
dup  it until I saw Louie's question to Damon. Is there some reason to
think it isn't?
Comment 6 Damon Chaplin 2002-06-21 18:23:24 UTC
Yes, it looks very much like a dup.

Carsten, I committed a fix to gnome-vfs on 17th Jun, so if you get
the same problem with newer code please reopen bug 84683.
Thanks.

*** This bug has been marked as a duplicate of 84693 ***
Comment 7 Carsten Menke 2002-06-24 18:39:49 UTC
Damon:

I rebuild gnome-vfs and replaced it with gnome-vfs-2.0.1, yes this 
fixes the issue. Thanx