(first of all, thanks for the help)
Duncan wrote:
>> % qdbus org.kde.kglobalaccel /component/kwin \
>> org.kde.kglobalaccel.Component.isActive
>> true
>
> You can also check to see if there's a kglobalaccel app running.
Yup it is runinng:
% pgrep -lf kglobal
2197 kdeinit4: kdeinit4: kglobalaccel
If I kill it, the "qdbus" query above then fails.
If I run it again, it gets back to working (though it's then different
in pgrep output as it's kinda standalone and not launched by kdeinit4).
> PID TTY TIME CMD
> 2195 ? 00:00:00 kglobalaccel
2195 vs 2197, what a chance. =)
> I don't know if freebsd uses split or monolithic kde packages but here on
> Gentoo, it's split packages, and I have both kglobalaccel and khotkeys
> installed as part of larger meta-packages.
Just the same on FreeBSD:
% pkg_info -W /usr/local/kde4/bin/kglobalaccel
[...] was installed by package kdebase-runtime-4.5.5
% pkg_info -W /usr/local/kde4/lib/kde4/kded_khotkeys.so
[...] was installed by package kdebase-workspace-4.5.5
> Talking about which... have you tried creating a fresh user, without an
> existing kde config (or from the command line without kde running, simply
> move the test user's kde config, usually ~/.kde or the like, out of the
> way, so a new, blank one is created for testing, when you start kde)?
Oh, right. I tried that just now: "mv .kde4 .kde4.bak" creates a new
profile which does NOT show the problem: hotkeys work correctly.
I then did:
% mv .kde4.bak .kde4
% rm .kde4/share/config/khotkeysrc
% rm .kde4/share/config/kglobalshortcutsrc
...nothing changed.
What other configuration stuff is involved in hotkey managing?
Keyboard layout maybe? I guess not... but I'm using compose:rwin, FWIW.
cheers,
--
Lapo Luchini - http://lapo.it/
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
