GNU bug report logs - #57589
Guix hangs on GDM with Wayland

Previous Next

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.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 57589 in the body.
You can then email your comments to 57589 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Mon, 05 Sep 2022 05:38:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Grigory Shepelev <shegeley <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 05 Sep 2022 05:38:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Grigory Shepelev <shegeley <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Guix hands on GDM with wayland
Date: Mon, 5 Sep 2022 08:37:21 +0300
[Message part 1 (text/plain, inline)]
Using Guix and Guix Home, having troubles starting GDM with (wayland? 
#t) as described. On putting this option in config and reconfiguring 
laptop just hangs on login on "default" graphical (alt+ctrl+f7) tty, 
black screen nothing happens. (excuse me for probably technically 
incorrect terms)

Attached all logs (from /var/log/gdm). A lot of errors. Some of them are

- dbus-daemon[861]: Cannot setup inotify for 
'/var/lib/gdm/.local/share/dbus-1/services'; error 'Permission denied'

- gnome-session-binary[862]: WARNING: Unable to find required component 
'org.gnome.Shell'

- gnome-session-binary[862]: WARNING: GsmSessionSave: Failed to create 
directory /var/lib/gdm/.config/gnome-session/saved-session: Permission 
denied

- gnome-session-binary[862]: WARNING: Unable to find required component 
'org.gnome.SettingsDaemon.Rfkill'

- Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.*: 
The name org.freedesktop.systemd1 was not provided by any .service files

- (gsd-a11y-settings:910): GLib-GIO-WARNING **: 21:58:01.344: Error 
releasing name org.gnome.SettingsDaemon.A11ySettings: The connection is 
closed
[greeter.log.4 (text/plain, attachment)]
[greeter.log.3 (text/plain, attachment)]
[greeter.log.2 (text/plain, attachment)]
[greeter.log.1 (text/plain, attachment)]
[greeter.log (text/x-log, attachment)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Mon, 05 Sep 2022 06:01:02 GMT) Full text and rfc822 format available.

Message #8 received at 57589 <at> debbugs.gnu.org (full text, mbox):

From: Josselin Poiret <dev <at> jpoiret.xyz>
To: Grigory Shepelev <shegeley <at> gmail.com>, 57589 <at> debbugs.gnu.org
Subject: Re: bug#57589: Guix hands on GDM with wayland
Date: Mon, 05 Sep 2022 08:00:24 +0200
Hi,

Could you also attach the relevant parts of your config files?

Best,
-- 
Josselin Poiret




Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Mon, 05 Sep 2022 13:25:02 GMT) Full text and rfc822 format available.

Message #11 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: Mon, 5 Sep 2022 16:24:22 +0300
[Message part 1 (text/plain, inline)]
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.log (text/x-log, attachment)]
[greeter.log.1 (text/plain, attachment)]
[greeter.log.2 (text/plain, attachment)]
[greeter.log.3 (text/plain, attachment)]
[greeter.log.4 (text/plain, attachment)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Mon, 05 Sep 2022 17:56:01 GMT) Full text and rfc822 format available.

Message #14 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: Mon, 5 Sep 2022 20:55:17 +0300
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.





Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Tue, 06 Sep 2022 11:06:03 GMT) Full text and rfc822 format available.

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)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Tue, 01 Nov 2022 15:57:02 GMT) Full text and rfc822 format available.

Message #20 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, 1 Nov 2022 15:55:33 +0000
[Message part 1 (text/plain, inline)]
Update. I can log into "Gnome on Xorg", change ownership of /tmp/.X11-unix
to root:gdm, log out, and them login into "Gnome". This will enable
Wayland.

вт, 6 сент. 2022 г. в 11:05, Grigory Shepelev <shegeley <at> gmail.com>:

> 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.
> >
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Mon, 21 Nov 2022 02:45:01 GMT) Full text and rfc822 format available.

Message #23 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: Mon, 21 Nov 2022 02:43:36 +0000
[Message part 1 (text/plain, inline)]
Figured out what was the problem. The /tmp dir. Once I had nonexisting /mnt
dir on Guix boot. So I've added this piece In my file-systems:

