Package: guix;
Reported by: Grigory Shepelev <shegeley <at> gmail.com>
Date: Mon, 5 Sep 2022 05:38:01 UTC
Severity: normal
Done: Bruno Victal <mirai <at> makinata.eu>
Bug is archived. No further changes may be made.
Message #17 received at 57589 <at> debbugs.gnu.org (full text, mbox):
From: Grigory Shepelev <shegeley <at> gmail.com> To: 57589 <at> debbugs.gnu.org Subject: Re: bug#57589: Guix hands on GDM with wayland Date: Tue, 6 Sep 2022 14:05:50 +0300
[Message part 1 (text/plain, inline)]
Creating new user didn't helped. I created new user (did this Guix way, via adding to config and reconfiguring the system) and logged it as a new user. Still X11 system displays with `xrandr`, and `echo $XDG_SESSION_TYPE`. I don't think there is a need to try moving all home files, creating new user should be enough to test provided option. Although I noticed a gear icon below in the right of the gdm screen when logging in as a default user (saw that in Ubuntu) with options "GNOME" or "GNOME on Xorg". Trying to login in "GNOME" (Wayland supposedly) gives a black screen for ~2s. After couple attempts logged back into "GNOME on Xorg". Attached logs again. They says something about DBUS. Any ideas? --- (gsd-keyboard:5189): dbind-WARNING **: 13:35:36.273: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files (gsd-xsettings:5219): dbind-WARNING **: 13:35:36.476: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files GNOME Shell-Message: 13:35:36.777: Registering session with GDM The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Unsupported maximum keycode 708, clipping. > X11 cannot support keycodes above 255. Errors from xkbcomp are not fatal to the X server (gnome-shell:5099): mutter-WARNING **: 13:36:02.454: Connection to xwayland lost --- On 05.09.2022 20:55, Grigory Shepelev wrote: > Had some info from Guix Matrix channel: > > GDM does wayland too with the option set to #t. I was able to get it > to work going back from sddm, but I had to remove the home folder and > recreate it from scratch, since gnome session was crashing on login. I > had no problem starting gnome on a new account so i figured something > was hanging around that cause a problem even after deleting all caches > and configs etc. > > By “home folder” I mean my user’s directory /home/use > > https://matrix.to/#/!jivGmMiiorFwdgwaxc:matrix.org/$W4HJQCzv8G0aHM3_PAFrtUaj6Q3aS18vMZCwlMch71I?via=matrix.org&via=hummingbard.com&via=privacytools.io > <https://matrix.to/#/!jivGmMiiorFwdgwaxc:matrix.org/$W4HJQCzv8G0aHM3_PAFrtUaj6Q3aS18vMZCwlMch71I?via=matrix.org&via=hummingbard.com&via=privacytools.io> > > > Most likely will try for new user tomorrow > > пн, 5 сент. 2022 г., 16:24 Grigory Shepelev <shegeley <at> gmail.com>: > > Oops. I accidentally replied privately to dev <at> jpoiret.xyz, not > mentioning 57589 <at> debbugs.gnu.org. I hope the history can be recovered > from this message. > > Josselin recommended to > > - check permissions on /tmp/.X11-unix/ (gdm user should have r+w > permissions) > > shegeley <at> zone51 /tmp$ ls -lah .X11-unix/ > total 0 > drwxrwxrwt 2 gdm gdm 80 сен 5 16:12 ./ > drwxrwxrwt 6 root root 160 сен 5 16:16 ../ > srwxrwxrwx 1 shegeley users 0 сен 5 16:12 X1 > srwxr-xr-x 1 gdm gdm 0 сен 5 16:12 X1024 > > - check /var/lib/gdm/, doesn't have the proper permissions > > Hm. That's really strange. For some reason /var/lib/gdm had > "transmission" as user-group. I assure you that I didn't > explicitly > do any "dirty stuff" like that permission changing in my config > > > shegeley <at> zone51 /tmp$ sudo ls -lah /var/lib/gdm > total 0 > drwx------ 1 gdm gdm 38 авг 26 21:46 . > drwxr-xr-x 1 root root 248 авг 28 18:37 .. > drwxr-xr-x 1 973 transmission 62 авг 26 21:46 .cache > drwx------ 1 973 transmission 44 авг 26 21:46 .config > drwx------ 1 973 transmission 10 авг 26 21:46 .local > shegeley <at> zone51 /tmp$ sudo chown -R gdm:gdm /var/lib/gdm > shegeley <at> zone51 /tmp$ sudo ls -lah /var/lib/gdm > total 0 > drwx------ 1 gdm gdm 38 авг 26 21:46 . > drwxr-xr-x 1 root root 248 авг 28 18:37 .. > drwxr-xr-x 1 gdm gdm 62 авг 26 21:46 .cache > drwx------ 1 gdm gdm 44 авг 26 21:46 .config > drwx------ 1 gdm gdm 10 авг 26 21:46 .local > > > After changing it was able to launch into GDM, but with X11 as display > manager :( Attached new logs. > > > On 05.09.2022 10:23, Josselin Poiret wrote: > > Hi again, > > > > Grigory Shepelev<shegeley <at> gmail.com> writes: > > > >> My config is heavily depends on it's directory (passing it with > >> --load-path). I can (and will) publish it all (I've been > planning to do > >> so) but I'd like to polish few parts. > >> > >> Any exact part are you looking for in config? I attached my > system-wide > >> services. > > I asked for that partly because it helps identifying common > errors, and > > it's always better for people debugging to have access to all the > > information, and partly because I couldn't see anything that > could help > > in the logs. However, it seems mutter can't write into > /tmp/.X11-unix/, > > could you check that the gdm user has the permission to write > there? It > > should be rwxrwxrwx. I don't see any modification in your config > that > > would prevent the x11-socket-directory-service from > %desktop-services to > > run. Also, it seems that /var/lib/gdm/ doesn't have the proper > > permissions, maybe because of [1]. You can try `sudo chown -R > gdm:gdm > > /var/lib/gdm` to fix that. > > > > [1]https://issues.guix.gnu.org/36508 > > > > HTH. >
[greeter-13:26-06-09-2022.log (text/x-log, attachment)]
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.