Bug 193598

Summary:	global hotkeys stop working shortly after startup
Product:	[Unmaintained] khotkeys	Reporter:	David Palacio <dpalacio>
Component:	general	Assignee:	Michael Jansen <kde>
Status:	CLOSED DUPLICATE
Severity:	normal	CC:	gerhard.gappmeier
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	.xsession-errors with kglobalaccel output .xsession-errors

Description David Palacio 2009-05-22 03:52:50 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Global hotkeys/shortcuts do work after the few first seconds KDE starts. After the startup sound notification is played global shortcuts stop working. Even if that sound notification is disabled, it stops working around the same time.

If I tweak the hotkey combination for a shortcut in systemsettings to a value different to it's current value (wether it is default or not), it works a little bit. For example:

Walk through windows: Current value: (Default: Alt+Tab)
Does not work.
I set it to: Control+Alt+Tab
It works, just once. That is, it does walk through windows but stops after the first step.

Comment 1 David Palacio 2009-05-22 03:54:08 UTC

A correction:

Global hotkeys/shortcuts do work *in* the few first seconds KDE starts.

Comment 2 David Palacio 2009-05-22 04:01:44 UTC

Created attachment 33910 [details]
.xsession-errors

.xsession-errors for current login

Comment 3 Michael Jansen 2009-05-22 14:20:22 UTC

1. Do you have more than one kglobalaccel demon running?
    https://bugs.kde.org/show_bug.cgi?id=193558

2. Do you use xmodmap?


3. Enable kglobalaccel debug output in kdebugdialog. Try to stop and restart
kglobalaccel (kquitapp kglobalaccel; kglobalaccel --nofork). Does it work? If
not attach the output kglobalaccel gives.

4. If kglobalaccel worked after restarting. Relogin and attach the content of
your .xsession-errors file.

You current .xsession-errors file is not useful because of the missing
kglobalaccel output. But i guess 1. is you problem anyway.

Comment 4 David Palacio 2009-05-22 14:52:54 UTC

Created attachment 33919 [details]
with kglobalaccel output

> 1. Do you have more than one kglobalaccel demon running?
    https://bugs.kde.org/show_bug.cgi?id=193558
Yes.

> 2. Do you use xmodmap?
No.

> 3. Enable kglobalaccel debug output in kdebugdialog. Try to stop and restart
> kglobalaccel (kquitapp kglobalaccel; kglobalaccel --nofork). Does it work? If
> not attach the output kglobalaccel gives.
I could use kquitapp on one kglobalaccel, but the other one had to be killed. Restarting kglobalaccel fixed it.

> 4. If kglobalaccel worked after restarting. Relogin and attach the content of
> your .xsession-errors file.

Comment 5 Gerhard Gappmeier 2009-05-23 12:53:04 UTC

Created attachment 33943 [details]
.xsession-errors

trace for the kglobalaccell/khotkeys problem

Comment 6 Gerhard Gappmeier 2009-05-23 13:00:08 UTC

I don't know actually what khotkeys is for,
but it causes kglobalaccel to lose it's dbus registration and then no global shortcut works anymore.
You can see that in the trace above.

Problem description:
For a few seconds after startup the global shortcuts work.
Then khotkeys is started and create a dbus error.
After that kglobalaccell shortcuts don't work anymore.

Workaround:
Disable khotkeys in KDE Service Manager.
Without this daemon started the global shortcuts lile Alt-F2, Alt-Tab work.

Leaving the question for me: What do I need khotkeys for?

Things to do:
1.) Prevent khotkeys generating this error.
2.) Make the DBUS stuff more robust, so that errors like this cannot stop existing registrations to work.

Comment 7 Michael Jansen 2009-05-23 23:42:41 UTC

Same problem, different symptoms. We hope to have it fixed today.

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