Bug 292736 - Presence applet appearance doesn't change with status change
Summary: Presence applet appearance doesn't change with status change
Status: RESOLVED FIXED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: presence-applet (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 0.4.0
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-28 23:33 UTC by e.lexhanna
Modified: 2012-07-06 12:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description e.lexhanna 2012-01-28 23:33:20 UTC
Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

The presence applet in the systray displays only a blue chat bubble regardless of the status (online, offline, away, unavailable). Also, after clicking on the applet the current status icon is a piece of paper. After clicking the piece of paper it will flip over and show all of the available statuses and their proper icons, but after clicking any it will continue to be just a piece of paper. The icon on the task bar then remains a blue chat bubble.

Reproducible: Always

Steps to Reproduce:
Just enable the presence applet in the systray or put it on the panel and try to change your status.

Actual Results:  
Icon remains a blue chat bubble regardless of the status you set. 

Expected Results:  
The icon displayed on the presence applet should change to reflect your current status (available=green circle, away=clock, offline=grey circle and so on).

It happens whether you activate the presence applet in the systray or add it as a widget on the panel.
Comment 1 David Edmundson 2012-01-29 17:29:15 UTC
Could you try running:

plasmoidviewer ktp-presence-applet

and tell us what happens and paste any output.
Comment 2 e.lexhanna 2012-01-29 17:42:28 UTC
Running that command a new window opens that says:

The object could not be created for the following reason: 
could not find requested component: ktp-presence-applet

Additionally, I have discovered that if I start a second instance of the presence applet the second instance will work correctly. I can then remove the first (nonworking) instance and the second instance will continue to function correctly for the remainder of the session. After a restart, however, it will not work correctly anymore.
Comment 3 Martin Klapetek 2012-01-29 19:21:50 UTC
It seems that you have either a misconfiguration in your system or it is wrongly installed.

Did you compile it yourself or did you install packages (what distro)?
Comment 4 e.lexhanna 2012-01-29 20:14:44 UTC
I used the package provided in the Arch Linux repository. All was working as it was supposed to until the KDE 4.8 update.

I tried re-installing the presence applet but that did not fix it. I have the entire telepathy-kde package group installed so I don't think it is due to a missing component.
Comment 5 Martin Klapetek 2012-01-29 20:32:33 UTC
Can you provide all telepathy-* packages versions?
Comment 6 David Edmundson 2012-01-29 20:42:10 UTC
Arch is still on version 0.2 of KDE-TP, which is why you can't load the new applet which I tried making you run. You're going to get an update on this in the next few days. 

This applet is completely rewritten, and will almost certainly solve your issue.

(which means you almost certainly have the old bug of trying to connect before the dataengine is ready problem). No point solving this, when we have a new release out which does away with all this.

When you get 0.3 (open the contact list help->about kde tp contact list and make sure it says 0.3) if you still have the problem, please please reopen this.
Comment 7 e.lexhanna 2012-01-29 20:45:51 UTC
Yup, I still have presence applet version 0.2. It wasn't updated with the rest of the KDE 4.8 stuff. Thanks for the help, I will be on the lookout for the new version.
Comment 8 David Edmundson 2012-01-29 20:48:58 UTC
NP, it's being packaged separately, we're not part of kde core. There's some holdup with one of the libs (don't fully know what).

The bug you saw was an obscure race condition (where two bits of code go to do something in different apps, and it only works if the combination finishes in the right order) with the bump to 4.8 a plasma change must have meant it started triggering for you. Let us know if you have any other issues in the future.