(file-system
  (mount-point "/tmp")
  (device "tmp")
  (type "tmpfs")
  (check? #f))

This exact piece was causing a problem. Seems like it's connected to
x11-socket-directory-service from (gnu services desktop). So, maybe the
tmpdir was mounted after GDM boot and override the needed /tmp settings.

вт, 1 нояб. 2022 г. в 15:55, Grigory Shepelev <shegeley <at> gmail.com>:

> Update. I can log into "Gnome on Xorg", change ownership of /tmp/.X11-unix
> to root:gdm, log out, and them login into "Gnome". This will enable
> Wayland.
>
> вт, 6 сент. 2022 г. в 11:05, Grigory Shepelev <shegeley <at> gmail.com>:
>
>> 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.
>> >
>
>
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Mon, 21 Nov 2022 06:51:01 GMT) Full text and rfc822 format available.

Message #26 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: Mon, 21 Nov 2022 06:50:11 +0000
[Message part 1 (text/plain, inline)]
When I log in with "Gnome on xorg" the /tmp directory doesn't exist. When I
log in "Gnome" (+Wayland) it exits.

пн, 21 нояб. 2022 г. в 02:43, Grigory Shepelev <shegeley <at> gmail.com>:

> Figured out what was the problem. The /tmp dir. Once I had nonexisting
> /mnt dir on Guix boot. So I've added this piece In my file-systems:
>
> (file-system
>   (mount-point "/tmp")
>   (device "tmp")
>   (type "tmpfs")
>   (check? #f))
>
> This exact piece was causing a problem. Seems like it's connected to
> x11-socket-directory-service from (gnu services desktop). So, maybe the
> tmpdir was mounted after GDM boot and override the needed /tmp settings.
>
> вт, 1 нояб. 2022 г. в 15:55, Grigory Shepelev <shegeley <at> gmail.com>:
>
>> Update. I can log into "Gnome on Xorg", change ownership of
>> /tmp/.X11-unix to root:gdm, log out, and them login into "Gnome". This will
>> enable Wayland.
>>
>> вт, 6 сент. 2022 г. в 11:05, Grigory Shepelev <shegeley <at> gmail.com>:
>>
>>> 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.
>>> >
>>
>>
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Tue, 22 Nov 2022 01:37:01 GMT) Full text and rfc822 format available.

Message #29 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, 22 Nov 2022 01:35:26 +0000
[Message part 1 (text/plain, inline)]
/tmp dir also won't exist on guix pull and then system reconfigure.

пн, 21 нояб. 2022 г. в 06:50, Grigory Shepelev <shegeley <at> gmail.com>:

> When I log in with "Gnome on xorg" the /tmp directory doesn't exist. When
> I log in "Gnome" (+Wayland) it exits.
>
> пн, 21 нояб. 2022 г. в 02:43, Grigory Shepelev <shegeley <at> gmail.com>:
>
>> Figured out what was the problem. The /tmp dir. Once I had nonexisting
>> /mnt dir on Guix boot. So I've added this piece In my file-systems:
>>
>> (file-system
>>   (mount-point "/tmp")
>>   (device "tmp")
>>   (type "tmpfs")
>>   (check? #f))
>>
>> This exact piece was causing a problem. Seems like it's connected to
>> x11-socket-directory-service from (gnu services desktop). So, maybe the
>> tmpdir was mounted after GDM boot and override the needed /tmp settings.
>>
>> вт, 1 нояб. 2022 г. в 15:55, Grigory Shepelev <shegeley <at> gmail.com>:
>>
>>> Update. I can log into "Gnome on Xorg", change ownership of
>>> /tmp/.X11-unix to root:gdm, log out, and them login into "Gnome". This will
>>> enable Wayland.
>>>
>>> вт, 6 сент. 2022 г. в 11:05, Grigory Shepelev <shegeley <at> gmail.com>:
>>>
>>>> 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.
>>>> >
>>>
>>>
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Thu, 24 Nov 2022 12:29:02 GMT) Full text and rfc822 format available.

Message #32 received at 57589 <at> debbugs.gnu.org (full text, mbox):

From: mirai <mirai <at> makinata.eu>
To: 57589 <at> debbugs.gnu.org
Subject: Guix hands on GDM with wayland
Date: Thu, 24 Nov 2022 12:28:37 +0000
I believe I'm in a similar situation here.

Like Grigory, I also have my /tmp directory mounted as tmpfs:
```
(file-system
  (mount-point "/tmp")
  (device "none")
  (type "tmpfs")
  (flags '(no-dev no-suid no-atime))
  (check? #f))
```

But GDM launches in X11 mode as seen with 'loginctl show-session'
```
$ loginctl list-sessions 
SESSION  UID USER SEAT  TTY 
     c2  977 gdm  seat0 tty7
     c3 1000 x
$ loginctl show-session c2
Id=c2
User=977
Name=gdm
Timestamp=Wed 2022-11-23 17:02:57 WET
TimestampMonotonic=12113524
VTNr=7
Seat=seat0
TTY=tty7
Remote=no
Service=gdm-launch-environment
Leader=548
Audit=4294967295
Type=x11
Class=greeter
Active=yes
State=active
IdleHint=yes
IdleSinceHint=1669223280659646
IdleSinceHintMonotonic=314277878
LockedHint=no
```

and the DE/WM selection list does not contain any 'Wayland' option.

For reference, GDM was configured with:
```
(modify-services %desktop-services
          (gdm-service-type config => (gdm-configuration
                                       (inherit config)
                                       (wayland? #t)
                                       (auto-suspend? #f))))
```




Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Thu, 01 Dec 2022 13:36:01 GMT) Full text and rfc822 format available.

Message #35 received at 57589 <at> debbugs.gnu.org (full text, mbox):

From: mirai <mirai <at> makinata.eu>
To: 57589 <at> debbugs.gnu.org
Cc: shegeley <at> gmail.com
Subject: Guix hands on GDM with wayland
Date: Thu, 1 Dec 2022 13:35:10 +0000
Grigory Shepelev wrote on 21 Nov 03:43 +0100:

> Figured out what was the problem. The /tmp dir. Once I had nonexisting /mnt
> dir on Guix boot. So I've added this piece In my file-systems:
> 
> (file-system
>   (mount-point "/tmp")
>   (device "tmp")
>   (type "tmpfs")
>   (check? #f))
> 
> This exact piece was causing a problem. Seems like it's connected to
> x11-socket-directory-service from (gnu services desktop). So, maybe the
> tmpdir was mounted after GDM boot and override the needed /tmp settings.

This might not be the case (like you, I'm also
using tmpfs for /tmp as mentioned in https://issues.guix.gnu.org/57589#9).
I've wrote a small guix system test for testing out this tmpfs theory at
https://issues.guix.gnu.org/59739 and so far, all the tests pass, with or without
/tmp as tmpfs mount.

Can you share your 'loginctl show-user gdm' and
'loginctl show-session <GDM session here>' output (before logging in with gdm, you
can do this via ssh or switch to another tty) and your system specs/GPU make?






Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Mon, 12 Dec 2022 03:57:01 GMT) Full text and rfc822 format available.

Message #38 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: Mon, 12 Dec 2022 03:56:10 +0000
[Message part 1 (text/plain, inline)]
> Like Grigory, I also have my /tmp directory mounted as tmpfs
As I've written I am not having this anymore. Deleting exactly this part
helped me to be able to launch Gnome on Wayland properly.

> Can you share your 'loginctl show-user gdm' and 'loginctl show-session
<GDM session here>' output (before logging in with gdm, you can do this via
ssh or switch to another tty) and your system specs/GPU make?

Sure. The machine is a Thinkpad T480, i5-8350U, UHD Graphics 620 (KBL GT2).
```
shegeley <at> zone51 ~$ sudo loginctl list-sessions
Password:
SESSION  UID USER     SEAT  TTY
     c2 1002 shegeley seat0 tty8
1 sessions listed.
shegeley <at> zone51 ~$ sudo loginctl show-user gdm
shegeley <at> zone51 ~$ loginctl show-session c2
Id=c2
User=1002
Name=shegeley
Timestamp=Thu 2022-12-01 12:30:54 +06
TimestampMonotonic=30296910
VTNr=8
Seat=seat0
TTY=tty8
Remote=no
Service=gdm-password
Leader=1752
Audit=4294967295
Type=wayland
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=1669886111929701
IdleSinceHintMonotonic=9888259624
LockedHint=no
```

> I've wrote a small guix system test for testing out this tmpfs theory at
https://issues.guix.gnu.org/59739 and so far, all the tests pass, with or
without /tmp as tmpfs mount.

Those tests are good, but I guess the problem is kinda "deeper". I am not
sure but my /tmp dir disappears time-to-time and I don't know the exact
conditions for disappearing for now. Seems like it's a guix pull but it
also sometimes just gone even though I didn't pull. I recommend you to try
deleting this tmpfs part completely and see the result yourself.

вт, 22 нояб. 2022 г. в 01:35, Grigory Shepelev <shegeley <at> gmail.com>:

> /tmp dir also won't exist on guix pull and then system reconfigure.
>
> пн, 21 нояб. 2022 г. в 06:50, Grigory Shepelev <shegeley <at> gmail.com>:
>
>> When I log in with "Gnome on xorg" the /tmp directory doesn't exist. When
>> I log in "Gnome" (+Wayland) it exits.
>>
>> пн, 21 нояб. 2022 г. в 02:43, Grigory Shepelev <shegeley <at> gmail.com>:
>>
>>> Figured out what was the problem. The /tmp dir. Once I had nonexisting
>>> /mnt dir on Guix boot. So I've added this piece In my file-systems:
>>>
>>> (file-system
>>>   (mount-point "/tmp")
>>>   (device "tmp")
>>>   (type "tmpfs")
>>>   (check? #f))
>>>
>>> This exact piece was causing a problem. Seems like it's connected to
>>> x11-socket-directory-service from (gnu services desktop). So, maybe the
>>> tmpdir was mounted after GDM boot and override the needed /tmp settings.
>>>
>>> вт, 1 нояб. 2022 г. в 15:55, Grigory Shepelev <shegeley <at> gmail.com>:
>>>
>>>> Update. I can log into "Gnome on Xorg", change ownership of
>>>> /tmp/.X11-unix to root:gdm, log out, and them login into "Gnome". This will
>>>> enable Wayland.
>>>>
>>>> вт, 6 сент. 2022 г. в 11:05, Grigory Shepelev <shegeley <at> gmail.com>:
>>>>
>>>>> 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.
>>>>> >
>>>>
>>>>
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Wed, 04 Jan 2023 03:09:02 GMT) Full text and rfc822 format available.

Message #41 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: Wed, 4 Jan 2023 03:08:04 +0000
I've figured out the problem with disappearing /tmp dir was caused by 
another package (steam, from nonguix*) due to how it's packed (it 
exposes /tmp dir as a guix contaner, using fhs deep in it's guts). So 
disappearing /tmp dir was only caused by this one.

For now the only problem that is the core of this bug report is: if you 
add /tmp file-system to yours system file-systems you won't be able to 
chose "Gnome on Wayland". And as I wrote, I suppose that's due to how 
x11-socket-directory-service from (gnu services desktop) works. It seems 
like your system's /tmp file-system will be created AFTER this 
x11-socket-directory-service will create it's own /tmp. It's mounted "on 
top".

---

* I don't know if it's appropriate to mention it here, I don't encourage 
anyone to use nonfree software.





Changed bug title to 'Guix hangs on GDM with Wayland' from 'Guix hands on GDM with wayland' Request was from Felix Lechner <felix.lechner <at> lease-up.com> to control <at> debbugs.gnu.org. (Fri, 06 Jan 2023 17:13:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-guix <at> gnu.org:
bug#57589; Package guix. (Thu, 12 Jan 2023 15:56:02 GMT) Full text and rfc822 format available.

Message #46 received at 57589 <at> debbugs.gnu.org (full text, mbox):

From: Bruno Victal <mirai <at> makinata.eu>
To: 57589 <at> debbugs.gnu.org
Subject: Guix hangs on GDM with Wayland
Date: Thu, 12 Jan 2023 15:55:21 +0000
I found out what's missing from your "/tmp" filesystem entry: you need to set the 'needed-for-boot?' field to #t.

I don't think the above counts as a user error, rather it is a workaround since x11-socket-directory-service relies on activation-service-type which does not take 'file-systems' service into account.


Cheers,
Bruno




Reply sent to Bruno Victal <mirai <at> makinata.eu>:
You have taken responsibility. (Wed, 22 Mar 2023 00:52:01 GMT) Full text and rfc822 format available.

Notification sent to Grigory Shepelev <shegeley <at> gmail.com>:
bug acknowledged by developer. (Wed, 22 Mar 2023 00:52:01 GMT) Full text and rfc822 format available.

Message #51 received at 57589-done <at> debbugs.gnu.org (full text, mbox):

From: Bruno Victal <mirai <at> makinata.eu>
To: 57589-done <at> debbugs.gnu.org
Cc: shegeley <shegeley <at> gmail.com>
Subject: close
Date: Wed, 22 Mar 2023 00:51:43 +0000
Fixed in b7506eb334d1cfceca78682879c69edf525c8ccd. (via #60756)




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 19 Apr 2023 11:24:22 GMT) Full text and rfc822 format available.

This bug report was last modified 1 year and 7 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.