GNOME Bugzilla – Bug 45698
Clicking option to enable, disable, enable desktop crashes Nautilus
Last modified: 2004-12-22 21:47:04 UTC
I've reliably been able to crash Nautilus by: 1) Turning on the "have Nautilus manage the desktop" option in the user-level preference menu 2) Turn the option off 3) Turn the option back on again I've done these operations in fairly quick succession...but it crashes almost every time. ------- Additional Comments From darin@bentspoon.com 2001-01-17 10:59:10 ---- If true, this sounds like it might even be a PR3 blocker. ------- Additional Comments From engber@eazel.com 2001-01-17 11:15:10 ---- I'm having trouble reproducing this on my machine. Brian was able to show it to me on his machine - but it wasn't that easy to do. ------- Additional Comments From don@eazel.com 2001-01-17 13:59:59 ---- On the table for PR3 while Mike investigates this ... ------- Additional Comments From don@eazel.com 2001-01-18 10:49:51 ---- Looks like the X server fix made MOST of this go away. Mike will continue to investigate this for 1.0. ------- Additional Comments From engber@eazel.com 2001-01-25 10:30:45 ---- I don't think this is a desktop specific problem, I think it could happen to any nautilus window. It's just easy to repro by turning on/off the desktop. ------- Additional Comments From sullivan@eazel.com 2001-01-29 13:47:59 ---- This could be a "state machine" bug that Darin has already fixed or knows how to fix. If this still happens, can we get a backtrace in the bug report? ------- Additional Comments From sullivan@eazel.com 2001-01-29 13:53:37 ----
+ Trace 9734
Here's a stack trace. It looks like the finish_loading callback doesn't take into account the possibility that the FMDirectoryView might get destroyed in the meantime. ------- Additional Comments From eli@eazel.com 2001-02-09 11:28:19 ---- Duane is now the proud owner for Desktop QA. ------- Additional Comments From darin@bentspoon.com 2001-02-22 13:46:45 ---- The stack trace in this bug report doesn't happen any more. But I am running into other assertions when I do this quickly. ------- Additional Comments From darin@bentspoon.com 2001-02-23 12:15:58 ---- The new problem seems to be some kind of trouble with widget destruction. Sometimes we die inside Bonobo's sync. machinery and other times when destroying the actual desktop. The bad object seems to be either the menu bar, or a menu or toolbar item. I'm having trouble figuring out the cause. Note that this doesn't usually result in a crash, but sometimes it does. Since it's some kind of double-destroy it's hard to figure out what the worst symptom could be. Perhaps we can defer this to 1.2 -- it's terrible, but probably OK to say "don't bash on that button in 1.0". ------- Additional Comments From don@eazel.com 2001-02-23 13:49:28 ---- Yeah, although this is a crash, I think it can be safely deferred to 1.2 since I believe it unlikely that people will actually be caffienated enough to do this. ------- Additional Comments From eli@eazel.com 2001-03-26 11:19:20 ---- SPAAAAAAAAAM! (Jon Allen has taken these components; QA Assigning bugs to him.) ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:51 ------- The original reporter (bfrank@eazel.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org.
Confirming and prioritizing.
Created attachment 7747 [details] i recreated the crash in 1.1.x
ccing naut-qa
*** This bug has been marked as a duplicate of 76342 ***