| Summary: | gnome-base/gdm-41.0 fails to start | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Deep Red <pkurash> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jetdog330, marco.dr |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=850604 https://bugs.gentoo.org/show_bug.cgi?id=850952 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 850604 | ||
| Bug Blocks: | |||
| Attachments: |
emerge --info
Xorg.0.log |
||
Created attachment 764992 [details]
Xorg.0.log
[ 32.455] (EE)
Fatal server error:
[ 32.455] (EE) xf86OpenConsole: Switching VT failed
[ 32.455] (EE)
[ 32.455] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 32.455] (EE) Please also check the log file at "/var/lib/gdm/.local/share/xorg/Xorg.0.log" for additional information.
[ 32.455] (EE)
[ 32.455] (WW) xf86CloseConsole: KDSETMODE failed: Operation not permitted
[ 32.455] (WW) xf86CloseConsole: VT_SETMODE failed: Operation not permitted
[ 32.459] (EE) Server terminated with error (1). Closing log file.
Hitting the same issue on my desktop. Cannot downgrade to gdm 40 as the ebuilds have been treecleaned. Does gdm-42.0 work? gdm-42 isn't working better. I managed to workaround the issue by changing gdm configuration to start using X server instead of Wayland by default. I tried changing it back and it appeared to work fine but just once. I couldn't spend more time on this yet so I left it to start using X. FTR, it looks like https://bugs.gentoo.org/show_bug.cgi?id=613222 except I remember gdm-40 was working fine. I wonder if this is https://gitlab.gnome.org/GNOME/mutter/-/issues/2210 Can you try putting 'MUTTER_DEBUG_USE_KMS_MODIFIERS=0' to /etc/environment and testing that? Or try applying this patch? https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2359.patch got hit by this on stable gnome system (amd64) after recent updates, on intel GPU. laptop does have nvidia card (soldered) but it's as disabled as it can be. logs clearly indicate stack using intel gpu. applying https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2359.patch does not help. I switched gdm to X11 meanwhile as I need it operational, that works. funny that starting gdm with x11 then re-enabling wayland works fine. Will be able to post more logs later. there was some dbus voodoo magic printed too: Name "org.freedesktop.systemd1" does not exist which leads to MANY topics of failed gdm startup, idk if it's relevant. I may have some helpful news to some here, without having to disable wayland.
The other day I manually masked every package update individually before my gdm broke, and I think I found a possible "instigator":
Add this to /etc/portage/package.mask:
>=media-sound/pulseaudio-15.0-r3
I've confirmed that pulseaudio-15.0-r2 does not have this issue. It fixes gdm from getting stuck at a black screen on startup, on 6 independent Gentoo installs I've tested, with varying GPUs:
-Intel
-NVidia
-Virtualbox VMSVGA
No idea why this worked so predictably for me, but it does!
(In reply to Yuri Sevatz from comment #9) > I may have some helpful news to some here, without having to disable wayland. > > The other day I manually masked every package update individually before my > gdm broke, and I think I found a possible "instigator": > > Add this to /etc/portage/package.mask: > > >=media-sound/pulseaudio-15.0-r3 > > I've confirmed that pulseaudio-15.0-r2 does not have this issue. It fixes > gdm from getting stuck at a black screen on startup, on 6 independent Gentoo > installs I've tested, with varying GPUs: > > -Intel > -NVidia > -Virtualbox VMSVGA > > No idea why this worked so predictably for me, but it does! surprisingly that also fixes the problem for me in one of the systems hitting this issue :/ But I guess it is a different bug than original one as I think -r3 got introduced later The good news are that updating to pulseaudio-16.0 solves it, maybe you could try too This is interesting as the only change between r2 and r3 is in pulseaudio bluetooth module (it would link with libgstreamer, libgstbase and libgstapp) assuming you do not have USE aptx or ldac, which are just gstreamer plugins. Is this worth looking into? I do not think I know how pulseaudio-16.0 fixes gnome. I did just try updating to media-sound/pulseaudio-16. GDM does not freeze with that installed out of the box. However... - There is no audio device enabled. - If i enable an audio device via changing `autospawn = no` -> `autospawn = yes` in /etc/pulse/client.conf, and then reboot, GDM gets stuck the same way it used to with media-sound/pulseaudio-16. The plot thickens! ;) Correction: - - If i enable an audio device via changing `autospawn = no` -> `autospawn = yes` in /etc/pulse/client.conf, and then reboot, GDM gets stuck the same way it used to with media-sound/pulseaudio-16. + - If i enable an audio device via changing `autospawn = no` -> `autospawn = yes` in /etc/pulse/client.conf, and then reboot, GDM gets stuck the same way it used to with media-sound/pulseaudio-**15**. (In reply to Yuri Sevatz from comment #13) > I did just try updating to media-sound/pulseaudio-16. GDM does not freeze > with that installed out of the box. > > However... > > - There is no audio device enabled. > - If i enable an audio device via changing `autospawn = no` -> `autospawn = > yes` in /etc/pulse/client.conf, and then reboot, GDM gets stuck the same way > it used to with media-sound/pulseaudio-16. > > The plot thickens! ;) If you enable the units with: systemctl --global enable pulseaudio.service pulseaudio.socket It will work properly (it is suggested in the elog messages too) (In reply to Pacho Ramos from comment #15) > If you enable the units with: > systemctl --global enable pulseaudio.service pulseaudio.socket > > It will work properly (it is suggested in the elog messages too) That did the trick! Thanks! Is there anything left to do here? Hello, sorry for abandoning this thread After quite a long time I managed to fix the issue after removing fbdev and radeonsi from VIDEO_CARDS section in /etc/portage/make.conf |
Created attachment 764536 [details] emerge --info After recent kernel update I decided to restart the computer. It was unable to load gdm (at version 41.0). The text from journalctl which seems to cause of the error: Feb 07 18:09:33 Sabayon-pc gnome-session[1345]: gnome-session-binary[1345]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Feb 07 18:09:33 Sabayon-pc gnome-session[1345]: gnome-session-binary[1345]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Feb 07 18:09:33 Sabayon-pc gnome-session-binary[1345]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Feb 07 18:09:33 Sabayon-pc gnome-session-binary[1345]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed P. S. Attached emerge --info to the post.