Bug 184640 - system notifications don't work
Summary: system notifications don't work
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: knotify (show other bugs)
Version: unspecified
Platform: Gentoo Packages Unspecified
: NOR normal
Target Milestone: ---
Assignee: Olivier Goffart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-17 13:53 UTC by Maciej J . Woloszyk
Modified: 2009-03-03 20:39 UTC (History)
4 users (show)

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 Maciej J . Woloszyk 2009-02-17 13:53:46 UTC
Version:            (using KDE 4.2.0)
Installed from:    Gentoo Packages

It seems there is some problem with knotify4 - process is running, configuration works fine, but notifications don't work. When trying to diagnose using dbus-monitor I found that when some event is processed and notification is passed dbus generates something like this:

error sender=:1.9 -> dest=:1.8 error_name=org.freedesktop.DBus.Error.UnknownMethod reply_serial=580
   string "No such method 'event' in interface 'org.kde.KNotify' at object path '/Notify' (signature 'sssayasx')"
Comment 1 FiNeX 2009-02-17 15:17:11 UTC
Would you like to check the trunk version too?
Comment 2 Maciej J . Woloszyk 2009-02-17 15:31:35 UTC
Well... I could, but I would probably have to recompile half of what's considered stable KDE to the trunk version... And I've been waiting for some time for the Gentoo devs to add it to the official tree I wouldn't like to break anything now.
I'll take a look at the Gentoo's kde-testing overlay to find out if there is any way to install single package from it.
Comment 3 Scott Thomson 2009-02-17 15:43:25 UTC
I can confirm the issue - same package versions on Gentoo.  However this issue only occurred after bumping qt to 4.5.0_rc1
Comment 4 Maciej J . Woloszyk 2009-02-18 08:05:26 UTC
Ok. I've downgraded Qt Back to 4.4.2, recompiled KDE and the problem is gone for now.
Comment 5 Olivier Goffart 2009-02-18 08:29:59 UTC
This bug has been fixed in KDE 4.2.1
Comment 6 Sokolov Nikolay 2009-03-03 17:00:16 UTC
kde developers, you are the best
Comment 7 Nikos Chantziaras 2009-03-03 20:39:20 UTC
Does someone know the commit that fixed this? I'd like to try and backport it to 4.2.0.