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 433648 - Error message when trying to add tomboy to the panel twice
Error message when trying to add tomboy to the panel twice
Status: RESOLVED DUPLICATE of bug 414789
Product: tomboy
Classification: Applications
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-26 17:02 UTC by Sebastian Dröge (slomo)
Modified: 2008-10-08 12:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2007-04-26 17:02:13 UTC 
Hi,
when trying to add tomboy to the panel a second time while another instance is already there gnome-panel gives and error about not being able to load the second tomboy instance and the tomboy search dialog is opened. This obviously happens because tomboy checks for another running instance and openes the search dialog there via DBus and then exits.

It would be nice if, instead of this useless error message, tomboy could display something more useful or allow more than one instance or doesn't show up for addition a second time in the add to panel dialog.

Bye
Comment 1 Sandy Armstrong 2007-04-26 17:07:32 UTC 
Strangely, I only receive this error if Tomboy is already in the notification area, and I try to add it to the panel (see bug #414789).  I can actually add as many Tomboy applets to the panel as I like, but only one will work.

Do you receive the OAFIID error?  If so, I may mark this as a dupe of #414789.
Comment 2 Boyd Timothy 2008-02-26 19:15:11 UTC 
Setting the default assignee and QA Contact to "tomboy-maint@gnome.bugs".
Comment 3 Sandy Armstrong 2008-10-08 12:45:45 UTC 
Confirming on openSUSE 11 with Tomboy 0.12.1.  I received the OAFIID error.  Marking as dupe.

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