bug#70940: You found a bug: the program derivation
Authenticating channel 'guix', commits 9edb3f6 to 6e86089 (6 new commits)...
Building from these channels:
brandhout-packageshttps://github.com/brandhout/guix_channel.git 5fe3961
nonguix https://gitlab.com/nonguix/nonguix.git 7081518
guix https://git.savannah.gnu.org/git/guix.git 6e86089
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
building
/gnu/store/zjw8b0v33zd45n3bg9g59f5zdpzi8hfk-compute-guix-derivation.drv...
Computing Guix derivation for 'x86_64-linux'... \Backtrace:
14 (primitive-load
"/gnu/store/13bvpk5dqjmdzspb276qzs24jcj3jjhh-compute-guix-derivation")
In ice-9/eval.scm:
155:9 13 (_ _)
159:9 12 (_ #(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(# ?)
?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
In ice-9/boot-9.scm:
152:2 11 (with-fluid* _ _ _)
152:2 10 (with-fluid* _ _ _)
In ./guix/store.scm:
2205:24 9 (run-with-store #
# ?)
2033:8 8 (_ #)
In ./guix/gexp.scm:
299:22 7 (_ #)
1205:2 6 (_ #)
1072:2 5 (_ #)
913:4 4 (_ #)
In ./guix/store.scm:
2090:12 3 (_ #)
1428:5 2 (map/accumulate-builds # # ?)
1444:15 1 (_ #
("/gnu/store/hszgl65h1d3vnsifb35l4zvdvk03hqdv-guix-daem?" ?) ?)
1444:15 0 (loop #f)
./guix/store.scm:1444:15: In procedure loop:
ERROR:
1. :
message:
"`/gnu/store/8dzvn0qr62a8l2ad3hx1xhjdvxifc7hn-guix-1.4.0-18.4c94b9e/bin/guix
substitute' died unexpectedly"
status: 1
guix pull: error: You found a bug: the program
'/gnu/store/13bvpk5dqjmdzspb276qzs24jcj3jjhh-compute-guix-derivation'
failed to compute the derivation for Guix (version:
"6e86089d563ccb67ae04cd941ca7b66c1777831f"; system: "x86_64-linux";
host version: "a682ddd70846d488cfbd82d65e8566ec6739813c"; pull-version: 1).
Please report the COMPLETE output above by email to .
This seems like a really low effort bug report, but I'm following
instructions and don't know what to include further.
bug#57832: virt-manager broken due to broken GtkSource dependency
Hi,
Since virt-manager 3.2.0 I cannot use the package anymore. Any action in
the GUI results in the following traceback:
```console
$virt-manager --debug
[Thu, 15 Sep 2022 15:55:10 virt-manager 17690] DEBUG (cli:195) Uncaught
exception:
Traceback (most recent call last):
File
"/gnu/store/976nmhmzaqfk4cim7q0h8x7f5z5api12-virt-manager-3.2.0/share/virt-manager/virtManager/xmleditor.py",
line 11, in
gi.require_version("GtkSource", "4")
File
"/gnu/store/b07y8a2axslnz97pjdg7lp73xwk1gf8w-python-pygobject-3.40.1/lib/python3.9/site-packages/gi/__init__.py",
line 129, in require_version
raise ValueError('Namespace %s not available for version %s' %
ValueError: Namespace GtkSource not available for version 4
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/gnu/store/976nmhmzaqfk4cim7q0h8x7f5z5api12-virt-manager-3.2.0/share/virt-manager/virtManager/manager.py",
line 455, in new_vm
from .createvm import vmmCreateVM
File
"/gnu/store/976nmhmzaqfk4cim7q0h8x7f5z5api12-virt-manager-3.2.0/share/virt-manager/virtManager/createvm.py",
line 30, in
from .storagebrowse import vmmStorageBrowser
File
"/gnu/store/976nmhmzaqfk4cim7q0h8x7f5z5api12-virt-manager-3.2.0/share/virt-manager/virtManager/storagebrowse.py",
line 11, in
from .hoststorage import vmmHostStorage
File
"/gnu/store/976nmhmzaqfk4cim7q0h8x7f5z5api12-virt-manager-3.2.0/share/virt-manager/virtManager/hoststorage.py",
line 16, in
from .createpool import vmmCreatePool
File
"/gnu/store/976nmhmzaqfk4cim7q0h8x7f5z5api12-virt-manager-3.2.0/share/virt-manager/virtManager/createpool.py",
line 18, in
from .xmleditor import vmmXMLEditor
File
"/gnu/store/976nmhmzaqfk4cim7q0h8x7f5z5api12-virt-manager-3.2.0/share/virt-manager/virtManager/xmleditor.py",
line 14, in
gi.require_version("GtkSource", "3.0")
File
"/gnu/store/b07y8a2axslnz97pjdg7lp73xwk1gf8w-python-pygobject-3.40.1/lib/python3.9/site-packages/gi/__init__.py",
line 129, in require_version
raise ValueError('Namespace %s not available for version %s' %
ValueError: Namespace GtkSource not available for version 3.0
```
I will happily provide more information if necessary
--
Met vriendelijke groet,
Rick Huijzer
bug#57071: Xscreensaver not working since latest patch
Hi Roman and Ludo,
It seems that xscreensaver-auth needs to be setuid instead of the main
xscreensaver binary. The screen-locker-service in xorg.scm sets the
provided package setuid and sets the required pam configuration for the
provided package. The problem is that the pam configuration needs to be set
for xscreensaver (/etc/pam.d/xscreensaver) and setuid needs to be set for
xscreensaver-auth.
Interestingly when I setuid xscreensaver-auth manually I run into the
following when unlocking:
Aug 10 13:35:02 localhost unix_chkpwd[2197]: check pass; user unknown
Aug 10 13:35:02 localhost unix_chkpwd[2197]: password check failed for user
(rhuijzer)
Aug 10 13:35:02 localhost xscreensaver-auth: pam_unix(xscreensaver:auth):
authentication failure; logname= uid=1000 euid=1000 tty=:0 ruser= rhost=
user=rhuijzer
But this might be fixed in time by [RFC PATCH] gnu: linux-pam: Change path
to unix_chkpwd helper <https://issues.guix.gnu.org/53468>.
I don't know how to fix this elegantly, maybe create a dedicated service
for xscreensaver instead of the standard screen-locker-service?
Thanks,
Op wo 10 aug. 2022 om 09:14 schreef Roman Scherer <
roman.sche...@burningswell.com>:
>
> Hi Ludo and Rick,
>
> sorry for the trouble. I'm running xscreensaver on a foreign distro and
> did not notice this. Probably because somehow my screen wasn't locked,
> but still showing random screensavers.
>
> However, now that I tried the `xscreensaver-command -lock` command I see
> a dialog with a "Password initialization failed" message.
>
> The xscreensave logs also show this:
>
> xscreensaver-auth: 06:45:55: OOM: /proc/99677/oom_score_adj: Permission
> denied
> xscreensaver-auth: 06:45:55: To prevent the kernel from randomly
> unlocking
> xscreensaver-auth: 06:45:55: your screen via the out-of-memory killer,
> xscreensaver-auth: 06:45:55: "xscreensaver-auth" must be setuid root.
> xscreensaver-auth: 06:46:06: PAM: warning: /etc/pam.d/xscreensaver does
> not exist.
> xscreensaver-auth: 06:46:06: PAM: password authentication is unlikely to
> work.
> xscreensaver-auth: 06:46:15: PAM: warning: /etc/pam.d/xscreensaver does
> not exist.
> xscreensaver-auth: 06:46:15: PAM: password authentication is unlikely to
> work.
>
> When the dialog popped up, I had to switch to a terminal and kill
> xscreensaver to be able to access my desktop again.
>
> Should we revert it, until we figured out what's necesarry to get this
> working again?
>
> r0man
>
> Ludovic Courtès writes:
>
> > Hi Rick,
> >
> > Rick Huijzer skribis:
> >
> >> The latest xscreensaver patch <https://issues.guix.gnu.org/56597>
> rendered
> >> xscreensaver unusable on my systems. When I try to unlock my screen I am
> >> greeted with the message 'xscreensaver: don't login as root', even
> though I
> >> don't invoke it as root.
> >>
> >>
> >> $xscreensaver-command -lock
> >> Aug 9 08:45:22 localhost shepherd[1]: [slim] xscreensaver-gfx:
> 08:45:22:
> >> 1: running as root: not launching hacks.
> >> Aug 9 09:10:29 localhost shepherd[1]: [slim] xscreensaver-command:
> locking
> >> Aug 9 09:10:32 localhost shepherd[1]: [slim] xscreensaver-gfx:
> 09:10:32:
> >> 0: running as root: not launching hacks.
> >>
> >> When I remove the
> >> (screen-locker-service xscreensaver)
> >> I run into all kinds of set-uid problems.
> >
> > Sorry about that, I built it during review but did not actually run it.
> >
> > One effect of ‘screen-locker-service’ is to make the program setuid-root
> > so that it can authenticate users. It would seem that something changed
> > in xscreensaver in that area; quoth ‘driver/subprocs.c’:
> >
> > if (getuid() == (uid_t) 0 || geteuid() == (uid_t) 0)
> > /* Prior to XScreenSaver 6, if running as root, we would change
> the
> >effective uid to the user "nobody" or "daemon" or "noaccess",
> >but even that was just encouraging bad behavior. Don't log in
> >as root. */
> > {
> > fprintf (stderr, "%s: %d: running as root: not launching
> hacks.\n",
> >blurb(), ssi->number);
> > screenhack_obituary (ssi, "", "XScreenSaver: Don't log in as
> root.");
> > goto DONE;
> > }
> >
> > OTOH the ‘disavow_privileges’ function is supposed to drop root
> > privileges early on.
> >
> > So I’m not sure how it’s supposed to be run. R0man, ideas?
> >
> > Thanks,
> > Ludo’.
>
--
Met vriendelijke groet,
Rick Huijzer
bug#57071: Xscreensaver not working since latest patch
Hi, The latest xscreensaver patch <https://issues.guix.gnu.org/56597> rendered xscreensaver unusable on my systems. When I try to unlock my screen I am greeted with the message 'xscreensaver: don't login as root', even though I don't invoke it as root. $xscreensaver-command -lock Aug 9 08:45:22 localhost shepherd[1]: [slim] xscreensaver-gfx: 08:45:22: 1: running as root: not launching hacks. Aug 9 09:10:29 localhost shepherd[1]: [slim] xscreensaver-command: locking Aug 9 09:10:32 localhost shepherd[1]: [slim] xscreensaver-gfx: 09:10:32: 0: running as root: not launching hacks. When I remove the (screen-locker-service xscreensaver) I run into all kinds of set-uid problems. I will happily provide more information if needed. -- Met vriendelijke groet, Rick Huijzer
