I understand Sergeys comment that libxklavier generates X-new-device events and these events are processed by gnome-settings-daemon. The problem of this bug seems that neither g-s-d nor anything else takes care of reapplying the user settings to a new keyboard. According to Peter Hutterer (https://bugs.freedesktop.org/show_bug.cgi?id=26293#c2) this has to be fixed in gnome.
I think with 4 duplicates and another 2 on gnome.org every aspect of the problem should be clear for status 'Confirmed'. 'Incomplete' would mean 'needs more info', is it?
Meanwhile I can confirm that it is still reproducible with a Live-CD of Lucid alpha 3.
I understand Sergeys comment that libxklavier generates X-new-device events and these events are processed by gnome-settings- daemon. The problem of this bug seems that neither g-s-d nor anything else takes care of reapplying the user settings to a new keyboard. According to Peter Hutterer (https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 26293#c2) this has to be fixed in gnome.
I think with 4 duplicates and another 2 on gnome.org every aspect of the problem should be clear for status 'Confirmed'. 'Incomplete' would mean 'needs more info', is it?
Meanwhile I can confirm that it is still reproducible with a Live-CD of Lucid alpha 3.