tomboy applet error can not add to panel when second login

Bug #239560 reported by Tim Richardson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tomboy
Expired
Medium
tomboy (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: tomboy

I have tomboy added to my panel in ubuntu hardy. Tomboy 0.10.2
If I log in twice as the same user (for example, remotely via vnc), the second session start withs the error "The panel encountered a problem while loading "OAFID::TomboyApplet. Do you want to delete the applet from your configuration?".

If I start it from a shell, it works.
Therefore, I have a workaround: to start tomtom as a session startup rather than having it added to the panel

Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for your report, that doesn't happen to me it works fine here, may you test the same with another user? do you have any error in the ~/.xsession-errors file? may you attach it to the report? thanks.

Changed in tomboy:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Tim Richardson (tim-richardson) wrote : Re: [Bug 239560] Re: tomboy applet error can not add to panel when second login

On Fri, 2008-06-13 at 12:26 +0000, Pedro Villavicencio wrote:
> thanks for your report, that doesn't happen to me it works fine here,
> may you test the same with another user? do you have any error in the
> ~/.xsession-errors file? may you attach it to the report? thanks.
>
> ** Changed in: tomboy (Ubuntu)
> Importance: Undecided => Low
> Status: New => Incomplete
>
I reproduced the bug.
I created a new user. I did not add tomboy to either the panel or via
sessions.
Then I did switch user and logged in again.
In the second session of this user, I tried to add tomboy to the panel.
This failed, with the same error message as in my first report.

in the home director of this user, I see the following lines from
the .xsession-errors file:

** (gnome-panel:21237): WARNING **: panel-applet-frame.c:1270: failed to
load applet OAFIID:TomboyApplet:
System exception: IDL:Bonobo/GeneralError:1.0 : Child process did not
give an error message, unknown failure occurred
GConf backend: There is an unsupported value at
path /apps/compiz/plugins/scale/allscreens/options/initiate_edge.
Settings from this path won't be read. Try to remove that value so that
operation can continue properly.
** Message: Got disconnected from the session message bus; retrying to
reconnect every 10 seconds

Changed in tomboy:
status: Incomplete → New
Revision history for this message
Tim Richardson (tim-richardson) wrote :

workaround is to add Tomboy as a session startup

Revision history for this message
Pedro Villavicencio (pedro) wrote :

thansk for the report, i cannot reproduce this , can you forward it upstream at bugzilla.gnome.org since you're facing the issue? for forwarding instructions please have a look to https://wiki.ubuntu.com/Bugs/Upstream/GNOME ; I'm leaving this as incomplete until that, thanks in advance.

Changed in tomboy:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Tim Richardson (tim-richardson) wrote :

It is forwarded here:
http://bugzilla.gnome.org/show_bug.cgi?id=547032

I don't know why you can't reproduce it. It is still happening in hardy. It also happens in Debian sid.
The easiest way to reproduce it is to enable multiple logins for the same user, then switch user and login to a second session. This way of reproducing it is in the upstream report. Anyway, it's upstream now, plus I reported it to Debian.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for sent it upstream, linking the task.

Changed in tomboy:
status: Incomplete → Triaged
Changed in tomboy:
status: Unknown → New
Revision history for this message
joseph alberino (jp-alberino) wrote :

I get a similar error, in lucid,
the error is "the panel encountered a problem while loading OAFIID :
GNOME_FASTER USER SWITCH APPLET,
It then asks if you want to delete the applet from the configuration, you say yes and its still present the next time you log in, any ideas?

Changed in tomboy:
importance: Unknown → Medium
Changed in tomboy:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.