| Summary: | does not use notification framework everywhere | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Ansgar <ansgar> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | lamarque |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Kopete from KDE SC 4.6.1 does not use KPassivePopup anymore. Can I close this bug? *** This bug has been marked as a duplicate of bug 183841 *** |
Version: (using KDE 4.3.4) OS: Linux Installed from: Debian testing/unstable Packages Some events in Kopete do not use the notification framework (as used for example by incoming messages). Instead they show a popup that disappears after a moment. I noticed this at least when I got disconnected from a Jabber server and believe the following is the code responsible for this: kdenetwork-4.3.4/kopete/protocols/jabber/jabberaccount.cpp: if(!errorText.isEmpty()) { if (!additionalErrMsg.isEmpty()) { KPassivePopup::message( i18n("Connection problem with Jabber server %1", server), QString ("%1\n%2").arg(errorText).arg(additionalErrMsg), Kopete::UI::Global::mainWidget() ); } else { KPassivePopup::message( i18n("Connection problem with Jabber server %1", server), errorText, Kopete::UI::Global::mainWidget() ); } } At least the message looks similar (it disappears too fast to be sure) and the screenshot for KPassivePopup in the API documentation looks similar.