[SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

prayner96 · 2023-02-08 17:00:42

The problem: I am having issues running xrdp (see my my Reddit post describing the issue if helpful). To solve the issue, I added `exec qtile` at the end of the ~/xinitrc script. I reboot, but nothing changes.

I comment out the xterm lines in ~/xinitrc, edit the line to `exec qtile start`, and I also added a comma at the end of a line of code to fix a sound keybinding issue in ~/.config/qtile/config.py. Finally, I ran `paru`, and I think this might have caused the problem. I rebooted the laptop and then the LightDM screen comes up. I type in username and pw successfully, but after 1 second of a black screen with an underscore flashing in the top left corner, the screen returns to LightDM. So I assume there is an issue with QTile startup. I access a tty and remove the `exec qtile start` line, uncomment the xTerm lines, and comment out the qtile config line I'd changed, but nothing changes upon reboot, I'm still stuck at the LightDM screen.

Below are the contents of the ~/.xsession contents:

1 Exception in callback Qtile.call_soon.<locals). f() at /usr/lib/python3.18/site-packages/libqtile/core/manager.py:861 1 handle: Handle Qtile.call_soon. <locals), f() at /usr/lib/python3.18/site-packages/libqtile/core/manager.py:861> 
2 Traceback (most recent call last):
3   File "/usr/lib/python3.18/asyncio/events.py", line 88, in _run
4     self._context.run(self._callback, self._args) 
5   File "/usr/lib/python3.18/site-packages/1ibqtile/core/manager.py", line 862, in f
6     func(*args) 
7   File "/usr/lib/python3.18/site-packages/1ibqtile/widget/base.py", line 730 in timer setup
8     update interval = self.tick() 
9   File "/usr/lib/python3.18/site-packages/libqtile/widget/clock.py", line 79, in tick
18     self.update(self.poll()) 
11   File "/usr/lib/python3.18/site-packages/libqtile/widget/base.py", line 697, in update
12     old_width= self.layout.width 
13   File "/usr/lib/python3.18/site-packages/libqtile/drawer.py", line 81, in width
14     return self.layout.get_pixel_size()[8]
15   File "/usr/lib/python3.18/site-packages/libqtile/pangocffi.py", line 138, in get_pixel size
16     pango.pango_layout_get_pixel_size(self._pointer, width, height) 
17 TypeError: initializer for ctype 'PangoLayout must be a cdata pointer, not NoneType

I don't understand why it is still happening after undoing changes.

I had a look at: https://wiki.archlinux.org/title/LightD … login_loop. The problem is still there after removing .Xauthority.
I also added `session-wrapper=/etc/lightdm/Xsession` to lightdm.conf but I'm still stuck...

Last edited by prayner96 (2023-02-10 20:38:58)

Scimmia · 2023-02-08 18:26:24

What does `pacman -Qo /usr/lib/python3.18/` show? Something is not right here.

LightDM doesn't use .xinitrc at all, so changes there aren't going to have any effect at all.

prayner96 · 2023-02-08 18:50:17

Output you requested:

https://imgur.com/a/od1iahb

prayner96 · 2023-02-08 18:51:39

So I actually used paru to update my packages just before rebooting, and after reading posts from people with the same issue, I think I might have to downgrade xorg-server?

Last edited by prayner96 (2023-02-08 18:52:05)

Scimmia · 2023-02-08 18:53:03

Um, that's /usr/lib/python3.10/. That makes a lot more sense, though. Did you transcribe that entire error by hand? Don't do that - see https://wiki.archlinux.org/title/List_o … n_services

prayner96 · 2023-02-08 19:06:23

Ah thank you for sharing that link! Didn't transcribe by hand, just sent stdout to a file and tried to google lens.

http://0x0.st/oC76.txt

There's no >3.10 version in that usr/lib/ folder

Last edited by prayner96 (2023-02-08 19:06:33)

prayner96 · 2023-02-08 19:08:03

That makes a lot more sense, though.

Are you referring to the package update comment I made or the lack of 3.18 file?

seth · 2023-02-08 21:38:44

3.10 makes more sense than 3.18 unless you've a time machine.

I think I might have to downgrade xorg-server?

