SLow startup time and cannot autologin in different DE

tea_niugnep · 2021-02-17 17:08:03

hi, I finished my first Arch installation recently but I met some problems when following the recommendations in wiki.

First, I cannot set auto-login for my no-root user.

I used lightDM & xfce4 first, write /etc/lightdm/lightdm.conf and put the user into new auto-login group as wiki said, but it didn't work.. And I cannot announce or change the greeter by changing the value of `greeter-session`, each time I set the greeter-session value in lightdm.conf, the start of lightdm broke.

Then I changed to sddm & kde plasma5, still I can't auto-login, I add the autologin.conf as wiki said. Now I don't think it's problem of DM, but I still dont know why.

Second problem is that I find after using sddm &kde, my laptop startup time become much longer than before.

I use grub:
grub ->Arch Linux terminal ->(A very long time) -> login GUI

and brightness has a sudden up when in terminal, after brightness up, the GUI come

I put the output of systemd-analyze in #2

I also dont understand the output in terminal when startup:
>/dev/root_disk: clean, xxx/yyy files, aaa/bbb blocks

Last edited by tea_niugnep (2021-02-17 17:11:22)

tea_niugnep · 2021-02-17 17:12:49

systemd-analyze:

Startup finished in 5.759s (firmware) + 3.585s (loader) + 1.186s (kernel) + 1.736s (userspace) = 12.267s
graphical.target reached after 1.736s in userspace

systemd-analyze blame:
1.252s systemd-random-seed.service
923ms systemd-resolved.service
371ms lvm2-monitor.service
240ms upower.service
227ms dev-nvme0n1p2.device
144ms systemd-journal-flush.service
107ms boot-efi.mount
82ms udisks2.service
68ms user@1000.service
66ms user@0.service
65ms systemd-logind.service
61ms NetworkManager.service
59ms systemd-udev-trigger.service
58ms polkit.service
52ms systemd-journald.service
44ms systemd-udevd.service
42ms systemd-fsck@dev-disk-by\x2duuid-44FB\x2d530E.service
40ms systemd-networkd.service
38ms systemd-tmpfiles-setup.service
32ms systemd-tmpfiles-clean.service
31ms modprobe@drm.service
27ms dev-disk-by\x2duuid-38c99e5f\x2d02dd\x2d4b4c\x2da139\x2d59d0717078e1.swap
27ms wpa_supplicant.service
19ms systemd-rfkill.service
15ms systemd-tmpfiles-setup-dev.service
13ms modprobe@fuse.service
12ms systemd-update-utmp.service
10ms dev-hugepages.mount
10ms dev-mqueue.mount
9ms sys-kernel-debug.mount
9ms systemd-backlight@leds:tpacpi::kbd_backlight.service
9ms sys-kernel-tracing.mount
8ms kmod-static-nodes.service
8ms modprobe@configfs.service
6ms user-runtime-dir@0.service
6ms systemd-remount-fs.service
6ms systemd-sysctl.service
6ms user-runtime-dir@1000.service
5ms systemd-backlight@backlight:intel_backlight.service
4ms tmp.mount
3ms systemd-user-sessions.service
3ms rtkit-daemon.service
2ms sys-kernel-config.mount
1ms sys-fs-fuse-connections.mount

seth · 2021-02-17 22:15:31

First, no shopping list threads. Open one thread per topic.
Second, don't bump. Simply edit your post if nobody has replied so far.
Third, please use code tags for shell IO and file contents, https://bbs.archlinux.org/help.php#bbcode

Fourth: on topic ;-)
The "auto-login group" is actually "autologin" and you'll still have to add the relevant user to the lightdm.conf, please post the output of

id

and your /etc/lightdm/lightdm.conf
In order to select a different greeter, you'll also have to install the greeter package. Did you?

The console output is from a filesystem check that is triggered during the boot and SDDM & Plasma are just much fatter than lightdm & xfce - technically, you don't need either.
https://wiki.archlinux.org/index.php/Ge … al_console
https://wiki.archlinux.org/index.php/Start_X_at_login

Arch Linux

#1 2021-02-17 17:08:03

SLow startup time and cannot autologin in different DE

#2 2021-02-17 17:12:49

Re: SLow startup time and cannot autologin in different DE

#3 2021-02-17 22:15:31

Re: SLow startup time and cannot autologin in different DE

Board footer