Bug 136498 - kopete fails to display offline status
Summary: kopete fails to display offline status
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-30 09:50 UTC by mojedokumenty
Modified: 2015-03-30 19:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Fix for editor alignment (3.20 KB, text/plain)
2007-06-09 11:01 UTC, Guillermo Antonio Amaral Bastidas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mojedokumenty 2006-10-30 09:50:46 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
OS:                Linux

Kopete ignores the status message for an offline contact and consequently does not display it in the list.

Offline statuses are widely used with jabber transports, for instance in the gadu-gadu transport (I'm aware there's support for this protocol in Kopete, but I'd like to stick to the trasport) or the tlen transport. Missing this functionality, Kopete falls short of my expectations and AFAIK it is going to be introduced in the subsequent version of PSI.
Comment 1 Guillermo Antonio Amaral Bastidas 2007-06-09 11:01:20 UTC
Created attachment 20813 [details]
Fix for editor alignment

I tested the latest SVN revision and it does indeed happen, this patch will
store the rich text alignment separately.
Comment 2 Guillermo Antonio Amaral Bastidas 2007-06-09 11:12:11 UTC
Sorry posted the patch on wrong bug somehow
:: FIX POSTES IS NOT FOR THIS BUG ::
Comment 3 Guillermo Antonio Amaral Bastidas 2007-06-09 11:13:18 UTC
Comment on attachment 20813 [details]
Fix for editor alignment

NOT FOR THIS BUG, PLEASE DISCARD
Comment 4 Josh Berry 2008-07-07 01:45:11 UTC
Confirmed in trunk r828808.
Comment 5 Pali Rohár 2015-03-30 19:35:35 UTC
It is working for jabber contacts, so closing this bug.