From: Anton Hvornum <torxed@archlinux.org>
To: qemu-devel@nongnu.org
Subject: pipewire re-connect
Date: Wed, 19 Jun 2024 08:50:19 +0200 [thread overview]
Message-ID: <29757ffe-61c2-41d0-8b93-4d8a6af4aea9@archlinux.org> (raw)
Hi.
Pipewire feature is working great, but I haven't found a way to get Qemu
to re-connect after a user runs `systemctl --user restart pipewire` for
instance.
Qemu will simply continue, without sound output until restarted.
//Anton
reply other threads:[~2024-06-19 13:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29757ffe-61c2-41d0-8b93-4d8a6af4aea9@archlinux.org \
--to=torxed@archlinux.org \
--cc=qemu-devel@nongnu.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.