Bug 142021 - kopete does not update automatically the vCard of Jabber contacts
Summary: kopete does not update automatically the vCard of Jabber contacts
Status: RESOLVED DUPLICATE of bug 156184
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-21 14:34 UTC by S. Burmeister
Modified: 2009-05-20 13:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2007-02-21 14:34:19 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
OS:                Linux

I have a contact in the list that did not have a photo. It's properties showed the photo-section greyed out. He then added a photo to his contact, yet kopete did not notice it. I am not sure whether this is a bug too, but anyway.

I quit kopete and re-started it, yet the photo was still not displayed and the photo section was still greyed out. I waited some minutes but it did not change.

I had to have a look at the vCard and only then the photo was updated.

Expected behaviour: Update the photo if the other person adds/changes it, or at least check whether a photo is available when the contact comes online or kopete is started.
Comment 1 Pino Toscano 2007-04-18 13:38:00 UTC
I can confirm the issue - Kopete does not automatically updates the vCard for a Jabber contact when it changes, thus does not update nickname, photo, etc.

Changing the $summary of the bug from:
> kopete does not retrieve photo of jabber-contacts
to
> kopete does not update automatically the vCard of Jabber contacts

and confirming it, with KDE 3.5.5 as well.
Comment 2 Dominik Tritscher 2008-07-22 11:33:17 UTC
Seems to be duplicate of http://bugs.kde.org/show_bug.cgi?id=141021
Comment 3 A. Spehr 2009-05-20 13:06:22 UTC

*** This bug has been marked as a duplicate of bug 156184 ***