bug#64593: ‘guix system image’ fails to create image while invoking ‘grub-bios-setup’
Hi Ludovic,
shouldn't it be `(bootloader grub-efi-bootloader)` if you're
building a `efi-raw` image?
With efi grub it builds and boots just fine, as I've tested before
submitting the patch.
Ludovic Courtès writes:
Hello,
There seems to be a recent regression:
$ cat mini-os.scm
(use-modules (gnu))
(operating-system
(host-name "mini-1")
(bootloader (bootloader-configuration
(bootloader grub-bootloader)
(targets '("/dev/sda"
(file-systems (cons (file-system
(device (file-system-label "my-root"))
(mount-point "/")
(type "ext4")) %base-file-systems))
(kernel-arguments (list "console=tty0 console=ttyS0,115200")))
$ guix system image mini-os.scm
bug#68034: Pull failure
this has been fixed in 3e41b252cfc81508bfcd0ac7103df212b35c3b91
bug#68031: Error running Guix pull: no code for module (gnu packages ed)
Richard Sent writes: This has been fixed in 3e41b252cfc81508bfcd0ac7103df212b35c3b91 Hi all, Noticed this error when running Guix pull today. Not entirely sure of the problem, but the console said to report it and I didn't notice any identical bug reports recently. Full log attached. Abridged version below. ice-9/boot-9.scm:3330:6: In procedure resolve-interface: no code for module (gnu packages ed) Computing Guix derivation for 'x86_64-linux'... guix pull: error: You found a bug: the program '/gnu/store/zd32rmipj4nqlq6rnc0mv638x3i7yvfs-compute-guix-derivation' failed to compute the derivation for Guix (version: "2a66a96634b33667a45f4493a37eef48033b7287"; system: "x86_64-linux"; host version: "49a7a95ba44e231e9e15a274f9a96de6fa012daf"; pull-version: 1). Please report the COMPLETE output above by email to .
bug#68483: Qutebrowser QT platform plugin could not be initialized
chris writes: > On 1月15日 月, Josselin Poiret wrote: >> Hi chris, >> >> chris writes: >> >> > Related to https://issues.guix.gnu.org/67289#7 >> > >> > Here is the qutebrowser 3 process shell output. Would anyone recommend a >> > solution? >> > ``` >> > $ qutebrowser >> > 20:40:33 WARNING: Could not find the Qt platform plugin "wayland" in "" >> >> Have you installed qt-wayland? Are you setting QT_QPA_PLATFORM >> anywhere? > > Hey Josselin, > > I've tried installing qtwayland through guix home by specifying "qtwayland" in > my home config file. QT_QPA_PLATFORM is specified in my home config this way > Here you go: ```sh qtw=$(guix build qtwayland@6)/lib/qt6/plugins QT_PLUGIN_PATH=$qtw QT_QPA_PLATFORM_PLUGIN_PATH=$qtw/platforms qutebrowser -s qt.force_platform wayland ``` Maybe a qutebrowser-wayland package variant should be defined to do the required wrapping. Otherwise you can just install qtwayland@6 to your profile and use ~/.guix-home/profile/lib/qt6/plugins in paths.
bug#68476: Shepherd stops responding if you set the time less than the current one
Aleksandr Vityazev writes: Hi, I have running shepherd version 0.10.3 for the system and the user. My current time is Mon Jan 15 06:30:52 PM MSK 2024, if I set the time less than the current one, both shepherds stop responding. I set the time like this: sudo date --set='20240115 18:00' It's a known problem, see https://issues.guix.gnu.org/66684
bug#68415: User's shepherd services defined in guix home config can not start after guix pull.
Feng Shu writes:
After I guix pull, services defined in guix home config can no
start:
-
服务 root 已启动。
WARNING: Use of `load' in declarative module (#{ g117}#). Add
#:declarative? #f to your define-module invocation.
unbound-variable(#f "Unbound variable: ~S" (service) #f)
Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to suppress
this message.
Creating XDG user directories... done
Comparing
/gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts
and
/gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts...
done (same)
Evaluating on-change gexps.
---
When I run command: herd status, show error:
feng@Guix ~$ herd status
error: connect: /run/user/1000/shepherd/socket: No such file or
directory
Have you tried debugging it? Is your home shepherd running? Do you
see shepherd mentions in ~/.guix-home/on-first-login?
Have you tried restarting your system?
bug#68483: Qutebrowser QT platform plugin could not be initialized
chris writes: Qutebrowser 3 does not have sound and this appears in the process output. "その ようなファイルやディレクトリはありません" means "the file or directory is not found". ``` [3158:3158:0116/000131.568005:ERROR:interface_endpoint_client.cc(694)] Message 4 rejected by interface blink.mojom.WidgetHost ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3473:3473:0116/000734.652713:ERROR:alsa_util.cc(204)] PcmOpen: default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3473:3473:0116/000734.653460:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3473:3473:0116/000824.855365:ERROR:alsa_util.cc(204)] PcmOpen: default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3473:3473:0116/000824.856521:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3473:3473:0116/000826.415347:ERROR:alsa_util.cc(204)] PcmOpen: default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3473:3473:0116/000826.416368:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,そのようなファイルやディレクトリはありません ``` Sound works for me both in X11 and Wayland environments. I use pipewire though.
bug#68483: Qutebrowser QT platform plugin could not be initialized
Clément Lassieur writes: On Mon, Jan 15 2024, chris wrote: On 1月15日 月, chris wrote: On 1月16日 火, Sergey Trofimov wrote: > > Here you go: > ```sh > qtw=$(guix build qtwayland@6)/lib/qt6/plugins > QT_PLUGIN_PATH=$qtw > QT_QPA_PLATFORM_PLUGIN_PATH=$qtw/platforms qutebrowser -s > qt.force_platform wayland > ``` I tried this command again just now and succeeded this time. I must have done something wrong the first time. Thank you Sergey! Hi, Would this work with non-wayland users too? (So that it would make sense to add it to the main package?) Thanks, Clément Yeah, it would work, but forcing the platform through parameters is not necessary. I added it just to be sure that wayland is being used instead of xcb. On the other hand I think adding qtwayland dependency to every qt-based gui program doesn't make sense. Maybe a qtwayland-home-service makes more sense which would install the dependency and set required environment variables. This way it would work for every Qt GUI program on wayland.
bug#68483: Qutebrowser QT platform plugin could not be initialized
Clément Lassieur writes:
On Tue, Jan 16 2024, Sergey Trofimov wrote:
Would this work with non-wayland users too? (So that it would
make
sense to add it to the main package?)
Thanks,
Clément
Yeah, it would work, but forcing the platform through
parameters is not
necessary. I added it just to be sure that wayland is being
used instead of
xcb. On the other hand I think adding qtwayland dependency to
every qt-based
gui program doesn't make sense. Maybe a qtwayland-home-service
makes more
sense which would install the dependency and set required
environment
variables. This way it would work for every Qt GUI program on
wayland.
Ok, I see, thanks!
As simple as:
--8<---cut here---start->8---
(simple-service 'qtwayland-vars-service
home-environment-variables-service-type
`(("QT_PLUGIN_PATH" . ,(file-append qtwayland
"/lib/qt6/plugins"))
("QT_QPA_PLATFORM_PLUGIN_PATH" . ,(file-append qtwayland
"/lib/qt6/plugins/platforms"
--8<---cut here---end--->8---
bug#68512: Qutebrowser 3, no sound from pipewire-only system
chris writes: Hello, The latest qutebrowser v3 from this pipewire-only system has no sound. Related messages from the shell process pasted below include CJK characters which debbugs renders as "??", all CJK messages translate as "file or directory not found" yeah, debbugs doesn't support unicode on the web fully. But when checking your messages in emacs debbugs interface, I see the CJK characters just fine. ``` ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3003:3003:0116/083803.232761:ERROR:alsa_util.cc(204)] PcmOpen: default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3003:3003:0116/083803.233758:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3003:3003:0116/083808.743619:ERROR:alsa_util.cc(204)] PcmOpen: default,そのようなファイルやディレクトリはありません ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave [3003:3003:0116/083808.744661:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,そのようなファイルやディレクトリはありません ``` About a year ago, user @iyzsong enabled pipewire support at qutebrowser v2 for me and sound has been good here until today when qutebrowser v3 was installed. iirc, a flag was enabled in qutebrowser or one of its dependencies. How is pipewire configured on your system? The thing is that qtwebengine@5 is linked with PulseAudio and ALSA libraries, but @6 is linked only with alsa. You probably miss pipewire-alsa compatibility configuration. Do you use home-pipewire-service-type? It sets both pulse/alsa shims and it works for me this way.
bug#68512: Qutebrowser 3, no sound from pipewire-only system
chris writes:
On 1月16日 火, Sergey Trofimov wrote:
How is pipewire configured on your system? The thing is that
qtwebengine@5
is linked with PulseAudio and ALSA libraries, but @6 is linked
only with
alsa. You probably miss pipewire-alsa compatibility
configuration. Do you
use home-pipewire-service-type? It sets both pulse/alsa shims
and it works
for me this way.
This system does not use dbus and pipewire was configured about
a year ago when
there were few options for using pipewire out of the box in any
sort of way.
Guix home is configured to write a pipewire and three
wireplumber config files,
as described at this link
https://wiki.alpinelinux.org/wiki/PipeWire#Configuration
.config/pipewire/pipewire.conf
.config/wireplumber/wireplumber.conf
.config/wireplumber/main.lua.d/80-disable-dbus.lua
.config/wireplumber/bluetooth.lua.d/80-disable-logind.lua
With with those files in place, pipewire and wireplumber are
started
sequentially to get working sound. I use this in my
.config/sway/config
(possibly this is copy-pasted from unmatched-paren)
```
exec_always killall -wqr "(pipewire|wireplumber)" \
|| sleep 1 && ((pipewire &); sleep 2 && (wireplumber &))
```
Well, qtwebengine doesn't link with PipeWire anyway, you have to
use either PulseAudio or ALSA. Here is an example
~/.config/alsa/asoundrc on my system, created by
home-pipewire-service-type. If you add such file to your setup -
qutebrowser should be able to use alsa lib to output audio through
pipewire.
--8<---cut here---start->8---
pcm_type.pipewire {
lib
"/gnu/store/a331f91m9g8898lccyj7fniqsyv406y9-pipewire-1.0.0/lib/alsa-lib/libasound_module_pcm_pipewire.so"
}
ctl_type.pipewire {
lib
"/gnu/store/a331f91m9g8898lccyj7fniqsyv406y9-pipewire-1.0.0/lib/alsa-lib/libasound_module_ctl_pipewire.so"
}
--8<---cut here---end--->8---
bug#68415: User's shepherd services defined in guix home config can not start after guix pull.
Feng Shu writes: Have you tried debugging it? Is your home shepherd running? Do you see I tried, but I do not know why: unbound-variable service That is not normal. You need to fix that. The below code run have problem, and I think shepherd is not run, for 'ps aux |grep shepherd' can not found info. home's shepherd is started by ~/.guix-home/on-first-login, which gets invoked in ~/.profile You can try running the script manually and see what happens. Please compare your home configuration before and after the pull. You can find the configs in /var/guix/profiles/per-user//guix-home--link/configuration.scm The subject is "can not start after guix pull", but it seems to me your home is misconfigured and the pull might be unrelated. (service home-shepherd-service-type (home-shepherd-configuration (shepherd shepherd) that's the default, no need to specify shepherd (services (list xautolock-service
bug#68512: Qutebrowser 3, no sound from pipewire-only system
chris writes: Sergey, your configuration file is working and audio is heard from qutebrowser on this system. Internet searches surfaced commands like these, `pw-cli` `strace -e connect pw-dump >/dev/null` Error messages were seen relating to socket files not found, `$XDG_RUNTIME_DIR/pipewire-0` `$XDG_RUNTIME_DIR/pipewire-0-manager` Various things attempted, but the socket files missing every time sway started Finally, tried removing the pipewire-starting parts of the sway config ``` # exec_always killall -wqr "(pipewire|wireplumber)" \ # || sleep 1 && ((pipewire &); sleep 2 && (wireplumber &)) ``` Then separately started pipewire and wireplumber "manually" from the shell. The socket files were created and when qutebrowser sound could be heard. I'm glad you sorted it out. Check what are the environment variables for your sway process (cat /proc//environ | tr -s '\0' '\n'). Maybe XDG_RUNTIME_DIR is missing there? Enabling debug logging for pipewire might help as well: https://docs.pipewire.org/page_daemon.html
bug#68512: Qutebrowser 3, no sound from pipewire-only system
chris writes:
Sergey,
Yesterday after reporting back here, I found that I was able to
change the commands used by sway from this
```
exec_always killall -wqr "(pipewire|wireplumber)" \
|| sleep 1 && ((pipewire &); sleep 2 && (wireplumber &))
```
To this
```
exec sleep 2 && pipewire
exec sleep 4 && wireplumber
```
Ugh, why don't you use home-pipewire-service-type?
In order to script-generate the asoundrc file, I wish to use
pipewire's store
directory path inside a scheme function. WOuld you teach me how
to do this? eg,
`$(guix build pipewire) #
/gnu/store/8572wxb5138hanhvn1lbfdm1kicxsd2k-pipewire-1.0.0`
No success trying various things from this thread
https://www.mail-archive.com/help-guix@gnu.org/msg11871.html
Packages are file-like, i.e. replaced with their location when
used in g-exp.
Here is an example how to define the configuration, I've adapted
it from gnu/home/services/home.scm
--8<---cut here---start->8---
(simple-service 'pipewire-configs
home-xdg-configuration-files-service-type
`(("alsa/asoundrc")
,(mixed-text-file
"asoundrc"
"<" pipewire "/share/alsa/alsa.conf.d/50-pipewire.conf>\n"
"<" pipewire
"/share/alsa/alsa.conf.d/99-pipewire-default.conf>\n"
"pcm_type.pipewire {\n"
" lib \"" pipewire
"/lib/alsa-lib/libasound_module_pcm_pipewire.so\"\n"
"}\n"
"ctl_type.pipewire {\n"
" lib \"" pipewire
"/lib/alsa-lib/libasound_module_ctl_pipewire.so\"\n"
"}\n")))
--8<---cut here---end--->8---
bug#68512: Qutebrowser 3, no sound from pipewire-only system
chris writes: This attempt from the discussion here https://lists.gnu.org/archive/html/guix-devel/2021-03/msg00441.html ``` (define s (open-connection)) (display (derivation->output-path (package-derivation s pipewire #:graft? #f) "out")) ``` It runs but returns the wrong store path, /gnu/store/kqw8zs84px1vzw98yv9xax4rc0n612qy-pipewire-0.3.77 The $(guix build pipewire) command returns this, /gnu/store/8572wxb5138hanhvn1lbfdm1kicxsd2k-pipewire-1.0.0 0.3.77 is the previous version, from a month ago. Is your checkout fresh? Did you `guix pull`?
bug#68512: Qutebrowser 3, no sound from pipewire-only system
chris writes: On 1月26日 金, Sergey Trofimov wrote: Ugh, why don't you use home-pipewire-service-type? `home-pipewire-service-type` has no option to skip dbus and thus far this system does not use dbus, ibus, elogind and systemd etc. The only dependency on `dbus` is that pipewire shepherd service has it in the requirement field. You can add a no-op shepherd service which would have (provision '(dbus)) to satisfy the dependency.
bug#70848: ntpd updating the time hangs shepherd
Hi, this is known, see https://issues.guix.gnu.org/66684
bug#54297: Qutebrowser failed to render local fonts.
This got fixed with upgrade to qt6
