Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland

2023-08-10 Thread Lisandro Damián Nicanor Pérez Meyer
Hi!

On Thu, 10 Aug 2023 at 19:21, Nazar Zhuk  wrote:
>
> On 8/10/23 14:45, Lisandro Damian Nicanor Perez Meyer wrote:
> > I can agree that something in Plasma should depend/recommend xdg-desktop-
> > portal-kde.  But neither KDE+Wayland nor pipewire are defaults for Debian, 
> > so
> > users wanting to use them are expected to do some work. Granted, it would be
> > just awesome if no action would be required, but that is sadly not the case
> > here. I am so downgrading this bug to normal.
>
> KDE is an option you can pick in the installer, which is what I did. It
> shouldn't require a user to know what other dependencies to install
> after with apt. Even if installing plasma-desktop later with apt it
> should have all the dependencies.

Right, but with that you should get X11 by default, not wayland.

> > I would argue that this bug should be retitled to only care about the xdg-
> > desktop-portal-kde package.
>
> xdg-desktop-portal-kde was originally installed. pipewire wasn't.

xdg-d-p-kde: cool! That's pretty good to read!
pipewire: expected, not the default sound subsystem for bookworm.

-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/



Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland

2023-08-10 Thread Nazar Zhuk

On 8/10/23 14:45, Lisandro Damian Nicanor Perez Meyer wrote:

I can agree that something in Plasma should depend/recommend xdg-desktop-
portal-kde.  But neither KDE+Wayland nor pipewire are defaults for Debian, so
users wanting to use them are expected to do some work. Granted, it would be
just awesome if no action would be required, but that is sadly not the case
here. I am so downgrading this bug to normal.


KDE is an option you can pick in the installer, which is what I did. It 
shouldn't require a user to know what other dependencies to install 
after with apt. Even if installing plasma-desktop later with apt it 
should have all the dependencies.



I would argue that this bug should be retitled to only care about the xdg-
desktop-portal-kde package.


xdg-desktop-portal-kde was originally installed. pipewire wasn't.

--
Nazar



Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland

2023-08-10 Thread Lisandro Damian Nicanor Perez Meyer
severity 1043424 normal
thanks

Hi!

On jueves, 10 de agosto de 2023 15:19:04 -03 Nazar Zhuk wrote:
> Package: plasma-desktop
> Version: 4:5.27.5-2
> Severity: important
> X-Debbugs-Cc: nazar@zhuk.online
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>I attempted screen sharing in Zoom on a fresh install of Debian 12
>with KDE Plasma under Wayland.
> 
>* What was the outcome of this action?
>KDE window allowed me to pick a screen or a window to share. It did
>not show previews. Upon selection the error was shown:
>KDE Portal Integration
>Failed to start screencasting
>Failed to create PipeWire context
> 
>* What outcome did you expect instead?
>I expected the screen/window to be shared.
> 
> I tested screen capture in
> https://mozilla.github.io/webrtc-landing/gum_test.html to make sure this
> isn't a Zoom issue. Same outcome.
> 
> After some searching and digging the issue appears to be that pipewire
> was not installed.
> 
> This fixed the problem:
> 
> sudo apt install pipewire
> systemctl --user start pipewire
> 
> pipewire should be a dependency of plasma-desktop or one of it's
> dependencies so this works out of the box.
> 
> Marking this as important since screen sharing is a must for a desktop OS
> in business.

I can agree that something in Plasma should depend/recommend xdg-desktop-
portal-kde.  But neither KDE+Wayland nor pipewire are defaults for Debian, so 
users wanting to use them are expected to do some work. Granted, it would be 
just awesome if no action would be required, but that is sadly not the case 
here. I am so downgrading this bug to normal.

I would argue that this bug should be retitled to only care about the xdg-
desktop-portal-kde package.

Kinds regards, Lisandro.





signature.asc
Description: This is a digitally signed message part.


Processed: Re: Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland

2023-08-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1043424 normal
Bug #1043424 [plasma-desktop] plasma-desktop: Missing dependency on pipewire 
breaks screen sharing under Wayland
Severity set to 'normal' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1043424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#809367: marked as done (libqt5gui5: XEMBED interop with gtksocket broken)

2023-08-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Aug 2023 15:45:12 -0300
with message-id <2725206.mvXUDI8C0e@minerva>
and subject line Re: Bug#809367: libqt5gui5: XEMBED interop with gtksocket 
broken
has caused the Debian Bug report #809367,
regarding libqt5gui5: XEMBED interop with gtksocket broken
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 ow...@bugs.debian.org
immediately.)


-- 
809367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5gui5
Version: 5.5.1+dfsg-10
Severity: normal

This bug appears when one embeds a QWindow inside a GTK socket container
using the functions QWindow::setParent and QWindow::fromWinId().
According to the doc, the size of the QWindow should track the size of the 
container.
This used to work with Qt-5.2 and no longer works with this version of Qt.

Here are the replication instructions:

* The following python program creates a window with a gtk socket
  and prints the window id of the socket

---
#!/usr/bin/env python

import gtk, sys, string

class Socket:
def __init__(self):
window = gtk.Window() 
window.set_default_size(200, 200) 
socket = gtk.Socket()
window.add(socket)
print(socket.get_id())
window.connect("destroy", lambda w: gtk.main_quit())
socket.connect("destroy", lambda w: gtk.main_quit())
socket.connect("plug-added", self.plugged_event)
socket.connect("plug-removed", self.unplugged_event)
window.show_all()

def plugged_event(self, widget):
print "A plug has been inserted."

def unplugged_event(self, widget):
print "A plug has been removed."
return True

Socket()
gtk.main()
---

* The following Qt program tries to embed itself
  into the container whose id is passed on the command line.

---
#include 
#include 
#include 
#include 
#include 
#include 

int main(int argc, char **argv)
{
  QApplication app(argc,argv);
  long wid = app.arguments().at(1).toLong(0,0);
  QLabel *lbl = new QLabel();
  lbl->setText("here");
  lbl->setAlignment(Qt::AlignCenter);
  lbl->winId();
  QWindow *wlbl = lbl->windowHandle();
  wlbl->setParent(QWindow::fromWinId(wid));
  lbl->show();
  app.exec();
}
---

* To reproduce, open a terminal window, run "gtksocket.py"
  and record the printed socket window id. This creates
  a toplevel window containing the socket. In a second terminal window,
  run "plug ".
  The label text "here" appears in socket window.

* Under Qt-5.2, the label text appears in the middle of
  the window because the QLabel widget has the same size
  as the gtksocket window.  Resizing the gtksocket window
  keeps the text "here" in the middle of the window because
  the QLabel widget size tracks that of the socker.

* Under Qt-5.5.1+dfsg-10, the label text appears in the top left
  corner of the window and stays there. Using program "xwininfo"
  shows that the size of the underlying X11 window effectively
  tracks the size of the gtksocket. But it appears that
  the size of the QWindow and of the associated QLabel
  remains stuck to its initial value.


As a consequence, XEMBED interop is broken in this version of Qt.




-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5gui5 depends on:
ii  fontconfig   2.11.0-6.3
ii  libc62.21-4
ii  libegl1-mesa [libegl1-x11]   11.0.8-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6.1-0.1
ii  libgl1-mesa-glx [libgl1] 11.0.8-1
ii  libglib2.0-0 2.46.2-1
ii  libharfbuzz0b1.0.1-1+b1
ii  libinput10   1.1.3-1
ii  libjpeg62-turbo  1:1.4.1-2
ii  libmtdev11.1.5-1
ii  libpng12-0   1.2.54-1
ii  libqt5core5a [qtbase-abi-5-5-1]  5.5.1+dfsg-10
ii  libqt5dbus5  5.5.1+dfsg-10
ii  libqt5network5   5.5.1+dfsg-10
ii  libstdc++6   5.3.1-4
ii  libudev1 228-2+b1
ii  libx11-6 2:1.6.3-1
ii  libxkbcommon00.5.0-1
ii  libxrender1  1:0.9.9-2

Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland

2023-08-10 Thread Nazar Zhuk
Package: plasma-desktop
Version: 4:5.27.5-2
Severity: important
X-Debbugs-Cc: nazar@zhuk.online

Dear Maintainer,

   * What led up to the situation?
   I attempted screen sharing in Zoom on a fresh install of Debian 12
   with KDE Plasma under Wayland.

   * What was the outcome of this action?
   KDE window allowed me to pick a screen or a window to share. It did
   not show previews. Upon selection the error was shown:
   KDE Portal Integration
   Failed to start screencasting
   Failed to create PipeWire context

   * What outcome did you expect instead?
   I expected the screen/window to be shared.

I tested screen capture in
https://mozilla.github.io/webrtc-landing/gum_test.html to make sure this
isn't a Zoom issue. Same outcome.

After some searching and digging the issue appears to be that pipewire
was not installed.

This fixed the problem:

sudo apt install pipewire
systemctl --user start pipewire

pipewire should be a dependency of plasma-desktop or one of it's
dependencies so this works out of the box.

Marking this as important since screen sharing is a must for a desktop OS
in business.


