From: chris <chris@bumblehead.com>
To: 68512@debbugs.gnu.org
Subject: bug#68512: Qutebrowser 3, no sound from pipewire-only system
Date: Tue, 16 Jan 2024 09:30:13 -0800 [thread overview]
Message-ID: <Zaa9JerMk8nqYrr8@guix-xps> (raw)
In-Reply-To: <ZaayK6WLGZQffi2f@guix-xps>
Possibly this was the change from Iyzsong which enabled sound here,
```sh
$ git diff fbbbc2088ce933d83f5b0be75308fdcb6b40fa57 d9368572abd3683bed4263eb5e149bb404baee59
diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm
index 76e9e519c7..01327f6ccf 100644
--- a/gnu/packages/qt.scm
+++ b/gnu/packages/qt.scm
@@ -2708,7 +2708,8 @@ (define-public qtwebengine-5
"src/buildtools/config/linux.pri"
(lambda (in out)
(display (get-string-all in) out)
- (display "\ngn_args += use_system_openh264=true\n" out)))
+ (display "\ngn_args += use_system_openh264=true\n" out)
+ (display "\ngn_args += link_pulseaudio = true\n" out)))
;; Qtwebengine is not installed into the same prefix as
;; qtbase. Some qtbase QTLibraryInfo constants will not
;; work. Replace with the full path to the qtwebengine-5
```
No equivalent is found by me in the qtwebengine definition that supplies qtwebgine 6
next prev parent reply other threads:[~2024-01-16 17:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 16:43 bug#68512: Qutebrowser 3, no sound from pipewire-only system chris
2024-01-16 17:30 ` chris [this message]
2024-01-16 17:39 ` chris
2024-01-16 18:12 ` chris
2024-01-16 19:25 ` Sergey Trofimov
2024-01-16 20:49 ` chris
2024-01-17 6:58 ` Sergey Trofimov
2024-01-17 9:49 ` chris
2024-01-17 9:56 ` chris
2024-01-25 9:09 ` chris
2024-01-25 18:37 ` Sergey Trofimov
2024-01-25 23:26 ` chris
2024-01-26 5:56 ` Sergey Trofimov
2024-01-26 8:18 ` chris
2024-01-26 12:46 ` Sergey Trofimov
2024-01-26 23:35 ` chris
2024-01-26 0:00 ` chris
2024-01-26 6:10 ` Sergey Trofimov
2024-01-26 8:19 ` chris
2024-01-26 9:45 ` Clément Lassieur
2024-01-26 23:32 ` chris
2024-01-26 9:10 ` bug#68512: done 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=Zaa9JerMk8nqYrr8@guix-xps \
--to=chris@bumblehead.com \
--cc=68512@debbugs.gnu.org \
/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).