Bug 231766 - does not use notification framework everywhere
Summary: does not use notification framework everywhere
Status: RESOLVED DUPLICATE of bug 183841
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-22 14:02 UTC by Ansgar
Modified: 2011-03-16 22:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ansgar 2010-03-22 14:02:56 UTC
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.
Comment 1 Lamarque V. Souza 2011-03-16 22:21:04 UTC
Kopete from KDE SC 4.6.1 does not use KPassivePopup anymore. Can I close this bug?
Comment 2 Lamarque V. Souza 2011-03-16 22:48:16 UTC

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