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 46664 - metadata code ignores CORBA-reported errors
metadata code ignores CORBA-reported errors
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Metadata
2.16.x
Other All
: High critical
: 2.16.x
Assigned To: Christian Neumair
Nautilus Maintainers
Depends on:
Blocks: 353629
 
 
Reported: 2001-02-15 16:34 UTC by engber
Modified: 2006-10-03 15:09 UTC
See Also:
GNOME target: 2.16.x
GNOME version: 2.15/2.16


Attachments
Proposed patch (9.15 KB, patch)
2006-09-12 19:22 UTC, Christian Neumair
committed Details | Review
Committed Patch (to HEAD) (9.15 KB, patch)
2006-09-14 18:36 UTC, Christian Neumair
committed Details | Review

Description engber 2001-09-10 01:00:37 UTC
The new metadata code in nautilus-directory-metafile.c ignores any errors which
are reported by the CORBA_environment.



------- Additional Comments From engber@eazel.com 2001-02-20 10:25:35 ----

Also in nautilus-metfile.c. There are FIXMEs in both files about this.



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:00 -------

The original reporter (engber@eazel.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
The original owner (engber@eazel.com) of this bug does not have an account here.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 John Fleck 2002-01-05 04:04:39 UTC
Changing to "old" target milestone for all bugs laying around with no milestone set.
Comment 2 Damon Chaplin 2002-04-23 18:45:38 UTC
Adding GNOME2 keyword as this is still relevant. See bug #73456.

What should each function do when an error is encountered?
Comment 3 Luis Villa 2002-05-01 15:46:55 UTC
Damon: what's the impact here? more possible crashes, I take it? but
mostly hypothetical ones that aren't happening?
Comment 4 Damon Chaplin 2002-05-10 18:57:05 UTC
It means that if an error occurs trying to communicate between Corba
components, there is a fairly high chance of a crash.

But I'd guess that if there is a communication error nautilus is in
pretty bad shape anyway, so I don't think this is too serious.
Comment 5 Christian Neumair 2005-12-20 19:20:23 UTC
Removing the milestone. The code will probably be freed from CORBA and/or replaced by a non-Nautilus specific solution.
Comment 6 Ed Catmur 2006-08-26 23:03:12 UTC
A crash happened here shortly after a nautilus -q; the returned corba_value contained bogus data.
Comment 7 Christian Neumair 2006-09-12 19:22:33 UTC
Created attachment 72640 [details] [review]
Proposed patch

This bug actually seems to do much harm under some circumstances.
Comment 8 Christian Neumair 2006-09-12 19:24:33 UTC
Raising priority/severity.
Comment 9 Alexander Larsson 2006-09-14 08:32:30 UTC
There seems to be a bug in the patch causing asserts:
http://mail.gnome.org/archives/nautilus-list/2006-September/msg00032.html
Comment 10 Christian Neumair 2006-09-14 18:26:39 UTC
I committed it after changing

  g_assert (found || error != NULL);

into

  g_assert (!found || error != NULL);

in

 nautilus-metafile.c:corba_register_monitor()

Sorry for this slip of the pen, yet another in a long series :/.
Comment 11 Christian Neumair 2006-09-14 18:28:20 UTC
Closing, fixed.
Comment 12 Christian Neumair 2006-09-14 18:36:27 UTC
Created attachment 72807 [details] [review]
Committed Patch (to HEAD)

For the sake of clarity, I'm obsoleting the old attachment 72640 [details] [review], replacing it with a new patch which has the changes specified in comment 10.
Comment 13 Federico Mena Quintero 2006-10-03 15:09:05 UTC
Thanks for the patch, Manny!  I'm backporting this for https://bugzilla.novell.com/show_bug.cgi?id=209234