Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#68653 - [linux] gdm doesn't start after boot
Attached to Project:
Arch Linux
Opened by Yaroslav Nikitenko (ynikitenko) - Tuesday, 17 November 2020, 18:25 GMT
Last edited by Toolybird (Toolybird) - Sunday, 28 May 2023, 06:50 GMT
Opened by Yaroslav Nikitenko (ynikitenko) - Tuesday, 17 November 2020, 18:25 GMT
Last edited by Toolybird (Toolybird) - Sunday, 28 May 2023, 06:50 GMT
|
DetailsDescription: When starting the system the cursor just blinks and gdm doesn't start.
Switching to other tty session and coming back starts gdm. This was described here (https://bbs.archlinux.org/viewtopic.php?id=256522), and here it is similar, with similar logs, but a bit different (https://www.linux.org.ru/forum/desktop/15747717), and I had the same problem. It was fixed by booting 'linux-lts' instead of 'linux'. Please write what information I shall also provide if you plan to investigate. I have more or less same logs as on the links. I use gdm with Gnome. Before switching the kernel, I commented out WaylandEnable=false in '/etc/gdm/custom.conf', but that didn't help. Additional info: * package version(s) linux 5.9.8.arch1-1 fails. linux-lts 5.4.77-1 works. * config and/or log files etc. * link to upstream bug report, if any I'm using an Acer Swift 5 laptop with Intel processor with integrated graphics. The drivers version is mesa-20.2.2-2. Steps to reproduce: Turn on laptop, boot your system. |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 28 May 2023, 06:50 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.
Sunday, 28 May 2023, 06:50 GMT
Reason for closing: No response
Additional comments about closing: Plus it's old and stale. If still an issue, please report upstream.

Maybe this patch from Ubuntu might help with the TTY issue ...

I'm experiencing the same issue. I'm using the nvidia proprietary driver and there seems to be a race condition with gdm trying to start X before /dev/dri/card0 becomes ready. I solved it by adapting this solution for gdm: https://bbs.archlinux.org/viewtopic.php?pid=1351600#p1351600

I cannot reproduce the issue. Is it still valid for you?