Subject: bug#68483: Qutebrowser QT platform plugin could not be initialized

From: chris <[email-masked]>
Date: Tue, 16 Jan 2024 07:12:42 -0800

On  1月16日 火, Sergey Trofimov wrote:
> 
> Clément Lassieur <[email-masked]> writes:
> 
> --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---

This works here. After adding the above to my home config, qutebrowser starts as `qutebrowser` without the extra params.

As for the sound issue, this system uses pipewire only, without dbus. mpv, musikcube and the previous version of qutebrowser have/had sound. When I first setup guix about a year ago, qutebrowser 2 did not produce sound and, to resolve the issue, Iyzsong, in the matrix or irc channel, said they would enable native support for pipewire through a flag at qutebrowser (or maybe one of the dependencies... I don't remember) and the next day after pull and reconfigure the sound began working and there were no sound problems until updating to qutebrowser 3 today.