Input from upstream:
(12:17:39 μμ) rtcm: alkisg: yeah, mutter resolves the ISO_Next_Group keysym to
keycodes and installs passive grabs for all those keycodes
(12:21:00 μμ) rtcm: alkisg: so yeah, compiz would need something like
https://git.gnome.org/browse/mutter/tree/src/core/keybindings.c#n367
So I'm guessing that metacity (which is what gnome-flashback uses) would
also need that? Should I put it in the Affects list?
Thanks a lot,
Alkis
** Description changed:
unity-settings-daemon => gsd-keyboard-manager.c has an Ubuntu specific patch
that strips the grp: part in XKB options:
- if (n_sources < 2 || g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"),
"Unity") == 0)
- strip_xkb_option (options, "grp:");
+ if (n_sources < 2 || g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"),
"Unity") == 0)
+ strip_xkb_option (options, "grp:");
The original upstream source code is:
- if (n_sources < 2)
- strip_xkb_option (options, "grp:");
+ if (n_sources < 2)
+ strip_xkb_option (options, "grp:");
That causes a problem: we're no longer able to type e.g. Greek in
- TuxPaint, because TuxPaint grabs the keyboard layout, and u-s-d then
- doesn't see the layout switching shortcut.
+ TuxPaint, because TuxPaint grabs the keyboard, and u-s-d then doesn't
+ see the layout switching shortcut.
But: if we do revert only that line of the source code to what's in upstream,
then we get another problem: that the XKB-defined layout switching shortcut
(e.g. Alt+Shift) doesn't update the keyboard indicator in the panel, only the
GNOME-defined shortcut (e.g. Win+Space) does.
To solve this, I think u-s-d needs to handle ISO_Next_Group. I don't know if
that part exists upstream, but I do know that it works fine in Fedora 20.
After solving this bug, a tiny issue will remain: that Alt+Shift inside
- keyb-grabbing applications won't update the keyboard indicator. Upstream
- GNOME doesn't want patches for that and may try to solve it in SDL, but
- the other 2 issues described above ^ are Ubuntu-specific.
+ keyboard-grabbing applications won't update the keyboard indicator.
+ Upstream GNOME doesn't want patches for that and may try to solve it in
+ SDL, but the other 2 issues described above ^ are Ubuntu-specific.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1315867
Title:
Don't strip XKB grp
Status in Unity Settings Daemon:
New
Status in “gnome-settings-daemon” package in Ubuntu:
New
Bug description:
unity-settings-daemon => gsd-keyboard-manager.c has an Ubuntu specific patch
that strips the grp: part in XKB options:
if (n_sources < 2 || g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"),
"Unity") == 0)
strip_xkb_option (options, "grp:");
The original upstream source code is:
if (n_sources < 2)
strip_xkb_option (options, "grp:");
That causes a problem: we're no longer able to type e.g. Greek in
TuxPaint, because TuxPaint grabs the keyboard, and u-s-d then doesn't
see the layout switching shortcut.
But: if we do revert only that line of the source code to what's in upstream,
then we get another problem: that the XKB-defined layout switching shortcut
(e.g. Alt+Shift) doesn't update the keyboard indicator in the panel, only the
GNOME-defined shortcut (e.g. Win+Space) does.
To solve this, I think u-s-d needs to handle ISO_Next_Group. I don't know if
that part exists upstream, but I do know that it works fine in Fedora 20.
After solving this bug, a tiny issue will remain: that Alt+Shift
inside keyboard-grabbing applications won't update the keyboard
indicator. Upstream GNOME doesn't want patches for that and may try to
solve it in SDL, but the other 2 issues described above ^ are Ubuntu-
specific.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1315867/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
