You are not logged in.
I have a problem with lightdm after installing arch. For simplicity, I tried installing arch again and not installing anything extra. Now I have installed:
(via pacstrap): base linux linux-firmware
(via pacman in chroot): vim wpa_supplicant networkmanager
(via pacman in normal boot): ligthdm lightdm-gkt-greeter xfce4 xfce4-goodies
If I make only lightdm enabled (I tried restarting several times), lightdm will start. However, if you activate the NetworkManager and lightdm, then lightdm will not start.
And if I disable NetworkManager later, the situation will not change.
How can I solve this problem?
Logs:
After starting:
# systemctl
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2deDP\x2d1-intel_backlight.device loaded active plugged /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight
sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d4-1\x2d4:1.0-bluetooth-hci0.device loaded active plugged /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0
sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d7-1\x2d7:1.0-tty-ttyACM0.device loaded active plugged Fingerprint Reader
sys-devices-pci0000:00-0000:00:1c.0-0000:3b:00.0-net-wlp59s0.device loaded active plugged QCA6174 802.11ac Wireless Network Adapter
sys-devices-pci0000:00-0000:00:1d.0-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device loaded active plugged KXG60ZNV512G NVMe TOSHIBA 512GB 1
sys-devices-pci0000:00-0000:00:1d.0-0000:3d:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device loaded active plugged KXG60ZNV512G NVMe TOSHIBA 512GB 2
sys-devices-pci0000:00-0000:00:1d.0-0000:3d:00.0-nvme-nvme0-nvme0n1.device loaded active plugged KXG60ZNV512G NVMe TOSHIBA 512GB
sys-devices-pci0000:00-0000:00:1f.3-sound-card0.device loaded active plugged Cannon Lake PCH cAVS
sys-devices-platform-dell\x2dlaptop-leds-dell::kbd_backlight.device loaded active plugged /sys/devices/platform/dell-laptop/leds/dell::kbd_backlight
sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devices-platform-serial8250-tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devices-platform-serial8250-tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-devices-virtual-misc-rfkill.device loaded active plugged /sys/devices/virtual/misc/rfkill
sys-module-configfs.device loaded active plugged /sys/module/configfs
sys-subsystem-bluetooth-devices-hci0.device loaded active plugged /sys/subsystem/bluetooth/devices/hci0
sys-subsystem-net-devices-wlp59s0.device loaded active plugged QCA6174 802.11ac Wireless Network Adapter
-.mount loaded active mounted Root Mount
boot-EFI.mount loaded active mounted /boot/EFI
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
run-user-0.mount loaded active mounted /run/user/0
sys-kernel-config.mount loaded active mounted Kernel Configuration File System
sys-kernel-debug.mount loaded active mounted Kernel Debug File System
sys-kernel-tracing.mount loaded active mounted Kernel Trace File System
tmp.mount loaded active mounted Temporary Directory (/tmp)
systemd-ask-password-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-ask-password-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
init.scope loaded active running System and Service Manager
session-1.scope loaded active running Session 1 of user root
dbus.service loaded active running D-Bus System Message Bus
getty@tty2.service loaded active running Getty on tty2
kmod-static-nodes.service loaded active exited Create list of static device nodes for the current kernel
● lightdm.service loaded failed failed Light Display Manager
NetworkManager.service loaded active running Network Manager
systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight:intel_backlight
systemd-backlight@leds:dell::kbd_backlight.service loaded active exited Load/Save Screen Backlight Brightness of leds:dell::kbd_backlight
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
user-runtime-dir@0.service loaded active exited User Runtime Directory /run/user/0
user@0.service loaded active running User Manager for UID 0
wpa_supplicant.service loaded active running WPA supplicant
-.slice loaded active active Root Slice
system-getty.slice loaded active active system-getty.slice
system-modprobe.slice loaded active active system-modprobe.slice
system-systemd\x2dbacklight.slice loaded active active system-systemd\x2dbacklight.slice
system.slice loaded active active System Slice
user-0.slice loaded active active User Slice of UID 0
user.slice loaded active active User and Session Slice
dbus.socket loaded active running D-Bus System Message Bus Socket
dm-event.socket loaded active listening Device-mapper event daemon FIFOs
systemd-coredump.socket loaded active listening Process Core Dump Socket
systemd-initctl.socket loaded active listening initctl Compatibility Named Pipe
systemd-journald-audit.socket loaded active running Journal Audit Socket
systemd-journald-dev-log.socket loaded active running Journal Socket (/dev/log)
systemd-journald.socket loaded active running Journal Socket
systemd-rfkill.socket loaded active listening Load/Save RF Kill Switch Status /dev/rfkill Watch
systemd-udevd-control.socket loaded active running udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
bluetooth.target loaded active active Bluetooth
cryptsetup.target loaded active active Local Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User System
network.target loaded active active Network
paths.target loaded active active Paths
remote-fs.target loaded active active Remote File Systems
slices.target loaded active active Slices
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
timers.target loaded active active Timers
man-db.timer loaded active waiting Daily man-db regeneration
shadow.timer loaded active waiting Daily verification of password and group files
systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
90 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
# systemctl status lightdm
● lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2020-06-27 13:10:34 MSK; 56s ago
Docs: man:lightdm(1)
Process: 458 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
Main PID: 458 (code=exited, status=1/FAILURE)
Jun 27 13:10:34 dellXPS systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Jun 27 13:10:34 dellXPS systemd[1]: Stopped Light Display Manager.
Jun 27 13:10:34 dellXPS systemd[1]: lightdm.service: Start request repeated too quickly.
Jun 27 13:10:34 dellXPS systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jun 27 13:10:34 dellXPS systemd[1]: Failed to start Light Display Manager.
and if I run
# systemctl restart lightdm
lightdm will start, and the next result of the previous command:
# systemctl status lightdm
● lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2020-06-27 13:11:36 MSK; 14s ago
Docs: man:lightdm(1)
Main PID: 551 (lightdm)
Tasks: 14 (limit: 18745)
Memory: 105.9M
CGroup: /system.slice/lightdm.service
├─551 /usr/bin/lightdm
├─557 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
└─598 lightdm --session-child 14 21
Jun 27 13:11:36 dellXPS systemd[1]: Starting Light Display Manager...
Jun 27 13:11:36 dellXPS systemd[1]: Started Light Display Manager.
Jun 27 13:11:36 dellXPS lightdm[551]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Jun 27 13:11:37 dellXPS lightdm[569]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Jun 27 13:11:37 dellXPS lightdm[569]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Last edited by ismagilov_aa (2020-07-02 08:51:52)
Offline
1. Remember the existence of journalctl.
2. Try a different greater to rule that out.
Offline
2. Try a different greater to rule that out.
You mean to try another display manager?
Offline
Sorry for the typo. I mean a different lightdm greeter.
Offline
Sorry for the typo. I mean a different lightdm greeter.
Could you share a link to any article describing this process?
Offline
You've installed lightdm-gkt-greeter. Check the lightdm wiki article here on the arch wiki and try another greeter to rule out the gtk greeter. I haven't used lightdm in a while, but every time I did, some greeter acted up.
Offline
You've installed lightdm-gkt-greeter. Check the lightdm wiki article here on the arch wiki and try another greeter to rule out the gtk greeter. I haven't used lightdm in a while, but every time I did, some greeter acted up.
I do not understand what happened. I installed another greeter, it started, but when I tried to log in, there was some problem and after rebooting it did not boot. I commented out the line back in the /etc/lightdm/lightdm.conf file (see the instructions from the wiki archa) and lightdm-gtk-greeter worked. I tried to restart several times and everything worked. True, if earlier systemd displayed a series of information and hung forever, now it is like this for a second, that is, lightdm starts, but not instantly. I think this is not scary.
But it looks very strange ... Maybe this is not always.
Maybe you know what happened and why it was fixed?
Offline
The previous message was erroneous. lightdm started to run, but as it turned out, not always and not always fast. Of 10 launches, only 3 started lightdm and then after 5 seconds.
Offline
Have you familiarized with journalctl yet?
Offline
There are a lot of things. The first thing that caught my eye. Maybe it's not at all.
Error getting user list from org.freedesctop.Accounts. ..... The name org.freedesctop.Accounts was not provided bu any .service files
Last edited by ismagilov_aa (2020-06-28 11:48:44)
Offline
That's meaningless. Post the journal.
Also afaik lightdm itself still logs to /var/log/lightdm, so have a look there as well.
Also post the output of "hostnamectl"
Offline
# hostnamectl
Static hostname: dellXPS
Icon name: computer-laptop
Chassis: laptop
Machine ID: 6230794c9d2f41f6a199c5e7d06920d1
Boot ID: f5dd2251446a4c9b8afb24519f179665
Operating System: Arch Linux
Kernel: Linux 5.7.6-arch1-1
Architecture: x86-64
# cat /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=464
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: posix_spawn avoided (fd close requested)
[+0.00s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.00s] DEBUG: Using VT 7
[+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.00s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.00s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.00s] DEBUG: XServer 0: Launching X Server
[+0.00s] DEBUG: Launching process 470: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.00s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.01s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.01s] DEBUG: User ismagilov added
[+0.45s] DEBUG: Process 470 exited with return value 1
[+0.45s] DEBUG: XServer 0: X server stopped
[+0.45s] DEBUG: Releasing VT 7
[+0.45s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+0.45s] DEBUG: Seat seat0: Display server stopped
[+0.45s] DEBUG: Seat seat0: Stopping session
[+0.45s] DEBUG: Seat seat0: Session stopped
[+0.45s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.45s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.45s] DEBUG: Seat seat0: Stopping
[+0.45s] DEBUG: Seat seat0: Stopped
[+0.45s] DEBUG: Required seat has stopped
[+0.45s] DEBUG: Stopping display manager
[+0.45s] DEBUG: Display manager stopped
[+0.45s] DEBUG: Stopping daemon
[+0.45s] DEBUG: Exiting with return value 1
journalctl very big.. (Posts cannot be longer than 1,048,576 bytes.)
maybe I can post only grep journalctl output?
Offline
journalctl very big.. (Posts cannot be longer than 1,048,576 bytes.)
maybe I can post only grep journalctl output?
Use a pastebin client. See the tip box at the top of the topic: https://wiki.archlinux.org/index.php/Li … in_clients
Offline
journalctl
https://pastebin.com/Q2ucFiBj
Offline
Is there something different with each of the nine boots contained in the journal you posted?
Offline
The last 8 have "lightdm.service: Failed with result 'exit-code'." the first one doesn't.
(Network manager is up before lightdm in the good one too, though)
Edit
[+0.00s] DEBUG: Launching process 470: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
…
[+0.45s] DEBUG: Process 470 exited with return value 1
It's because the X11 server crashes.
=> Cause a failing boot, reboot, but only into the multi-user.target (see link in signature) and post the xorg logs (see other link ;-)
Last edited by seth (2020-06-30 13:31:29)
Offline
Oh. I didn’t know that journalctl stores all starts. It makes sense to watch only the most recent launch. The first few were without graphical interfaces. Here is only the most recent launch.
Offline
Also this is a system with hybrid graphics and nouveau - how did you configure it?
https://wiki.archlinux.org/index.php/Optimus
Offline
Cause a failing boot, reboot, but only into the multi-user.target (see link in signature) and post the xorg logs (see other link ;-)
If I understood correctly, then I had to start, see what the problem was, call systemctl set-default, restart the computer and show the file /var/log/Xorg.0.log
https://pastebin.com/d3rADzgE
Offline
[ 3.973] (II) VESA: driver for VESA chipsets: vesa
[ 3.973] (EE) open /dev/dri/card0: No such file or directory
[ 3.973] (WW) Falling back to old probe method for modesetting
[ 3.974] (EE) open /dev/dri/card0: No such file or directory
[ 3.974] (II) modeset(G0): using drv /dev/dri/card1
[ 3.974] (EE) Screen 0 deleted because of no matching config section.
…
[ 4.338] (EE) Screen(s) found, but none have a usable configuration.
[ 4.338] (EE)
Fatal server error:
[ 4.338] (EE) no screens found(EE)
[ 4.338] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 4.338] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 4.338] (EE)
[ 4.338] (EE) Server terminated with error (1). Closing log file.
Also this is a system with hybrid graphics and nouveau - how did you configure it?
https://wiki.archlinux.org/index.php/Optimus
Offline
If I disable NetworkManager log look like
https://pastebin.com/eDWRA7xr
I did not configure this system in any way. Although it is recommended to prescribe nouveau.modeset=0 for my computer. But I did nothing except installing the system (following the instructions from the wiki) and installing a couple of packages.
Offline
Then see the link I posted and configure it. That's not optional.
The difference is the availability of the nvidia chip when X11 starts, resp. which chip gets selected as main one.
Offline
I add
nouveau.modeset=0
to grub; install
pacman -S xf86-video-intel
and now everything works (also added bbswitch to save energy). Thanks!!!
Offline
How to mark topic as SOLVED?
Offline
Edit the first post and prepend [SOLVED] to the thread title.
Offline