-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-desktop depends on:
ii  accountsservice  22.08.8-6
ii  breeze   4:5.27.5-2
ii  kactivitymanagerd5.27.5-2
ii  kde-cli-tools4:5.27.5.1-2
ii  kded55.103.0-1
ii  kio  5.103.0-1
ii  kpackagetool55.103.0-1
ii  layer-shell-qt   5.27.5-2
ii  libaccounts-qt5-11.16-2
ii  libc62.36-9+deb12u1
ii  libglib2.0-0 2.74.6-2
ii  libibus-1.0-51.5.27-5
ii  libkaccounts24:22.12.3-1
ii  libkf5activities55.103.0-1
ii  libkf5activitiesstats1   5.103.0-1
ii  libkf5authcore5  5.103.0-1
ii  libkf5baloo5 5.103.0-2
ii  libkf5bookmarks5 5.103.0-1
ii  libkf5codecs55.103.0-1
ii  libkf5completion55.103.0-1
ii  libkf5configcore55.103.0-2
ii  libkf5configgui5 5.103.0-2
ii  libkf5configwidgets5 5.103.0-1
ii  libkf5coreaddons55.103.0-1
ii  libkf5crash5 5.103.0-1
ii  libkf5dbusaddons55.103.0-1
ii  libkf5globalaccel-bin5.103.0-1
ii  libkf5globalaccel5   5.103.0-1
ii  libkf5guiaddons5 5.103.0-1
ii  libkf5i18n5  5.103.0-1
ii  libkf5iconthemes55.103.0-1
ii  libkf5itemviews5 5.103.0-1
ii  libkf5jobwidgets55.103.0-1
ii  libkf5kcmutils5  5.103.0-3
ii  libkf5kcmutilscore5  5.103.0-3
ii  libkf5kdelibs4support5   5.103.0-1
ii  libkf5kiocore5   5.103.0-1
ii  libkf5kiofilewidgets55.103.0-1
ii  libkf5kiogui55.103.0-1
ii  libkf5kiowidgets55.103.0-1
ii  libkf5newstuffcore5  5.103.0-1
ii  libkf5notifications5 5.103.0-1
ii  libkf5notifyconfig5  5.103.0-1
ii  libkf5package5   5.103.0-1
ii  libkf5plasma55.103.0-1
ii  libkf5plasmaquick5   5.103.0-1
ii  libkf5quickaddons5   5.103.0-1
ii  libkf5runner55.103.0-1
ii  libkf5service-bin5.103.0-1
ii  libkf5service5   5.103.0-1
ii  libkf5solid5 5.103.0-1
ii  libkf5sonnetcore55.103.0-1
ii  libkf5sonnetui5  5.103.0-1
ii  libkf5widgetsaddons5 5.103.0-1
ii  libkf5windowsystem5  5.103.0-1
ii  libkf5xmlgui55.103.0-1
ii  libkworkspace5-5 4:5.27.5-2
ii  libnotificationmanager1  4:5.27.5-2
ii  libpackagekitqt5-1   1.1.1-1
ii  libphonon4qt5-4  4:4.11.1-4
ii  libprocesscore9  4:5.27.5-2
ii  libqt5concurrent5 

[bts-link] source package qtbase-opensource-src

2023-08-10 Thread debian-bts-link
#
# bts-link upstream status pull for source package qtbase-opensource-src
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #809367 (http://bugs.debian.org/809367)
# Bug title: libqt5gui5: XEMBED interop with gtksocket broken
#  * https://bugreports.qt.io/browse/QTBUG-50212
#  * remote status changed: Reported -> Closed
#  * remote resolution changed: (?) -> Fixed
#  * closed upstream
tags 809367 + fixed-upstream
usertags 809367 - status-Reported
usertags 809367 + status-Closed resolution-Fixed

thanks



Processed: [bts-link] source package qtbase-opensource-src

2023-08-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package qtbase-opensource-src
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #809367 (http://bugs.debian.org/809367)
> # Bug title: libqt5gui5: XEMBED interop with gtksocket broken
> #  * https://bugreports.qt.io/browse/QTBUG-50212
> #  * remote status changed: Reported -> Closed
> #  * remote resolution changed: (?) -> Fixed
> #  * closed upstream
> tags 809367 + fixed-upstream
Bug #809367 [libqt5gui5] libqt5gui5: XEMBED interop with gtksocket broken
Added tag(s) fixed-upstream.
> usertags 809367 - status-Reported
Usertags were: status-Reported.
There are now no usertags set.
> usertags 809367 + status-Closed resolution-Fixed
There were no usertags set.
Usertags are now: resolution-Fixed status-Closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
809367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems