-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Issues after bluefin 38-20230930 upgrade to latest 38-20231004 #564
Comments
Can confirm, I am on 38.20231005 and Super+L and Media keys stopped working |
I have also tested Bazzite GNOME – same issue as with Bluefin. Switched to Beyond and all is OK. |
Thank you very much for your report. It took me some time, but I was able to reproduce the issue. I've installed a fresh vm with Indeed the shortcuts are working. After that i have rebased with I've pinpointed the issue. Working on a fix. |
I have made PR that should fix the issue. After its merged you should have functional keyboard shortcuts again. This issue will close automatic. Feel free to re-open this issue if it did not fix the problem for you. Thanks again for the reports. |
Greetings Team,
I have upgraded today 3 of my devices (2 desktop PC and one VM) from bluefin 38-20230930 to latest 38-20231004 and all of them had the same issue - I cannot use special keys and some GNOME shortcuts do not work.
e.g.
Looking further in the logs, I found references to
gsd-media-keys
core dumps, e.g.Oct 04 14:53:51 ryzen5 systemd-coredump[2679]: Process 2657 (gsd-media-keys) of user 1000 dumped core.
andOct 04 16:35:12 ryzen5 systemd[1096]: Failed to start org.gnome.SettingsDaemon.MediaKeys.service - GNOME keyboard shortcuts service.
Has anyone else had this problem?
Update:
Went to pin to specific version - tested 38-20231003, 38-20231002 and latest working for me is 38-20231001,
Went also on Fedora 39 branch - same thing as above.
Update 2
Same problem, for me, also with 38.20231005
The text was updated successfully, but these errors were encountered: