From: bakuhatu <bakuhatu@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pipewire screensharing not working in KDE
Date: Sun, 23 Jan 2022 23:14:21 +0100 [thread overview]
Message-ID: <20220123221421.VX3jkx7JM00OwlZmEhjXjaGEpMRDmem9TgSrA8P6mNE@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: 1674 bytes --]
New comment by bakuhatu on void-packages repository
https://github.com/void-linux/void-packages/issues/31274#issuecomment-1019578144
Comment:
I might have done the `QT_LOGGING_RULES` thing wrong last time.
I tried again with `QT_LOGGING_RULES="*.debug=true" /usr/lib64/libexec/xdg-desktop-portal-kde -v`
saw this:
`kf.crash: Could not find drkonqi in search paths: ("/usr/lib/libexec", "/usr/lib/qt5/libexec", "/usr/lib64/libexec")`
but no `kf.wayland.client: Unknown interface announced: zkde_screencast_unstable_v1`
Also, I tried looking at [waylandintegration.cpp](https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/blob/master/src/waylandintegration.cpp):
```
connect(m_registry, &KWayland::Client::Registry::interfaceAnnounced, this, [this](const QByteArray &interfaceName, quint32 name, quint32 version) {
if (interfaceName != "zkde_screencast_unstable_v1")
return;
m_screencasting = new Screencasting(m_registry, name, version, this);
});
```
This is the part @Johnnynator was talking about I guess.
I think it's connecting an interfaceAnnounced signal to m_registry, but I don't understand what the last two parameters are for and I can't find what `connect` is. My C++ knowledge is pretty basic so idk.
I couldn't find the `interfaceAnnounced` implementation, though I found the declaration in [kwayland/registry.h](https://github.com/KDE/kwayland/blob/10e3d60ab413e4389b9ecf88909f854f6eddbf1c/src/client/registry.h). I guess the implementation is the 4th argument to connect, but I don't know how to find where it calls that function/emits that signal to see what it's using as `interfaceName`.
next prev parent reply other threads:[~2022-01-23 22:14 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
2021-09-15 23:28 ` JaceHensley
2021-11-09 18:33 ` JaceHensley
2022-01-23 20:13 ` bakuhatu
2022-01-23 22:14 ` bakuhatu [this message]
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=20220123221421.VX3jkx7JM00OwlZmEhjXjaGEpMRDmem9TgSrA8P6mNE@z \
--to=bakuhatu@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).