Version: 0.12 beta1 (using KDE KDE 3.5.2) Installed from: Ubuntu Packages OS: Linux Since I updated to Kopete 0.12 beta 1, I experience the problem that setting my global status to "Occupied" causes Kopete to set my ICQ status to "Do not disturb" (according to systray tooltip).
Sorry, I cannot see any global status called "Occupied". There are "Online", "Away", "Busy", "Invisble" and "Offline".
busy and occupied mean pretty much the same thing. at least, imho "busy" is closer to "occupied" than "do not disturb".
Okay. But not all protocols support "Occupied". If "Set Status"->"Busy" set one account to "Occupied" and another to "Do not Disturb" clients on the other side would send messages to the one with the more available status: the icq account. At least if they support groups or meta-contacts, too (like Miranda).
I mean the Busy status (I translated the string from german myself). Anyways, I think Occupied/Busy and Do Not Disturb are completely different things. I use Occupied/Busy to say "I'm doing someting,but you might try contacting me anyway" and Do Not Disturb to say "Don't interrupt me at all - only if it is REALLY important". And therefore I see Occupied very close to Busy (and not to Do Not Disturb) - in the german translation both are translated as Beschäftigt btw. MSN has Busy mapped to global Busy in Kopete (though there is no Do Not Disturb here), so I think in ICQ it should be mapped to Occupied. I don't know about other protocols (only that AIM only knows Away) but I think that the global Busy thing should generally be mapped to Busy or Occupied or as a fallback to Away. Do not Disturb is something else, imho.
The status set by "Set Status"->"Busy" was intentionally unified: The problem described in comment #3 is very annoying. The logic behind (at least for Jabber and ICQ) is to set the least available status by "Set Status"->"Busy" because there is no "Busy" status. This can't fit anybody's needs and a solution could be custom status entries in "Set Status" where the user can select the status target for each protocol.
Does this problem still exist in a recent KDE 4 version of kopete?
This problem still exists in Kopete 0.99.90.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.