Bug 204904 - Kopete cannot delete Google Talk contacts
Summary: Kopete cannot delete Google Talk contacts
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-23 19:54 UTC by Claus Appel
Modified: 2018-11-05 02:46 UTC (History)
2 users (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 Claus Appel 2009-08-23 19:54:00 UTC
Version:           0.70.4 (using 4.2.4 (KDE 4.2.4), 4.2.4-6.fc11 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.29.6-217.2.3.fc11.i586

Kopete seems unable to delete Google Talk contacts. I try to delete them (right-click -> Remove contact -> Remove), and it seems to work at first glance, but soon after they show up in my contact list again. Kopete does not ask me if I want to re-add them, they just re-appear on their own.
Comment 1 Peter Roots 2009-12-02 15:26:36 UTC
same problem with yahoo contacts in kubuntu karmic kopete 4.3.2
Comment 2 Andrew Crouthamel 2018-11-02 22:54:45 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Claus Appel 2018-11-03 11:47:50 UTC
Does Kopete even support Google Talk anymore? I have not used it in ages.

I cannot log in with my Gmail credentials. When I tried, Kopete failed to connect and I got an email from Google with a warning that "someone" had tried to log in using my credentials in a non-Google application. 

It sounds like Google Talk doesn't work at all in Kopete these days. I suggest that we close the bug.
Comment 4 Andrew Crouthamel 2018-11-05 02:46:40 UTC
Thanks for the update!