Do you use nvidia 390xx?

prayner96 · 2023-02-08 21:44:31

No time machine, ask Scimmia though.

Laptop: Ideapad Slim 7i Pro
Intel driver: Intel® Evo Platform Powered by 11th Gen Intel® Core i7-11370H Processor
Integrated Intel® Iris Xᵉ Graphics

No Nvidia.

seth · 2023-02-08 21:47:41

What makes you think you need to downgrade xorg-server?
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

prayner96 · 2023-02-10 13:28:59

seth wrote:

What makes you think you need to downgrade xorg-server?
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

I ran `paru` before rebooting. I was looking for forum posts with the same problem, and a few posts came up such as: https://www.reddit.com/r/archlinux/comm … n_looping/, where comments suggest downgrading Xorg. I was just fishing for quick solutions.

Xorg.0.log: http://0x0.st/HrXB.txt
Xorg.1.log: http://0x0.st/HrXa.txt
Xorg.2.log: http://0x0.st/HrXm.txt

[  1186.280] (II) Module intel: vendor="X.Org Foundation"
[  1186.280] 	compiled for 1.21.1.1, module version = 2.99.917
[  1186.280] 	Module class: X.Org Video Driver
[  1186.280] 	ABI class: X.Org Video Driver, version 25.2
[  1186.280] (II) LoadModule: "modesetting"
[  1186.280] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1186.282] (II) Module modesetting: vendor="X.Org Foundation"
[  1186.282] 	compiled for 1.21.1.3, module version = 1.21.1
[  1186.282] 	Module class: X.Org Video Driver
[  1186.282] 	ABI class: X.Org Video Driver, version 25.2
[  1186.282] (II) LoadModule: "fbdev"
[  1186.282] (WW) Warning, couldn't open module fbdev
[  1186.282] (EE) Failed to load module "fbdev" (module does not exist, 0)

Scimmia · 2023-02-10 13:47:14

You're using xf86-video-intel. How old is your CPU? Unless it's very old, you should be using the modesetting ddx. If you do want to use the Intel ddx, you need to switch to mesa-amber.

Don't know if that's causing your problem, though.

Last edited by Scimmia (2023-02-10 13:47:35)

seth · 2023-02-10 13:47:41

1.log and 2.log are dated, 0.log is from the currently running server:

[   166.351] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 10 12:56:55 2023

And it's running since 75 minutes w/o any relevant errors.

=> Please post the lightdm log (in /var/log) and your system journal,

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Edit: it's Tiger Lake

[   166.358] (--) PCI:*(0@0:2:0) 8086:9a49:17aa:3802 rev 1, Mem @ 0x605c000000/16777216, 0x4000000000/268435456, I/O @ 0x00003000/64, BIOS @ 0x????????/131072

and OP is far better off w/o xf86-video-intel, but likewise don't really see how the SW rasterizer will be a problem w/ qtile

Last edited by seth (2023-02-10 13:52:02)

prayner96 · 2023-02-10 14:08:45

System journal
http://0x0.st/HrX4.txt

Lightdm log
http://0x0.st/HrXt.txt

Will look into the intel driver issue separately.

seth · 2023-02-10 14:14:46

[+72.01s] DEBUG: Greeter requests session qtile
[+72.01s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+72.01s] DEBUG: Terminating login1 session c1
[+72.01s] DEBUG: Session pid=744: Sending SIGTERM
[+72.02s] DEBUG: Greeter closed communication channel
[+72.02s] DEBUG: Session pid=744: Exited with return value 0
[+72.02s] DEBUG: Seat seat0: Session stopped
[+72.02s] DEBUG: Seat seat0: Greeter stopped, running session
[+72.02s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+72.02s] DEBUG: Session pid=783: Running command /etc/lightdm/Xsession qtile start
[+72.02s] DEBUG: Creating shared data directory /var/lib/lightdm-data/baz_morty
[+72.02s] DEBUG: Session pid=783: Logging to .xsession-errors
[+72.21s] DEBUG: Activating VT 7
[+72.21s] DEBUG: Activating login1 session 2
[+72.21s] DEBUG: Seat seat0 changes active session to 
[+72.21s] DEBUG: Seat seat0 changes active session to 2
[+72.21s] DEBUG: Session 2 is already active
[+72.53s] DEBUG: Session pid=783: Exited with return value 1
[+72.53s] DEBUG: Seat seat0: Session stopped

