You are not logged in.
My system keyboard settings (be) are ignored by lightdm-greeter (sticking with qwerty).
Several forums advise to change the /etc/lightdm/lightdm.conf but oddly BL does not take into account these settings and rather refers to the settings located in in /usr/share/lightdm/lightdm.conf.d/.
In order to avoid possible overwriting the bunsen specific config file 50_bunsen.conf (during upgrade), it is advised to create a further config file, for example 60_custom.conf with the following content:
[SeatDefaults]
display-setup-script=/usr/bin/setxkbmap be
greeter-setup-script=/usr/bin/numlockx on
Of course you should have (apt-get) installed numlockx first.
Greetz,
Lenny
Last edited by lenny_135 (2018-01-21 14:08:46)
Offline
Hi Lenny, welcome to BunsenLabs!
My system keyboard settings (be) are ignored by lightdm-greeter (sticking with qwerty).
Several forums advise to change the /etc/lightdm/lightdm.conf but oddly BL does not take into account these settings and rather refers to the settings located in in /usr/share/lightdm/lightdm.conf.d/.
In order to avoid possible overwriting the bunsen specific config file 50_bunsen.conf (during upgrade), it is advised to create a further config file, for example 60_custom.conf with the following content:...
Yes, adding a file to /usr/share/lightdm/lightdm.conf.d/ is the recommended way for a user to add settings. If the number is higher than 50 then it will take priority over anything set by lower-numbered files, like 50_bunsen.conf, so the user settings will not be overwritten by an upgrade.
However, I'm surprised to hear that /etc/lightdm/lightdm.conf is ignored. My understanding was that config files in /etc would take priority over anything in /usr.
That was my experience when changing a lightdm setting ( greeter-hide-users ) that was set in /usr/share/lightdm/lightdm.conf.d/01_debian.conf. I think your code should have worked equally well in /etc/lightdm/lightdm.conf. Are you sure you didn't mistakenly put it in /etc/lightdm/lightdm-gtk-greeter.conf?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Hi John, many thanks for your reply and kind welcome.
However, I'm surprised to hear that /etc/lightdm/lightdm.conf is ignored. My understanding was that config files in /etc would take priority over anything in /usr.
After a further trial (commented out the relevant /usr lines and uncommented the corresponding ones in /etc), I re-confirm that /etc/lightdm/lightdm.conf is indeed ignored or overruled later in the login process by other settings (dbus ?).
You also seem to be of opinion that this is not conventional (/etc should have priority). That is the reason why I posted this topic for helping other BunsenLabs users with a Logitech wireless keyboard (the K750 is marvellous for (fast) typing and is moreover solar powered - charged overday and heavily drained during the night ;-)).
Cheers
Offline
That /etc should have priority is definitely the convention, and also is consistent with my personal experience. I can only think you might have a spelling error somewhere in your /etc/lightdm/* files.
Please post your output of:
/usr/sbin/lightdm --show-config
Here is what I see:
john@bunsen1:~$ /usr/sbin/lightdm --show-config
[SeatDefaults]
A greeter-session=lightdm-greeter
C greeter-hide-users=false
A session-wrapper=/etc/X11/Xsession
B session-setup-script=/usr/lib/bunsen/configs/bl-user-setup
Sources:
A /usr/share/lightdm/lightdm.conf.d/01_debian.conf
B /usr/share/lightdm/lightdm.conf.d/50_bunsen.conf
C /etc/lightdm/lightdm.conf
Also, see here: https://forums.bunsenlabs.org/viewtopic … 807#p17807
Last edited by johnraff (2018-01-31 04:19:08)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
This is the output of lightdm --show-config when activating the setxkbmap be in the /etc/lightdm/lightdm.conf (conventional but non working configuration):
lenny@bunsen:~$ /usr/sbin/lightdm --show-config
[SeatDefaults]
A greeter-session=lightdm-greeter
A greeter-hide-users=true
A session-wrapper=/etc/X11/Xsession
B session-setup-script=/usr/lib/bunsen/configs/bl-user-setup
[LightDM]
D display-setup-script=/usr/bin/setxkbmap be
D greeter-setup-script=/usr/bin/numlockx on
Sources:
A /usr/share/lightdm/lightdm.conf.d/01_debian.conf
B /usr/share/lightdm/lightdm.conf.d/50_bunsen.conf
C /usr/share/lightdm/lightdm.conf.d/60_custom.conf
D /etc/lightdm/lightdm.conf
It seems that the "D" items are never executed (keyboard remains "qwerty").
When setxkbmap be is activated in /usr/share/lightdm/lightdm.conf.d/60_custom.conf (unconventional but working configuration), the output is as follows:
lenny@bunsen:~$ /usr/sbin/lightdm --show-config
[SeatDefaults]
A greeter-session=lightdm-greeter
A greeter-hide-users=true
A session-wrapper=/etc/X11/Xsession
B session-setup-script=/usr/lib/bunsen/configs/bl-user-setup
C display-setup-script=/usr/bin/setxkbmap be
C greeter-setup-script=/usr/bin/numlockx on
Sources:
A /usr/share/lightdm/lightdm.conf.d/01_debian.conf
B /usr/share/lightdm/lightdm.conf.d/50_bunsen.conf
C /usr/share/lightdm/lightdm.conf.d/60_custom.conf
D /etc/lightdm/lightdm.conf
Thanks for the link to topic 17807. Interesting literature. I definitively should try the lightdm debug mode and go through the output.
But my problem is a specific problem for some Logitech keyboards (models K400 and K750), probably dbus related and might therefore not be revealed in the debug logs (I'll keep you posted). When I connect a standard keyboard the global keyboard settings (Belgian layout) automatically apply in lightdm. A separate (forced) execution of setxkbmap be is then not required.
Offline
OK this looks like the error:
This is the output of lightdm --show-config when activating the setxkbmap be in the /etc/lightdm/lightdm.conf (conventional but non working configuration):
lenny@bunsen:~$ /usr/sbin/lightdm --show-config [LightDM] D display-setup-script=/usr/bin/setxkbmap be D greeter-setup-script=/usr/bin/numlockx on
---
When setxkbmap be is activated in /usr/share/lightdm/lightdm.conf.d/60_custom.conf (unconventional but working configuration), the output is as follows:
lenny@bunsen:~$ /usr/sbin/lightdm --show-config [SeatDefaults] C display-setup-script=/usr/bin/setxkbmap be C greeter-setup-script=/usr/bin/numlockx on
The display-setup-script settings need to be in the [SeatDefaults] section of the config file: in your /etc/lightdm/lightdm.conf you've got them under [LightDM].
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
That is indeed the error ! The scripts were defined in the wrong section.
I must have been misleaded by the commented options put "before" the [SeatDefaults] section (which I just did amend and uncomment).
Great to see that logic prevails ! Just unfortunate that the setxkbmap be is required for these two Logitec keyboards (system settings do not apply), but with this easy workaround the system is up and running.
MANY thanks johnraff !
Offline
Glad it worked.
Surprised you couldn't change your keyboard layout by editing /etc/default/keyboard though.
Last edited by johnraff (2018-02-04 02:55:35)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline