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 108285 - broken link prevents proper server startup
broken link prevents proper server startup
Status: RESOLVED DUPLICATE of bug 90983
Product: bonobo-activation [was: oaf]
Classification: Deprecated
Component: general
2.2.x
Other Linux
: Normal minor
: ---
Assigned To: Michael Meeks
Luis Villa
Depends on:
Blocks:
 
 
Reported: 2003-03-13 09:00 UTC by Leif Johnson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Leif Johnson 2003-03-13 09:00:52 UTC
In the course of developing a panel applet, I put a symbolic link from
/usr/lib/bonobo/servers to a bonobo server file in my development
directory. Later, I renamed the target file in my development directory, so
the link was broken. The next time I tried to restart bonobo (using
'bonobo-slay'), it basically crashed my entire desktop : my fonts reverted
to defaults, the panel died, and Nautilus popped up recurring warning
dialogs about an error involving bonobo. It took a few hours to track down
the problem.

I know having a broken link in /usr/lib/bonobo/servers is somewhat deviant
in the first place, but it would be nice if bonobo could do a check for
this. If it's too complicated, though, that's ok, I'll just have to be more
vigilant for broken links. :)

I didn't really know if this bug ought to be filed under 'bonobo' instead
of 'bonobo-activation' ; I put it here because the BONOBO_ACTIVATION_PATH
(and not the BONOBO_PATH) seems to be involved in loading the server files.
Comment 1 Michael Meeks 2003-03-17 11:02:46 UTC
Yes; well - this is almost a feature :-)

It means (broadly) that you catch broken .server files far, far faster
than otherwise - it's best for b-a-s to crash on startup, than to
silently mis-munge a .server file IMHO.

Of course - if you want to change that - then we need to pinch GConf's
syslogging code, and start logging errors to syslog - which I think is
prolly fairly difficult to do with libXML. so ... if you want to do
that, please do send in patches - I'm interested in folding them back in.

*** This bug has been marked as a duplicate of 90983 ***