qtile immediately terminates w/ an error code.
If it's not the intel driver, check ~/.xsession-errors (there're no other logs from qtile in the system journal or lightdm log)

And try an openbox session.

Feb 10 14:38:52 bazmorty dbus-daemon[383]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.29' (uid=0 pid=1070 comm="sudo pacman --sync -y -u --")
Feb 10 14:38:52 bazmorty sudo[1070]: baz_morty : TTY=tty4 ; PWD=/home/baz_morty ; USER=root ; COMMAND=/usr/bin/pacman --sync -y -u --
Feb 10 14:45:17 bazmorty dbus-daemon[383]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.30' (uid=0 pid=8683 comm="sudo pacman --remove -l -o -c -l -- python-pep517")
Feb 10 14:45:17 bazmorty sudo[8683]: baz_morty : TTY=tty4 ; PWD=/home/baz_morty ; USER=root ; COMMAND=/usr/bin/pacman --remove -l -o -c -l -- python-pep517
Feb 10 14:45:35 bazmorty dbus-daemon[383]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.31' (uid=0 pid=8695 comm="sudo pacman --remove -- python-pep517")
Feb 10 14:45:35 bazmorty sudo[8695]: baz_morty : TTY=tty4 ; PWD=/home/baz_morty ; USER=root ; COMMAND=/usr/bin/pacman --remove -- python-pep517

What was that about?

Last edited by seth (2023-02-10 14:17:08)

prayner96 · 2023-02-10 14:24:56

Exception in callback Qtile.call_soon.<locals>.f() at /usr/lib/python3.10/site-packages/libqtile/core/manager.py:861
handle: <Handle Qtile.call_soon.<locals>.f() at /usr/lib/python3.10/site-packages/libqtile/core/manager.py:861>
Traceback (most recent call last):
  File "/usr/lib/python3.10/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/lib/python3.10/site-packages/libqtile/core/manager.py", line 862, in f
    func(*args)
  File "/usr/lib/python3.10/site-packages/libqtile/widget/base.py", line 730, in timer_setup
    update_interval = self.tick()
  File "/usr/lib/python3.10/site-packages/libqtile/widget/clock.py", line 79, in tick
    self.update(self.poll())
  File "/usr/lib/python3.10/site-packages/libqtile/widget/base.py", line 697, in update
    old_width = self.layout.width
  File "/usr/lib/python3.10/site-packages/libqtile/drawer.py", line 81, in width
    return self.layout.get_pixel_size()[0]
  File "/usr/lib/python3.10/site-packages/libqtile/pangocffi.py", line 138, in get_pixel_size
    pango.pango_layout_get_pixel_size(self._pointer, width, height)
TypeError: initializer for ctype 'PangoLayout *' must be a cdata pointer, not NoneType

This all started when I added `exec qtile start` in my .xinitrc, which I had never done before. I am not sure why it would be related to the driver, but I need to fix that anyway.

prayner96 · 2023-02-10 14:27:02

:: packages not in the AUR: python-pep517

Paru had this output, which I understand means that I should remove the package as it is no longer useful.

seth · 2023-02-10 14:32:42

The removie it from your xinitrc, but unless you're using https://wiki.archlinux.org/title/Displa … _a_session your xinitrc isn't part of the session process anyway.

TypeError: initializer for ctype 'PangoLayout *' must be a cdata pointer, not NoneType

pacman -Qs 'ttf|otf|font'

prayner96 · 2023-02-10 14:50:38

local/adobe-source-code-pro-fonts 2.038ro+1.058it+1.018var-1
    Monospaced font family for user interface and coding environments
local/cantarell-fonts 1:0.303.1-1
    Humanist sans serif font
local/fontconfig 2:2.14.2-1
    Library for configuring and customizing font access
local/freetype2 2.12.1-1
    Font rasterization library
local/gnu-free-fonts 20120503-8
    A free family of scalable outline fonts
