[frameworks-knotifications] [Bug 364798] New: knotifications processes clicks wrong

[Jiri Slaby via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364798

Bug ID: 364798
Summary: knotifications processes clicks wrong
Product: frameworks-knotifications
Version: 5.22.0
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: ***@kde.org
Reporter: ***@gmail.com
CC: kdelibs-***@kde.org

When I double click an icon in systemtray, it does nothing, but it should open
the main window of the relevant application. This works without knotifications
correctly, e.g. in icewm.

I noticed this problem on KDE 5 with psi+:
https://github.com/psi-plus/psi-plus-snapshots

FWIW middle and right clicks and scroll events are not passed down to the app
correctly too.

For testing purposes, I wrote a minimalistic simple app creating only a
QSystemTrayIcon:
https://github.com/jirislaby/collected_sources/tree/master/qt5-icon

When I click on the icon in icewm (i.e. no knotifications), I get:
left button: activate 3
middle button: activate 4
right button: activate 1
double click: activate 3 & activate 2
scroll: wasn't tried

In KDE 5, the app built against qt5 (libQt5Core.so.5 =>
/usr/lib64/libQt5Core.so.5):
left button: activate 3
middle button: activate 1 (WRONG)
right button: NOTHING (WRONG)
double click: activate 3 & activate 3 (WRONG)
scroll: NOTHING (WRONG)

In KDE 5, the app built against qt4 (libQtCore.so.4 =>
/usr/lib64/libQtCore.so.4):
left button: activate 3
middle button: activate 4
right button: NOTHING (WRONG)
double click: activate 3 & activate 3 (WRONG)
scroll: eventFilter true 31

Reproducible: Always

[Jiri Slaby via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #1 from Jiri Slaby <***@gmail.com> ---
Created attachment 99714
--> https://bugs.kde.org/attachment.cgi?id=99714&action=edit
icewm click backtrace

[Jiri Slaby via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #2 from Jiri Slaby <***@gmail.com> ---
Created attachment 99715
--> https://bugs.kde.org/attachment.cgi?id=99715&action=edit
KDE5+qt4 click backtrace

[Jiri Slaby via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #3 from Jiri Slaby <***@gmail.com> ---
Created attachment 99716
--> https://bugs.kde.org/attachment.cgi?id=99716&action=edit
KDE5+qt5 click backtrace

[Jiri Slaby via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #4 from Jiri Slaby <***@gmail.com> ---
Versions:
qt4: libqt4-4.8.7-4.1.x86_64
qt5: libQt5Core5-5.6.0-1.1.x86_64
KDE5: plasma-framework-5.22.0-1.1.x86_64
knotifications: libKF5Notifications5-5.22.0-1.2.x86_64

[Jiri Slaby via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #5 from Jiri Slaby <***@gmail.com> ---
And yet, what should the activate numbers actually be:
QPlatformSystemTrayIcon::Context 1
QPlatformSystemTrayIcon::DoubleClick 2
QPlatformSystemTrayIcon::Trigger 3
QPlatformSystemTrayIcon::MiddleClick 4

according to:
http://doc.qt.io/qt-5/qplatformsystemtrayicon.html#ActivationReason-enum

[Jiri Slaby via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364798

--- Comment #6 from Jiri Slaby <***@gmail.com> ---
And indeed, removing /usr/lib64/libKF5Notifications.so.5* makes the problem
disappear.

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=364798

Aleix Pol <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@kde.org
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WAITINGFORINFO

--- Comment #7 from Aleix Pol <***@kde.org> ---
So it was a binary compatibility issue?

[Jiri Slaby]

https://bugs.kde.org/show_bug.cgi?id=364798

Jiri Slaby <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|RESOLVED |UNCONFIRMED

--- Comment #8 from Jiri Slaby <***@gmail.com> ---
(In reply to Aleix Pol from comment #7)

Post by Aleix Pol
So it was a binary compatibility issue?

Not at all -- it only means that libKF5Notifications5 is the culprit.

Now, even when the KDE/plasma stack in opensuse completely runs on the top of
qt5, the problem still persists.

[Jiri Slaby]

https://bugs.kde.org/show_bug.cgi?id=364798

Jiri Slaby <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|5.22.0 |5.29.0

[Eridani Rodríguez]

https://bugs.kde.org/show_bug.cgi?id=364798

Eridani Rodríguez <***@yahoo.com.mx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@yahoo.com.mx