Bug 337598 - /usr/bin/kcmshell5 khotkeys does not save actual trigger
Summary: /usr/bin/kcmshell5 khotkeys does not save actual trigger
Status: RESOLVED DUPLICATE of bug 337230
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_khotkeys (show other bugs)
Version: 5.1.0
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-19 04:59 UTC by Ben Kevan
Modified: 2015-07-05 09:55 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Kevan 2014-07-19 04:59:40 UTC
open /usr/bin/kcmshell5 khotkeys

add custom KMenuEdit or modify the existing "Search" menu by adding a trigger

Expect that the trigger would hold

Behavior is the trigger does not hold. 
bkevan@HC07003115SUSE:~> /usr/bin/kcmshell5 khotkeys
Trying to open ksycoca from "/home/bkevan/.cache/ksycoca5"
libGL error: dlopen /usr/lib/dri/updates/i965_dri.so failed (/usr/lib/dri/updates/i965_dri.so: cannot open shared object file: No such file or directory)
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{d03619b6-9b3c-48cc-9d9c-a2aadb485550}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{d03619b6-9b3c-48cc-9d9c-a2aadb485550}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{27e3928e-f574-4ed7-a21f-8fbf9edfb7fb}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{27e3928e-f574-4ed7-a21f-8fbf9edfb7fb}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{cc506cb9-db2b-4f08-ac76-81ccd7e2730f}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{cc506cb9-db2b-4f08-ac76-81ccd7e2730f}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{f7af6a7b-d14d-426b-8759-9289d6b0cbd9}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{f7af6a7b-d14d-426b-8759-9289d6b0cbd9}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence)
QObject::connect:  (sender name:   '{e93f9dac-565d-4c41-9bde-e99d6cb96b71}')
Comment 1 Ben Kevan 2014-07-19 16:33:37 UTC
I should note that I see the following: 
[Data_1_2]
Comment=Comment
Enabled=true
Name=Chrome - Ben
Type=SIMPLE_ACTION_DATA

[Data_1_2Actions]
ActionsCount=1

[Data_1_2Actions0]
CommandURL=google-chrome-2.desktop
Type=MENUENTRY

[Data_1_2Conditions]
Comment=
ConditionsCount=0

[Data_1_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_1_2Triggers0]
Key=Meta+C
Type=SHORTCUT
Uuid={27e3928e-f574-4ed7-a21f-8fbf9edfb7fb}


Within ~/.config/khotkeysrc

and confirm that doing a different hot key changes the file.
Comment 2 Ben Kevan 2014-07-19 16:37:10 UTC
Just to note.. if you go into global shortcuts.. you can see the values there, but the shortcuts still do not function.
Comment 3 bapride11 2014-10-10 05:01:30 UTC
Bug is still present in 5.0.95.
Comment 4 pdf 2014-10-10 05:54:02 UTC
Indeed, lack of working global hotkeys is a blocker for KF5 as a daily-driver here.  Similar log, but with line numbers:

```
kcmshell5 khotkeys
"Theme tree: (Breeze)"
Trying to open ksycoca from "/home/user/.project-neon5-kde//cache/ksycoca5"
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence) in /build/buildd/project-neon5-khotkeys-0.0+git20141005.0318+neon4~ac950d9~14.04/libkhotkeysprivate/triggers/shortcut_trigger.cpp:105
QObject::connect:  (sender name:   '{d03619b6-9b3c-48cc-9d9c-a2aadb485550}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence) in /build/buildd/project-neon5-khotkeys-0.0+git20141005.0318+neon4~ac950d9~14.04/libkhotkeysprivate/triggers/shortcut_trigger.cpp:105
QObject::connect:  (sender name:   '{d03619b6-9b3c-48cc-9d9c-a2aadb485550}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence) in /build/buildd/project-neon5-khotkeys-0.0+git20141005.0318+neon4~ac950d9~14.04/libkhotkeysprivate/triggers/shortcut_trigger.cpp:105
QObject::connect:  (sender name:   '{4932623c-eb5c-48a8-8735-9fd72fd8dacc}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence) in /build/buildd/project-neon5-khotkeys-0.0+git20141005.0318+neon4~ac950d9~14.04/libkhotkeysprivate/triggers/shortcut_trigger.cpp:105
QObject::connect:  (sender name:   '{e41a82ee-b5c7-437b-8863-29bdcc4f8e63}')
QObject::connect: No such signal QAction::globalShortcutChanged(QKeySequence) in /build/buildd/project-neon5-khotkeys-0.0+git20141005.0318+neon4~ac950d9~14.04/libkhotkeysprivate/triggers/shortcut_trigger.cpp:105
QObject::connect:  (sender name:   '{2188c4c5-5c12-403c-bf53-2026bbfc6c38}')
```
Comment 5 Maxime Corteel 2014-10-16 17:53:41 UTC
I have the same log and have had the same problem for a long time.
Comment 6 Maxime Corteel 2014-10-26 12:38:13 UTC
I can now set shortcuts, but they don't survive the end of my session. I have new log information if that can help.
Comment 7 David Edmundson 2014-11-03 10:24:27 UTC

*** This bug has been marked as a duplicate of bug 337230 ***
Comment 8 ilkerk 2015-07-05 09:55:18 UTC
This bug is annoying. Here is a bad workaround that worked for me. "Edit Applciations" and create a folder for shortcuts. Then create an app for each script, then assign a shortcut to that app.