[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 343592] Desktop grid effect does not work with some custom shortcuts (Default: ctrl+F8)
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2015-02-03 16:19:33
Message-ID: bug-343592-17878-ErAKS0Ri9R () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=343592

--- Comment #14 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to Martin Gräßlin from comment #11)
> hmm, I'm rather thinking that it's related to kglobalacceld being started by
> dbusd and thus might be missing an env variable.

I'm not aware that the keyboard map would be controlled by some environment
variable?

(In reply to Martin Gräßlin from comment #12)
> might be related to: https://codereview.qt-project.org/#/c/104506/1

"If the window contains a widget that accepts text input..."
?
"... a Meta+... shortcut will be interpreted as if no modifier was pressed."
?




@Maverik
This will setup a german layout "by default"

---- /etc/X11/xorg.conf.d/11-keyboard.conf ---

Section "InputClass"
    Identifier          "Keyboard Defaults"
    MatchIsKeyboard     "yes"
    Option              "XkbLayout" "de"
    Option              "XkbVariant" "deadgraveacute"
#    Option              "XkbModel" "microsofccurve2k" # probably not - wtf.
does M$ no longer forge it???
    Option              "XkbOptions" "terminate:ctrl_alt_bksp,compose:caps" #
nice to have
    Option              "XkbRules" "xorg"
    Option              "XkbKeycodes" "evdev"
EndSection

-------------------------------------------------------------------------------


You might have/want to adjust some options, but for a basic text it might show
whether kglobalaccel simply misses the map change.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]