Bug 385800 - Shortcut is reset
Summary: Shortcut is reset
Status: RESOLVED DUPLICATE of bug 300532
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keys (show other bugs)
Version: 5.5.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-16 06:25 UTC by Pablo
Modified: 2018-01-31 03:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
the menu item when set (14.90 KB, image/png)
2017-10-16 06:25 UTC, Pablo 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo 2017-10-16 06:25:28 UTC 
Created attachment 108371 [details]
the menu item when set

Global Keyboard Shortcuts -> Plasma (KDE component)
Activate Application Launcher  Widget.
The key is reset upon reboot, or some update now and then, not all reboots cause it to be reset either.

I set it to custom - none, as I have phpstorm that uses the combination of Alt+F1.

Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial
Comment 1 Nate Graham 2017-10-16 12:19:52 UTC 
Are you using the KDE backports PPA to get newer Plasma versions, or are you using Bog-standard Plasma from 16.04.x?
Comment 2 Pablo 2017-10-16 14:47:51 UTC 
Bog-standard
Comment 3 Nate Graham 2018-01-17 19:45:02 UTC 
Any chance you can re-test with a more recent version of KDE Plasma, like 5.11.5?
Comment 4 Pablo 2018-01-17 20:37:04 UTC 
Will test next week.
Comment 5 Pablo 2018-01-24 08:04:16 UTC 
Well after doing this:
https://askubuntu.com/questions/993639/how-to-install-kde-plasma-5-11-on-ubuntu-16-04-kubuntu-16-04
on virtual-box kubuntu 16.04 installation I got in plasma-desktop 4:5.11.5-0neon+16.04+xebial+build79
after going into system settings->shortcuts->global shortcuts->plasma I put the "Activate Application Launchwer Widget" to none.
After reboot it was again Alt-F1
Comment 6 Christoph Feck 2018-01-31 03:52:32 UTC 

*** This bug has been marked as a duplicate of bug 300532 ***