bug#29212: XLockMore displays wrong time

Hello Ludo, l...@gnu.org (Ludovic Courtès) writes: > Since GuixSD provides /etc/localtime already, we can actually unset TZ. > And when we do so, setuid binaries simply honor /etc/localtime and don’t > go searching for timezone data elsewhere, and they see the right time. > > Can you confirm

bug#25758: (no subject)

bug#25759: (no subject)

bug#29212: XLockMore displays wrong time

Hi, Diego Nicola Barbato skribis: > XLockMore (as invoked by the command `xlock') displays the wrong time on > the lock screen. Instead of honouring the timezone set in `config.scm' > (as do other programs e.g. the `date' command) it displays UTC. The problem is that

bug#29219: CUPS filter still can't access Ghostscript (gs)

I added two printers through CUPS' web interface (localhost:631) using the PPD driver file which I downloaded (from openprinting.org): one called ljet4 (which calls Ghostscript) and one called Postscript (which just calls `cat`)⁰. The latter worked. But although I was expecting commit

bug#29211: XScreenSaver does not recognise password

Diego Nicola Barbato skribis: > You are right. `type -P xscreensaver' returns > `/home/diego/.guix-profile/bin/xscreensaver'. And if i run > `/run/setuid-programs/xscreensaver &' instead of `xscreensaver &' > everything works as expected. > > Apparently my setup should

bug#28664: Old narinfos of tarballs purged on berlin

l...@gnu.org (Ludovic Courtès) skribis: > l...@gnu.org (Ludovic Courtès) skribis: > >> l...@gnu.org (Ludovic Courtès) skribis: >> >>> As a followup to , Ricardo upgraded to the >>> latest Guix on berlin, and I’ve now removed old .narinfos corresponding >>> to tarballs

bug#29211: XScreenSaver does not recognise password

Apparently this is not a bug.

bug#29211: XScreenSaver does not recognise password

Hello Ludo, l...@gnu.org (Ludovic Courtès) writes: > Hi Diego, > > Diego Nicola Barbato skribis: > >> When I lock my screen with XScreenSaver by first running >> `xscreensaver &' and then `xscreensaver-command --lock' I am unable to >> unlock the screen by entering my

bug#29186: building guile-emacs fails: required libaries not found: libjpeg

Efraim Flashner writes: >> + (add-before 'configure 'setenv >> + (lambda _ >> + (setenv "CFLAGS" "-g"))) >> (add-after 'unpack 'autogen >>(lambda _ >> (zero? (system* "sh" "autogen.sh")) > >

bug#29186: building guile-emacs fails: required libaries not found: libjpeg

Efraim Flashner writes: > Will it build with libjpeg-turbo or libjpeg-9? I'm not sure how feasable > it is, but I'd like to remove libjpeg-8 (and some other old libraries) > if its possible. As communicated over irc; yes, it build with libjpeg-9. janneke -- Jan Nieuwenhuizen

bug#29212: XLockMore displays wrong time

Hello Guix, XLockMore (as invoked by the command `xlock') displays the wrong time on the lock screen. Instead of honouring the timezone set in `config.scm' (as do other programs e.g. the `date' command) it displays UTC. Greetings Diego

bug#29211: XScreenSaver does not recognise password

Hi Diego, Diego Nicola Barbato skribis: > When I lock my screen with XScreenSaver by first running > `xscreensaver &' and then `xscreensaver-command --lock' I am unable to > unlock the screen by entering my password. This happens even though I > have added

bug#29211: XScreenSaver does not recognise password

Hello Guix, When I lock my screen with XScreenSaver by first running `xscreensaver &' and then `xscreensaver-command --lock' I am unable to unlock the screen by entering my password. This happens even though I have added `(screen-locker-service xscreensaver "xscreensaver")' to my services in my

bug#29186: building guile-emacs fails: required libaries not found: libjpeg

On Tue, Nov 07, 2017 at 08:06:05PM +0100, Jan Nieuwenhuizen wrote: > Jan Nieuwenhuizen writes: > > From 2a369f5151e0c7565fc271fb52def543b447477d Mon Sep 17 00:00:00 2001 > From: Jan Nieuwenhuizen > Date: Tue, 7 Nov 2017 20:02:35 +0100 > Subject: [PATCH] gnu: guile-emacs: compile

bug#29186: building guile-emacs fails: required libaries not found: libjpeg

On Tue, Nov 07, 2017 at 08:06:05PM +0100, Jan Nieuwenhuizen wrote: > Jan Nieuwenhuizen writes: > > > However, now the build fails with a segfault: > > > > EMACSLOADPATH= '../src/bootstrap-emacs' -batch --no-site-file > > --no-site-lisp -l autoload \ > >--eval "(setq generate-autoload-cookie

bug#29200: `guix build --fallback` does not work with offloading

Marius Bakke skribis: > I've noticed that when offloading, --fallback sometimes fails to > actually fall back. Here is a shell transcript: The problem is that guix-daemon does not pass “fallbackness” settings to ‘guix offload’ (you can check (guix scripts offload) to see