Autologin not working booting to systemd option

For questions regarding system and application security
Message
Author
User avatar
bpr323
Posts: 169
Joined: Thu Jun 20, 2019 10:17 am

Re: Autologin not working booting to systemd option

#11 Post by bpr323 »

Thanks, lightdm restored.
On a side note - which files (or sim links?) do I need to copy from /home/me/ to /etc/skel/ for MX Snapshot - to create a distribution-quality ISO clone of my build?
If I copy everything, it bloats up skel but the result works, albeit with sudo minstall only (no install icons)

User avatar
dolphin_oracle
Developer
Posts: 22057
Joined: Sun Dec 16, 2007 12:17 pm

Re: Autologin not working booting to systemd option

#12 Post by dolphin_oracle »

Any settings files

But don’t copy .config/MX-Linux/xdg-check or put a desktop folder under /etc/skel.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
bpr323
Posts: 169
Joined: Thu Jun 20, 2019 10:17 am

Re: Autologin not working booting to systemd option

#13 Post by bpr323 »

My /home/me/.config/MX-Linux/xdg_check file is empty i.e. 0 bytes
/Desktop folder is also completely empty inside

User avatar
dolphin_oracle
Developer
Posts: 22057
Joined: Sun Dec 16, 2007 12:17 pm

Re: Autologin not working booting to systemd option

#14 Post by dolphin_oracle »

bpr323 wrote: Fri Dec 08, 2023 3:42 pm My /home/me/.config/MX-Linux/xdg_check file is empty i.e. 0 bytes
/Desktop folder is also completely empty inside
yes, they will be empty, but they should not go into /etc/skel if you want an installer icon to show up in your snapshot.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
bpr323
Posts: 169
Joined: Thu Jun 20, 2019 10:17 am

Re: Autologin not working booting to systemd option

#15 Post by bpr323 »

Awesome!
Thank you so much mate, I would have never guesssed :)
You're a Lagend!

User avatar
bpr323
Posts: 169
Joined: Thu Jun 20, 2019 10:17 am

Re: Autologin not working booting to systemd option

#16 Post by bpr323 »

The MX Snapshot and Live USB Maker worked well, except for a couple of minor glitches:
1) My default system locale is set to en_AU.UTF-8 (Australian English) so when I boot the new live USB I'm greeted with the message: "You've logged in in a new language. You can automatically update the names of the standard folders in your home folder to match this new language". When I click Yes it creates a bunch of std folders right on the desktop. After the install completes it pops the same question again and if I agree to rename, it creates these folders on the desktop again. If I don't agree, - no standard folders are created in the /home/user directory.
Does this mean I have to tweak the skel to somehow indicate the US locale is the default?"
2) It creates a "Live USB" folder on the desktop which points to the /home/demo/live usb storage folder, which is empty.

Needless to say, none of the above happens when I use the "personal" snapshot. So I'm guessing that using a "distribution" type snapshot when the user's default locale is set to anything but "en_US" is not supported?

User avatar
fehlix
Developer
Posts: 12617
Joined: Wed Apr 11, 2018 5:09 pm

Re: Autologin not working booting to systemd option

#17 Post by fehlix »

bpr323 wrote: Sat Dec 09, 2023 9:21 am The MX Snapshot and Live USB Maker worked well, except for a couple of minor glitches:
1) My default system locale is set to en_AU.UTF-8 (Australian English) so when I boot the new live USB I'm greeted with the message: "You've logged in in a new language. You can automatically update the names of the standard folders in your home folder to match this new language". When I click Yes it creates a bunch of std folders right on the desktop. After the install completes it pops the same question again and if I agree to rename, it creates these folders on the desktop again. If I don't agree, - no standard folders are created in the /home/user directory.
Does this mean I have to tweak the skel to somehow indicate the US locale is the default?"
2) It creates a "Live USB" folder on the desktop which points to the /home/demo/live usb storage folder, which is empty.

Needless to say, none of the above happens when I use the "personal" snapshot. So I'm guessing that using a "distribution" type snapshot when the user's default locale is set to anything but "en_US" is not supported?
Please post those questions/issues into a new tread, b/c locale settings seems not the be related to the topic title
"Re: Autologin not working booting to systemd option" of this thread.
Also include some more information, b/c non-personal "snapshot" would have the locale set based on the boot parameter lang/tz- respectivey. And also mentioned whether this is a skel-tweaked modified snapshot,
which may create such locale confusions. Also post QSI when booted from Live-snapshot.

at MOD's: can we get this posts moved into a new thread "locale issues with tweaked snapshot" or something like this.

User avatar
bpr323
Posts: 169
Joined: Thu Jun 20, 2019 10:17 am

Autologin not working booting to systemd option

#18 Post by bpr323 »

dolphin_oracle wrote: Thu Dec 07, 2023 10:08 am looking at some of the installation information, I'm wondering if the fact that the dock driver loads AFTER ligthdm, and the fact that we have an init script fro lightdm as well as a systemd service, may be causing you some grief.
Yes - editing lightdm.conf and moving the autologin commands to the top of the file (plus uncommenting the top two lines) seems to have solved the problem:

[SeatDefaults]
type=xlocal
user-session=default
autologin-user=me
autologin-user-timeout=3
greeter-session=lightdm-greeter
xserver-allow-tcp=false
session-wrapper=/etc/X11/Xsession
display-setup-script=/usr/local/bin/early-bg
xserver-command=X -dpi $DPI

Thanks mate, your comment prompted me to fix this from the "race condition" perspective - there's something else happening in the background - hence 3 sec delay timeout to let that "other" process kick off the secure login, then autologin applies and reloads the screen.

I would like to get to the bottom of this and fix it properly - but I don't know, which log file(s) to check for clues

Post Reply

Return to “Security”