Le mercredi 20 mai 2026 à 23:29 +0200, Denis 'GNUtoo' Carikli a écrit : > On Tue, 19 May 2026 03:09:34 +0200 > Denis 'GNUtoo' Carikli <[email protected]> wrote: > > Which Trisquel version exactly? > > > > On Trisquel 12 (ecne), many Guix commands weren't working before due > > to the lack of Apparmor profile. > I've re-tested and 'guix pull' still works fine in my case. I also > didn't find a bugreport about the issue mentioned in this thread yet. > > A possible issue is that I'm unsure if upgrading the guix-daemon in the > way documented in the Guix manual works as it requires an apparmor > profile. >
This is on Trisquel 12, but I only have the problem on one computer with Trisquel 12 and guix (while I have several computers in that case), so perhaps I have some different setup there. In the journal, I noticed the following when I run guix pull: juin 01 11:01:34 rosa kernel: audit: type=1400 audit(1780304494.536:211): apparmor="DENIED" operation="file_receive" class="file" profile="guix- daemon" name="/disconnected/var/cache/nscd/group" pid=12877 comm="guix- daemon" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 juin 01 11:01:39 rosa kernel: audit: type=1400 audit(1780304499.408:212): apparmor="DENIED" operation="capable" class="cap" profile="guix-daemon" pid=12886 comm="guix-daemon" capability=7 capname="setuid" So maybe there is an apparmor issue indeed? I know absolutely nothing about apparmor, so any advice on this is appreciated. Cheers, David.
