GNOME Bugzilla – Bug 84693
Nautilus crash while editing gnome prefs
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 2.0.0 Synopsis: Nautilus crash while editing gnome prefs Bugzilla-Product: nautilus Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.0) Description: Description of Problem: Nautilus crashed (segv) after i tried to start the sound prefs capplet. The capplet did start however. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' [New Thread 1024 (LWP 1395)] [New Thread 2049 (LWP 1403)] [New Thread 1026 (LWP 1404)] [New Thread 2051 (LWP 1405)] [New Thread 3076 (LWP 1410)] [New Thread 4101 (LWP 1411)] [New Thread 5126 (LWP 1412)] [New Thread 6151 (LWP 1413)] [New Thread 7176 (LWP 1414)] [New Thread 8201 (LWP 1415)] [New Thread 9226 (LWP 1416)] [New Thread 10251 (LWP 1417)] 0x40a5e319 in __wait4 () from /lib/libc.so.6
+ Trace 23563
Thread 1 (Thread 1024 (LWP 1395))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-09 19:35 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
I got this one to. CVS build today.
Would really love to see this fixed Monday for inclusion in 2.0.0 tarballs tomorrow night, alex, dave :)
*** Bug 84831 has been marked as a duplicate of this bug. ***
Happens to me too. I have the default Nautilus window up, then hit Control-L, go to preferences://. I can open up a capplet the first time without a crash, and I can close and re-open that same capplet, but as soon as I launch a second one, Nautilus crashes.
Alex, Dave? I'm about ready to be very, very begging-on-my-knees about this bug...
OK, so, I've watched Dave try to reproduce this, and he can't, and I can't, so removing the 2.0.0. If you guys can give more specific repro directions, or more details about your setups, please do.
I'm using RedHat 7.2 here, ximian gnome installed, all gnome2 development snapshots. Is that enough info?? I'll try to reproduce the bug and report later...
I can get a very similar trace just by doing this: o Goto preferences: in nautilus. o double-click on Sound capplet to open it. o Click on 'Close' to close it. o Click on 'x' to close the nautilus window. Happens every time for me. Crashes at gnome-vfs-monitor.c:120 just like the above trace.
*** Bug 85309 has been marked as a duplicate of this bug. ***
I can always reproduce this crash using the steps given by Damon Chaplin.
*** Bug 85385 has been marked as a duplicate of this bug. ***
Reproduced the bug in a clean enviroment (new user), same results (see bug 85385, marked as dup).
I'm seeing this too:- 1. Start Here 2. Desktop Preferences 3. Open any capplet 4. Close the capplet 5. Open another capplet crash happens every time. Latest tarballs of everything as at 20020615 (including GTK+-2.0.4)
I just saw this one. I: * opened preferences:/// * opened the file type capplet, played with it some * closed it (without making any changes to the file types * did a window manager close on the nautilus window * crash-o-rama
*** Bug 85443 has been marked as a duplicate of this bug. ***
*** Bug 85453 has been marked as a duplicate of this bug. ***
*** Bug 85467 has been marked as a duplicate of this bug. ***
*** Bug 85489 has been marked as a duplicate of this bug. ***
*** Bug 85512 has been marked as a duplicate of this bug. ***
Sigh. I still can't duplicate this. Damon, can I take a look at your machine?
*** Bug 85538 has been marked as a duplicate of this bug. ***
I just got it again when closing the sound applet after enabling "Sound server startup"
Created attachment 9283 [details] [review] Patch that fixes it for me
If it failed to create a file monitor (e.g. if you don't have FAM) it was returning a pointer to freed memory rather than NULL.
Way to go, you RULE! Patch works for me too. [Ahem. Adding keywords.] I don't know what the freeze policy is, but having this patch in 2.0.0 would make the control centre much more usable by killing this crasher. It's fairly simple too :)
Applied on HEAD and gnome-2-0 branch. Please reopen if you still see the problem.
*** Bug 85687 has been marked as a duplicate of this bug. ***
*** Bug 85761 has been marked as a duplicate of this bug. ***
*** Bug 85742 has been marked as a duplicate of this bug. ***
*** Bug 85701 has been marked as a duplicate of this bug. ***
*** Bug 85789 has been marked as a duplicate of this bug. ***
*** Bug 85914 has been marked as a duplicate of this bug. ***
*** Bug 85956 has been marked as a duplicate of this bug. ***
*** Bug 85896 has been marked as a duplicate of this bug. ***
*** Bug 86069 has been marked as a duplicate of this bug. ***
*** Bug 86230 has been marked as a duplicate of this bug. ***
*** Bug 86228 has been marked as a duplicate of this bug. ***
*** Bug 86271 has been marked as a duplicate of this bug. ***
*** Bug 86304 has been marked as a duplicate of this bug. ***
*** Bug 86297 has been marked as a duplicate of this bug. ***
Damon: I'm still seeing this crash on Solaris (21st June from CVS), with the exact steps that Greg Schafer has mentioned. The stack trace is also similar. Any clues?
*** Bug 86315 has been marked as a duplicate of this bug. ***
Anand: the bug was in gnome-vfs. Did you update that as well (from the gnome-2-0 branch)?
Damon: This is gnome-vfs from CVS head (24th June). The last changelog entry is dated 13-06-2002 by you. Should i be using that version?
Anand: you need the gnome-2-0 branch. The ChangeLog entry for my fix was: 2002-06-17 Damon Chaplin <damon@ximian.com> * libgnomevfs/gnome-vfs-monitor.c (gnome_vfs_monitor_do_add): if the monitor_add call fails, return NULL as the handle. It was returning a pointer to freed memory before. Fixes bug #84693. Approved by Ian McKellar. So it looks like your version is too old. You should probably avoid HEAD now, as that is aimed at GNOME 2.2 and is changing quite a bit.
*** Bug 86559 has been marked as a duplicate of this bug. ***
Damon: Works great now!! Thanks.
*** Bug 89551 has been marked as a duplicate of this bug. ***