[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1109233: marked as done (kpipewire: bad backport of 0ac4aa41)

Your message dated Tue, 15 Jul 2025 15:04:26 +0000
with message-id <E1ubhCk-00DQWR-2s@fasolo.debian.org>
and subject line Bug#1109233: fixed in kpipewire 6.3.6-1
has caused the Debian Bug report #1109233,
regarding kpipewire: bad backport of 0ac4aa41
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1109233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109233
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: krdp
Version: 6.3.5-1
Severity: important


Dear Maintainer,

Using krdc as the client, and krdp as the server, I cannot send any input:
neither mouse nor keyboard events are forwarded to the remote Wayland session.

I have done some preliminary debugging, and I suspect this may be related to
Debian packaging, so I'd like to consult with the experts here before possibly
wasting upstream's time.

The long story short is: I can get this working by modifying PortalSession::sendEvent
and removing the test that encodedStream->isActive().  The code handling stream
activation (in kpipewire) has had an upstream commit applied to it, hence I am
bringing it to Debian first.

If I am reading PipeWireBaseEncodedStream::start in the kpipewire source code
correctly, there is supposed to be some callback in kpipewire
that sends PipeWireProduce::started which will cause m_active to be set to true.

Presumably, that m_produceThread never returns that value.

In particular, on the remote side I'm getting output like:

kpipewire_vaapi_logging: VAAPI: profile 14 is not supported by the device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: profile 14 is not supported by the device "/dev/dri/renderD128"
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
org.kde.krdp: New client connected:  Unspecified platform Unspecified version
org.kde.krdp: Video stream initialized
org.kde.krdp: Received caps:
org.kde.krdp:   RDPGFX_CAPVERSION_8 AVC: false YUV420: false
org.kde.krdp:   RDPGFX_CAPVERSION_81 AVC: true YUV420: true
org.kde.krdp:   RDPGFX_CAPVERSION_10 AVC: true YUV420: false
org.kde.krdp:   RDPGFX_CAPVERSION_101 AVC: true YUV420: false
org.kde.krdp:   RDPGFX_CAPVERSION_102 AVC: true YUV420: false
org.kde.krdp:   RDPGFX_CAPVERSION_103 AVC: true YUV420: false
org.kde.krdp:   RDPGFX_CAPVERSION_104 AVC: true YUV420: true
org.kde.krdp:   RDPGFX_CAPVERSION_105 AVC: true YUV420: true
org.kde.krdp:   RDPGFX_CAPVERSION_106 AVC: true YUV420: true
org.kde.krdp:   UNKNOWN_VERSION AVC: false YUV420: false
org.kde.krdp:   RDPGFX_CAPVERSION_107 AVC: true YUV420: true
org.kde.krdp: Selected caps: RDPGFX_CAPVERSION_107
[AVHWDeviceContext @ 0x7f21d4059ac0] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

Is it possible that this initialization failure is preventing the active state from being set?
I'd really rather not start recompiling libraries to figure that out.  The above could just be
a red-herring, and something else is preventing PipeWireProduce::started from being sent.

In any case, I'm happy to try out other patches.  I'd also be curious to know if this problem is
unique to me, or if other people are experiencing this.  In particular, this is different
from 1093137, because only the keyboard is broken in that bug (whereas all input is being blocked
because isActive is false in my case).

I'm additionally puzzled that simply removing the isActive guard worked (shouldn't a bunch of
other things be broken if the pipewire stream didn't start correctly?).

Any help is appreciated.

Best,
Antonio Russo

--- End Message ---
--- Begin Message --- 
Source: kpipewire
Source-Version: 6.3.6-1
Done: Aurélien COUDERC <coucouf@debian.org>

We believe that the bug you reported is fixed in the latest version of
kpipewire, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1109233@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurélien COUDERC <coucouf@debian.org> (supplier of updated kpipewire package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 15 Jul 2025 16:45:40 +0200
Source: kpipewire
Architecture: source
Version: 6.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Aurélien COUDERC <coucouf@debian.org>
Closes: 1109233
Changes:
 kpipewire (6.3.6-1) unstable; urgency=medium
 .
   [ Aurélien COUDERC ]
   * Fix incorrect backport of commit 0ac4aa41 that broke desktop
     sharing. (Closes: #1109233, thanks Antonio Russo for the detailed
     analysis !)
   * New upstream release (6.3.6).
     - Fix build with Qt 6.10.
   * Refresh patches.
   * Backport upstream commit: [9fe7a568] Adjust timers from the correct
     thread
Checksums-Sha1:
 528fa2910590de9183a4eb7bc5bfd3beb11c69a3 3302 kpipewire_6.3.6-1.dsc
 7f460e32a8a2553c8e70aae2080d9387951e978d 152344 kpipewire_6.3.6.orig.tar.xz
 b5fe67e1173cd116b05a538a6cd61edece47c75f 488 kpipewire_6.3.6.orig.tar.xz.asc
 1ed6750b891dcb672196e5109b5b1d697e9f21e0 26300 kpipewire_6.3.6-1.debian.tar.xz
 f5d6a0dcb1c1bc94535ef5cafca393d2b7b6def2 22551 kpipewire_6.3.6-1_amd64.buildinfo
Checksums-Sha256:
 5b961ffb3424cf7436ac38cc266d83d908af23c698651e249945e24db1a7cfb0 3302 kpipewire_6.3.6-1.dsc
 624fda643619b546ea40cf552a4e378279978b71374342d842d8a590c4304ab5 152344 kpipewire_6.3.6.orig.tar.xz
 80afcaf9a9338fba10dab3488004165677c3e0f6a3301e1da304a379a5ab7b25 488 kpipewire_6.3.6.orig.tar.xz.asc
 3a72ae758225d5aa7cdb06f96d0b177eae4bedeffbd54116c7b317d9c32d05f1 26300 kpipewire_6.3.6-1.debian.tar.xz
 34021bfa20f376ab59957387c29f2e48ba646552c71eda2fa08d4ddfe9fe5e75 22551 kpipewire_6.3.6-1_amd64.buildinfo
Files:
 d21da9b68d1e97d4ab407bb6d92bf3d5 3302 libs optional kpipewire_6.3.6-1.dsc
 dd14db52ddb1a9bbabe6fa99e5d7be91 152344 libs optional kpipewire_6.3.6.orig.tar.xz
 e10688c6a7aa45fba6e5cd2fe78c6b98 488 libs optional kpipewire_6.3.6.orig.tar.xz.asc
 bac2f58438be40bb51ffa0d92ed0bf0f 26300 libs optional kpipewire_6.3.6-1.debian.tar.xz
 0ceb915063ba7eff0e0fb986e0f88afe 22551 libs optional kpipewire_6.3.6-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmh2adkTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJJBoEACmZQeA07rfZBsKg2ss77LQe+mibyq/
n6cyokRMg05mqN14CRMXv5bP7zlRMi3b+h+uJ0EWPxCd1zd4e1Hvd+/PtUD0zgFD
46oRxr9qP/gSNQs2OxYdeHgKYv6IkYXJ34Ymm2mp2/cyK4Gh2KeDFJAFtP27AxvK
5eJBmnCqr3iS4wKjexCibFvVDxG/wYS6wzC838m5hPVusJqu1sjkNys/Te/SFkjU
wXWiAPxH7q4N/9wKS1ftH/zwTxCCUMW3w/KDFOkjcKeacdarcr6UQLg7hg97ktCN
sjHid2nhiO9JDnl53Z+dab2I987NtDy7zvyXCvdO9u8pDukApMjcPKcFnvAqpKUU
2ALZ12XwwX3AVlgFAIDsj6FWiwRWe/OxzARz5TI0oGMbcDqTU5ZzlKxoSxtzdRsj
TXKLFZyx1d7C6TKsfRJ10BjirFuO5/Ej5ibEGOqjDnQcB4UkETP3gO+90/5D/y+M
8gSMM7GyxenhKj0l9TIUA7Ceq0HiKkFEXsjxB80s19xtUSFDO4ffsv1tbA5smGOF
d7Rl9wAgUFlbLnryjfriFkIgi1h3PiOl4u9f5TviMwW3CQZQld4IQUw4KKFIaz/Z
tTJJdaSnXsSa3CkF9gETC5F4cWqvzN6EMrAAOB3cBHUx84j6RpBvDzpR1WyMfPN1
Npt+saqhtsgZtA==
=gEEJ
-----END PGP SIGNATURE-----

Attachment: pgp9ndXdsihQh.pgp
Description: PGP signature


--- End Message ---
Reply to: