Bug 101411

Summary: disconnected notification blocks all of kopete, including "new-chat bubble"
Product: [Unmaintained] kopete Reporter: S. Burmeister <sven.burmeister>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description S. Burmeister 2005-03-13 08:23:43 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

If e.g. icq gets disconnected and the connection-status plugin tries to re-connect but fails, it generates a new error message for every time it fails. If you acknowledge those notifications before a successful reconnction, there will be as many, as there were failures, not necessary and very annoying.
Further and more important, these notifications block the rest of kopete. This is not sensible because MSN for example has nothing to do with ICQ and most important. If one is on a different desktop than the warning, a "new-chat bubble" pops up but cannot be used because it is blocked by something not obvious to the user, as often each desktop's kicker displays just the tasks for that desktop.

Expected behaviour:
- Do not block anything

- when connection is lost bring up one! notification

- notification should be bound to the chat-window, i.e. closing the chat-window closes the notification, focusing the chat window, focuses the notification for that account, i.e. focusing MSN has nothing to do with the ICQ notification

- do not notify if re-connecting fails, as it is already visible in that icon moving in kopete main and the chat-window telling you that you are offline, or online if re-connection was successful

- auto-close notifications not up to date, i.e. all notifications telling the user that ICQ connection failed when re-connection was successful
Comment 1 Olivier Goffart 2005-03-15 23:32:12 UTC

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