From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pipewire screensharing not working in KDE
Date: Thu, 16 Sep 2021 01:11:47 +0200 [thread overview]
Message-ID: <20210915231147.4ohGTcy0GJCaXDsOkym66IA-PplM_6M-8spaNv9yVtM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31274@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/31274#issuecomment-920452751
Comment:
I'm not sure yet where the issue is. `xdg-desktop-portal-kde` does not motivate kf.wayland.client enough to announce `zkde_screencast_unstable_v1`. so the ` m_screencasting = new Screencasting(m_registry, name, version, this);` line will never be called.
The autotest `testScreencastV1Interface` from `kwayland-server` on the other hand does manage to get the kwayland lib to announce screencast and does not fail. I need to check where the two differ and (except the obvious parts).
Another note for myself `QT_LOGGING_RULES="*.debug=true"` is pretty useful to get more verbose log, we want to see a line containing `kf.wayland.client: Unknown interface announced: zkde_screencast_unstable_v1` in the output
next prev parent reply other threads:[~2021-09-15 23:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 12:33 [ISSUE] " marcschulze98
2021-06-23 1:46 ` HadetTheUndying
2021-06-23 10:29 ` paper42
2021-06-23 11:03 ` Johnnynator
2021-06-23 11:04 ` Johnnynator
2021-06-23 17:16 ` Johnnynator
2021-06-24 10:53 ` paper42
2021-09-14 19:55 ` JaceHensley
2021-09-15 23:11 ` Johnnynator [this message]
2021-09-15 23:28 ` JaceHensley
2021-11-09 18:33 ` JaceHensley
2022-01-23 20:13 ` bakuhatu
2022-01-23 22:14 ` bakuhatu
2022-01-24 18:54 ` JaceHensley
2022-01-24 19:21 ` bakuhatu
2022-01-24 19:54 ` bakuhatu
2022-02-06 18:41 ` russnes
2022-02-07 23:34 ` bakuhatu
2022-02-11 17:05 ` JaceHensley
2022-02-11 17:58 ` Johnnynator
2022-02-11 20:12 ` JaceHensley
2022-02-11 23:45 ` Johnnynator
2022-02-15 20:48 ` [ISSUE] [CLOSED] " Johnnynator
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=20210915231147.4ohGTcy0GJCaXDsOkym66IA-PplM_6M-8spaNv9yVtM@z \
--to=johnnynator@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).