| Summary: | [liboscar/icq] authorization popup pops up at every login | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Tobias Knieper <tobias.knieper> |
| Component: | ICQ and AIM Plugins | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | johann-nikolaus |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Tobias Knieper
2005-04-10 19:52:57 UTC
I'm guessing you're talking about ICQ. yes, sure. sorry.. the popups have disappeared today, but don't know why... I can confirm this with kopete from KDE 3.4. After the update I had to request confirmation again, two of my contacts confirmed, and I just restarted kopete three times and the popups appear each time. A third contact confirmed while I was online, and this one does not pop up. However, the first restart after the session when he confirmed, he was marked as awaiting confirmation. This is all right after the second restart. *** Bug 106172 has been marked as a duplicate of this bug. *** This should be fixed for KDE 3.5 I have the problem still with KDE 3.5 rc1 I have the same bug with version 0.12.1, compiled from sources (Gentoo). Please reopen the bug. Oops, I mixed that up... I will report another issue, it's not concerning this bug. I still have the problem with kopete 0.12.1 (kde 3.5.4 - kubuntu)! it does not matter which client the other chat partner owns. maybe it has something to do with the option to enable/disable require authorization. because for me i disabled the need for authorization but the message though appears. i asked the other contact .. and he says he is authorized. so the problem is only that thedialog till appears.. not that he is not authorized. when i once log in into icq with another client (e.g. go.icq.com or trillian) the contact is authorized/the message does not appear anymore. -> please reopen the bug! |