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 40762 - Crash when a component fails
Crash when a component fails
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Extension Library
unspecified
Other Linux
: Normal normal
: ---
Assigned To: John Sullivan
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2000-04-28 19:25 UTC by Darin Adler
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Darin Adler 2001-09-10 01:18:15 UTC
We die if a main or sidebar view fails. We can't afford to behave that way. We
need to report an error nicely and maybe allow switching to another view.



------- Additional Comments From mjs@noisehavoc.org 2000-04-29 19:57:56 ----

Adding dep on 408, this will be hard to test w/o a good consistent test case.

This is also intimately tied into the mess in ntl-window-msgs.c, so I am adding
a dep on that bug (#505)



------- Additional Comments From sullivan@eazel.com 2000-06-27 17:05:26 ----

A few notes: Using the content loser component, if mode is "crash" and place is
"pre-merge", it fails silently, leaving no content view installed, but
everything else still working -- can change to another view. If mode is "crash"
and place is "post-merge", then it leaves merged buttons & menu items in place
forever. If mode is "crash" and place is "post-merge" and the initial directory
is set to view by content loser, then you get a hang on launch.



------- Additional Comments From sullivan@eazel.com 2000-06-28 13:52:53 ----

I've added code and a dialog box such that in some content view failures, the
content view goes away and the user gets a dialog telling them that they can
choose another view or go to another location.

Still to be done: 
(1) some similar user-notifying thing for sidebar panel failures.
(2) fix the cases that currently hang.
(3) make sure that merged menu & toolbar items are cleaned up somehow.



------- Additional Comments From sullivan@eazel.com 2000-07-24 14:29:15 ----

Bug 41739 & 1740 were split out from this. What remains in this bug report is to
implement a UI for handling failure in sidebar panels akin to the UI I
implemented for failures in the content view.



------- Additional Comments From sullivan@eazel.com 2000-07-31 11:02:37 ----

Also split off bug 41841 about the hanging case, which needs to be addressed
differently than the crashing case.



------- Additional Comments From sullivan@eazel.com 2000-09-08 15:28:27 ----

Setting all bugs to P6 to start official bug-prioritization plan. Please don't
set the priority to anything other than P6 unless you've got the gold seal of
approval for doing so.



------- Additional Comments From eli@eazel.com 2000-10-16 19:42:35 ----

Batch-assigning QA ownership of remaining bugs to eli@eazel.com



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:18 -------
Bug depends on bug(s) 40408.
Bug blocks bug(s) 41739.