FS#70124 - lxdm fails to display

Attached to Project: Arch Linux
Opened by Fabrizio del Tin (fdteuniversity.pub) - Monday, 22 March 2021, 07:41 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 24 March 2021, 04:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

With latest update, lxdm fails to display.

Discussion on the forum:
https://bbs.archlinux.org/viewtopic.php?id=264722

There is no sign that lxdm fails.

journalctl -u lxdm-plymouth.service

-- Boot ..... --
Mar 21 09:50:01 phantom systemd[1]: Started LXDE Display Manager.

lxdm shows as running and active with no error, but during boot you only see the boot lines. The graphical environment does not start. Switching console and reswitching to graphical mode, you see all black.

Replacing lxdm with xdm, I could launch lxde succeddfully. However, many apps are not working: lxsession-default-apps crashes. pipewire-pulse seems not working, as pavucontrol shows no audio interface. However, alsa sees the interface (alsamixer).

A user commented that downgrading glib2 (to 2.68.0-2) solves the issue. gobject-introspection-runtime and/or python-gobject seem also involved. I downgraded to 03/01/2021 to make everything work again.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 24 March 2021, 04:21 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#70131 
Comment by Fabrizio del Tin (fdteuniversity.pub) - Monday, 22 March 2021, 07:45 GMT
Please, step up this to Critical.
Comment by cylgalad (cylgalad) - Monday, 22 March 2021, 08:15 GMT
A lot of lxde stuff started segfaulting with glib2-2.68.0-2, the most annoying are lxsession-xdg-autostart and lxappearance, but several other lxsession apps segfaults as well.
Comment by Oscar Alonso (jester400) - Monday, 22 March 2021, 17:10 GMT
I had the same problem I downgraded glib2 and seems to work again.
Comment by Doug Newgard (Scimmia) - Monday, 22 March 2021, 17:49 GMT
downgrading glib2 will cause unresolvable symbols in other libs, though. Partial update.
Comment by Thomas Lübking (luebking) - Tuesday, 23 March 2021, 06:34 GMT
https://bugs.archlinux.org/task/70131
The forum thread linked by Dennis links here and the backtrace over there fits the pattern.

Loading...