Bug 117321 - Kopete keeps showing an intrusive error message when connecting to a MSN account in invisible mode
Summary: Kopete keeps showing an intrusive error message when connecting to a MSN acco...
Status: RESOLVED DUPLICATE of bug 117089
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-30 03:15 UTC by Victor Temistocles Nardes
Modified: 2005-11-30 05:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Temistocles Nardes 2005-11-30 03:15:53 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Slackware Packages
Compiler:          gcc 3.3.6 
OS:                Linux

Every time I connect to my MSN account through kopete in invisible mode the following message appears a lot:

"You can not send messages when you are offline or when you are invisible."

This happens when I am offline ang get connected, but I couldn't reproduce this behaviour when changing status from Online/Busy/Away/Etc to invisible. However, after the login is completed, the message keeps appearing frequently. I have two reasons to report hits as a bug:

1) We already have one message when we are invisible and try to chat with someone:

"You can not send messages when you are offline or when you are invisible.

2) If it where showed only one message, It would not be a great problem, but I've counted once 8 error messages on login and closed kopete after getting 10 more later during its use!

Suggestion: This bug can be fixed by either removing the message (solving issues 1 and 2) or at least letting us have an option not to show the message again (solving issue 2 only).
Comment 1 Victor Temistocles Nardes 2005-11-30 03:18:17 UTC
I am using kopete 0.11 from KDE 3.5.0
Comment 2 Thiago Macieira 2005-11-30 05:08:26 UTC
This was fixed after 0.11 (KDE 3.5.0 release).

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