Solved: DE can't launch anything and TTY is just a flashing underscore

Wolfyxon · 2023-04-13 13:34:17

Yesterday I upgraded these packages: godot gupnp-igd libnice libpaper libraqm openal
Today, when booting I noticed that I can't open Dmenu, terminal and wifi is unable to connect to any network.
After booting to multi-user.target and downgrading them all everything is back to normal.

Xorg log: http://0x0.st/H8s_.1.log
pacman:

[2023-04-13T07:45:05+0200] [PACMAN] Running 'pacman -Syu'
[2023-04-13T07:45:05+0200] [PACMAN] synchronizing package lists
[2023-04-13T07:45:09+0200] [PACMAN] starting full system upgrade
[2023-04-13T07:46:04+0200] [ALPM] transaction started
[2023-04-13T07:46:05+0200] [ALPM] upgraded godot (4.0.1-1 -> 4.0.2-1)
[2023-04-13T07:46:05+0200] [ALPM] upgraded gupnp-igd (1.2.0-3 -> 1.6.0-1)
[2023-04-13T07:46:05+0200] [ALPM] upgraded libnice (0.1.21-1 -> 0.1.21-2)
[2023-04-13T07:46:05+0200] [ALPM] upgraded libpaper (2.0.10-2 -> 2.0.12-1)
[2023-04-13T07:46:05+0200] [ALPM] upgraded libraqm (0.10.0-1 -> 0.10.1-1)
[2023-04-13T07:46:05+0200] [ALPM] upgraded openal (1.23.0-2 -> 1.23.1-1)
[2023-04-13T07:46:05+0200] [ALPM] transaction completed
[2023-04-13T07:46:05+0200] [ALPM] running '30-systemd-update.hook'...
[2023-04-13T07:46:05+0200] [ALPM] running '30-update-mime-database.hook'...
[2023-04-13T07:46:06+0200] [ALPM] running 'update-desktop-database.hook'...

Last edited by Wolfyxon (2023-04-13 14:21:09)

V1del · 2023-04-13 13:54:59

None of these packages should be able to have such an effect and you are likely making wrong assumptions and the fix would've just been to reboot without downgrading anything.

That said your xorg.conf is a complete auto-generated mess. Remove all xf86-video drivers and remove your /rootxorg.conf.new, however that log looks dated, and normally your default xorg will be on /var/log/Xorg.0.log instead of Xorg.1.log

I suggest you update again and on reproduction post the actual xorg log of that boot and

sudo jurnalctl -b

more logical guess would be you ran into the KMS race condition https://wiki.archlinux.org/title/Kernel … _KMS_start where you'll want to add the nvidia and the i915 module to the MODULES section (i915 first) and remove the kms from the HOOKS section

Last edited by V1del (2023-04-13 13:57:38)

Wolfyxon · 2023-04-13 14:06:49

that log looks dated, and normally your default xorg will be on /var/log/Xorg.0.log instead of Xorg.1.log

That's my previous log before downgrading.

That said your xorg.conf is a complete auto-generated mess

I'm using a custom config, I made it when I was trying to fix something. Removing it has no effect so I'll do that.

Remove all xf86-video drivers

Why?
Journal before downgrading: http://0x0.st/H8sV.txt

I'll re-upgrade and post the results

Last edited by Wolfyxon (2023-04-13 14:07:37)

Wolfyxon · 2023-04-13 14:12:00

