Bug 139609 - Contacts keep "traveling" between categories
Summary: Contacts keep "traveling" between categories
Status: RESOLVED DUPLICATE of bug 122996
Alias: None
Product: kopete
Classification: Unmaintained
Component: Gadu-Gadu Plugin (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-04 20:01 UTC by Michał ,,KNT'' Gorycki
Modified: 2008-07-22 17:37 UTC (History)
0 users

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 Michał ,,KNT'' Gorycki 2007-01-04 20:01:13 UTC
Version:           0.12.5 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages

Once a while I see few (three or four mabye) metacontacts copies in the wrong group. I move them withe mouse (some times with the shift key), or with the context menu. The metacontact is moved. But next time I launch Kopete or even after a long session with the computer those metacontacts copies are appearing in the wrong categories. Each metacontact has it's "wrong" group to witch it "travels" (although once this category changed).
Comment 1 Michał ,,KNT'' Gorycki 2007-02-10 16:09:45 UTC
One of the metacontacts kept "traveling" to a category it didn't belong to even if I kept moving it back. After fourth or fifth moving Kopete crashed.
Comment 2 Matt Rogers 2007-06-09 07:28:44 UTC
I have no idea what could cause this. Do you use more than one IM client?
Comment 3 Michał ,,KNT'' Gorycki 2007-06-11 15:04:58 UTC
No. The only thing witch I can say is that most of the contacts are Gadu-Gadu ones.
Comment 4 Matt Rogers 2007-09-26 04:45:02 UTC
Still no idea what's going on. Does this problem still occur? Maybe somebody with more Gadu knowledge can take a look. 
Comment 5 Michał ,,KNT'' Gorycki 2007-09-26 11:07:08 UTC
Yes, a quick check confirmed it's still an issue.
Comment 6 Michael 2008-07-22 17:37:49 UTC

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