Ok, I can confirm the XKB issue there, easy way to test is to run from the
build dir (keyboard panel subdir):
setxkbmap us; ./test-keyboard (instead of us pick a layout which is not
your default one, the code will not run if the default config matches the one
used)
the issue is not due to the
ok, my guess is that upstream broke something in that commit:
http://git.gnome.org/browse/gnome-settings-daemon/commit/plugins/keyboard/gsd-keyboard-manager.c?id=f5b6a8055e24fdde1efdeaff9895e0039c84e53a
they just never really hit the bug because they dropped the xkb code
before 3.5.2 which was
Pushed a new one with 61_... updated and an upstream patch reverted to
facilitate this. Seems the compose key works now. Didn't test lid
suspend on the laptop yet.
Problems
- XKB activation error on launch, which must be related to the
aforementioned patch not being right yet.
--
You
(I'd really appreciate it if someone else could take a look at this and
g-c-c; I'm too close to the updates to see stupid mistakes just now)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
I did some work on updating to 3.5.4.
lp:~laney/gnome-settings-daemon/3.5.4
Some outstanding issues
- 61_unity_use_application_indicator.patch is large and doesn't apply, so
disabled
- Lid close doesn't suspend
- Compose key stopped working, which is possibly a larger problem with
5 matches
Mail list logo
