The previews also will not close automatically, and do not show any windows (not sure if this is intentional or not. Reproducible: Always
Created attachment 87411 [details] Picture of the problem
I had hit that one, too. But was never able to find a pattern to reproduce (sometimes it actually works).
I can reproduce the bug consistently. Happens on every boot and has persisted over the last few days of nightly updates from project neon.
ok, found the upper layer problem: QWindow::setMouseGrabEnabled(true) returns false, mouse and keyboard fail to grab.
pushbuttons grab the mouse while down -> queued connection or explicit xcb_flush? (though that'd be really a problem if connecting "clicked" would break grabbing the pointer)
(In reply to comment #5) > pushbuttons grab the mouse while down -> queued connection or explicit > xcb_flush? (though that'd be really a problem if connecting "clicked" would > break grabbing the pointer) wooha, your a genius :-) Yep that seems to be it, I already tested that updating Xtime makes the grab work again, but afterwards it break. No surprise the release... Qt::QueuedConnection should fix it and if that's the case I'm going to develop a test case for Qt.
pity, Qt::QueuedConnection doesn't work.
installing the grab on the kcm works, though.
This is still a problem in nightly builds of project neon. Can't the preview just close whenever it loses focus?
(In reply to enoopt.adams from comment #9) > Can't the preview just close whenever it loses focus? unfortunately not as it never gains focus. It's an unmanaged window.
Cannot reproduce on X11, similar Wayland bug https://bugs.kde.org/show_bug.cgi?id=374971 Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 Qt Version: 5.11.1 KDE Frameworks Version: 5.51.0 Kernel Version: 4.15.0-34-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7,7 GiB of RAM
I also can't reproduce on X11. Operating System: Arch Linux KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.2
*** This bug has been marked as a duplicate of bug 374971 ***