local/libfontenc 1.1.7-1
    X11 font encoding library
local/libxfont2 2.0.6-1
    X11 font rasterisation library
local/libxft 2.3.7-1
    FreeType-based font drawing library for X
local/woff2 1.0.2-4
    Web Open Font Format 2 reference implementation
local/xorg-bdftopcf 1.1.1-1 (xorg xorg-apps)
    Convert X font from Bitmap Distribution Format to Portable Compiled Format
local/xorg-font-util 1.3.3-1 (xorg-fonts xorg)
    X.Org font utilities
local/xorg-fonts-100dpi 1.0.3-8 (xorg)
    X.org 100dpi fonts
local/xorg-fonts-75dpi 1.0.3-8 (xorg)
    X.org 75dpi fonts
local/xorg-fonts-alias-100dpi 1.0.4-1
    X.org font alias files - 100dpi font familiy
local/xorg-fonts-alias-75dpi 1.0.4-1
    X.org font alias files - 75dpi font familiy
local/xorg-fonts-encodings 1.0.6-1 (xorg-fonts xorg)
    X.org font encoding files
local/xorg-mkfontscale 1.2.2-1 (xorg-apps xorg)
    Create an index of scalable font files for X

I did change font for the terminal or something a while back...

seth · 2023-02-10 14:57:12

Check your Qtile settings whether you configured a font that no longer exists

Also

seth wrote:

And try an openbox session.

prayner96 · 2023-02-10 16:19:21

$ openbox-session 
Openbox-Message: Failed to open the display from the DISPLAY environment variable.

Nothing in Qtile config file, I have a default sans font. I attached the .py file:
http://ix.io/4nFn

From Arch wiki: "Qtile writes its log into ~/.local/share/qtile/qtile.log". Attached:
http://0x0.st/Hr8L.txt

seth · 2023-02-10 16:37:16

Openbox-Message: Failed to open the display from the DISPLAY environment variable.

From lightdm, not the console…

qtile has a completely different and obvious error:

2023-02-09 11:04:16,753 ERROR libqtile manager.py:load_config():L112 Configuration error:
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/libqtile/core/manager.py", line 110, in load_config
    self.config.validate()
  File "/usr/lib/python3.10/site-packages/libqtile/confreader.py", line 143, in validate
    raise ConfigError("No such key: %s" % k.key)
libqtile.confreader.ConfigError: No such key:

It doesn't say which line and I've no experience w/ qtile, but

Key([mod], "", lazy.next_layout(), desc="Toggle between layouts"),

looks fishy.

prayner96 · 2023-02-10 20:38:04

looks fishy.

That was it! I don't know how you sniffed that one out.

Just needed a key (e.g., Tab):

Key([mod], "Tab", lazy.next_layout(), desc="Toggle between layouts"),

I looked at the undotree history and I removed "Tab" from that line 20 days ago. I don't understand why it suddenly broke qtile 2 days ago, but I imagine that it's because I added `exec qtile start` to the ~/.xinitrc.

Thanks Seth and Scimmia, that was a good learning experience.

Arch Linux

#1 2023-02-08 17:00:42

[SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#2 2023-02-08 18:26:24

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#3 2023-02-08 18:50:17

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#4 2023-02-08 18:51:39

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#5 2023-02-08 18:53:03

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#6 2023-02-08 19:06:23

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#7 2023-02-08 19:08:03

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#8 2023-02-08 21:38:44

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#9 2023-02-08 21:44:31

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#10 2023-02-08 21:47:41

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#11 2023-02-10 13:28:59

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#12 2023-02-10 13:47:14

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#13 2023-02-10 13:47:41

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#14 2023-02-10 14:08:45

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#15 2023-02-10 14:14:46

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#16 2023-02-10 14:24:56

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#17 2023-02-10 14:27:02

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#18 2023-02-10 14:32:42

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#19 2023-02-10 14:50:38

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#20 2023-02-10 14:57:12

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#21 2023-02-10 16:19:21

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#22 2023-02-10 16:37:16

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

#23 2023-02-10 20:38:04

Re: [SOLVED] LightDM stuck after editing ~/.xinitrc and upgrading packages

Board footer