Opened 11 days ago
Last modified 10 days ago
#17412 new defect
Systray icon shows available/green even if disconnected from the chat server
| Reported by: | attila123 | Owned by: | grim |
|---|---|---|---|
| Milestone: | Component: | pidgin (gtk) | |
| Version: | 2.13.0 | Keywords: | available disconnected |
| Cc: |
Description (last modified by attila123)
I created an XMPP account, which points to a service which is not always available (actually it is a protocol translator (running in localhost) from a proprietary chat application). (This is now the only account I have in pidgin.)
Expected behaviour: I would expect that whenever any connection/account is broken (yes, even one of them), then the systray icon would change to something else than the green circle ("available" sign). That way I would quickly notice that one of my connections have a problem and I need to take action.
Actual behaviour: When I have an account which is disconnected (e.g. "Unable to connect"), I can only see it when I open pidgin main window (Buddy List). (Then the problem is described, and "Modify Account" and "Reconnect" buttons are available). But I do not see the problem from the systray icon of pidgin which is still green. This gives me the false impression that everything is OK, and others can send chat messages to me.
I think it is such a basic need from an IM program that I set the type to 'defect'.
I am on Linux / Cinnamon desktop if that matters.
Change History (5)
comment:1 Changed 11 days ago by attila123
- Description modified (diff)
comment:2 Changed 11 days ago by attila123
comment:3 Changed 11 days ago by grim
I just did some basic testing and it appears that the global status just stays at whatever it was last at. This sucks. That said, I am in the process of rewriting the entire status widget for Pidgin 3 so I'll be sure to make sure this get's handled there.
comment:4 Changed 11 days ago by grim
Ticket #1152 has been marked as a duplicate of this ticket.
comment:5 Changed 10 days ago by grim
- Owner set to grim




Looks like it is a very long standing issue without any solution :( E.g. https://developer.pidgin.im/ticket/181 https://developer.pidgin.im/ticket/1152