Created attachment 902435 [details] GDM error log I did a full reinstall which solved a lot of problems, but on gdm I am now getting a black screen with flashing cursor. When on this screen I can go into another TTY and login as the user, then launch gnome with: MOZ_ENABLE_WAYLAND=1 QT_QPA_PLATFORM=wayland XDG_SESSION_TYPE=wayland dbus-run-session gnome-session Gnome starts flawlessly with everything working. Hardware: 7950x 128GB RAM AMD iGPU (7950x) primary - display connected. 2080ti nvidia dGPU - no display connected. Software: ~amd64, GCC 13. Error log attached.
Comment on attachment 902435 [details] GDM error log Please do not use "rich text" when attaching a log snippet.
From the attachment: > Sep 08 17:54:14 gentoo systemd[1]: Starting GNOME Display Manager... > Sep 08 17:54:14 gentoo systemd[1]: Started GNOME Display Manager. > Sep 08 17:54:15 gentoo gdm[1022]: GLib: g_str_has_prefix: assertion 'str != NULL' failed > Sep 08 17:54:15 gentoo gdm[1022]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed > Sep 08 17:54:15 gentoo gdm-launch-environment][1059]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-1059) opened. > Sep 08 17:54:17 gentoo gdm[1022]: Gdm: GdmDisplay: Session never registered, failing > Sep 08 17:54:17 gentoo gdm[1022]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed > Sep 08 17:54:17 gentoo gdm[1022]: Gdm: Child process -1090 was already dead.
Sorry! I just tossed it into gnomes text editor and saved it. I'll use nano or something in the future. I'm in the process of reinstalling again (third time is the charm, right?). Maybe that will fix it? But uh, I've had nothing but problems with gentoos gdm implementation for like the last year or two. I generally use gentoo for a couple months and take a long break. I have never been able to get wayland to work with gnomes gdm when a nvidia card is involved, for example. I could tinker around with the rules file and sometimes get it to work, but it always broke again on the next update (iirc). The actual gnome software is solid though, its just gdm that gives me headaches.
as an update, a fresh install does fix it. It promptly breaks and goes back to black screen + cursor after: 1) installing cuda 2) enabling pipewire/wireplumber and disabling pulseaudio 3) installing steam
I have many of the same gdm issues. I saw in the logs that when gdm gave up on Wayland the error /usr/libexec/gdm-wayland-sessions has no schemas
The GDM schema is available in /usr/share/gdm. I also made a version that could be compiled, and it now shows in gsettings as well, but I still get the same error. I switched to lightdm, which is working fine.
*** Bug 943702 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=766ec225b86eee6352407d13d850a70333a3aea7 commit 766ec225b86eee6352407d13d850a70333a3aea7 Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2024-12-01 11:16:00 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2024-12-01 11:16:00 +0000 gnome-base/gdm: Migrate away from gnome2.eclass and ensure schemas are updated Follow the model of gnome-shell ebuilds Bug: https://bugs.gentoo.org/939358 Signed-off-by: Pacho Ramos <pacho@gentoo.org> gnome-base/gdm/gdm-46.2-r2.ebuild | 220 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 220 insertions(+)
