Github messages for voidlinux
 help / color / mirror / Atom feed
From: z411 <z411@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Screensharing broken on KDE Plasma 6 update
Date: Tue, 14 May 2024 20:23:02 +0200	[thread overview]
Message-ID: <20240514182302.A52BB21E84@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50326@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

New comment by z411 on void-packages repository

https://github.com/void-linux/void-packages/issues/50326#issuecomment-2110849004

Comment:
Thanks for the quick reply and patch.

So it seems Plasma 6 couldn't handle having a PipeWire connection start *after* the session is started. Makes sense as I was also starting PipeWire through session autostart, which is the recommended way to do it in the Void wiki. Maybe we could include runit user services for PipeWire and Wireplumber and edit the wiki to redirect people to use them instead? Seems like a cleaner way to me, and most probably what most desktop environments expect.

  parent reply	other threads:[~2024-05-14 18:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  3:51 [ISSUE] " z411
2024-05-14  9:36 ` Luciogi
2024-05-14 10:55 ` SpidFightFR
2024-05-14 10:59 ` classabbyamp
2024-05-14 11:01 ` SpidFightFR
2024-05-14 11:07 ` classabbyamp
2024-05-14 13:03 ` Luciogi
2024-05-14 13:22 ` SpidFightFR
2024-05-14 16:03 ` Luciogi
2024-05-14 16:05 ` Luciogi
2024-05-14 16:06 ` Luciogi
2024-05-14 16:06 ` Luciogi
2024-05-14 16:25 ` Luciogi
2024-05-14 18:22 ` z411
2024-05-14 18:23 ` z411 [this message]
2024-05-14 18:23 ` z411
2024-05-14 18:28 ` z411
2024-05-14 18:28 ` z411
2024-05-14 18:29 ` z411
2024-05-14 20:03 ` classabbyamp
2024-05-15  9:54 ` Luciogi
2024-05-15 12:04 ` Luciogi
2024-05-15 13:30 ` [ISSUE] [CLOSED] " sgn

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=20240514182302.A52BB21E84@inbox.vuxu.org \
    --to=z411@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 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 NNTP newsgroup(s).