FS#72765 - Failed to start GNOME Display Manager.

Attached to Project: Arch Linux
Opened by Sergiu (physicalit) - Tuesday, 16 November 2021, 13:00 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 27 February 2022, 10:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
I have a system (nvidia gpu) with minimal packages on it, I use it for docker, but I also have a Desktop environment, gnome on it and that is it, no costume modification or anything..
After the update I did a few days ago gdm service won't start, someone fucked it up.. I am very curious why this is not posted on the main page of the community cause if I have this issue on a very basic system.. most likely all gnome users have it..


Additional info:
* package version(s) GDM 41.0
* config and/or log files etc. Standard, nothing was modified.
* link to upstream bug report, if any, not found.

Steps to reproduce:
Start the computer and the system will fail to start gdm.

× gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
Active: failed (Result: core-dump) since Tue 2021-11-16 14:50:25 EET; 5s ago
Process: 14308 ExecStart=/usr/bin/gdm (code=dumped, signal=SEGV)
Main PID: 14308 (code=dumped, signal=SEGV)
CPU: 27ms

Nov 16 14:50:25 node1 systemd[1]: gdm.service: Failed with result 'core-dump'.
Nov 16 14:50:25 node1 systemd[1]: gdm.service: Scheduled restart job, restart counter is at 5.
Nov 16 14:50:25 node1 systemd[1]: Stopped GNOME Display Manager.
Nov 16 14:50:25 node1 systemd[1]: gdm.service: Start request repeated too quickly.
Nov 16 14:50:25 node1 systemd[1]: gdm.service: Failed with result 'core-dump'.
Nov 16 14:50:25 node1 systemd[1]: Failed to start GNOME Display Manager.
Nov 16 14:50:25 node1 systemd[1]: gdm.service: Triggering OnFailure= dependencies.
Nov 16 14:50:25 node1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service no


node1 :: /home/giumbai » gdm
[1] 22020 segmentation fault (core dumped) gdm

The error is so general.. nothing I can investigate.. no other service is down or affected.. the system works normally.. only issue I can not boot in the graphical mode.
Please do not push updated that are not tested as stable!!!!!!!!!!!!!!!!!!! I feel like I should not say this.. but, please stop pushing bugs!!!!!
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 27 February 2022, 10:47 GMT
Reason for closing:  Upstream
Additional comments about closing:  This isn't an archlinux issue and is an issue with gdm and nvidia drivers
Comment by Antonio Rojas (arojas) - Tuesday, 16 November 2021, 13:38 GMT
Please refrain from using the bug tracker to rant. "most likely all gnome users have it" is obviously false, as this is the first bug report about this a week after the release. If you want to help, start by posting a proper backtrace.
Comment by Sergiu (physicalit) - Tuesday, 16 November 2021, 14:18 GMT
So, apparently everything above Nvidia 470 driver version kills gdm. Also driver 470 version is not compatible with gdm 4.1.. so both packages need to be downgraded.
Comment by Doug Newgard (Scimmia) - Tuesday, 16 November 2021, 14:34 GMT
What GPU? Nvidia just dropped support for some after 470.
Comment by Sergiu (physicalit) - Tuesday, 16 November 2021, 15:04 GMT
So, it worked earlier cause actually sued nouveau instead of the proprietary driver. No matter the version, I think gdm does not speaks with the Nvidia api. I have attached the full debug log of gdm.
I could not find any single reason in the log why it fails, there are some references to this bug https://bugzilla.redhat.com/show_bug.cgi?id=1924079, but I don't think it crashes because of that.

I think that all users that use the nvidia, nvidia-lts or the manual install of the nvidia driver from their website are affected.
Comment by Sergiu (physicalit) - Tuesday, 16 November 2021, 15:08 GMT
I also tested to see if I can use the GPU from the pytorch frameworks and works fine, so other processes can access the gpu only gdm can't and also it doesn't gives any error in the log.. it just says core dumped.. with nothing more to go on. I enabled debug mode, as seen in the above attachment.
Comment by Alireza Zare (zare) - Monday, 29 November 2021, 11:38 GMT
Have you found a workaround to this bug?
Comment by Sergiu (physicalit) - Monday, 29 November 2021, 14:40 GMT
Unfortunately no, I am just doing the updates hoping one of them will fix this issue.. They really broke it this time around..
Comment by Jan Alexander Steffens (heftig) - Monday, 29 November 2021, 15:18 GMT
Has this improved with mutter 41.1+r20 ?
Comment by Alireza Zare (zare) - Tuesday, 30 November 2021, 08:32 GMT
Not really!
Comment by Sergiu (physicalit) - Tuesday, 30 November 2021, 08:43 GMT
The only working workarond I found was to install nouveau driver and adding the the moduls to mkinitcpio.conf
So, basically not using the proprietary driver anymore.
I would prefer using the proprietary driver, but for now I need to do some work on my machine uaing the Deaktop Env.
Comment by x (aatdark) - Thursday, 09 December 2021, 23:30 GMT
I was running into the same issue but i'm running nouveau.
I identified my problem as that i had nvidia-utils installed (not sure why).
This created an blacklist entry for nouveau in /usr/lib/modprobe.d/nvidia-utils.conf
Note that the nvidia proprietary drive is not installed / loaded.

after commenting out this blacklist entry my system boots fine again. Maybe this helps other people.
Comment by Sergiu (physicalit) - Thursday, 09 December 2021, 23:47 GMT
As I said, nouveau works. Your issue has nothing to do with the issue mentioned above. Is normal for nvidia-utils to put the nuveau module on blacklist. You can not run bowth proprietary driver and open source at the same time..
Comment by Magnus (DeArchDev) - Sunday, 09 January 2022, 14:32 GMT
This issue is a really old issue(which, according to this https://www.reddit.com/r/archlinux/comments/33i85y/gdm_and_nvidia_problem/ also existed 7 years ago). It's probably a upstream bug which still hasn't been solved. You might want to create a new arch forum page instead of a issue, which might help solve your issue

Loading...