https://bugs.kde.org/show_bug.cgi?id=457977
--- Comment #2 from Mitja <mtj...@gmail.com> --- Thanks for the clarification. I will wait till QT 6 is fully implemented before reporting the issue to the authors. Best regards. Mitja V sre., 17. avg. 2022 21:57 je oseba Nate Graham <bugzilla_nore...@kde.org> napisala: > https://bugs.kde.org/show_bug.cgi?id=457977 > > Nate Graham <n...@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |RESOLVED > Resolution|--- |DOWNSTREAM > CC| |n...@kde.org > > --- Comment #1 from Nate Graham <n...@kde.org> --- > This happens because the app in question does not implement the > Wayland-specific activation protocol. It's still rather new and a lot of > apps > don't yet have support for it. They should. :) So you should report this > to the > developers of those apps. > > Note: it's currently expected that it doesn't work for KDE apps because > generic > support in Qt for the activation protocol was only merged for Qt6, and KDE > apps > haven't been ported to use Qt 6 yet. But once they are, this should start > working for them. But non-Qt 3rd-party apps will still need to manually > implement the activation protocol. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
