unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: chris <chris@bumblehead.com>
To: Sergey Trofimov <sarg@sarg.org.ru>
Cc: "Josselin Poiret" <dev@jpoiret.xyz>,
	chris@bumblehead.com, 68483@debbugs.gnu.org,
	"Clément Lassieur" <clement@lassieur.org>
Subject: bug#68483: Qutebrowser QT platform plugin could not be initialized
Date: Tue, 16 Jan 2024 07:12:42 -0800	[thread overview]
Message-ID: <Zaac6uU_TrUzCMma@guix-xps> (raw)
In-Reply-To: <875xztv7a2.fsf@sarg.org.ru>

On  1月16日 火, Sergey Trofimov wrote:
> 
> Clément Lassieur <clement@lassieur.org> 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.




  reply	other threads:[~2024-01-16 15:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 19:40 bug#68483: Qutebrowser QT platform plugin could not be initialized chris
2024-01-15 22:15 ` Josselin Poiret via Bug reports for GNU Guix
2024-01-15 22:44   ` chris
2024-01-16  6:38     ` Sergey Trofimov
2024-01-16  7:07       ` chris
2024-01-16  7:48         ` chris
2024-01-16 10:42           ` Clément Lassieur
2024-01-16 10:47             ` Sergey Trofimov
2024-01-16 11:02               ` Clément Lassieur
2024-01-16 11:35                 ` Sergey Trofimov
2024-01-16 15:12                   ` chris [this message]
2024-01-16 15:45                     ` chris
2024-01-16 16:19                       ` chris
2024-01-16 16:57                       ` chris
2024-01-16  7:53         ` chris
2024-01-16  8:14         ` chris
2024-01-16 10:00           ` Sergey Trofimov
2024-01-16 16:27 ` bug#68483: closing chris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zaac6uU_TrUzCMma@guix-xps \
    --to=chris@bumblehead.com \
    --cc=68483@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=dev@jpoiret.xyz \
    --cc=sarg@sarg.org.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).