-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Summoning Settings And Opening Menu Simultaneously Crashes KDE Plasma #756
Comments
Here's the stack trace by the way:
|
Hi again! Thanks for the detailed report. Can you reproduce this also without the controller? If it's really just both commands being executed more or less simultaneously, something like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Short Summary
Hello!
I recently found a way to crash Kando AND the entirety of KDE Plasma Wayland.
It's related to trying to summon the configurer and the Kando menu at the same time.
Steps to Reproduce the Issue
Using an input remapper called JoyShockMapper, I have bound tapping the L3 button twice to be bound to LWINDOWS + SPACE (LeftMeta + Space).
In KDE, I have bound that to do the command:
kando --menu "Main Menu"
Kando uses the L3 button as a way to progress into menus.
I also have a radial option in Kando to open Kando, bound as
kando --settings
. It's nested one layer deep inside a submenu after root.Main Menu > Configuration > Kando Settings.
By double-tapping L3, I am activing the
kando --settings
command from Kando, and thekando --menu "Main Menu"
command from KDE at the same time.kando --settings
kando --menu "Menu Name"
at the same time as thekando --settings
This causes the entire desktop to crash.
One workaround would be to allow users to disable controller support.
Thankyou for your consideration.
Kando Version
v1.6.0
Installation Method
Via a package manger
Desktop Environment
KDE on Wayland
Environment Version
KDE Plasma 6.2 on Arch Linux 6.12.4-arch1-1
Additional Information
JoyShockMapper itself likely isn't the culprit, it's probably related to trying to resolve the conflict between the Kando menu and the settings manager.
The text was updated successfully, but these errors were encountered: