bug#59279: bug#59378: [PATCH] gnu: mpv: Add libxpresent input.

[Ludovic Courtès]

Hi,

Martin Marshall  skribis:

> Fixes issue 59279 "MPV does not work on X11".
>
> * gnu/packages/video.scm (mpv)[inputs]: Add libxpresent.

Works for me too.  Applied, thanks!

Ludo’.

bug#59474: Guix Home generated .profile sets XDG_ vars that break GDM+Gnome login on foreign distros

[Liliana Marie Prikler]

Am Montag, dem 21.11.2022 um 22:02 -0800 schrieb Matt Armstrong:
> The first thing I see is that $HOME/.guix-home/seutp-environment is
> modifying various XDG_ variables incorrectly.  It prepends new values
> without honor the variable's default value if it doesn't happen to be
> set already.
This is a known problem with Debian.  Unlike Ubuntu, which relies on
Flatpak and Snaps for its basic operations, Debian doesn't and hence
hasn't set up these variables explicitly.  Note that this isn't unique
to Guix Home or even just Guix.

> For example, if XDG_DATA_DIRS is not set its default value is
> "/usr/local/share/:/usr/share/".
None of these directories exist in Guix System.  Assuming them would be
a fault.  Note that the install script you're meant to use already
initializes these variables since July [1].

> XDG_STATE_HOME is set to a non-standard value.  In the current XDG
> Base Directory Specification it defaults to "$HOME/.local/state", but
> Guix Home sets it to "$HOME/.local/var/lib".
This is a genuine bug with Guix Home.

> XDG_LOG_HOME is a non-standard variable.  The spec suggests that logs
> should go in XDG_STATE_HOME.  Why not a establish a GUIX_LOG_HOME
> variable instead?  (if it ever does become a standard XDG variable,
> its default may not be the same one picked by Guix Home, causing the
> same issue as above).
Another genuine bug with Guix Home, although the variable does predate
our support for XDG_STATE_HOME.  I suggest finding all uses of this
variable in Guix Home and replacing them accordingly.

> Setting XDG_RUNTIME_DIR is not something I would expect Guix Home to
> do -- it is the job of whatever logs the user in.
I'm unsure about that one.

> XDG_CACHE_HOME, XDG_CONFIG_HOME, XDG_DATA_HOME are set to their
> defaults unnecessarily.
Explicit is better than implicit.

Cheers


[1]
http://git.savannah.gnu.org/cgit/guix.git/commit/?id=23aafc800c9e678662766440916449ec5bbce830

bug#57589: Guix hands on GDM with wayland

[Grigory Shepelev]

/tmp dir also won't exist on guix pull and then system reconfigure.

пн, 21 нояб. 2022 г. в 06:50, Grigory Shepelev :

> 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 :
>
>> 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 :
>>
>>> 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 :
>>>
 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 :
 >
 >Oops. I accidentally replied privately to d...@jpoiret.xyz, not
 >mentioning 57...@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@zone51 /tmp$ ls -lah .X11-unix/
 >  total 0
 >  drwxrwxrwt 2 gdm  gdm80 сен  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@zone51 /tmp$ sudo ls -lah /var/lib/gdm
 > total 0
 > drwx-- 1 gdm  gdm   38 авг 26 21:46 .
 > drwxr-xr-

bug#59425: guix can't mount mountpoint path, and the home path.

[bbb ee]

The new tests show guix can mount all path except mountpoint path, and the
home path.
```
dev_1@dev_1 /mnt/recoverData$ mountpoint . ; guix shell --container
coreutils -- echo Elmo
. is a mountpoint
guix shell: error: mount: mount "/mnt/recoverData" on
"/tmp/guix-directory.Fu8aV9//mnt/recoverData": Invalid argument

dev_1@dev_1 /mnt/recoverData/borg_restore$ mountpoint . ; guix shell
--container coreutils -- echo Elmo
. is not a mountpoint
Elmo

dev_1@dev_1 ~$ mountpoint . ; guix shell --container coreutils -- echo Elmo
. is not a mountpoint
guix shell: error: mount: mount "/home/dev_1" on
"/tmp/guix-directory.shXxIg//home/dev_1": Invalid argument

dev_1@dev_1 ~/Downloads$ mountpoint . ; guix shell --container coreutils --
echo Elmo
. is not a mountpoint
Elmo
```

bug#59425: only dir which realpath is in /tmp is mountalbe

[bbb ee]

If I access a unmountable dir from /tmp using symlink, I still can't monnt
it:
```
dev_1@dev_1 /tmp$ ln -s ~ .
dev_1@dev_1 /tmp$ cd dev_1
dev_1@dev_1 /tmp/dev_1$ df .
Filesystem 1K-blocks  Used Available Use% Mounted on
/dev/nvme0n1p7 209921236 180796556  19661028  91% /
dev_1@dev_1 /tmp/dev_1$ guix shell --container coreutils -- echo Elmo
guix shell: error: mount: mount "/home/dev_1" on
"/tmp/guix-directory.X9jW4K//home/dev_1": Invalid argument
dev_1@dev_1 /tmp/dev_1$ realpath /tmp/dev_1
/home/dev_1
```
So not all subdir of /tmp is mountable, only dir which realpath is in /tmp
is mountalbe

bug#58251: Mesa missing patches for Vulkan shared libraries

[Kaelyn via Bug reports for GNU Guix]

I've just created https://issues.guix.gnu.org/59453 with the patch to mesa on 
core-updates to fix the library paths in the Vulkan layer manifests. I split 
the change out from my previous mesa update patch 
(https://issues.guix.gnu.org/58566) as mesa on core-updates has since been 
updated to version 22.2.4.

bug#59179: BUG: &invalid-base32-character (./guix/base32.scm:296:65: ERROR)

[zimoun]

Hi,

On Sat, 12 Nov 2022 at 14:36, Mathieu Othacehe  wrote:

> Fixed by Andrew with: 0760a8511d512ebac388eda0b9e18fd7451ca4b3. Sorry
> for the breakage!

Cool!  But why did it happen?  A hash mismatch should not lead to a
backtrace.


Cheers,
simon

bug#59447: Offload fails with: Throw to key `match-error'

[Mathieu Othacehe]

Hello,

I'm trying to offload an aarch64-linux build on Berlin and it fails this
way:

--8<---cut here---start->8---
process 75612 acquired build slot '/var/guix/offload/10.0.0.9:22/3'
Backtrace:
In ice-9/boot-9.scm:
  1752:10 12 (with-exception-handler _ _ #:unwind? _ # _)
In unknown file:
  11 (apply-smob/0 #)
In ice-9/boot-9.scm:
724:2 10 (call-with-prompt _ _ #)
In ice-9/eval.scm:
619:8  9 (_ #(#(#)))
In guix/ui.scm:
   2263:7  8 (run-guix . _)
  2226:10  7 (run-guix-command _ . _)
In guix/scripts/offload.scm:
   814:22  6 (guix-offload . _)
In ice-9/boot-9.scm:
  1752:10  5 (with-exception-handler _ _ #:unwind? _ # _)
In guix/scripts/offload.scm:
   595:21  4 (process-request _ _ "/gnu/store/vqmlpayiwfagh6s86jwns…" …)
   514:36  3 (choose-build-machine _)
In guix/inferior.scm:
345:2  2 (port->inferior _ _)
327:2  1 (read-repl-response _ _)
In ice-9/boot-9.scm:
  1685:16  0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Throw to key `match-error' with args `("match" "no matching pattern" #)'.
guix build: error: unexpected EOF reading a line
make: *** [Makefile:7087: release] Error 1
--8<---cut here---end--->8---

It can be reproduced 100% by running a `make release` or using this
command: 

--8<---cut here---start->8---
guix deploy -L maintenance/hydra/modules maintenance/hydra/deploy-overdrive1.scm
--8<---cut here---end--->8---

Thanks,

Mathieu

bug#55336: Graphical installer: Selecting a partition scheme always takes me back to the start

[Mathieu Othacehe]

Hey,

> I tried again with w0wi4jvanaddk1zcvwzhlnn7fkfwab82-image.iso in the
> same machine and the issue is gone. I could install the system almost
> flawlesly. So no oportunity to try out the new mechanism :)

Thanks a lot for testing again and reporting :)

Mathieu

bug#53594: no matching pattern #

[Mathieu Othacehe]

Hey Ludo,

> If we cannot reproduce this bug, I propose that we remove it from the
> list of release blockers at .

I haven't had this issue for a long time, seems fair to unblock the
release issue.

Thanks,

Mathieu