Blame SOURCES/0001-keyboard-Apply-num-lock-to-newly-connected-keyboards.patch

7401e8
From 508108257fae1e3f2cb8e4bbd1764c695e60f9c9 Mon Sep 17 00:00:00 2001
7401e8
From: Bastien Nocera <hadess@hadess.net>
7401e8
Date: Tue, 28 Jan 2014 12:10:32 +0100
7401e8
Subject: [PATCH] keyboard: Apply num-lock to newly connected keyboards
7401e8
7401e8
before 34395459cc8f0da6f163736743bced441ef86390, apply_all_settings()
7401e8
and then apply_numlock() would sync up the numlock LED on a newly
7401e8
hotplugged device.
7401e8
34395459cc8f0da6f163736743bced441ef86390 removed that call, so devices
7401e8
now come up with the numlock LED off even when the numlock is on, and a
7401e8
subsequent state change will wrongly toggle it, i.e. LED off when numlock
7401e8
is on, LED on when numlock is off.
7401e8
7401e8
This should really be fixed in the xserver but it's unlikely to happen,
7401e8
restoring this patch in gnome-settings-daemon seems the simplest solution
7401e8
for now.
7401e8
7401e8
https://bugzilla.gnome.org/show_bug.cgi?id=722753
7401e8
---
7401e8
 plugins/keyboard/gsd-keyboard-manager.c | 1 +
7401e8
 1 file changed, 1 insertion(+)
7401e8
7401e8
diff --git a/plugins/keyboard/gsd-keyboard-manager.c b/plugins/keyboard/gsd-keyboard-manager.c
7401e8
index 846fd4f..5f09f50 100644
7401e8
--- a/plugins/keyboard/gsd-keyboard-manager.c
7401e8
+++ b/plugins/keyboard/gsd-keyboard-manager.c
7401e8
@@ -1248,6 +1248,7 @@ device_added_cb (GdkDeviceManager   *device_manager,
7401e8
         source = gdk_device_get_source (device);
7401e8
         if (source == GDK_SOURCE_KEYBOARD) {
7401e8
                 g_debug ("New keyboard plugged in, applying all settings");
7401e8
+                apply_numlock (manager);
7401e8
                 apply_input_sources_settings (manager->priv->input_sources_settings, NULL, 0, manager);
7401e8
                 run_custom_command (device, COMMAND_DEVICE_ADDED);
7401e8
         }
7401e8
-- 
7401e8
1.8.4.2
7401e8