Oh, you were right. That was just a random error...
(I've done a couple reboots, everything is ok)

Last edited by Wolfyxon (2023-04-13 14:21:49)

seth · 2023-04-13 14:12:06

You've iwd, dhcpcd and networkmanager enabled and they trip over each other - pick one, disable the others.
If you want to use iwd as NM backend, see https://wiki.archlinux.org/title/Networ … Fi_backend

Next up, this is an optimus system - https://wiki.archlinux.org/title/NVIDIA_Optimus
Anything you configured for xorg is gonna be relevant.

Please post the xorg and lightdm logs (/var/log for both)

Wolfyxon · 2023-04-13 14:19:02

You've iwd, dhcpcd and networkmanager enabled and they trip over each other - pick one, disable the others.

I'll do that

I think my issue is solved now but I'll post it if it's necessary.
(These are my current logs)
Lightdm

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=516
[+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: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 523: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] 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.02s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.02s] DEBUG: User wolfyxon added
[+2.53s] DEBUG: Got signal 10 from process 523
[+2.53s] DEBUG: XServer 0: Got signal from X server :0
[+2.53s] DEBUG: XServer 0: Connecting to XServer :0
[+2.70s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+2.70s] DEBUG: Session pid=592: Started with service 'lightdm-greeter', username 'lightdm'
[+2.71s] DEBUG: Session pid=592: Authentication complete with return value 0: Success
[+2.71s] DEBUG: Seat seat0: Session authenticated, running command
[+2.71s] DEBUG: Session pid=592: Running command /usr/bin/lightdm-gtk-greeter
[+2.71s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+2.71s] DEBUG: Session pid=592: Logging to /var/log/lightdm/seat0-greeter.log
[+3.03s] DEBUG: Activating VT 7
[+3.03s] DEBUG: Activating login1 session c1
[+3.03s] DEBUG: Seat seat0 changes active session to c1
[+3.03s] DEBUG: Session c1 is already active
[+3.38s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+3.54s] DEBUG: Greeter start authentication for wolfyxon
[+3.54s] DEBUG: Session pid=651: Started with service 'lightdm', username 'wolfyxon'
[+3.55s] DEBUG: Session pid=651: Got 1 message(s) from PAM
[+3.55s] DEBUG: Prompt greeter with 1 message(s)
[+5.24s] DEBUG: Continue authentication
[+5.25s] DEBUG: Session pid=651: Authentication complete with return value 0: Success
[+5.25s] DEBUG: Authenticate result for user wolfyxon: Success
[+5.25s] DEBUG: User wolfyxon authorized
[+5.26s] DEBUG: Greeter requests session i3
[+5.26s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+5.26s] DEBUG: Terminating login1 session c1
[+5.26s] DEBUG: Session pid=592: Sending SIGTERM
[+5.28s] DEBUG: Greeter closed communication channel
[+5.28s] DEBUG: Session pid=592: Exited with return value 0
[+5.28s] DEBUG: Seat seat0: Session stopped
[+5.28s] DEBUG: Seat seat0: Greeter stopped, running session
[+5.28s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+5.28s] DEBUG: Session pid=651: Running command /etc/lightdm/Xsession i3
[+5.28s] DEBUG: Creating shared data directory /var/lib/lightdm-data/wolfyxon
[+5.28s] DEBUG: Session pid=651: Logging to .xsession-errors
[+5.78s] DEBUG: Activating VT 7
[+5.78s] DEBUG: Activating login1 session 2
[+5.78s] DEBUG: Seat seat0 changes active session to 
[+5.78s] DEBUG: Seat seat0 changes active session to 2
[+5.78s] DEBUG: Session 2 is already active

Xorg: http://0x0.st/H8sw.0.log

Last edited by Wolfyxon (2023-04-13 14:19:27)

seth · 2023-04-13 14:49:27

[     5.546] (==) ServerLayout "layout"
[     5.546] (**) |-->Screen "intel" (0)
[     5.546] (**) |   |-->Monitor "<default monitor>"
[     5.547] (**) |   |-->Device "intel"
[     5.547] (**) |   |-->GPUDevice "nvidia"
[     5.547] (==) No monitor specified for screen "intel".
[     5.547] (**) |-->Inactive Device "nvidia"

This looks likey you're using (or have used) optimus-manager?
But

[     6.752] (II) NVIDIA(G0): NVIDIA GPU NVIDIA GeForce GTX 1650 (TU117-A) at PCI:1:0:0

and

[     6.751] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[     6.751] (--) NVIDIA(0):     DFP-0 (boot)

and the chip is eligible for prime w/ full powersaving support (let alone "intel_idle.max_cstate=1")

Remove optimus-manager and the configlet

grep -ri intel /{etc,usr/share}/X11/xorg.conf*

In doubt also see https://wiki.archlinux.org/title/LightD … TTY_output

Wolfyxon · 2023-04-13 17:19:04

This looks likey you're using (or have used) optimus-manager?

Remove optimus-manager and the configlet

I don't use it.

grep -ri intel /{etc,usr/share}/X11/xorg.conf*

/etc/X11/xorg.conf.backup:        Screen 0 "intel"
/etc/X11/xorg.conf.backup:        Identifier "intel"
/etc/X11/xorg.conf.backup:        Identifier "intel"
/etc/X11/xorg.conf.backup:        Device "intel"
/etc/X11/xorg.conf.NO:        Screen 0 "intel"
/etc/X11/xorg.conf.NO:        Identifier "intel"
/etc/X11/xorg.conf.NO:        Identifier "intel"
/etc/X11/xorg.conf.NO:        Device "intel"
/etc/X11/xorg.conf.nvidia-xconfig-original:        Screen 0 "intel"
/etc/X11/xorg.conf.nvidia-xconfig-original:        Identifier "intel"
/etc/X11/xorg.conf.nvidia-xconfig-original:        Identifier "intel"
/etc/X11/xorg.conf.nvidia-xconfig-original:        Device "intel"

There's a few backup and unused configs.

seth · 2023-04-13 19:00:23

You might have re/moved the file but the log has xorg.conf and the layout/scree/device configs didn't come out of thin air either.
Make sure that stuff doesn't show up in present logs anymore (though given your grep results, i shouldn't)

Arch Linux

#1 2023-04-13 13:34:17

Solved: DE can't launch anything and TTY is just a flashing underscore

#2 2023-04-13 13:54:59

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

#3 2023-04-13 14:06:49

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

#4 2023-04-13 14:12:00

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

#5 2023-04-13 14:12:06

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

#6 2023-04-13 14:19:02

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

#7 2023-04-13 14:49:27

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

#8 2023-04-13 17:19:04

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

#9 2023-04-13 19:00:23

Re: Solved: DE can't launch anything and TTY is just a flashing underscore

Board footer