Ubuntu
kdenetwork package

kopete loses status message after closed or even if the user (un)locks his session

Bug #99058 reported by J Janz
2
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kopete

When user closes kopete (closing only kopete - not remaining in the notification area - or the whole user kde session, or even shutdown the system) or locks his kde session and restarts it (again, restarts the system, or the user session, or just kopete) or unlocks the session, the user entered status message (called there "away message") is cleared. It should be persisted.

Tested in kubuntu edgy.
Also, tested only for jabber accounts (I don't even have - or want - a MSN account to test).

See original description
Revision history for this message
J Janz (jjanz) wrote :

Forgot to say: tested in kubuntu edgy. Not tested in feisty beta yet. If I do that soon, I post it here (if if the bug is not there).

description: updated
J Janz (jjanz)
description: updated
J Janz (jjanz)
description: updated
Revision history for this message
J Janz (jjanz) wrote :

Ok, tested in feisty and the problem is still there. :-(
I've made a little bit more detailed tests (in feisty).
I've set user' status to Online typing a status message and locked kde session. The status was automatically set to Away and the status message was still there. But when I unloked the session and status got back to Online, the status message was gone (cleared).
I've made the same test from Busy instead of Online. When I locked kde session, status was not set to Away, then status message didn't change, neither by locking it or unlocking it, once status also didn't change.
I've got the same problem starting from Free to Chat status. I locked kde session, status was set to Away (status message was there) and, when I unlocked, I've found another problem: it turned to Online instead of Free to Chat and status message was cleared.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta?

Changed in kdenetwork:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdenetwork:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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