From time to time, the application launcher does no longer open when I left-click on it - until I logout & login again: https://youtu.be/Uc0VJjPZmyY I have a dual-monitor setup, running Fedora 27 on an AMD kaveri based system (7650k).
It were these kinds of bugs that made me leave KDE back in the 4x days, now after 6 years using XFCE it is sad to see quality hasn't improved that much. I've already filed a dozen of crash reports via Fedora automatic bug reporter, since I started using it a month a go.
Did you, by chance, use the "minimize all" feature/plasmoid?
not knowingly, can it be triggered by accident? I initially thought maybe the menu is shown on the wrong screen (in a hidden area because of the lower resolution of my 2nd screen) - but this is also not the case. It simply doesn't appear :/
I have to admit that I've seen this happen one or two times, too. Never been able to figure out what triggers it, and I've never been able to reproduce on command. I don't have any 3rd party widgets or scripts or anything like that.
I experience the issue almost every time. Funny enough, for fallback reasons I've added the smaller application menu - and after some time it now exhibits the same issue. So I have two icons, application starter and application menu, both not displaying :/
another thing I noted: when I remove such a mis-behaving application menu (hover mouse above, wait for popup and click red "x" icon), the plugin is removed. When I now choose "revert", it is restored, it still doesn't work. In case I remove it completle and add a new one, it works again.
Found out what is causing this: When I switch the virtual desktop while the application / launcher is shown, it is left in broken state.
For what it's worth, that trigger recipe is not reproducible for me on my fedora 27 box.
> For what it's worth, that trigger recipe is not reproducible > for me on my fedora 27 box. Funny, I've just verified it has nothing to do with my multi-monitor setup. Just took my SSD and bootet it in my laptop (single-screen), same behaviour.
To be clear, * how exactly are you switching virtual desktops ? (I tested both clicking and keyboard shortcuts) * mind verifying versions of installed components? rpm -q qt5-qtbase kf5-plasma plasma-workspace I'm testing with: qt5-qtbase-5.9.4-4.fc27.x86_64 kf5-plasma-5.43.0-3.fc27.x86_64 plasma-workspace-5.11.5-3.fc27.x86_64
> how exactly are you switching virtual desktops By clicking on the virtual desktop chooser kf5-plasma is a little bit older on my machine: qt5-qtbase-5.9.4-1.fc27.x86_64 kf5-plasma-5.42.0-1.fc27.x86_64 plasma-workspace-5.11.5-3.fc27.x86_64 I'll enable updates-testing and report back
FWIW, I cannot reproduce with any method of switching between virtual desktops either. But I am using Plasma 5.12.2 and Frameworks 5.43.
video of the issue: https://www.youtube.com/watch?v=xznM6m2IUAU&feature=youtu.be updated to updates-testing: qt5-qtbase-5.9.4-1.fc27.x86_64 kf5-plasma-5.43.0-3.fc27.x86_64 plasma-workspace-5.11.5-3.fc27.x86_64 ... issue is still existant. Is there anything I can do to diagnose this issue?
another finding: doesn't make a difference whether I have the application menu in the taskbar or on the desktop, broken behaviour is the same.
Thanks for the video showing how you can reproduce the issue. Unfortunately, I can't reproduce it on my Kubuntu 17.10 (Plasma 5.12.2) machine when I follow the same steps. It works just fine when I click on the pager while the menu is open.
Can reproduce in: Plasma: 5.12.2 Apps: 17.12.2 Frameworks: 5.43.0 Qt: 5.10.1 Kernel: 4.14.22-1-MANJARO OS: Netrunner Rolling
Sorry my prev comment is wrong - i can't reproduce this issue - i set up two virtual desktop one on top of other - tried to switch virtual desktops while App Launcher is opened and reopen it again - App Launcher opens every time - same for desktop applet
I finally found the root cause of this issue: I am using kwin/kde with no compositor. When I enable the compositor, the application menu behaves as expected - when I start plasma with the compositor disabled it is broken once I switch to another virtual desktop while the menu was open.
Yep, can confirm. Steps to reproduce: 1. Have at least two virtual desktops 2. Disable compositor on startup (System Settings > Display & Monitor > Compositor Uncheck "Enable compositor on startup") 3. Reboot 4. Open your menu (kicker kickoff, SimpleMenu, whatever) 5. Use a keyboard shortcut to switch desktops 6. Boom, menu no longer launches until plasmashell is restarted or you re-enable the compositor.
Just retested - was able to reproduce only once - not by shortcut - but by clicking on Pager in the Panel - with Kicker as menu Plasma: 5.12.2 Apps: 17.12.2 Frameworks: 5.43.0 Qt: 5.10.1 Kernel: 4.14.25-1-MANJARO OS: Netrunner Rolling
There are use-cases where disabling the compositor makes actually sense - like running inside VirtualBox on a 4k monitor setup. Now imagine the outrage if Windows-7 would not open the start-menu after a few times in case the user decides to disable Aero. Too bad even core components are that buggy :/
Can you see if this is fixed with the new Kickoff UI in Plasma 5.21 (currently in git master)? A lot of this code was rewritten which means there's a chance it got fixed in the process. Thanks!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!