Bug#1073512: kwin-wayland: when opening a new window above an existing one the lower one gets the focus
Package: kwin-wayland Version: 4:5.27.11-1+b1 Severity: important I have thunderbird open full screen. When opening a new window via Ctrl-N to send an email the below window gets the focus. This is extremly annoying because thunderbird might perform actions on the list of emails below the new-mail window if you start typing without changing the focus with a mouse click. Window behaviou is configured "Activation on mouse contact - priority for mouse". If I open the new-mail window by mouse click it works as expected – the new window gets the focus. Sometimes also opening the window by keyboard works but most time it results in focus for the thunderbird main window. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 kwin-wayland depends on: ii kwayland-integration 5.27.11-1+b1 ii kwin-common 4:5.27.11-1+b1 ii libc62.38-13 ii libcap2-bin 1:2.66-5 ii libepoxy01.5.10-1+b2 ii libfontconfig1 2.15.0-1.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libkdecorations2-5v5 4:5.27.11-1 ii libkf5configcore55.115.0-2 ii libkf5configgui5 5.115.0-2 ii libkf5configwidgets5 5.115.0-2 ii libkf5coreaddons55.115.0-2 ii libkf5crash5 5.115.0-2 ii libkf5dbusaddons55.115.0-2 ii libkf5globalaccel-bin5.115.0-2 ii libkf5globalaccel5 5.115.0-2 ii libkf5globalaccelprivate55.115.0-2 ii libkf5i18n5 5.115.1-2+b1 ii libkf5idletime5 5.115.0-2 ii libkf5notifications5 5.115.0-2 ii libkf5plasma55.115.0-2 ii libkf5service-bin5.115.0-2 ii libkf5service5 5.115.0-2 ii libkf5windowsystem5 5.115.0-2 ii libkwineffects14 4:5.27.11-1+b1 ii libkwinglutils14 4:5.27.11-1+b1 ii libpipewire-0.3-0t64 1.0.7-1 ii libqaccessibilityclient-qt5-00.6.0-1+b1 ii libqt5core5t64 [qtbase-abi-5-15-13] 5.15.13+dfsg-2 ii libqt5dbus5t64 5.15.13+dfsg-2 ii libqt5gui5t645.15.13+dfsg-2 ii libqt5network5t645.15.13+dfsg-2 ii libqt5qml5 5.15.13+dfsg-2 ii libqt5quick5 5.15.13+dfsg-2 ii libqt5widgets5t645.15.13+dfsg-2 ii libstdc++6 14-20240330-1 ii libxcb-randr01.17.0-2 ii libxcb-xfixes0 1.17.0-2 ii libxcb1 1.17.0-2 ii xwayland 2:24.1.0-1 kwin-wayland recommends no packages. kwin-wayland suggests no packages. -- no debconf information OpenPGP_signature.asc Description: OpenPGP digital signature
Processing of plasma-wayland-protocols_1.13.0-1_source.changes
plasma-wayland-protocols_1.13.0-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.13.0-1.dsc plasma-wayland-protocols_1.13.0.orig.tar.xz plasma-wayland-protocols_1.13.0.orig.tar.xz.asc plasma-wayland-protocols_1.13.0-1.debian.tar.xz plasma-wayland-protocols_1.13.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
plasma-wayland-protocols_1.13.0-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 May 2024 23:23:20 +0200 Source: plasma-wayland-protocols Architecture: source Version: 1.13.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: plasma-wayland-protocols (1.13.0-1) unstable; urgency=medium . [ Aurélien COUDERC ] * New upstream release (1.13.0). * Bump Standards-Version to 4.7.0, no change required. Checksums-Sha1: e6c1f0c198f9f2aad3223a5fb0771370b575bf60 2545 plasma-wayland-protocols_1.13.0-1.dsc e8458516bd326338a57b6bf81cbb357faf5c7549 45016 plasma-wayland-protocols_1.13.0.orig.tar.xz 5a9af4e65a69e7d3b1c133f46d149409719e1c08 833 plasma-wayland-protocols_1.13.0.orig.tar.xz.asc af9a5dc3d43f66e085a88852e8adc68c04987cf2 8204 plasma-wayland-protocols_1.13.0-1.debian.tar.xz a7cb17a1c65f1cc4d18997a4531355c052ee827a 10962 plasma-wayland-protocols_1.13.0-1_amd64.buildinfo Checksums-Sha256: c1c384e15367b9cfc9b76cc77edd6c5f8b38ca0d455f3987d3296749c125e527 2545 plasma-wayland-protocols_1.13.0-1.dsc dd477e352f5ff6e6ac686286c4b22b19bf5a4921b85ee5a7da02bb7aa115d57e 45016 plasma-wayland-protocols_1.13.0.orig.tar.xz 1cd672afdb24505b7488bf8d0fe4ed6b489c243e70644c89bb3f7167ea23d429 833 plasma-wayland-protocols_1.13.0.orig.tar.xz.asc b8fe02dde9b263ed5c39f4869745d02cbfa1703d3015b0851a7e5b13b877a710 8204 plasma-wayland-protocols_1.13.0-1.debian.tar.xz d29db465ac7db03c6305c6b8a3b9c52aa6f2b7780339f77b1804b685495cd519 10962 plasma-wayland-protocols_1.13.0-1_amd64.buildinfo Files: 2901e93df614ee3d7f389df3b17dc0ad 2545 libdevel optional plasma-wayland-protocols_1.13.0-1.dsc 5d30de6367ab1ff92b2ece7b159b3c8b 45016 libdevel optional plasma-wayland-protocols_1.13.0.orig.tar.xz 1f482fcb9375a89c65f995d4b966f968 833 libdevel optional plasma-wayland-protocols_1.13.0.orig.tar.xz.asc 9006e9994c81b353380c240fb6babf55 8204 libdevel optional plasma-wayland-protocols_1.13.0-1.debian.tar.xz e4f820ca42027a329750baf8ad8fa321 10962 libdevel optional plasma-wayland-protocols_1.13.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmZbF3MTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJF3IEADTrzT4B7dVYMAof6X/BioqWSvGRoVV GRwYF+HaUjSkOVeWP72l9++pnprLQW6hTaTeBSo1suG4lJSI6mIWthj2FoTg8yCS JNir3WAudiGup09n0a7i73+SCi82Yo8s43nAptimjBRQwVBk72PwnxUE6fCWlQSn hXcxZgdsAHqSlHwzeyvZvRdE97W2tesb+L82TF5PGyMOMw/+R8eE2JEaq1b3Qwz2 g/WqJvsLRExhWNk2gr3atiw/DFC3QkCUNPeSsf6bkOuk7CwGUXwfFhUyC6djjdtO V59QTJDUFrULkAF2amEzbNqikuBbmRQox73nVUY+cAwewtuiamkJ2cRAVEov2ylL fKsB8bI0FXn02tFy998HNYihiw/Sq3PeDNs7apnue6fGyCeuThCJHbKxN0P1yg1b lNjSFymktC30oXyfg+12tj29gjbvJnSEY+f+R4KwuejnbOeH0t3TxM+ioehFRRyv kXFUjLFhR9XbzZLYmRNHvCDlR3WzXDHsuq/TChvY33HXAkrPkeH1i8nQ1IA4Ru2F zsTizzLPVJRCDk/bzX9sqU+IxtQSyKUQBkxA1K21jzbn+JXRGABYsA9hkCn7UtMh JaOXZUZpJbWyc53Hw37Tm2pS08fkO0u72KROKUKONvy89tYcZeoUVNmRiwHDbdHm +1xOBKjAaCVNpQ== =sgum -END PGP SIGNATURE- pgpwljNw6IYlt.pgp Description: PGP signature
Bug#1068784: When configuring Wayland to be the default at the login screen this doesn't change the session the user is automatically logged into
Package: sddm Version: 0.19.0-5 When configuring Wayland to be the default at the login screen (dropdown in the upper left) as recommended at places where people asked about how to switch from X11 to Wayland, this doesn't change the session the user is automatically logged into. I think it should be changed or the user be asked if they'd like to change the default after auto-login if they changed it at the lockscreen. Here I got this reply https://github.com/sddm/sddm/issues/1912 : >If you set > >[Autologin] >Session= > >it'll use the last used session for autologin. kcm_sddm does not support that, >so you'll have to put that into /etc/sddm.conf.d/y_autologin.conf to override >the value from kde_settings.conf.
Re: Help in porting to wayland?
Le 23 mars 2024 12:51:18 GMT+01:00, "Aurélien COUDERC" a écrit : > >Le 23 mars 2024 04:25:07 GMT+01:00, Salvo Tomaselli a >écrit : >>Hello, Hi ! >>I maintain trabucco, which uses XGrabKey() to show up on the screen with a >>shortcut. >> >>Naturally, this doesn't work if a wayland session is in use. >> >>I could not find any guide on what should I replace it with. >> >>Any pointers on where to look to do that? No idea but I'm transferring to the packaging discussion list in case someone has one. Happy hacking ! -- Aurélien
Bug#1066936: Qt5 Wayland applications with touch support crash
Package: libqt5waylandclient5
Version: 5.15.8-2
Native Wayland Qt5 applications with touchscreen support have a nasty tendency
to segfault while receiving touch input, especially when one is trying to write
using a stylus as the palm also makes contact with the touchscreen. This issue
has only been recently fixed in Qt 6.7 and as far as I know there is no
upstream fix at the moment for Qt 5.15. An if statement (highlighted with
pointer arrow) is added to function QWaylandInputDevice::Touch::touch_frame()
in qwaylandinputdevice.cpp in Qt 6.7 to fix the bug:
if (mFocus) {
// Returns a reference to the last item in the list. The list must not
be empty.
// If the list can be empty, call isEmpty() before calling this
function.
// See: https://doc.qt.io/qt-5.15/qlist.html#last
-> if (mPendingTouchPoints.empty())
return;
const QWindowSystemInterface::TouchPoint =
mPendingTouchPoints.constLast();
I encountered the issue using MrWriter, compiled from source, on Ubuntu 22.04
(linked against Qt 5.15.3). Said issue was severe enough in my experience to
interfere with day-to-day activities. As Ubuntu is downstream to Debian, I
thought it would be better if I report the bug here.
Bug#1063145: x11-to-wayland-regression: clipboard copy-paste from chromium to konsole doesn't work
Package: kwin-wayland Version: 4:5.27.10-1 Severity: normal This is X11-to-Wayland regression. Steps to reproduce: - Start KDE in Wayland mode - Open konsole window - Open chromium window - Copy to clipboard some text from chromium - Close chromium - Try to paste the text to konsole This will not work. I use up-to-date sid. Versions: kwin-wayland 4:5.27.10-1 xwayland 2:23.2.4-1 konsole4:23.08.1-1 chromium 121.0.6167.139-1 plasma-workspace-wayland 4:5.27.10-3 qtwayland5:amd64 5.15.10-2 xserver-xorg 1:7.7+23 kwin-x11 4:5.27.10-1 The bug is not reproducible with X11! -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.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 kwin-wayland depends on: ii kwayland-integration 5.27.10-1 ii kwin-common4:5.27.10-1 ii libc6 2.37-15 ii libcap2-bin1:2.66-4+b2 ii libepoxy0 1.5.10-1+b2 ii libfontconfig1 2.14.2-6+b1 ii libfreetype6 2.13.2+dfsg-1+b1 ii libkdecorations2-5v5 4:5.27.10-1 ii libkf5configcore5 5.107.0-1 ii libkf5configgui5 5.107.0-1 ii libkf5configwidgets5 5.107.0-2 ii libkf5coreaddons5 5.107.0-1 ii libkf5crash5 5.107.0-1 ii libkf5dbusaddons5 5.107.0-1 ii libkf5globalaccel-bin 5.107.0-2 ii libkf5globalaccel5 5.107.0-2 ii libkf5globalaccelprivate5 5.107.0-2 ii libkf5i18n55.107.0-1+b1 ii libkf5idletime55.107.0-1 ii libkf5notifications5 5.107.0-1 ii libkf5plasma5 5.107.0-1 ii libkf5service-bin 5.107.0-1 ii libkf5service5 5.107.0-1 ii libkf5windowsystem55.107.0-1 ii libkwineffects14 4:5.27.10-1 ii libkwinglutils14 4:5.27.10-1 ii libpipewire-0.3-0 1.0.3-1 ii libqaccessibilityclient-qt5-0 0.6.0-1 ii libqt5core5a [qtbase-abi-5-15-10] 5.15.10+dfsg-6 ii libqt5dbus55.15.10+dfsg-6 ii libqt5gui5 5.15.10+dfsg-6 ii libqt5network5 5.15.10+dfsg-6 ii libqt5qml5 5.15.10+dfsg-2 ii libqt5quick5 5.15.10+dfsg-2 ii libqt5widgets5 5.15.10+dfsg-6 ii libstdc++6 14-20240201-3 ii libxcb-randr0 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb11.15-1 ii xwayland 2:23.2.4-1 kwin-wayland recommends no packages. kwin-wayland suggests no packages. -- no debconf information
Bug#1061166: qt6-gtk-platformtheme: GTK Theme not applied on wayland unless QT_QPA_PLATFORM=xcb is set
Package: qt6-gtk-platformtheme Version: 6.6.1+dfsg-6 Severity: normal X-Debbugs-Cc: koce...@tutanota.com Dear Maintainer, When using Gnome/Wayland, if you install qt6-gtk-platformtheme, and try to run qbittorrent for example, you can notice that it's using a generic qt6 theme, and not the one that the system is using. Cursor size is also messed up. This can be worked around by setting `QT_QPA_PLATFORM=xcb`. The environmental variable is not needed when using X11. Steps to reproduce: 1. Have a working GNOME setup 2. Log into a wayland session 3. Install qt6-gtk-platformtheme and qbittorrent 4. Run qbittorrent and notice that the theme is all messed up. 5. Try running it as follows: `QT_QPA_PLATFORM=xcb qbittorrent` or start it from an X11 session, and notice that the proper theming is applied. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 qt6-gtk-platformtheme depends on: ii libc6 2.37-13 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-02.78.3-1 ii libgtk-3-0 3.24.39-1 ii libpango-1.0-0 1.51.0+ds-3 ii libqt6core6 [qt6-base-private-abi] 6.6.1+dfsg-6 ii libqt6gui6 6.6.1+dfsg-6 ii libstdc++6 13.2.0-9 ii libx11-62:1.8.7-1 qt6-gtk-platformtheme recommends no packages. qt6-gtk-platformtheme suggests no packages. -- no debconf information
Bug#1061165: qt5-gtk-platformtheme: GTK Theme not applied on wayland unless QT_QPA_PLATFORM=xcb is set
Package: qt5-gtk-platformtheme Version: 5.15.10+dfsg-6 Severity: normal X-Debbugs-Cc: koce...@tutanota.com Dear Maintainer, When using Gnome/Wayland, if you install qt5-gtk-platformtheme, and try to run keepassxc for example, you can notice that it's using a generic qt5 theme, and not the one that the system is using. Cursor size is also messed up. This can be worked around by setting `QT_QPA_PLATFORM=xcb`. The environmental variable is not needed when using X11. Steps to reproduce: 1. Have a working GNOME setup 2. Log into a wayland session 3. Install qt5-gtk-platformtheme and keepassxc 4. Run keepassxc and notice that the theme is all messed up. 5. Try running it as follows: `QT_QPA_PLATFORM=xcb keepassxc` or start it from an X11 session, and notice that the proper theming is applied. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (10001, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 qt5-gtk-platformtheme depends on: ii libc6 2.37-13 ii libglib2.0-0 2.78.3-1 ii libgtk-3-0 3.24.39-1 ii libpango-1.0-0 1.51.0+ds-3 ii libqt5core5a [qtbase-abi-5-15-10] 5.15.10+dfsg-6 ii libqt5dbus55.15.10+dfsg-6 ii libqt5gui5 5.15.10+dfsg-6 ii libstdc++6 13.2.0-9 ii libx11-6 2:1.8.7-1 qt5-gtk-platformtheme recommends no packages. qt5-gtk-platformtheme suggests no packages. -- no debconf information
Bug#1059410: sddm: DisplayServer=wayland caused a complete lockout
Package: sddm Version: 0.20.0-2 Severity: important Dear Maintainer, Thank you for packaging SDDM. After creating a file named /etc/sddm.conf.d/use_wayland.conf with the following content: [General] DisplayServer=wayland SDDM showed a black screen and captured keyboard inputs preventing me from switching to the tty consoles, locking me out of the system. Rebooting multiple times did not help. (I had to resort to booting with systemd.unit=emergency.target) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sddm depends on: ii adduser 3.137 ii debconf [debconf-2.0] 1.5.82 ii libc6 2.37-13 ii libgcc-s1 13.2.0-8 ii libpam0g1.5.2-9.1 ii libqt5core5a5.15.10+dfsg-5 ii libqt5dbus5 5.15.10+dfsg-5 ii libqt5gui5 5.15.10+dfsg-5 ii libqt5network5 5.15.10+dfsg-5 ii libqt5qml5 5.15.10+dfsg-2 ii libqt5quick55.15.10+dfsg-2 ii libstdc++6 13.2.0-8 ii libsystemd0 255-1 ii libxau6 1:1.0.9-1 ii libxcb-xkb1 1.15-1 ii libxcb1 1.15-1 ii qml-module-qtquick2 5.15.10+dfsg-2 ii x11-common 1:7.7+23 ii xauth 1:1.1.2-1 ii xkb-data2.38-2 ii xserver-xorg [xserver] 1:7.7+23 Versions of packages sddm recommends: ii libpam-systemd 255-1 ii sddm-theme-debian-elarun [sddm-theme] 0.20.0-2 ii sddm-theme-maldives [sddm-theme] 0.20.0-2 ii sddm-theme-maui [sddm-theme] 0.20.0-2 ii sddm-theme-maya [sddm-theme] 0.20.0-2 Versions of packages sddm suggests: ii libpam-kwallet5 5.27.9-1 pn qtvirtualkeyboard-plugin -- debconf information: * shared/default-x-display-manager: sddm sddm/daemon_name: /usr/bin/sddm
Bug#1050821: marked as done (kmag does not work with wayland plasma shell. OK on X11)
Your message dated Sat, 7 Oct 2023 08:54:43 -0500 with message-id and subject line Bug reported upstream has caused the Debian Bug report #1050821, regarding kmag does not work with wayland plasma shell. OK on X11 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.) -- 1050821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kmag Version: 4:22.12.3-1 Severity: important Tags: upstream Dear Maintainer, * What led up to the situation? Attempted to use kmag to enlarge a portion of screen * What exactly did you do (or not do) that was effective (or ineffective)? When using the Plasma/Wayland shell, the program only presented a gray window and no enlarged mouse cursor. * What was the outcome of this action? kmag did not enlarge any part of the screen. Tried different focus and window options to no effect. (see screenshot) * What outcome did you expect instead? Under Plasma/X11 kmag functions as designed. (see screenshot) -- 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/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 kmag depends on: ii kio 5.103.0-1 ii libc6 2.36-9+deb12u1 ii libkf5configcore5 5.103.0-2 ii libkf5configgui5 5.103.0-2 ii libkf5configwidgets5 5.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libkf5kiocore5 5.103.0-1 ii libkf5widgetsaddons5 5.103.0-1 ii libkf5xmlgui5 5.103.0-1 ii libqaccessibilityclient-qt5-0 0.4.1-1+b1 ii libqt5core5a 5.15.8+dfsg-11 ii libqt5gui5 5.15.8+dfsg-11 ii libqt5printsupport5 5.15.8+dfsg-11 ii libqt5widgets5 5.15.8+dfsg-11 ii libstdc++6 12.2.0-14 kmag recommends no packages. kmag suggests no packages. -- no debconf information -- Peter Hyman (609)598-0262 (612)440-PETE (7383) --- End Message --- --- Begin Message --- This bug has already been reported to KDE and confirmed. Like with many X11 applications, kmag just won't work yet under Wayland. Closing here. https://bugs.kde.org/show_bug.cgi?id=438912 -- Peter Hyman--- End Message ---
Bug#1013222: marked as done (src:qt6-wayland: please package private headers)
Your message dated Tue, 26 Sep 2023 18:02:35 + with message-id and subject line Bug#1013222: fixed in qt6-wayland 6.4.2-4 has caused the Debian Bug report #1013222, regarding src:qt6-wayland: please package private headers 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.) -- 1013222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt6-wayland Severity: wishlist Dear Maintainer, Please package private QtWaylandClient headers and related CMake config. Telegram authors offer a forked plugin for XDG shell integration. In order to build the telegram-desktop package against Qt6 keeping all features with Wayland, the headers are necessary. signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: qt6-wayland Source-Version: 6.4.2-4 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of qt6-wayland, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated qt6-wayland 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Sep 2023 19:12:41 +0200 Source: qt6-wayland Binary: libqt6waylandclient6 libqt6waylandclient6-dbgsym libqt6waylandcompositor6 libqt6waylandcompositor6-dbgsym libqt6waylandeglclienthwintegration6 libqt6waylandeglclienthwintegration6-dbgsym libqt6waylandeglcompositorhwintegration6 libqt6waylandeglcompositorhwintegration6-dbgsym libqt6wlshellintegration6 libqt6wlshellintegration6-dbgsym qml6-module-qtwayland-client-texturesharing qml6-module-qtwayland-client-texturesharing-dbgsym qml6-module-qtwayland-compositor qml6-module-qtwayland-compositor-dbgsym qt6-wayland qt6-wayland-dbgsym qt6-wayland-dev qt6-wayland-dev-tools qt6-wayland-dev-tools-dbgsym qt6-wayland-doc qt6-wayland-doc-html qt6-wayland-examples qt6-wayland-examples-dbgsym qt6-wayland-private-dev Architecture: source amd64 all Version: 6.4.2-4 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Description: libqt6waylandclient6 - Qt 6 Wayland Client library libqt6waylandcompositor6 - Qt 6 Wayland Compositor library libqt6waylandeglclienthwintegration6 - Qt 6 Wayland WaylandEglClientHwIntegration library libqt6waylandeglcompositorhwintegration6 - Qt 6 Wayland WaylandEglCompositorHwIntegration library libqt6wlshellintegration6 - Qt 6 Wayland ShellIntegration library qml6-module-qtwayland-client-texturesharing - Qt 6 Wayland Shared Texture Provider QML module qml6-module-qtwayland-compositor - Qt 6 Wayland Compositor QML module qt6-wayland - Qt 6 Wayland platform plugin qt6-wayland-dev - Qt 6 Wayland - development files qt6-wayland-dev-tools - Qt 6 Wayland developer tools qt6-wayland-doc - Qt 6 wayland documentation qt6-wayland-doc-html - Qt 6 wayland HTML documentation qt6-wayland-examples - Qt 6 wayland examples qt6-wayland-private-dev - Qt 6 Wayland - private development files Closes: 1013222 Changes: qt6-wayland (6.4.2-4) experimental; urgency=medium . [ Patrick Franz ] * Add package for the private headers (Closes: #1013222). * Replace libfontconfig1-dev with libfontconfig-dev in the B-Ds as the former is superseded by the latter. Checksums-Sha1: af8848dd2e6a707c65094f26eecba039511252d3 3657 qt6-wayland_6.4.2-4.dsc 23bcda8a878acb8c5a52b1c8649f4a557a6ad031 47340 qt6-wayland_6.4.2-4.debian.tar.xz 54093cb612375144dfa2819810d2370a39c6a997 5588680 libqt6waylandclient6-dbgsym_6.4.2-4_amd64.deb 25c7883ce988e7f9c67321e71dac3be82bb1fc58 230824 libqt6waylandclient6_6.4.2-4_amd64.deb bb9ea33ab96d7eeba06ce507201aaf3bdc7a47f0 13451676 libqt6waylandcompositor6-dbgsym_6.4.2-4_amd64.deb 4cc26f76edcb0cc86da9151bff2c539f3d00a173 386708 libqt6waylandcompositor6_6.4.2-4_amd64.deb ef2772e5e4e164f75ecf2e1486420e9e2fabfafe 413920 libqt6waylandeglclienthwintegration6-dbgsym_6.4.2-4_amd64.deb b85ec2e282a699a227e3a04111a8835bd9e6aca9 19788 libqt6waylandeglclienthwintegration6_6.4.2
Bug#1050821: kmag does not work with wayland plasma shell. OK on X11
Package: kmag Version: 4:22.12.3-1 Severity: important Tags: upstream Dear Maintainer, * What led up to the situation? Attempted to use kmag to enlarge a portion of screen * What exactly did you do (or not do) that was effective (or ineffective)? When using the Plasma/Wayland shell, the program only presented a gray window and no enlarged mouse cursor. * What was the outcome of this action? kmag did not enlarge any part of the screen. Tried different focus and window options to no effect. (see screenshot) * What outcome did you expect instead? Under Plasma/X11 kmag functions as designed. (see screenshot) -- 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/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 kmag depends on: ii kio 5.103.0-1 ii libc6 2.36-9+deb12u1 ii libkf5configcore5 5.103.0-2 ii libkf5configgui5 5.103.0-2 ii libkf5configwidgets5 5.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libkf5kiocore5 5.103.0-1 ii libkf5widgetsaddons5 5.103.0-1 ii libkf5xmlgui5 5.103.0-1 ii libqaccessibilityclient-qt5-0 0.4.1-1+b1 ii libqt5core5a 5.15.8+dfsg-11 ii libqt5gui5 5.15.8+dfsg-11 ii libqt5printsupport5 5.15.8+dfsg-11 ii libqt5widgets5 5.15.8+dfsg-11 ii libstdc++6 12.2.0-14 kmag recommends no packages. kmag suggests no packages. -- no debconf information -- Peter Hyman (609)598-0262 (612)440-PETE (7383)
Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland
On 8/10/23 20:49, Lisandro Damián Nicanor Pérez Meyer wrote: pipewire: expected, not the default sound subsystem for bookworm. Screen sharing under KDE uses pipewire. That makes KDE dependent on pipewire, regardless of what the default is. Default desktop environment is Gnome, that doesn't mean other environments shouldn't install their dependencies. -- Nazar
Bug#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland
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
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
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
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#1043424: plasma-desktop: Missing dependency on pipewire breaks screen sharing under Wayland
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
Bug#1042285: marked as done (qt6-wayland: FTBFS: dh_missing: error: missing files, aborting)
Your message dated Tue, 01 Aug 2023 16:10:30 + with message-id and subject line Bug#1042285: fixed in qt6-wayland 6.4.2-2 has caused the Debian Bug report #1042285, regarding qt6-wayland: FTBFS: dh_missing: error: missing files, aborting 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.) -- 1042285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt6-wayland Version: 6.4.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Reproducible builds: remove build paths from .prl files > sed -i -e '/^QMAKE_PRL_BUILD_DIR/d' > debian/tmp/usr/lib/x86_64-linux-gnu/libQt6*.prl > make[1]: Leaving directory '/<>' >dh_install -O--buildsystem=cmake\+ninja >dh_installdocs -O--buildsystem=cmake\+ninja >dh_installchangelogs -O--buildsystem=cmake\+ninja >dh_installsystemduser -O--buildsystem=cmake\+ninja >dh_perl -O--buildsystem=cmake\+ninja >dh_link -O--buildsystem=cmake\+ninja >dh_strip_nondeterminism -O--buildsystem=cmake\+ninja >dh_compress -O--buildsystem=cmake\+ninja >dh_fixperms -O--buildsystem=cmake\+ninja >dh_missing -O--buildsystem=cmake\+ninja > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-extension/compositor/custom-extension-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-extension/cpp-client/custom-extension-cpp-client > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-extension/qml-client/custom-extension-qml-client > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-shell/client-plugin/libexampleshellplugin.so > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-shell/compositor/custom-shell-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/hwlayer-compositor/hwlayer-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/ivi-compositor/ivi-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/minimal-cpp/minimal-cpp exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/minimal-qml/minimal-qml exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/multi-output/multi-output > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/multi-screen/multi-screen > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/overview-compositor/overview-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/pure-qml/pure-qml exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/server-buffer/compositor/compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/server-buffer/cpp-client/server-buffer-cpp-client > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/server-side-decoration/server-side-decoration > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/spanning-screens/spanning-screens > exists in debian/tmp but is not installed to anywhere > dh_missing: error: missing files, aborting > The following debhelper tools have reported
Bug#1042285: qt6-wayland: FTBFS: dh_missing: error: missing files, aborting
Source: qt6-wayland Version: 6.4.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Reproducible builds: remove build paths from .prl files > sed -i -e '/^QMAKE_PRL_BUILD_DIR/d' > debian/tmp/usr/lib/x86_64-linux-gnu/libQt6*.prl > make[1]: Leaving directory '/<>' >dh_install -O--buildsystem=cmake\+ninja >dh_installdocs -O--buildsystem=cmake\+ninja >dh_installchangelogs -O--buildsystem=cmake\+ninja >dh_installsystemduser -O--buildsystem=cmake\+ninja >dh_perl -O--buildsystem=cmake\+ninja >dh_link -O--buildsystem=cmake\+ninja >dh_strip_nondeterminism -O--buildsystem=cmake\+ninja >dh_compress -O--buildsystem=cmake\+ninja >dh_fixperms -O--buildsystem=cmake\+ninja >dh_missing -O--buildsystem=cmake\+ninja > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-extension/compositor/custom-extension-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-extension/cpp-client/custom-extension-cpp-client > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-extension/qml-client/custom-extension-qml-client > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-shell/client-plugin/libexampleshellplugin.so > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/custom-shell/compositor/custom-shell-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/hwlayer-compositor/hwlayer-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/ivi-compositor/ivi-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/minimal-cpp/minimal-cpp exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/minimal-qml/minimal-qml exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/multi-output/multi-output > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/multi-screen/multi-screen > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/overview-compositor/overview-compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/pure-qml/pure-qml exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/server-buffer/compositor/compositor > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/server-buffer/cpp-client/server-buffer-cpp-client > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/server-side-decoration/server-side-decoration > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/wayland/spanning-screens/spanning-screens > exists in debian/tmp but is not installed to anywhere > dh_missing: error: missing files, aborting > The following debhelper tools have reported what they installed (with > files per package) >* dh_install: libqt6waylandclient6 (2), libqt6waylandcompositor6 (2), > libqt6waylandeglclienthwintegration6 (2), > libqt6waylandeglcompositorhwintegration6 (2), libqt6wlshellintegration6 (2), > qml6-module-qtwayland-client-texturesharing (2), > qml6-module-qtwayland-compositor (21), qt6-wayland (20), qt6-wayland-dev > (261), qt6-wayland-dev-tools (1) >* dh_installdocs: libqt6waylandclient6 (0), libqt6waylandcompositor6 > (0), libqt6waylandeglclienthwintegration6 (0), > libqt6waylandeglcompositorhwintegration6 (0), libqt6wlshellintegration6 (0), > qml6-module-qtwayland-client-texturesharing (0), > qml6-module-qtwayland-compositor (0), qt6-wayland (0), qt6-wayland-dev (0), > qt6-wayland-dev-tools (0) >
Bug#1038089: marked as done (libqt6gui6: Please have `libqt6gui6` recommend `qt6-wayland`)
Your message dated Mon, 17 Jul 2023 19:37:03 + with message-id and subject line Bug#1038089: fixed in qt6-base 6.4.2+dfsg-13 has caused the Debian Bug report #1038089, regarding libqt6gui6: Please have `libqt6gui6` recommend `qt6-wayland` 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.) -- 1038089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libqt6gui6 Version: 6.4.2+dfsg-11 Severity: wishlist Dear Maintainer, Could `libqt6gui6` recommend the `qt6-wayland` package, similar to how `libqt5gui5` recommends `qtwayland5`? This'd allow Qt6 programs to run under Wayland by default if available, without them all needing to add their own dependency. Many thanks, Sam --- End Message --- --- Begin Message --- Source: qt6-base Source-Version: 6.4.2+dfsg-13 Done: Lisandro Damián Nicanor Pérez Meyer We believe that the bug you reported is fixed in the latest version of qt6-base, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated qt6-base 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 17 Jul 2023 15:52:14 -0300 Source: qt6-base Architecture: source Version: 6.4.2+dfsg-13 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Lisandro Damián Nicanor Pérez Meyer Closes: 1025823 1038089 1041300 Changes: qt6-base (6.4.2+dfsg-13) experimental; urgency=medium . * Team upload to unstable. . [ Pino Toscano ] * Drop the support for the dead GNU/kFreeBSD (which was never really used): - drop the kfreebsd-any qualifiers from the firebird-dev build dependency - drop the kfreebsd-any qualifiers from binary packages - drop the kfreebsd-any qualifiers in install files * Backport upstream commit eeb66b99df521c4a32b8eda1d889f615319355a6 to support Alpha; patch upstream_Add-enable-Alpha-detection.patch. (Closes: #1025823) * Mark some Linux-only examples in qt6-base-examples as such. * Recommend qt6-wayland in libqt6gui6, so it is installed by default. (Closes: #1038089) . [ Lisandro Damián Nicanor Pérez Meyer ] * Fix wrong Break+Replaces on qt6-base-dev against libqt6opengl6-dev (Closes: #1041300). Thanks Helmut Grohne for the bug report. * Remove libgl1-mesa-dev from build dependencies. It has been superseded by libgl-dev, which is already a build dependency. Checksums-Sha1: 762e162563fdc4b35a59a8b00c4aa33c0146c778 4817 qt6-base_6.4.2+dfsg-13.dsc 9591bc2e2f4e0ed5c7f8b98d9e4bd6fe1af101c1 185204 qt6-base_6.4.2+dfsg-13.debian.tar.xz b432e7a591ae9ec944a9a25e97746d5922956add 14474 qt6-base_6.4.2+dfsg-13_source.buildinfo Checksums-Sha256: 0709da4358a93ab30c546bac76b1450a58eb7e6167ad4d7b15bf7739aba6a1bd 4817 qt6-base_6.4.2+dfsg-13.dsc 01c7df92d72789ba04be5ed5758143d30c4b5a76a58dc8076ab54583c40fd871 185204 qt6-base_6.4.2+dfsg-13.debian.tar.xz 8f3bec65c001a9fe991e5886dac805d0c58289143659186d1346d1e959da95e2 14474 qt6-base_6.4.2+dfsg-13_source.buildinfo Files: f78ce548373eac8f4fe0e5743cd0f59c 4817 libs optional qt6-base_6.4.2+dfsg-13.dsc 419ba6495da8c5eaaf4ea119d645fc13 185204 libs optional qt6-base_6.4.2+dfsg-13.debian.tar.xz 1a2473a9fc5f743e9faa0ae020d726fc 14474 libs optional qt6-base_6.4.2+dfsg-13_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAmS1jgkUHGxpc2FuZHJv QGRlYmlhbi5vcmcACgkQq2RfQGKGp9Cr3xAAtaASu9ArAnzV64uGIE1sRCn66G60 Rt6Zj+svSn6gfitR0kdUaiFJzp6Iy/ehRdScjySudc/lqoxBCGaBgD86iiTZSc+S jHxjLqSyErjCy1GlAELPysHWOftIuYvVIF1KGz8ULwXjNADilUabbU92FhYQuiZh k0w52oHBVsM7FAqAJPeZIiH7DrhfE8rH+ZZ3nZ2Guxk1vYR4QZE1TKxGWrwzUV7L NV2iK0nO8IVxEjzbaFoAvUEbLExbIyj35SsFVCAdn8VjeAQlYuI8JEIsrwmwlkGT a56ByB7SgSOHmDjz1abfq51Bp612xD/62mJEhKbdebjtqjezuEmG7Y1+SsL5WMjm AfNTUv8kPkRygFDqyKM+Ct9C6gLXpDTFk1XRDjN76gGTczJYmt3ZNoX1JYvpWp/K TccuNCgmSl117iAui+JFXCsHQtJFvzzG505KkNVPNYJN+FK/PFANZATPbDFMhXFG /4D+4OLvGgnbhcQ5mOytAb9+y50YCOKMZAKIh54qf1e8dAfcsJBr+/u3MUB0VoMz BXVUIUjXSrglPlXScjUTdujhUE0
Bug#1039998: kwin-wayland: kwin_wayland_wrapper spams thousands of messages to the journal
Package: kwin-wayland Version: 4:5.27.5-3 Severity: minor X-Debbugs-Cc: mister...@web.de Dear Maintainer, kwin_wayland_wrapper writes thousands of lines a day to the journal. A majority of those lines read: Jun 30 13:10:11 kwin_wayland_wrapper[5999]: kwin_screencast: Dropping a screencast frame because the compositor is slow This makes it hard to read the journal as those messages come in rapid succession at least 2 pages (on my terminal) per second. On my system here i get: $ journalctl --since today | grep "Dropping a screencast frame because\ the compositor is slow" | wc -l 29393 And: $ journalctl --since today | grep kwin_wayland_wrapper | wc -l 39132 I think that this is an over excessive amount of messages to the journal as it makes it harder to find messages of other programs which are not that verbose. Therefore I consider this behaviour to be a bug. Thanks for maintaining kwin-wayland! Marcel -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.10-1-siduction-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kwin-wayland depends on: ii kwayland-integration 5.27.5-2 ii kwin-common 4:5.27.5-3 ii libc6 2.36-9 ii libcap2-bin 1:2.66-4 ii libepoxy0 1.5.10-1 ii libfontconfig12.14.1-4 ii libfreetype6 2.12.1+dfsg-5 ii libkdecorations2-5v5 4:5.27.5-2 ii libkf5configcore5 5.107.0-1 ii libkf5configgui5 5.107.0-1 ii libkf5configwidgets5 5.107.0-1 ii libkf5coreaddons5 5.107.0-1 ii libkf5crash5 5.107.0-1 ii libkf5dbusaddons5 5.107.0-1 ii libkf5globalaccel-bin 5.107.0-2 ii libkf5globalaccel55.107.0-2 ii libkf5globalaccelprivate5 5.107.0-2 ii libkf5i18n5 5.107.0-1 ii libkf5idletime5 5.107.0-1 ii libkf5notifications5 5.107.0-1 ii libkf5plasma5 5.107.0-1 ii libkf5service-bin 5.107.0-1 ii libkf5service55.107.0-1 ii libkf5windowsystem5 5.107.0-1 ii libkwineffects14 4:5.27.5-3 ii libkwinglutils14 4:5.27.5-3 ii libpipewire-0.3-0 0.3.71-2+b2 ii libqaccessibilityclient-qt5-0 0.4.1-1+b1 ii libqt5core5a [qtbase-abi-5-15-8] 5.15.8+dfsg-12 ii libqt5dbus5 5.15.8+dfsg-12 ii libqt5gui55.15.8+dfsg-12 ii libqt5network55.15.8+dfsg-12 ii libqt5qml55.15.8+dfsg-3 ii libqt5quick5 5.15.8+dfsg-3 ii libqt5widgets55.15.8+dfsg-12 ii libstdc++613.1.0-6 ii libxcb-randr0 1.15-1 ii libxcb-xfixes01.15-1 ii libxcb1 1.15-1 ii xwayland 2:22.1.9-1 kwin-wayland recommends no packages. kwin-wayland suggests no packages. -- debconf-show failed
Bug#1038089: libqt6gui6: Please have `libqt6gui6` recommend `qt6-wayland`
Package: libqt6gui6 Version: 6.4.2+dfsg-11 Severity: wishlist Dear Maintainer, Could `libqt6gui6` recommend the `qt6-wayland` package, similar to how `libqt5gui5` recommends `qtwayland5`? This'd allow Qt6 programs to run under Wayland by default if available, without them all needing to add their own dependency. Many thanks, Sam
Bug#1034338: kwin-wayland: Resizing Window leads to malformed decorations
Package: kwin-wayland Version: 4:5.27.2-1 Severity: important When resizing windows decorated by non-standard decorations in Plasma 5.27.2 Wayland, the window decorations such as window title and buttons are malformed and nigh unusable. This was reported here [1] and apparently got fixed with this commit [2], as mentioned in the bug report. This happens on a fresh install of the current bookworm installation without further adjustments and noticeably impacts the workflow when the window is not correctly displayed most of the time and moving/resizing windows with the mouse is not feasible due to this anymore. Cherry-picking that commit would be greatly appreciated. Kind regards, Jonas [1] https://bugs.kde.org/show_bug.cgi?id=465790 [2] https://invent.kde.org/plasma/kwin/-/commit/715f4147fec2734a0ed56f7ae799e678e18f451f
Bug#983455: marked as done (kate: becomes unusable after background file change on wayland)
Your message dated Wed, 5 Apr 2023 16:01:11 +0200 with message-id and subject line Re: kate: becomes unusable after background file change on wayland has caused the Debian Bug report #983455, regarding kate: becomes unusable after background file change on wayland 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.) -- 983455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kate Version: 4:20.12.2-1 Severity: important Dear Maintainer, when using kate on wayland and any of the currently opened files changes in the background, e.g. when using git (rebase/cherry-pick/switch-branch), the edit area of the window becomes corrupted and unusable. Closing just the changed file does not end the issue. This issue only appears when using the plasma wayland session, not with x11. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kate depends on: ii kate5-data 4:20.12.2-1 ii kio 5.78.0-4 ii ktexteditor-katepart 5.78.0-3 ii libc62.31-9 ii libkf5bookmarks5 5.78.0-2 ii libkf5completion55.78.0-3 ii libkf5configcore55.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons55.78.0-2 ii libkf5crash5 5.78.0-3 ii libkf5dbusaddons55.78.0-2 ii libkf5guiaddons5 5.78.0-3 ii libkf5i18n5 5.78.0-2 ii libkf5iconthemes55.78.0-2 ii libkf5jobwidgets55.78.0-2 ii libkf5kiocore5 5.78.0-4 ii libkf5kiofilewidgets55.78.0-4 ii libkf5kiogui55.78.0-4 ii libkf5kiowidgets55.78.0-4 ii libkf5newstuff5 5.78.0-2 ii libkf5parts5 5.78.0-3 ii libkf5plasma55.78.0-3 ii libkf5service-bin5.78.0-2 ii libkf5service5 5.78.0-2 ii libkf5syntaxhighlighting55.78.0-2 ii libkf5texteditor55.78.0-3 ii libkf5textwidgets5 5.78.0-2 ii libkf5threadweaver5 5.78.0-2 ii libkf5wallet-bin 5.78.0-2 ii libkf5wallet55.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5windowsystem5 5.78.0-2 ii libkf5xmlgui55.78.0-2 ii libkuserfeedbackcore11.0.0-3 ii libkuserfeedbackwidgets1 1.0.0-3 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5dbus5 5.15.2+dfsg-5 ii libqt5gui5 5.15.2+dfsg-5 ii libqt5sql5 5.15.2+dfsg-5 ii libqt5widgets5 5.15.2+dfsg-5 ii libqt5xml5 5.15.2+dfsg-5 ii libstdc++6 11-20210220-1 ii plasma-framework 5.78.0-3 ii qml-module-org-kde-kquickcontrolsaddons 5.78.0-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-4 ii qml-module-qtquick2 5.15.2+dfsg-4 Versions of packages kate recommends: ii sonnet-plugins 5.78.0-2 Versions of packages kate suggests: pn darcs pn exuberant-ctags ii git 1:2.30.1-1 ii khelpcenter 4:20.12.0-1 ii konsole-kpart4:20.12.2-1 pn mercurial pn subversion -- no debconf information --- End Message --- --- Begin Message --- Fixed in bookworm.--- End Message ---
Bug#1032595: marked as done (krfb keyboard Wayland)
Your message dated Sun, 12 Mar 2023 06:49:11 + with message-id and subject line Bug#1032595: fixed in krfb 4:22.12.3-2 has caused the Debian Bug report #1032595, regarding krfb keyboard Wayland 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.) -- 1032595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: krfb Version: 4:22.12.3-1 krfb will not accept keyboard input from a vnc client under Wayland. There is a two line fix for the issue upstream: https://invent.kde.org/network/krfb/-/merge_requests/44/diffs?commit_id=01c775f2e89b705d8375c0ccc0543fc82be53414 I applied it to a krfb source deb and built it. It does enable keyboard input under Wayland. -- Dave Maxwell Network Administrator Big Walnut Local Schools -- _This email may contain confidential and/or privileged information and is covered by the Electronic Communications Privacy Act, 18 USC SS 2510-2521. If it does not contain privileged information concerning a BWLSD employee or student, this email and responses are subject to Ohio public records requests. If you are not the intended recipient (or have this email in error) please notify the sender immediately and destroy this email. Any unauthorized copying, disclosure or distribution of the material in this email is strictly forbidden._ --- End Message --- --- Begin Message --- Source: krfb Source-Version: 4:22.12.3-2 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of krfb, 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 1032...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated krfb 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 Mar 2023 07:23:50 +0100 Source: krfb Architecture: source Version: 4:22.12.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 1032595 Changes: krfb (4:22.12.3-2) unstable; urgency=medium . * Team upload. * Remove inactive Uploaders. * Modernize building: - add the dh-sequence-kf5 build dependency to use the kf5 addon automatically, removing pkg-kde-tools - drop all the manually specified addons and buildsystem for dh * CI: enable again blhc, as it works fine now with blhc 0.13. * Re-export upstream signing key without extra signatures. * Backport upstream commit 01c775f2e89b705d8375c0ccc0543fc82be53414 to hook up keyevents on Wayland; patch upstream_Hook-up-keyevents-on-Wayland.patch (Closes: #1032595) * Fix building on non-Linux architectures, by limiting the Wayland support to Linux architectures: - restrict some build dependencies as linux-any: libkf5wayland-dev, libwayland-dev, plasma-wayland-protocols, and qtwayland5-dev-tools * Add more build dependencies to enable the dma-buf support in the pipewire screencast plugin: libegl-dev, libepoxy-dev, libgbm-dev. * Add more build dependencies related to the Wayland support: libqt5waylandclient5-dev, and qtbase5-private-dev. Checksums-Sha1: 093e2608544b5c845739e7b7fa3a1433f8a42152 3175 krfb_22.12.3-2.dsc 58009a3279cf1093c4cac43d6c9d74fa05d7a6a4 16168 krfb_22.12.3-2.debian.tar.xz 5c888ac3a961c73ef4092473b1134948965eecd9 16859 krfb_22.12.3-2_source.buildinfo Checksums-Sha256: 00010101df2e0faba385b6fa311a2d6561c2b961d808eb215f470d54b10dafe2 3175 krfb_22.12.3-2.dsc 532dedf084f317365957675fe6d1a024d47584e30e9d48f143ab29fd0d275b3a 16168 krfb_22.12.3-2.debian.tar.xz f045893c69ff718d805033239d4de640a302790054d3a0a5d42472adf7794788 16859 krfb_22.12.3-2_source.buildinfo Files: 54993a91e17338a7072dbd3d7c169ec2 3175 kde optional krfb_22.12.3-2.dsc d808d874e31046d8d8f025c4267077d8 16168 kde optional krfb_22.12.3-2.debian.tar.xz 39f7546df0f4c86d0a319d8b9d725f19 16859 kde optional krfb_22.12.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmQNcBcACgkQLRkciEOx P03Gsw//egoou1W7blIkCkoWsyu2CPPn50rX5Ib5075vrGnPnTH3/ovLIVogghLC
Bug#1032595: krfb keyboard Wayland
Package: krfb Version: 4:22.12.3-1 krfb will not accept keyboard input from a vnc client under Wayland. There is a two line fix for the issue upstream: https://invent.kde.org/network/krfb/-/merge_requests/44/diffs?commit_id=01c775f2e89b705d8375c0ccc0543fc82be53414 I applied it to a krfb source deb and built it. It does enable keyboard input under Wayland. -- Dave Maxwell Network Administrator Big Walnut Local Schools -- _This email may contain confidential and/or privileged information and is covered by the Electronic Communications Privacy Act, 18 USC SS 2510-2521. If it does not contain privileged information concerning a BWLSD employee or student, this email and responses are subject to Ohio public records requests. If you are not the intended recipient (or have this email in error) please notify the sender immediately and destroy this email. Any unauthorized copying, disclosure or distribution of the material in this email is strictly forbidden._
Bug#1031690: marked as done (Regression in wayland mixed DPI setups)
Your message dated Mon, 06 Mar 2023 20:44:22 +0100 with message-id <2671821.mvXUDI8C0e@turnagra> and subject line Re: Bug#1031690: Regression in wayland mixed DPI setups has caused the Debian Bug report #1031690, regarding Regression in wayland mixed DPI setups 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.) -- 1031690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-workspace-wayland Version: 4:5.27.0-1 Severity: important Tags: upstream Hello there, it looks like there's a regression in mixed DPI setups (one hiDPI screen at "150%", a lower-DPI screen at "100%"), on Wayland, for some non-KDE applications. In my case, flatpak firefox has too small tabs depending on which screen it initially got launched. This was working much better pre-5.27. It looks like upstream is on this; * https://bugs.kde.org/show_bug.cgi?id=443215 * https://bugs.kde.org/show_bug.cgi?id=465733 But I couldn't really identify directly which patch, and on which software, to test. Happy to build/test here. Best, OdyX -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace-wayland depends on: ii kpackagetool5 5.103.0-1 ii kwayland-integration 5.27.0-1 ii kwin-wayland 4:5.27.0-1 ii libc6 2.36-8 ii libkf5configcore5 5.103.0-1 ii libkf5configgui5 5.103.0-1 ii libkf5configwidgets5 5.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5guiaddons5 5.103.0-1 ii libkf5kcmutils5 5.103.0-1 ii libkf5kiogui5 5.103.0-1 ii libkf5notifications5 5.103.0-1 ii libkf5package55.103.0-1 ii libkf5service-bin 5.103.0-1 ii libkf5service55.103.0-1 ii libkworkspace5-5 4:5.27.0-1 ii libphonon4qt5-4 4:4.11.1-4 ii libqt5core5a 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui55.15.8+dfsg-2 ii libstdc++612.2.0-14 ii phonon4qt54:4.11.1-4 ii plasma-workspace 4:5.27.0-1 ii qtwayland55.15.8-2 plasma-workspace-wayland recommends no packages. plasma-workspace-wayland suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 5.27.2-1 Le dimanche, 5 mars 2023, 15.21:40 h CET Aurélien COUDERC a écrit : > Le lundi 20 février 2023, 18:10:58 CET Didier 'OdyX' Raboud a écrit : > > Package: plasma-workspace-wayland > > Version: 4:5.27.0-1 > > Severity: important > > Tags: upstream > > > > Hello there, > > > > it looks like there's a regression in mixed DPI setups (one hiDPI screen > > at "150%", a lower-DPI screen at "100%"), on Wayland, for some non-KDE > > applications. In my case, flatpak firefox has too small tabs depending > > on which screen it initially got launched. > > This has been marked as fixed upstream in 5.27.1. > > Could you retest on 5.27.2 that we have in unstable and close this bug if it > is indeed fixed ? So far, it looks fixed indeed, thanks for your patience. Best, OdyX--- End Message ---
Bug#1031690: Regression in wayland mixed DPI setups
Dear Odyx, Le lundi 20 février 2023, 18:10:58 CET Didier 'OdyX' Raboud a écrit : > Package: plasma-workspace-wayland > Version: 4:5.27.0-1 > Severity: important > Tags: upstream > > Hello there, > > it looks like there's a regression in mixed DPI setups (one hiDPI screen > at "150%", a lower-DPI screen at "100%"), on Wayland, for some non-KDE > applications. In my case, flatpak firefox has too small tabs depending > on which screen it initially got launched. This has been marked as fixed upstream in 5.27.1. Could you retest on 5.27.2 that we have in unstable and close this bug if it is indeed fixed ? Thanks, -- Aurélien
Bug#1031658: marked as done (plasma-desktop: Depends on plasma-workspace-wayland looks wrong)
Your message dated Tue, 28 Feb 2023 20:52:12 + with message-id and subject line Bug#1031658: fixed in plasma-desktop 4:5.27.2-1 has caused the Debian Bug report #1031658, regarding plasma-desktop: Depends on plasma-workspace-wayland looks wrong 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.) -- 1031658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-desktop Version: 4:5.27.0-1 Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear maintainer, Latest update (4:5.27.0-1) of this package adds a dependency on plasma-workspace-wayland (it already dependes on plasma-workspace); however it looks like this is not accurate since plasmadesktop works just fine with plasma-workspace/kwin-x11, as I'm doing right now. Please consider to add an OR dependency like plasma-workspace-wayland | plasma-workspace so that users can choose to install only packages that they need, like only X11 or only wayland. Thanks, Lorenzo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages plasma-desktop depends on: ii accountsservice 22.08.8-6 ii breeze 4:5.27.0-1 ii kactivitymanagerd5.27.0-1 ii kde-cli-tools4:5.27.0-1 ii kded55.103.0-1 ii kio 5.103.0-1 ii kpackagetool55.103.0-1 ii layer-shell-qt 5.27.0-1 ii libaccounts-qt5-11.16-2 ii libc62.36-8 ii libglib2.0-0 2.74.5-1 ii libibus-1.0-51.5.27-5 ii libkaccounts24:22.12.1-1 ii libkf5activities55.103.0-1 ii libkf5activitiesstats1 5.103.0-1 ii libkf5authcore5 5.103.0-1 ii libkf5baloo5 5.103.0-1 ii libkf5bookmarks5 5.103.0-1 ii libkf5codecs55.103.0-1 ii libkf5completion55.103.0-1 ii libkf5configcore55.103.0-1 ii libkf5configgui5 5.103.0-1 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-1 ii libkf5kcmutilscore5 5.103.0-1 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 libkf5xmlgui5
bug: KDE Wayland Wacom cursor missing in recent update (Debian testing)
Dear Debian Developers, I am writing to report a bug I encountered with KDE Plasma under Wayland when using a Wacom tablet. Specifically, the pen cursor of the Wacom tablet is invisible, although it does draw when the pen is pressed to the tablet. I am using Debian testing with latest updates (installing stable is not an option for many reasons due to the fact that I am using a Pinebook Pro). I believe this is an issue with Wayland because using libinput, I was able to verify that the driver detects the pen in proximity to the tablet and also detects the exact coordinates of where the pen is located. When logging in with X11, the cursor is there and functioning normally. This problem started after one of many updates in early February to Plasma/Wayland. Unfortunately, I cannot pinpoint the exact package that causes this (I've looked through changelogs of many). I would also like to note that when logging in with X11, the issue does not happen, and the cursor is visible. I hope this information is helpful, and I would be happy to provide any additional information that may be useful in resolving this issue. I tried using 'reportbug' but since I couldn't find the exact package causing the issue, wanted to send an email instead. Thank you for your time and consideration. Best regards, Nick Bailuc nick.bai...@gmail.com
Processed: Re: Bug#1031690: Regression in wayland mixed DPI setups
Processing control commands: > forwarded -1 https://bugs.kde.org/show_bug.cgi?id=465733 Bug #1031690 [plasma-workspace-wayland] Regression in wayland mixed DPI setups Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=465733'. > tags -1 +fixed-upstream Bug #1031690 [plasma-workspace-wayland] Regression in wayland mixed DPI setups Added tag(s) fixed-upstream. -- 1031690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031690: Regression in wayland mixed DPI setups
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=465733 Control: tags -1 +fixed-upstream It looks like this was fixed in https://bugs.kde.org/show_bug.cgi?id=465733, in the 5.27.1 Plasma release. TIA, best, OdyX Le lundi, 20 février 2023 18.10:58 h CET, vous avez écrit : > Package: plasma-workspace-wayland > Version: 4:5.27.0-1 > Severity: important > Tags: upstream > > Hello there, > > it looks like there's a regression in mixed DPI setups (one hiDPI screen > at "150%", a lower-DPI screen at "100%"), on Wayland, for some non-KDE > applications. In my case, flatpak firefox has too small tabs depending > on which screen it initially got launched. > > This was working much better pre-5.27. -- OdyX
Bug#1031690: Regression in wayland mixed DPI setups
Package: plasma-workspace-wayland Version: 4:5.27.0-1 Severity: important Tags: upstream Hello there, it looks like there's a regression in mixed DPI setups (one hiDPI screen at "150%", a lower-DPI screen at "100%"), on Wayland, for some non-KDE applications. In my case, flatpak firefox has too small tabs depending on which screen it initially got launched. This was working much better pre-5.27. It looks like upstream is on this; * https://bugs.kde.org/show_bug.cgi?id=443215 * https://bugs.kde.org/show_bug.cgi?id=465733 But I couldn't really identify directly which patch, and on which software, to test. Happy to build/test here. Best, OdyX -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace-wayland depends on: ii kpackagetool5 5.103.0-1 ii kwayland-integration 5.27.0-1 ii kwin-wayland 4:5.27.0-1 ii libc6 2.36-8 ii libkf5configcore5 5.103.0-1 ii libkf5configgui5 5.103.0-1 ii libkf5configwidgets5 5.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5guiaddons5 5.103.0-1 ii libkf5kcmutils5 5.103.0-1 ii libkf5kiogui5 5.103.0-1 ii libkf5notifications5 5.103.0-1 ii libkf5package55.103.0-1 ii libkf5service-bin 5.103.0-1 ii libkf5service55.103.0-1 ii libkworkspace5-5 4:5.27.0-1 ii libphonon4qt5-4 4:4.11.1-4 ii libqt5core5a 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui55.15.8+dfsg-2 ii libstdc++612.2.0-14 ii phonon4qt54:4.11.1-4 ii plasma-workspace 4:5.27.0-1 ii qtwayland55.15.8-2 plasma-workspace-wayland recommends no packages. plasma-workspace-wayland suggests no packages. -- no debconf information
Bug#1031658: plasma-desktop: Depends on plasma-workspace-wayland looks wrong
Package: plasma-desktop Version: 4:5.27.0-1 Severity: normal X-Debbugs-Cc: plore...@disroot.org Dear maintainer, Latest update (4:5.27.0-1) of this package adds a dependency on plasma-workspace-wayland (it already dependes on plasma-workspace); however it looks like this is not accurate since plasmadesktop works just fine with plasma-workspace/kwin-x11, as I'm doing right now. Please consider to add an OR dependency like plasma-workspace-wayland | plasma-workspace so that users can choose to install only packages that they need, like only X11 or only wayland. Thanks, Lorenzo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0van (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages plasma-desktop depends on: ii accountsservice 22.08.8-6 ii breeze 4:5.27.0-1 ii kactivitymanagerd5.27.0-1 ii kde-cli-tools4:5.27.0-1 ii kded55.103.0-1 ii kio 5.103.0-1 ii kpackagetool55.103.0-1 ii layer-shell-qt 5.27.0-1 ii libaccounts-qt5-11.16-2 ii libc62.36-8 ii libglib2.0-0 2.74.5-1 ii libibus-1.0-51.5.27-5 ii libkaccounts24:22.12.1-1 ii libkf5activities55.103.0-1 ii libkf5activitiesstats1 5.103.0-1 ii libkf5authcore5 5.103.0-1 ii libkf5baloo5 5.103.0-1 ii libkf5bookmarks5 5.103.0-1 ii libkf5codecs55.103.0-1 ii libkf5completion55.103.0-1 ii libkf5configcore55.103.0-1 ii libkf5configgui5 5.103.0-1 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-1 ii libkf5kcmutilscore5 5.103.0-1 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.0-1 ii libnotificationmanager1 4:5.27.0-1 ii libpackagekitqt5-1 1.1.0-1 ii libphonon4qt5-4 4:4.11.1-4 ii libprocesscore9 4:5.27.0-1 ii libqt5concurrent55.15.8+dfsg-2 ii libqt5core5a 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui5 5.15.8+dfsg-2 ii libqt5network5 5.15.8+dfsg-2 ii libqt5qml5 5.15.8+dfsg-2 ii libqt5quick5 5.15.8+dfsg-2 ii libqt5quickwidgets5 5.15.8+dfsg-2 ii libqt5sql5 5.15.8+dfsg-2 ii
Re: Plasma with Wayland: No ssh-agent started automatically?
On Sunday, 19 February 2023 10:13:20 CET Martin Steigerwald wrote: > Shmerl - 19.02.23, 04:21:16 CET: > > I've been using KDE Wayland session for a while, but I also switched > > to systemd boot for KDE, may be that helped with ssh-agent. I've been using wayland for 3 years now and it's working perfectly well. It took me some time to have it working in the first place but it never failed me since. It's working at least as well as legacy x11 used to. x11 which I eradicated as much as I could, zotero6 is the only app I have, still using legacy xwayland, but I'll switch to zotero7 asap. On another, newer install, I ditched sddm for gdm which allows me to have no xorg server at all. Hope sddm 0.20 will be available soon. As for `eval "$(ssh-agent -s)"`, I can see in my bash history I start using it at least from 2022. Cheers Chris > > > > Here are some details: > > https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ > > > > > > To enable it: > > > > kwriteconfig5 --file startkderc --group General --key systemdBoot true > > > > Not sure about kick-off issues, I'm using fullscreen Aplication > > Dashboard, and it works fine. > > Haha, no systemd running here. > > But good tip that is could be related to the way Plasma is starting up. > > > If you have some problems with Wayland session - better report bugs, > > so they wouldn't get lost. I've reported a bunch in the past, and > > they were fixed. > > Sure. Just currently not much time for that, so much other stuff. > > Best, >
Re: Plasma with Wayland: No ssh-agent started automatically?
Shmerl - 19.02.23, 04:21:16 CET: > I've been using KDE Wayland session for a while, but I also switched > to systemd boot for KDE, may be that helped with ssh-agent. > > Here are some details: > https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ > > > To enable it: > > kwriteconfig5 --file startkderc --group General --key systemdBoot true > > Not sure about kick-off issues, I'm using fullscreen Aplication > Dashboard, and it works fine. Haha, no systemd running here. But good tip that is could be related to the way Plasma is starting up. > If you have some problems with Wayland session - better report bugs, > so they wouldn't get lost. I've reported a bunch in the past, and > they were fixed. Sure. Just currently not much time for that, so much other stuff. Best, -- Martin
Re: Plasma with Wayland: No ssh-agent started automatically?
I think this happened to me before. I've been using KDE Wayland session for a while, but I also switched to systemd boot for KDE, may be that helped with ssh-agent. Here are some details: https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ To enable it: kwriteconfig5 --file startkderc --group General --key systemdBoot true Not sure about kick-off issues, I'm using fullscreen Aplication Dashboard, and it works fine. Never had issues with typing in Konsole (I have AMD GPU). If you have some problems with Wayland session - better report bugs, so they wouldn't get lost. I've reported a bunch in the past, and they were fixed. Regards, Shmerl.
Re: Plasma with Wayland: No ssh-agent started automatically?
Am Dienstag, 14. Februar 2023, 23:07:52 CET schrieb Martin Steigerwald: > Martin Steigerwald - 14.02.23, 22:27:16 CET: > > Do I really need to start ssh-agent by hand with Plasma (Wayland) > > session type? > > Never mind. I tried some weeks back and it seemed that there *was* a ssh-agent running, but some processes had SSH_AGENT.* set and some not. For reasons I did not investigate further, it seemed to depend on how child processes were spawned. > That is not the only issue. Kick off menu with scaling 150% spanning the > whole 1920x1080 laptop screen and artifacts while typing in Konsole are > other issues with Wayland. Multi screen setups, esp. with different scaling factors seem to have issues, too. And any scaling factor different from 100% led to blurring, even in text. > That still does not appear to be ready for me. > > Maybe some day. I have a recurring event "Test Wayland & KDE" every December ;-). Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Plasma with Wayland: No ssh-agent started automatically?
Martin Steigerwald - 14.02.23, 22:27:16 CET: > Do I really need to start ssh-agent by hand with Plasma (Wayland) > session type? Never mind. That is not the only issue. Kick off menu with scaling 150% spanning the whole 1920x1080 laptop screen and artifacts while typing in Konsole are other issues with Wayland. That still does not appear to be ready for me. Maybe some day. Thanks, -- Martin
Plasma with Wayland: No ssh-agent started automatically?
Hi! I just switched the session type from Plasma (X11) to Plasma (Wayland). No ssh-agent is started automatically anymore. There is an older forum post about this: ssh-agent not started in Wayland https://forum.kde.org/viewtopic.php?t=153769 Do I really need to start ssh-agent by hand with Plasma (Wayland) session type? Thanks, -- Martin
plasma-wayland-protocols_1.10.0-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 20 Jan 2023 17:50:59 +0100 Source: plasma-wayland-protocols Architecture: source Version: 1.10.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: plasma-wayland-protocols (1.10.0-1) unstable; urgency=medium . [ Aurélien COUDERC ] * New upstream release (1.10.0). This is the same as 1.10 with the correct versioning scheme. Checksums-Sha1: 46dd4b0af852d3636a25d88e70b7dc40002990d0 2545 plasma-wayland-protocols_1.10.0-1.dsc 8f1028209fe6c16f6831c8800595b9951f381f6e 43268 plasma-wayland-protocols_1.10.0.orig.tar.xz 317501d1702dd630053a1374702dfa1b608c9199 488 plasma-wayland-protocols_1.10.0.orig.tar.xz.asc 15f4af340436e7f74081a93858d9a6786d8d8644 5792 plasma-wayland-protocols_1.10.0-1.debian.tar.xz b010ab624e64f1ea7b8befd998f7b2ab7297be60 10590 plasma-wayland-protocols_1.10.0-1_amd64.buildinfo Checksums-Sha256: f7e8564a9605823dddeea64ceb406d80a3d2c8bea67fc3bceaf8d5298c1731f8 2545 plasma-wayland-protocols_1.10.0-1.dsc 31948867c9a04613e6de0d23adfcbc5acecddef0b39f986b345ec6c1972736fe 43268 plasma-wayland-protocols_1.10.0.orig.tar.xz 316ac3c4c007e8743faf3cc0821af3aad474c9f2d90a39c202a420bbf533e752 488 plasma-wayland-protocols_1.10.0.orig.tar.xz.asc 10ab9403f7f920b6ec394715ba9bfbd435cde4a5f29536c450b372660c143ac9 5792 plasma-wayland-protocols_1.10.0-1.debian.tar.xz d361032ada6d796d4f62ac168ecd109d1d5f5a949d36de6e72c3f702faf108da 10590 plasma-wayland-protocols_1.10.0-1_amd64.buildinfo Files: 0af13a4d0f49a47af9902767b7816d4c 2545 libdevel optional plasma-wayland-protocols_1.10.0-1.dsc 28ae1490011ff205cbf8d99be6dd124f 43268 libdevel optional plasma-wayland-protocols_1.10.0.orig.tar.xz d6372ddc08e0b44c97d6a0c09ee2fca4 488 libdevel optional plasma-wayland-protocols_1.10.0.orig.tar.xz.asc f1d317a7f613ff7678771ef8780f677d 5792 libdevel optional plasma-wayland-protocols_1.10.0-1.debian.tar.xz 2af73875813fd31275678e5fe59ee2c6 10590 libdevel optional plasma-wayland-protocols_1.10.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmPLu8oTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJMS7D/9bc87vxF1aR+SZ9/CdaZ1BYXDVZJbc o2XmMGXRYNNTHuDIw2qyrApV273MbPinXaNd4Vt5Aly3w5PMWGEInE31usC1+ljD UQ/B2p1+v7pD7okWrVK2O/tb2OKWUSWPG1JmxbpUsKRuRIjPO6p6TaVcM9cyeTwh x0P0taReD6X4bm5eI/xdOmoU4QUm9qen9zUCR6dKl0A3jvCpcDEznjNOxhH/pGJp Tlf+7zg24HAGWKH03IfOS50YTZG2shSDFlSmZMPEj+0H/WMzvRrFUND7dj9hXMAO XDFRFR9YTuweU6ibO6Tnd283VHi8CnPUNnEcb4diwmooKFbUfEUsayx+x8paUdkt Kd7OK8vlV0hrsbwjxwlaTmr6sTaNg8P82LRhmY654dM9frifXyO0CkECm8WZDpar Llk0qdlcNkTn675vAuWG8B6+5jMTpnIw9ir7YdbGjrFhE20pNGiIEVEK1untTtd+ eBgEZCF4A3gyMOS9rl3bH35kbIxA9DQd+kIbCqdDKHGMF7AsgifInlfxrfl6sMPz +hohW87RpOWL9tu1KmoME40Nbnei0VqTklfKzqADRkLd9FHpZ+8SdGUim4NPxhSV i4XfyCqDK8Upyfn8aKziBnPefZ/7WsLNBBlKRREcdlgNnhv/uCNGP4Y7GOZoBde1 uUVcAuxel9IRgQ== =ZSkB -END PGP SIGNATURE-
Processing of plasma-wayland-protocols_1.10.0-1_source.changes
plasma-wayland-protocols_1.10.0-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.10.0-1.dsc plasma-wayland-protocols_1.10.0.orig.tar.xz plasma-wayland-protocols_1.10.0.orig.tar.xz.asc plasma-wayland-protocols_1.10.0-1.debian.tar.xz plasma-wayland-protocols_1.10.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
plasma-wayland-protocols_1.10.0-1_source.changes REJECTED
The .changes was signed using a weak algorithm (such as SHA-1) === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Processing of plasma-wayland-protocols_1.10.0-1_source.changes
plasma-wayland-protocols_1.10.0-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.10.0-1.dsc plasma-wayland-protocols_1.10.0.orig.tar.xz plasma-wayland-protocols_1.10.0.orig.tar.xz.asc plasma-wayland-protocols_1.10.0-1.debian.tar.xz plasma-wayland-protocols_1.10.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
plasma-wayland-protocols_1.10-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Jan 2023 22:47:54 +0100 Source: plasma-wayland-protocols Architecture: source Version: 1.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: plasma-wayland-protocols (1.10-1) unstable; urgency=medium . [ Aurélien COUDERC ] * New upstream release (1.10). * Bump Standards-Version to 4.6.2, no change required. Checksums-Sha1: c2a93ac07b0a8ea6a0cd5efe12b7b77ba3d892f9 2496 plasma-wayland-protocols_1.10-1.dsc fd383db6f6f75c12b4b5d4ef8f54c59b725a0c17 43268 plasma-wayland-protocols_1.10.orig.tar.xz 7ec0eb1758d86ce0da6adcde65873635a7c007b2 488 plasma-wayland-protocols_1.10.orig.tar.xz.asc 5ed8345ba099eb5be23c77c38cb6a80f3fe21368 5744 plasma-wayland-protocols_1.10-1.debian.tar.xz 5c0d884996b2c069ca671d63110cc9ae8df1ffbd 10545 plasma-wayland-protocols_1.10-1_amd64.buildinfo Checksums-Sha256: 41cadb22bf271beb1e3533201f1be816ab8a6ecae36f9bbdbb351e719a0e 2496 plasma-wayland-protocols_1.10-1.dsc 18cdfd239c9e6c157f8cacb77445648921ff3b236242fdab8be7681098c9d9c9 43268 plasma-wayland-protocols_1.10.orig.tar.xz eaec87b8208621f580b34e14b606b801e514d94a8d4f3ad597d0ee7f006ebcbc 488 plasma-wayland-protocols_1.10.orig.tar.xz.asc caac5022558cebff9a8e930ca81346fe727ef4e3b7223cd6809baac53afc89e6 5744 plasma-wayland-protocols_1.10-1.debian.tar.xz 9e62384de5d6867fa593e66b9c513b853c81a0dfa3d216933ffcc60571506a69 10545 plasma-wayland-protocols_1.10-1_amd64.buildinfo Files: ae784bcca64d5ecf743f0467aa270591 2496 libdevel optional plasma-wayland-protocols_1.10-1.dsc 2ad67aea0cdf2c026d904b8c13ad7b72 43268 libdevel optional plasma-wayland-protocols_1.10.orig.tar.xz 2b38184d35ba728d82a84f91c201bd14 488 libdevel optional plasma-wayland-protocols_1.10.orig.tar.xz.asc 8e482799bbb4b25e9563809afd7919f8 5744 libdevel optional plasma-wayland-protocols_1.10-1.debian.tar.xz 797633146d32f45c9d2e2ec6266a21ea 10545 libdevel optional plasma-wayland-protocols_1.10-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmPIaTQACgkQcaflM/KR oyTIbg/9F6XbYFPtMz1yYuf2nJnFnpNLBn1dqN9APPu9ZA+twEtBiJJOOl+8LPyt YZXiQbzhUKov/CFg5DPuXPXota/b7mO1j836Iccl2H9GWT+ooX+zoCQefBN5zPou lIbTs7OxFlaEGwimpDbIj6BlBTcwwK+mynpWc+xGHBxM5EA7eb/qHltapOLtdtYx 6Yt+jGpZdo2xjfWP2IOdg0ouFCtuEtF6hSIjo/e1BDSB04AiF1sIPWdDmmOj+bSa 7yasGy5MioibEJKCXvxhVKyqFy5DE05WkCL+N42EiIbRMLOC8VwIx4jG6BR/Vkas aOi85TOaQYkwVS6EJ/F889Qkju/MVHhVKGsDr3sEAu2kzeHF/aDsjlORQfTJfBx6 CVyBLwekeQLgOCTGIZjeegoc8HVu52fhM5v2KkSNk8XfVJvTJ1tXOepq4WDdcKEp TNVbYY3QwXIBSnc5i8P/KC5gnGF4mbUq+FNiBNZNTtBVem7HSMLj7SuIojsovRAM mVz5agj9+h0fMfbF75X0aNj7TGtCMRgukF7xJckEX86OIy5NEUdMkybsOq1Bsf4t GppnCdpuLowQIgwU6PlPpgSfHZAFEhmPsu8hJiIZ/iwibcxvBnBdcS1a90COyS1V P0z/jVCGCbmW4BuOnGBzyBmraAXODWB+4iudUuI/xSp3dxsFWvU= =KQKN -END PGP SIGNATURE-
Processing of plasma-wayland-protocols_1.10-1_source.changes
plasma-wayland-protocols_1.10-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.10-1.dsc plasma-wayland-protocols_1.10.orig.tar.xz plasma-wayland-protocols_1.10.orig.tar.xz.asc plasma-wayland-protocols_1.10-1.debian.tar.xz plasma-wayland-protocols_1.10-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1029098: marked as done (qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate)
Your message dated Tue, 17 Jan 2023 18:05:17 + with message-id and subject line Bug#1029098: fixed in qt6-wayland 6.4.2-1 has caused the Debian Bug report #1029098, regarding qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate 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.) -- 1029098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt6-wayland Version: 6.4.2~rc1-2 Severity: normal X-Debbugs-Cc: dobey.p...@gmail.com, lisan...@debian.org With a CMakeLists.txt having: find_package(Qt6 REQUIRED COMPONENTS WaylandClient) Runnning CMake issues: ``` -- Could NOT find Qt6WaylandGlobalPrivate (missing: Qt6WaylandGlobalPrivate_DIR) CMake Warning at /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake:167 (find_package): Found package configuration file: /usr/lib/x86_64-linux-gnu/cmake/Qt6WaylandClient/Qt6WaylandClientConfig.cmake but it set Qt6WaylandClient_FOUND to FALSE so package "Qt6WaylandClient" is considered to be NOT FOUND. Reason given by package: Qt6WaylandClient could not be found because dependency Qt6WaylandGlobalPrivate could not be found. Configuring with --debug-find-pkg=Qt6WaylandGlobalPrivate might reveal details why the package was not found. Configuring with -DQT_DEBUG_FIND_PACKAGE=ON will print the values of some of the path variables that find_package uses to try and find the package. Call Stack (most recent call first): CMakeLists.txt:16 (find_package) ``` A public module should not require a private one, so either WaylandClient has a CMake error or it is not really public. -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: qt6-wayland Source-Version: 6.4.2-1 Done: Lisandro Damián Nicanor Pérez Meyer We believe that the bug you reported is fixed in the latest version of qt6-wayland, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated qt6-wayland 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 17 Jan 2023 14:44:16 -0300 Source: qt6-wayland Architecture: source Version: 6.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Lisandro Damián Nicanor Pérez Meyer Closes: 1029098 Changes: qt6-wayland (6.4.2-1) unstable; urgency=medium . * Team upload. * Add libwayland-dev as qt6-wayland-dev dependency, as CMake files look for its presence. * Switch to the official 6.4.2 tarball, the tarball is the same. * Install private components, which are not tied to private headers and required by the main, public components (Closes: #1029098). Thanks Rodney Dawes for the bug report! https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013222#50 Checksums-Sha1: 601a8bc4774de4bedc647f55c33025573ab1 3340 qt6-wayland_6.4.2-1.dsc 394c001681779c22aa39cf97216508e10dcb2a18 836720 qt6-wayland_6.4.2.orig.tar.xz e6a97ef2a95a113666396dd286296887960e93b8 46404 qt6-wayland_6.4.2-1.debian.tar.xz 37bb7cee6088e209c7680321248e1db30d8de805 14822 qt6-wayland_6.4.2-1_source.buildinfo Checksums-Sha256: 466dbd5f3040d9b67a0cc10b2fad4f741c4ee94c093308245497e9f012cbd1e0 3340 qt6-wayland_6.4.2-1.dsc 24cf1a0af751ab1637b4815d5c5f3704483d5fa7bedbd3519e6fc020d8be135f 836720 qt6-wayland_6.4.2.orig.tar.xz 4bd0d6f6a6a7cc9ffc1a61a6a26168c0ae6a1f4979fc1eb44f472217c51ea574 46404 qt6-wayland_6.4.2-1.debian.tar.xz 327dabef3a05ef5c4371e8c98f3159210328bd3539510b6267ddecf551ddcb2e 14822 qt6-way
Bug#1029098: qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate
Control: tag -1 pending These are indeed implementation-private modules, adding them does not requires the use of private headers. The fix has been implemented in commit 5e44bf5ab207edfbe481090e75478a750271a548. I'll be pushing the package ASAP. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/
Processed: Re: Bug#1029098: qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate
Processing control commands: > tag -1 pending Bug #1029098 [src:qt6-wayland] qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate Added tag(s) pending. -- 1029098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029098: qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate
Probably the "Private" name here is misleading: this might be a private module but not directly related with public headers (ie, an implementation detail).
Bug#1029098: qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate
Source: qt6-wayland Version: 6.4.2~rc1-2 Severity: normal X-Debbugs-Cc: dobey.p...@gmail.com, lisan...@debian.org With a CMakeLists.txt having: find_package(Qt6 REQUIRED COMPONENTS WaylandClient) Runnning CMake issues: ``` -- Could NOT find Qt6WaylandGlobalPrivate (missing: Qt6WaylandGlobalPrivate_DIR) CMake Warning at /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake:167 (find_package): Found package configuration file: /usr/lib/x86_64-linux-gnu/cmake/Qt6WaylandClient/Qt6WaylandClientConfig.cmake but it set Qt6WaylandClient_FOUND to FALSE so package "Qt6WaylandClient" is considered to be NOT FOUND. Reason given by package: Qt6WaylandClient could not be found because dependency Qt6WaylandGlobalPrivate could not be found. Configuring with --debug-find-pkg=Qt6WaylandGlobalPrivate might reveal details why the package was not found. Configuring with -DQT_DEBUG_FIND_PACKAGE=ON will print the values of some of the path variables that find_package uses to try and find the package. Call Stack (most recent call first): CMakeLists.txt:16 (find_package) ``` A public module should not require a private one, so either WaylandClient has a CMake error or it is not really public. -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1024976: Serious regression with window decorations under GNOME/Wayland
Hi Am 29.11.22 um 12:18 schrieb Dmitry Shachnev: Hi Michael! On Mon, Nov 28, 2022 at 02:24:29AM +0100, Michael Biebl wrote: Hi, after the lasted update of Qt5, the window decorations of KDE/Qt apps look out-of place under GNOME/Wayland. I've attached a before and after the upgrade screenshot. Keepassxc on the after screenshot doesn't use matching window decorations anymore. This is caused by the change [1] that enabled native Wayland support on GNOME. Now we don't need XWayland which is a big improvement in my opinion. Yeah, native Wayland support is definitely nice. As a side effect, window decorations are now client-side (drawn by Qt itself), not server-side. There is a qgnomeplatform theme [2][3] which makes Qt draw decorations which look better in a GNOME environment. After installing, you can enable it by exporting QT_QPA_PLATFORMTHEME=gnome somewhere. Installing qgnomeplatform-qt5 makes Qt/KDE apps look a bit better. It's not quite the same as when using XWayland, but that is probably because I tweaked the GNOME decorations a little and qgnomeplatform doesn't pick up those modifications. Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1024976: Serious regression with window decorations under GNOME/Wayland
Hi Michael! On Mon, Nov 28, 2022 at 02:24:29AM +0100, Michael Biebl wrote: > Hi, > > after the lasted update of Qt5, the window decorations of KDE/Qt apps > look out-of place under GNOME/Wayland. > > I've attached a before and after the upgrade screenshot. > Keepassxc on the after screenshot doesn't use matching window > decorations anymore. This is caused by the change [1] that enabled native Wayland support on GNOME. Now we don't need XWayland which is a big improvement in my opinion. As a side effect, window decorations are now client-side (drawn by Qt itself), not server-side. There is a qgnomeplatform theme [2][3] which makes Qt draw decorations which look better in a GNOME environment. After installing, you can enable it by exporting QT_QPA_PLATFORMTHEME=gnome somewhere. Do you think there is anything else I can do to improve the situation? [1]: https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/7e0886e100cb79f5 [2]: https://github.com/FedoraQt/QGnomePlatform [3]: https://tracker.debian.org/pkg/qgnomeplatform -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1023174: marked as done (plasma-desktop: Plasma toolbar tooltip window previews not working under wayland: module "org.kde.pipewire" is not installed)
Your message dated Sun, 06 Nov 2022 21:44:33 + with message-id and subject line Bug#1023174: fixed in plasma-workspace 4:5.26.2-1 has caused the Debian Bug report #1023174, regarding plasma-desktop: Plasma toolbar tooltip window previews not working under wayland: module "org.kde.pipewire" is not installed 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.) -- 1023174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-desktop Version: 4:5.26.0-1 Severity: normal Dear Maintainer, when starting a Plasma Wayland session, window previews are missing in the toolbar tooltips. This is probably related to the fact that the following shows up in the logs: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PipeWireThumbnail.qml:11:1: module "org.kde.pipewire" is not installed Looks like a missing dependency somewhere? I tried installing libkpipewire by hand but that did not help. Kind regards, Ralf -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER 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-1+b1 ii breeze 4:5.26.0-1 ii kactivitymanagerd5.26.0-1 ii kde-cli-tools4:5.26.0-1 ii kded55.98.0-1 ii kio 5.98.0-1 ii kpackagetool55.98.0-1 ii layer-shell-qt 5.26.0-1 ii libaccounts-qt5-11.16-2 ii libc62.35-4 ii libglib2.0-0 2.74.0-3 ii libibus-1.0-51.5.27-2+b1 ii libkaccounts24:21.12.3-1 ii libkf5activities55.98.0-1 ii libkf5activitiesstats1 5.98.0-1 ii libkf5authcore5 5.98.0-1 ii libkf5baloo5 5.98.0-1+b1 ii libkf5bookmarks5 5.98.0-1 ii libkf5codecs55.98.0-1 ii libkf5completion55.98.0-1 ii libkf5configcore55.98.0-1 ii libkf5configgui5 5.98.0-1 ii libkf5configwidgets5 5.98.0-1 ii libkf5coreaddons55.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5dbusaddons55.98.0-1 ii libkf5declarative5 5.98.0-2 ii libkf5globalaccel-bin5.98.0-1 ii libkf5globalaccel5 5.98.0-1 ii libkf5guiaddons5 5.98.0-2 ii libkf5i18n5 5.98.0-1+b1 ii libkf5iconthemes55.98.0-2+b1 ii libkf5itemviews5 5.98.0-1 ii libkf5jobwidgets55.98.0-1 ii libkf5kcmutils5 5.98.0-1 ii libkf5kcmutilscore5 5.98.0-1 ii libkf5kdelibs4support5 5.98.0-1 ii libkf5kiocore5 5.98.0-1 ii libkf5kiofilewidgets55.98.0-1 ii libkf5kiogui55.98.0-1 ii libkf5kiowidgets55.98.0-1 ii libkf5newstuffcore5 5.98.0-1 ii libkf5notifications5 5.98.0-1 ii libkf5notifyconfig5 5.98.0-1 ii libkf5package5 5.98.0-1 ii libkf5plasma55.98.0-1 ii libkf5plasmaquick5 5.98.0-1 ii libkf5quickaddons5 5.98.0-2 ii libkf5runner55.98.0-1 ii libkf5service-bin5.98.0-1 ii libkf5service5 5.98.0-1 ii libkf5solid5 5.98.0-1 ii libkf5sonnetcore55.98.0-1 ii libkf5sonnetui5 5.98.0-1 ii libkf5widgetsaddons5 5.98.0-1 ii
Bug#1015627: marked as done (qt6-wayland: ftbfs with LTO (link time optimization) enabled)
Your message dated Sat, 05 Nov 2022 10:20:08 + with message-id and subject line Bug#1015627: fixed in qt6-wayland 6.4.0-2 has caused the Debian Bug report #1015627, regarding qt6-wayland: ftbfs with LTO (link time optimization) enabled 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.) -- 1015627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qt6-wayland Version: 6.2.4-2 Severity: minor Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-lto This package currently fails to build (at least on the amd64 architecture) with link time optimizations enabled. For a background for LTO please see https://wiki.debian.org/ToolChain/LTO The goal is to enable this optimization by default in an upcoming Debian release in dpkg-buildflags for 64bit architectures. The goal is to get this package to build with link time optimizations, or to explicitly disable link time optimizations for this package build. To reproduce the build failure, enable the lto optimization in testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS in the debian/rules file, or if this macro is unset, just set it: export DEB_BUILD_MAINT_OPTIONS = optimize=+lto Please try to fix the build with lto enabled, fixing the packaging or forwarding the issue upstream. If the issue cannot be fixed, explicitly disallow building the package with lto by adding to your rules file: export DEB_BUILD_MAINT_OPTIONS = optimize=-lto or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/dpkglto/qt6-wayland_6.2.4-2_unstable_dpkglto.log The last lines of the build log are at the end of this report. [...] - _ZTVN15QtWaylandServer22zqt_texture_sharing_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer22zqt_texture_sharing_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer22zqt_texture_sharing_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer22zxdg_output_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer22zxdg_output_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer22zxdg_output_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer23qt_hardware_integration8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer23qt_hardware_integration8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer23qt_hardware_integrationE@Base 6.2.2 - _ZTVN15QtWaylandServer23qt_text_input_method_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer23qt_text_input_method_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer23qt_text_input_method_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer25zwp_text_input_manager_v28ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer25zwp_text_input_manager_v28ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer25zwp_text_input_manager_v2E@Base 6.2.2 - _ZTVN15QtWaylandServer26zxdg_decoration_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer26zxdg_decoration_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer26zxdg_decoration_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer27zwp_idle_inhibit_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer27zwp_idle_inhibit_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer27zwp_idle_inhibit_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer27zxdg_toplevel_decoration_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer27zxdg_toplevel_decoration_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer27zxdg_toplevel_decoration_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer31qt_text_input_method_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer31qt_text_input_method_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer31qt_text_input_method_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer6wl_shm8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer6wl_shm8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer6wl_shmE@Base 6.2.2 - _ZTVN15QtWaylandServer7wl_seat8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer7wl_seat8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer7wl_seatE@Base 6.2.2 - _ZTVN15QtWaylandServer8wl_shell8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer8wl_shell8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer8wl_shellE@Base 6.2.2 - _ZTVN15QtWaylandServer8wl_touch8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer8wl_touch8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer8wl_touchE@Base 6.2.2 - _ZTVN15QtWaylandServer9wl_buffer
Bug#1023088: marked as done (qt6-wayland FTCBFS: does not pass QT_HOST_PATH and more)
Your message dated Sat, 05 Nov 2022 10:20:08 +
with message-id
and subject line Bug#1023088: fixed in qt6-wayland 6.4.0-2
has caused the Debian Bug report #1023088,
regarding qt6-wayland FTCBFS: does not pass QT_HOST_PATH and more
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.)
--
1023088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt6-wayland
Version: 6.3.1-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
qt6-wayland fails to cross build from source. The immediate failure is a
missing QT_HOST_PATH variable. Beyond that, it also needs
QT_HOST_PATH_CMAKE_DIR and the relevant cmake files from a native
qt6-wayland-dev. Surprisingly qt6-wayland-dev does not yet depend on
qt6-wayland-dev-tools even though its cmake files reference the
contained tool. I think this is a missing runtime dependency. Finally,
we also need to tell qt6-wayland to cross build its tools. I'm attaching
a patch that makes qt6-wayland cross buildable for your convenience.
Helmut
diff --minimal -Nru qt6-wayland-6.3.1/debian/changelog
qt6-wayland-6.3.1/debian/changelog
--- qt6-wayland-6.3.1/debian/changelog 2022-08-15 19:24:06.0 +0200
+++ qt6-wayland-6.3.1/debian/changelog 2022-10-30 00:56:48.0 +0200
@@ -1,3 +1,14 @@
+qt6-wayland (6.3.1-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: (Closes: #-1)
++ Pass QT_HOST_PATH and QT_HOST_PATH_CMAKE_DIR.
++ Depend on a native version of ourselves.
++ qt6-wayland-dev needs to depend on qt6-wayland-dev-tools.
++ Do build tools when cross compiling.
+
+ -- Helmut Grohne Sun, 30 Oct 2022 00:56:48 +0200
+
qt6-wayland (6.3.1-2) unstable; urgency=medium
[ Patrick Franz ]
diff --minimal -Nru qt6-wayland-6.3.1/debian/control
qt6-wayland-6.3.1/debian/control
--- qt6-wayland-6.3.1/debian/control2022-08-15 18:52:08.0 +0200
+++ qt6-wayland-6.3.1/debian/control2022-10-30 00:56:48.0 +0200
@@ -24,6 +24,7 @@
qt6-base-private-dev (>= 6.3.1+dfsg~),
qt6-declarative-dev (>= 6.3.1+dfsg~),
qt6-declarative-private-dev (>= 6.3.1+dfsg~),
+ qt6-wayland-dev:native ,
xauth ,
xvfb ,
zlib1g-dev,
@@ -144,6 +146,7 @@
libqt6waylandeglclienthwintegration6 (= ${binary:Version}),
libqt6waylandeglcompositorhwintegration6 (= ${binary:Version}),
libqt6wlshellintegration6 (= ${binary:Version}),
+ qt6-wayland-dev-tools (= ${binary:Version}),
${misc:Depends},
Description: Qt 6 Wayland - development files
Qt is a cross-platform C++ application framework. Qt's primary feature
diff --minimal -Nru qt6-wayland-6.3.1/debian/rules
qt6-wayland-6.3.1/debian/rules
--- qt6-wayland-6.3.1/debian/rules 2021-12-13 22:33:29.0 +0100
+++ qt6-wayland-6.3.1/debian/rules 2022-10-30 00:56:48.0 +0200
@@ -4,12 +4,22 @@
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+extra_cmake_args :=
+
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+extra_cmake_args += \
+ -DQT_HOST_PATH=/usr \
+ -DQT_HOST_PATH_CMAKE_DIR=/usr/lib/${DEB_BUILD_MULTIARCH}/cmake \
+ -DQT_BUILD_TOOLS_WHEN_CROSSCOMPILING=ON
+endif
+
%:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
override_dh_auto_configure:
dh_auto_configure -- \
- -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH)
+ -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) \
+ $(extra_cmake_args)
execute_after_dh_auto_install:
# Reproducible builds: remove build paths from .prl files
--- End Message ---
--- Begin Message ---
Source: qt6-wayland
Source-Version: 6.4.0-2
Done: Patrick Franz
We believe that the bug you reported is fixed in the latest version of
qt6-wayland, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Patrick Franz (supplier of updated qt6-wayland 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Fo
Bug#954781: libqt5core5a: QT will not use Wayland on Gnome
On Thu, Nov 03, 2022 at 06:02:03PM +0300, Dmitry Shachnev wrote:
> > 3. The only problem is that qtwayland5 wayland platform plugin is not
> > installed by default in a clean install of debian so applications fail
> > to run wayland natively (fallback to xcb).
> >
> > I think we would need the qtwayland5 installed by default when gnome is
> > installed (since wayland is the default there). Do you know which
> > package should Depends or Recommends qtwayland5 (maybe gnome-core or
> > some other package)?
>
> libqt5gui5 currently suggests it. Do you think it needs to be a
> recommendation?
I think it should be at least a recommendation when wayland is installed
since we're defaulting to run natively. Can we make this behaviour
promoting qtwayland5 to Recommends in libqt5gui5? Because I think people
running X11 will also get the qtwayland5, right? If so, is there other
package that we could use to recommend or depend so it's only installed
when wayland is installed?
I forgot to mention in the first email, but there is a bug filled
against qtwayland5 regarding this matter too [1].
> > The terminal output below shows 3 executions of kristall. The first was
> > using the version from unstable. The second was using the experimental
> > version - fallback to xcb because the wayland platform plugin wasn't
> > installed. The third is using experimental's version after qtwayland5
> > was installed.
> >
> > charles@debianSid-vm:~$ kristall
> > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
> > QT_QPA_PLATFORM=wayland to run on Wayland anyway.
> > defaultServiceProvider::requestService(): no service found for -
> > "org.qt-project.qt.mediaplayer"
> > Loaded 79 bytes of type "text" / "gemini"
> > charles@debianSid-vm:~$ kristall
> > qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
> > defaultServiceProvider::requestService(): no service found for -
> > "org.qt-project.qt.mediaplayer"
> > Loaded 79 bytes of type "text" / "gemini"
> > charles@debianSid-vm:~$ kristall
> > QSocketNotifier: Can only be used with threads started with QThread
> > defaultServiceProvider::requestService(): no service found for -
> > "org.qt-project.qt.mediaplayer"
> > Loaded 79 bytes of type "text" / "gemini"
> > ignoring 1 out of 1
> > 2 0 "text/gemini"
> > Loaded 1265 bytes of type "text" / "gemini"
> > cache: pushing url QUrl("gemini://gemini.circumlunar.space/")
> > ignoring 1 out of 1
> > 2 0 "text/gemini"
> > Loaded 350 bytes of type "text" / "gemini"
> > cache: pushing url QUrl("gemini://gemini.circumlunar.space/news/")
> > qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
> > qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
> > Loaded 79 bytes of type "text" / "gemini"
>
> This is probably just debug output, does not indicate actual errors.
I think so too. I just left for completeness :-)
Thanks,
Charles
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998698
signature.asc
Description: PGP signature
Bug#954781: libqt5core5a: QT will not use Wayland on Gnome
I think it should be more than a recommendation
On Thu, Nov 3, 2022 at 4:06 PM Dmitry Shachnev wrote:
> Hi Carlos!
>
> On Mon, Oct 31, 2022 at 06:55:49PM -0300, Carlos Henrique Lima Melara
> wrote:
> > Took a little while, sorry. Last week was pretty busy. I managed to try
> > it today. I will attach the terminal output in the end. So my feedback
> > is below.
> >
> > 1. I wasn't able to reproduce the misplaced menus (QTBUG-68636) in
> > unstable or experimental versions.
>
> Me too, actually.
>
> > 2. Your patch makes qt choose the wayland plugin on gnome's wayland
> > session by default.
>
> Good. It will reach unstable together with next transition, 5.15.7
> or 5.15.8.
>
> > 3. The only problem is that qtwayland5 wayland platform plugin is not
> > installed by default in a clean install of debian so applications fail
> > to run wayland natively (fallback to xcb).
> >
> > I think we would need the qtwayland5 installed by default when gnome is
> > installed (since wayland is the default there). Do you know which
> > package should Depends or Recommends qtwayland5 (maybe gnome-core or
> > some other package)?
>
> libqt5gui5 currently suggests it. Do you think it needs to be a
> recommendation?
>
> > The terminal output below shows 3 executions of kristall. The first was
> > using the version from unstable. The second was using the experimental
> > version - fallback to xcb because the wayland platform plugin wasn't
> > installed. The third is using experimental's version after qtwayland5
> > was installed.
> >
> > charles@debianSid-vm:~$ kristall
> > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
> QT_QPA_PLATFORM=wayland to run on Wayland anyway.
> > defaultServiceProvider::requestService(): no service found for -
> "org.qt-project.qt.mediaplayer"
> > Loaded 79 bytes of type "text" / "gemini"
> > charles@debianSid-vm:~$ kristall
> > qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
> > defaultServiceProvider::requestService(): no service found for -
> "org.qt-project.qt.mediaplayer"
> > Loaded 79 bytes of type "text" / "gemini"
> > charles@debianSid-vm:~$ kristall
> > QSocketNotifier: Can only be used with threads started with QThread
> > defaultServiceProvider::requestService(): no service found for -
> "org.qt-project.qt.mediaplayer"
> > Loaded 79 bytes of type "text" / "gemini"
> > ignoring 1 out of 1
> > 2 0 "text/gemini"
> > Loaded 1265 bytes of type "text" / "gemini"
> > cache: pushing url QUrl("gemini://gemini.circumlunar.space/")
> > ignoring 1 out of 1
> > 2 0 "text/gemini"
> > Loaded 350 bytes of type "text" / "gemini"
> > cache: pushing url QUrl("gemini://gemini.circumlunar.space/news/")
> > qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
> > qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
> > Loaded 79 bytes of type "text" / "gemini"
>
> This is probably just debug output, does not indicate actual errors.
>
> --
> Dmitry Shachnev
>
Bug#954781: libqt5core5a: QT will not use Wayland on Gnome
Hi Carlos!
On Mon, Oct 31, 2022 at 06:55:49PM -0300, Carlos Henrique Lima Melara wrote:
> Took a little while, sorry. Last week was pretty busy. I managed to try
> it today. I will attach the terminal output in the end. So my feedback
> is below.
>
> 1. I wasn't able to reproduce the misplaced menus (QTBUG-68636) in
> unstable or experimental versions.
Me too, actually.
> 2. Your patch makes qt choose the wayland plugin on gnome's wayland
> session by default.
Good. It will reach unstable together with next transition, 5.15.7
or 5.15.8.
> 3. The only problem is that qtwayland5 wayland platform plugin is not
> installed by default in a clean install of debian so applications fail
> to run wayland natively (fallback to xcb).
>
> I think we would need the qtwayland5 installed by default when gnome is
> installed (since wayland is the default there). Do you know which
> package should Depends or Recommends qtwayland5 (maybe gnome-core or
> some other package)?
libqt5gui5 currently suggests it. Do you think it needs to be a
recommendation?
> The terminal output below shows 3 executions of kristall. The first was
> using the version from unstable. The second was using the experimental
> version - fallback to xcb because the wayland platform plugin wasn't
> installed. The third is using experimental's version after qtwayland5
> was installed.
>
> charles@debianSid-vm:~$ kristall
> Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
> QT_QPA_PLATFORM=wayland to run on Wayland anyway.
> defaultServiceProvider::requestService(): no service found for -
> "org.qt-project.qt.mediaplayer"
> Loaded 79 bytes of type "text" / "gemini"
> charles@debianSid-vm:~$ kristall
> qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
> defaultServiceProvider::requestService(): no service found for -
> "org.qt-project.qt.mediaplayer"
> Loaded 79 bytes of type "text" / "gemini"
> charles@debianSid-vm:~$ kristall
> QSocketNotifier: Can only be used with threads started with QThread
> defaultServiceProvider::requestService(): no service found for -
> "org.qt-project.qt.mediaplayer"
> Loaded 79 bytes of type "text" / "gemini"
> ignoring 1 out of 1
> 2 0 "text/gemini"
> Loaded 1265 bytes of type "text" / "gemini"
> cache: pushing url QUrl("gemini://gemini.circumlunar.space/")
> ignoring 1 out of 1
> 2 0 "text/gemini"
> Loaded 350 bytes of type "text" / "gemini"
> cache: pushing url QUrl("gemini://gemini.circumlunar.space/news/")
> qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
> qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
> Loaded 79 bytes of type "text" / "gemini"
This is probably just debug output, does not indicate actual errors.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#1023408: kwin-wayland: black screen on tty1 after resume from hibernation instead of wayland logon screen
Package: kwin-wayland Version: 4:5.26.0-1 Severity: important Dear Maintainer, after sending the laptop to hibernation, the restart did not work. I see the boot message and end up in a black screen. Every terminal (Ctrl+Alt+2 for instance) works. terminal 7 shows a movable cursor. But terminal 1 with the wayland session just shows a black screen -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 kwin-wayland depends on: ii kwayland-integration 5.26.0-1 ii kwin-common 4:5.26.0-1 ii libc6 2.36-4 ii libcap2-bin 1:2.44-1 ii libepoxy0 1.5.10-1 ii libfontconfig12.13.1-4.5 ii libfreetype6 2.12.1+dfsg-3 ii libkdecorations2-5v5 4:5.26.0-1 ii libkf5configcore5 5.98.0-2 ii libkf5configgui5 5.98.0-2 ii libkf5configwidgets5 5.98.0-1 ii libkf5coreaddons5 5.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5dbusaddons5 5.98.0-1 ii libkf5globalaccel-bin 5.98.0-1 ii libkf5globalaccel55.98.0-1 ii libkf5globalaccelprivate5 5.98.0-1 ii libkf5i18n5 5.98.0-1+b1 ii libkf5idletime5 5.98.0-1 ii libkf5notifications5 5.98.0-1 ii libkf5plasma5 5.98.0-1 ii libkf5service-bin 5.98.0-1 ii libkf5service55.98.0-1 ii libkf5windowsystem5 5.98.0-1 ii libkwineffects14 4:5.26.0-1 ii libkwinglutils14 4:5.26.0-1 ii libpipewire-0.3-0 0.3.59-1+b1 ii libqaccessibilityclient-qt5-0 0.4.1-1+b1 ii libqt5core5a [qtbase-abi-5-15-6] 5.15.6+dfsg-2 ii libqt5dbus5 5.15.6+dfsg-2 ii libqt5gui55.15.6+dfsg-2 ii libqt5network55.15.6+dfsg-2 ii libqt5qml55.15.6+dfsg-2 ii libqt5quick5 5.15.6+dfsg-2 ii libqt5widgets55.15.6+dfsg-2 ii libstdc++612.2.0-7 ii libxcb-randr0 1.15-1 ii libxcb-xfixes01.15-1 ii libxcb1 1.15-1 ii xwayland 2:22.1.3-2 kwin-wayland recommends no packages. kwin-wayland suggests no packages. -- no debconf information
Bug#1023296: plasma-workspace: ssh-agent not working in KDE Plasma Wayland session
Package: plasma-workspace Version: 4:5.26.0-2 Severity: normal Dear Maintainer, when I start a KDE Plasma Wayland session, the ssh-agent is not working: attempting to load my SSH key into the agent (in Konsole via ssh-add) fails saying "Could not open a connection to your authentication agent." This is probably caused by the fact that the SSH_AUTH_SOCK env var is not set. (I am now setting it in my .bashrc to work around the issue.) I have no idea how that env var is *supposed* to end up in the plasma session, but whatever mechanism is supposed to achieve that is not working. I can see that ssh-agent comes with a systemd user service, which is setting the required variable in "dbus-update-activation-environment", so maybe KDE is somehow supposed to fetch that and that is not working? Or maybe it's something else entirely. From feedback I got on IRC, it seems other distros have special ssh-agent scripts in /etc/xdg/plasma-workspace/env/, but I don't know if that is something standard. Kind regards, Ralf -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER 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-workspace depends on: ii dbus-user-session [default-dbus-session-bus]1.14.4-1 ii drkonqi 5.26.0-2 ii frameworkintegration5.98.0-1 ii gdb 12.1-3 ii init-system-helpers 1.65.2 ii iso-codes 4.11.0-1 ii kactivitymanagerd 5.26.0-1 ii kded5 5.98.0-1 ii kinit 5.98.0-1 ii kio 5.98.0-1 ii kpackagetool5 5.98.0-1 ii kwin-common 4:5.26.0-1 ii libappstreamqt2 0.15.5-1 ii libc6 2.35-4 ii libcolorcorrect54:5.26.0-2 ii libcrypt1 1:4.4.28-2 ii libfontconfig1 2.13.1-4.5 ii libfreetype62.12.1+dfsg-3 ii libgcc-s1 12.2.0-3 ii libgps283.22-4.1+b1 ii libice6 2:1.0.10-1 ii libicu7171.1-3 ii libkf5activities5 5.98.0-1 ii libkf5activitiesstats1 5.98.0-1 ii libkf5archive5 5.98.0-1 ii libkf5authcore5 5.98.0-1 ii libkf5baloo55.98.0-1+b1 ii libkf5bookmarks55.98.0-1 ii libkf5calendarevents5 5.98.0-2 ii libkf5completion5 5.98.0-1 ii libkf5config-bin5.98.0-2 ii libkf5configcore5 5.98.0-2 ii libkf5configgui55.98.0-2 ii libkf5configwidgets55.98.0-1 ii libkf5coreaddons5 5.98.0-1 ii libkf5crash55.98.0-1 ii libkf5dbusaddons5 5.98.0-1 ii libkf5declarative5 5.98.0-2 ii libkf5globalaccel-bin 5.98.0-1 ii libkf5globalaccel5 5.98.0-1 ii libkf5guiaddons55.98.0-2 ii libkf5holidays5 1:5.98.0-1 ii libkf5i18n5 5.98.0-1+b1 ii libkf5iconthemes5 5.98.0-2+b1 ii libkf5idletime5 5.98.0-1 ii libkf5jobwidgets5 5.98.0-1 ii libkf5kcmutils5 5.98.0-1 ii libkf5kexiv2-15.0.0 21.12.3-1 ii libkf5kiocore5 5.98.0-1 ii libkf5kiofilewidgets5 5.98.0-1 ii libkf5kiogui5 5.98.0-1 ii libkf5kiowidgets5 5.98.0-1 ii lib
Bug#1023174: Acknowledgement (plasma-desktop: Plasma toolbar tooltip window previews not working under wayland: module "org.kde.pipewire" is not installed)
Turns out the missing package is "qml-module-org-kde-pipewire". It should be added as a dependency of plasma-desktop. ; Ralf
Bug#1023174: plasma-desktop: Plasma toolbar tooltip window previews not working under wayland: module "org.kde.pipewire" is not installed
Package: plasma-desktop Version: 4:5.26.0-1 Severity: normal Dear Maintainer, when starting a Plasma Wayland session, window previews are missing in the toolbar tooltips. This is probably related to the fact that the following shows up in the logs: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PipeWireThumbnail.qml:11:1: module "org.kde.pipewire" is not installed Looks like a missing dependency somewhere? I tried installing libkpipewire by hand but that did not help. Kind regards, Ralf -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER 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-1+b1 ii breeze 4:5.26.0-1 ii kactivitymanagerd5.26.0-1 ii kde-cli-tools4:5.26.0-1 ii kded55.98.0-1 ii kio 5.98.0-1 ii kpackagetool55.98.0-1 ii layer-shell-qt 5.26.0-1 ii libaccounts-qt5-11.16-2 ii libc62.35-4 ii libglib2.0-0 2.74.0-3 ii libibus-1.0-51.5.27-2+b1 ii libkaccounts24:21.12.3-1 ii libkf5activities55.98.0-1 ii libkf5activitiesstats1 5.98.0-1 ii libkf5authcore5 5.98.0-1 ii libkf5baloo5 5.98.0-1+b1 ii libkf5bookmarks5 5.98.0-1 ii libkf5codecs55.98.0-1 ii libkf5completion55.98.0-1 ii libkf5configcore55.98.0-1 ii libkf5configgui5 5.98.0-1 ii libkf5configwidgets5 5.98.0-1 ii libkf5coreaddons55.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5dbusaddons55.98.0-1 ii libkf5declarative5 5.98.0-2 ii libkf5globalaccel-bin5.98.0-1 ii libkf5globalaccel5 5.98.0-1 ii libkf5guiaddons5 5.98.0-2 ii libkf5i18n5 5.98.0-1+b1 ii libkf5iconthemes55.98.0-2+b1 ii libkf5itemviews5 5.98.0-1 ii libkf5jobwidgets55.98.0-1 ii libkf5kcmutils5 5.98.0-1 ii libkf5kcmutilscore5 5.98.0-1 ii libkf5kdelibs4support5 5.98.0-1 ii libkf5kiocore5 5.98.0-1 ii libkf5kiofilewidgets55.98.0-1 ii libkf5kiogui55.98.0-1 ii libkf5kiowidgets55.98.0-1 ii libkf5newstuffcore5 5.98.0-1 ii libkf5notifications5 5.98.0-1 ii libkf5notifyconfig5 5.98.0-1 ii libkf5package5 5.98.0-1 ii libkf5plasma55.98.0-1 ii libkf5plasmaquick5 5.98.0-1 ii libkf5quickaddons5 5.98.0-2 ii libkf5runner55.98.0-1 ii libkf5service-bin5.98.0-1 ii libkf5service5 5.98.0-1 ii libkf5solid5 5.98.0-1 ii libkf5sonnetcore55.98.0-1 ii libkf5sonnetui5 5.98.0-1 ii libkf5widgetsaddons5 5.98.0-1 ii libkf5windowsystem5 5.98.0-1 ii libkf5xmlgui55.98.0-1+b1 ii libkuserfeedbackcore11.2.0-2 ii libkworkspace5-5 4:5.26.0-2 ii libnotificationmanager1 4:5.26.0-2 ii libpackagekitqt5-1 1.0.2-1 ii libphonon4qt5-4 4:4.11.1-4 ii libprocesscore9 4:5.26.0-2+b1 ii libqt5concurrent55.15.6+dfsg-2 ii libqt5core5a 5.15.6+dfsg-2 ii libqt5dbus5 5.15.6+dfsg-2 ii libqt5gui5 5.15.6+dfsg-2 ii libqt5network5 5.15.6+dfsg-2 ii libqt5qml5 5.15.6+dfsg-2 ii libqt5quick5 5.15.6+dfsg-2 ii libqt5quickwidgets5 5.15.6+dfsg-2 ii
Bug#1023088: qt6-wayland FTCBFS: does not pass QT_HOST_PATH and more
Source: qt6-wayland
Version: 6.3.1-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
qt6-wayland fails to cross build from source. The immediate failure is a
missing QT_HOST_PATH variable. Beyond that, it also needs
QT_HOST_PATH_CMAKE_DIR and the relevant cmake files from a native
qt6-wayland-dev. Surprisingly qt6-wayland-dev does not yet depend on
qt6-wayland-dev-tools even though its cmake files reference the
contained tool. I think this is a missing runtime dependency. Finally,
we also need to tell qt6-wayland to cross build its tools. I'm attaching
a patch that makes qt6-wayland cross buildable for your convenience.
Helmut
diff --minimal -Nru qt6-wayland-6.3.1/debian/changelog
qt6-wayland-6.3.1/debian/changelog
--- qt6-wayland-6.3.1/debian/changelog 2022-08-15 19:24:06.0 +0200
+++ qt6-wayland-6.3.1/debian/changelog 2022-10-30 00:56:48.0 +0200
@@ -1,3 +1,14 @@
+qt6-wayland (6.3.1-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: (Closes: #-1)
++ Pass QT_HOST_PATH and QT_HOST_PATH_CMAKE_DIR.
++ Depend on a native version of ourselves.
++ qt6-wayland-dev needs to depend on qt6-wayland-dev-tools.
++ Do build tools when cross compiling.
+
+ -- Helmut Grohne Sun, 30 Oct 2022 00:56:48 +0200
+
qt6-wayland (6.3.1-2) unstable; urgency=medium
[ Patrick Franz ]
diff --minimal -Nru qt6-wayland-6.3.1/debian/control
qt6-wayland-6.3.1/debian/control
--- qt6-wayland-6.3.1/debian/control2022-08-15 18:52:08.0 +0200
+++ qt6-wayland-6.3.1/debian/control2022-10-30 00:56:48.0 +0200
@@ -24,6 +24,7 @@
qt6-base-private-dev (>= 6.3.1+dfsg~),
qt6-declarative-dev (>= 6.3.1+dfsg~),
qt6-declarative-private-dev (>= 6.3.1+dfsg~),
+ qt6-wayland-dev:native ,
xauth ,
xvfb ,
zlib1g-dev,
@@ -144,6 +146,7 @@
libqt6waylandeglclienthwintegration6 (= ${binary:Version}),
libqt6waylandeglcompositorhwintegration6 (= ${binary:Version}),
libqt6wlshellintegration6 (= ${binary:Version}),
+ qt6-wayland-dev-tools (= ${binary:Version}),
${misc:Depends},
Description: Qt 6 Wayland - development files
Qt is a cross-platform C++ application framework. Qt's primary feature
diff --minimal -Nru qt6-wayland-6.3.1/debian/rules
qt6-wayland-6.3.1/debian/rules
--- qt6-wayland-6.3.1/debian/rules 2021-12-13 22:33:29.0 +0100
+++ qt6-wayland-6.3.1/debian/rules 2022-10-30 00:56:48.0 +0200
@@ -4,12 +4,22 @@
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+extra_cmake_args :=
+
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+extra_cmake_args += \
+ -DQT_HOST_PATH=/usr \
+ -DQT_HOST_PATH_CMAKE_DIR=/usr/lib/${DEB_BUILD_MULTIARCH}/cmake \
+ -DQT_BUILD_TOOLS_WHEN_CROSSCOMPILING=ON
+endif
+
%:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
override_dh_auto_configure:
dh_auto_configure -- \
- -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH)
+ -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) \
+ $(extra_cmake_args)
execute_after_dh_auto_install:
# Reproducible builds: remove build paths from .prl files
Processed: Re: Bug#1023024: Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE
Processing control commands: > tags -1 + wontfix Bug #1023024 [plasma-workspace] Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE Ignoring request to alter tags of bug #1023024 to the same tags previously set -- 1023024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1023024: Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE
Processing control commands: > tags -1 + wontfix Bug #1023024 [plasma-workspace] Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE Added tag(s) wontfix. -- 1023024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023024: Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE
control: tags -1 + wontfix Dear mYnDstrEAm, Le 29 octobre 2022 12:29:23 GMT+02:00, mYnDstrEAm a écrit : >Package: plasma-workspace >Version: 5.20.5-6 > >First of all I don't know which package is causing this but it has to do with >Wayland and KDE. Wayland on Debian 11 is provided as a technology preview and is not supported. You should either upgrade to Debian testing if you need to run Wayland, or stay on X11 if you need to run Debian stable. Happy hacking, -- Aurélien
Bug#1023024: Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE
Package: plasma-workspace Version: 5.20.5-6 First of all I don't know which package is causing this but it has to do with Wayland and KDE. Full description of the issue with some logs: https://unix.stackexchange.com/questions/722870/how-to-prevent-kde-session-from-quitting-when-switching-the-display-in-debian-11 In short: I have two displays and am using Debian 11/KDE with Wayland. As a workaround to prevent another bug, I have the HDMI cable to the second display disconnected except when I use it. I have found a workaround that allows me to use (switch to) the second display without the session crashing. When switching the monitor back again, the KDE session crashes (this means I need to login again and restart running apps and so on).
Bug#954781: libqt5core5a: QT will not use Wayland on Gnome
Hi Charles! On Sun, Oct 16, 2022 at 02:04:14AM +, charlesmel...@riseup.net wrote: > Hi, Dmitry and other maintainers, > > I've came accross this problem a couple months ago because I maintain a > QT application (Kristall). It was pretty hard to pinpoint the need to > install qtwayland5 to make everything work when setting the variable. > Besides the message displayed when running the program via cli, it also > goes to journalctl if running via Icon so users might be worried. To try > to help them, I created a bug against kristall [1] and I'm going to ship > a debian/README to explain the situation. > [...] Can you please test the Qt version from experimental and check if it works good for you? -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#954781: marked as done (libqt5core5a: QT will not use Wayland on Gnome)
Your message dated Sun, 23 Oct 2022 22:23:11 + with message-id and subject line Bug#954781: fixed in qtbase-opensource-src 5.15.6+dfsg-3 has caused the Debian Bug report #954781, regarding libqt5core5a: QT will not use Wayland on Gnome 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.) -- 954781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libqt5core5a Version: 5.12.5+dfsg-9 Severity: normal Dear Maintainer, Runnin any QT Application on Gnome will blacklist Wayland. You see the explicit message when starting an application from the terminal. % wireshark Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. (for me this is really annoying as I have a HiDPI and a normal Monitor, X11 doesnt allow different scaling). Fedora considers QT 5.12+ ready to enable this by default, see the two used pathes under [1], Section "Scope". I'd hope debian could follow here, and use those patches in testing. [1] - https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt5core5a depends on: ii libc6 2.30-2 ii libdouble-conversion3 3.1.5-5 ii libgcc-s1 10-20200312-2 ii libglib2.0-0 2.64.1-1 ii libicu63 63.2-3 ii libpcre2-16-0 10.34-7 ii libstdc++6 10-20200312-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages libqt5core5a recommends: ii qttranslations5-l10n 5.12.5-1 Versions of packages libqt5core5a suggests: ii libthai0 0.1.28-3 -- no debconf information --- End Message --- --- Begin Message --- Source: qtbase-opensource-src Source-Version: 5.15.6+dfsg-3 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of qtbase-opensource-src, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qtbase-opensource-src 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Oct 2022 00:43:06 +0300 Source: qtbase-opensource-src Architecture: source Version: 5.15.6+dfsg-3 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 954781 Changes: qtbase-opensource-src (5.15.6+dfsg-3) experimental; urgency=medium . * Backport upstream patch to fix misplaced menus with Wayland on GNOME. * Backport upstream patch to use Wayland platform plugin on GNOME Wayland sessions by default (closes: #954781). * Update debian/libqt5core5a.symbols for ia64 and sparc64. Checksums-Sha1: cf20e2b8993fc506aa4a7d2333015239470a5ed1 5479 qtbase-opensource-src_5.15.6+dfsg-3.dsc 294e281898f31effe9d0ec33262217d83af66840 222632 qtbase-opensource-src_5.15.6+dfsg-3.debian.tar.xz 76e3c3159bbd31da18dc8727025f355daf981b9d 15141 qtbase-opensource-src_5.15.6+dfsg-3_source.buildinfo Checksums-Sha256: 3b9aa7d8b4f4a2bc1799e085db2a0281bd5b79a6651c6958ced762d3023aa76d 5479 qtbase-opensource-src_5.15.6+dfsg-3.dsc 6b4e92c60c43bbd1ce2b15b26211accb75f371c7d0e723615c8dd8e624b533e2 222632 qtbase-opensource-src_5.15.6+dfsg-3.debian.tar.xz 274442a6de04088788d352bc1cd57ca932626e45373ac0f815d5078cf688b8ee 15141 qtbase-opensource-src_5.15.6+dfsg-3_source.buildinfo Files: 1c3fe1dfb6d3d693c5280fd9acaa4b1a 5479 libs optional qtbase-opensource-src_5.15.6+dfsg-3.dsc 64c4ec38c27cf1b251ebaed13b403075 222632 libs optional qtbase-opensource-src_5.15.6+dfsg-3.debian.tar.xz b26949350013ab0ebc2146a56fe7fb8a 15141 libs optional qtbase-opensource-src_5
Bug#954781: libqt5core5a: QT will not use Wayland on Gnome
Hi, Dmitry and other maintainers, I've came accross this problem a couple months ago because I maintain a QT application (Kristall). It was pretty hard to pinpoint the need to install qtwayland5 to make everything work when setting the variable. Besides the message displayed when running the program via cli, it also goes to journalctl if running via Icon so users might be worried. To try to help them, I created a bug against kristall [1] and I'm going to ship a debian/README to explain the situation. Thanks to sergiodj, we discovered this bug and that fedora is patching qt base to run wayland natively in gnome since december of 2019 [2] - so they've had a lot of time to test and find bugs. The rationale and benefits are: "Qt Wayland plugin has been available for a long time, but it hasn't been in condition where it could be enabled by default. With Qt 5.12 the state of the Wayland plugin is much better and it's becoming more and more reliable. It now supports all the needed protocols and has been enabled by default for non-Gnome Wayland sessions. With Qt Wayland on Gnome Wayland session we need to support CSD, it's actually the only way how decorations are going to work in Qt apps right now. Qt Wayland implements basic decorations, which really doesn't match Gnome Adwaita theme, therefore there are new CSD being implemented as part of QGnomePlatform. To make Qt applications run natively on Wayland we need to modify Qt 5, specifically qt5-qtbase module, where we allow the Wayland plugin to be used also for Gnome sessions. The new decorations from QGnomePlatform will be used automatically once they are fully implemented and updated in Fedora. Qt applications running with the Wayland plugin run generally faster and smoother on Wayland enabled sessions like Gnome Wayland and better support HiDPI displays (respects desktop scale)." On Mon, 23 Mar 2020 15:33:40 +0300 Dmitry Shachnev wrote: > On Mon, Mar 23, 2020 at 01:23:43PM +0100, Norbert Lange wrote: > > Runnin any QT Application on Gnome will blacklist Wayland. You see > > the explicit message when starting an application from the terminal. > > > > % wireshark Warning: Ignoring > > XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to > > run on Wayland anyway. > > > > (for me this is really annoying as I have a HiDPI and a normal > > Monitor, X11 doesnt allow different scaling). > > > > Fedora considers QT 5.12+ ready to enable this by default, see the > > two used pathes under [1], Section "Scope". > > > > I'd hope debian could follow here, and use those patches in testing. > > The problem is that upstream Qt considers GNOME/Wayland support not > yet ready. > > There is an umbrella bug (QTBUG-68619) which depends on some other > bugs. At the moment only one of them is open (QTBUG-68636), so I think > as soon as someone fixes it, it will be possible to enable that > support. The QTBUG-68619 has been closed because QTBUG-68636 has also been closed. But the latter has been fixed only in qt 6.2.3 so it won't be extended to our current qt5 version. It seems to me that this bug is pretty minor regarding its impact, and I found a lot of matchs in Debian's bug db regarding the QT_QPA_PLATFORM [3]. That's why I'd like to know if you would consider changing the qtwayland5 to Recommends or Depends in order to alleviate users burden if they decide to run wayland natively via the envvar. It's also an alternative to follow Fedora's approach, though I think the first option would be preferred. Thanks and best regards, Charles [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018251 [2] https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome [3] https://www.mail-archive.com/search?q=QT_QPA_PLATFORM%3Dwayland=debian-bugs-dist%40lists.debian.org
plasma-wayland-protocols_1.9.0-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 28 Sep 2022 23:46:05 +0200 Source: plasma-wayland-protocols Architecture: source Version: 1.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: plasma-wayland-protocols (1.9.0-1) unstable; urgency=medium . [ Aurélien COUDERC ] * New upstream release (1.9.0). * Update upstream metadata. Checksums-Sha1: 8ff722bd978074e96f1b6e5855a2c0591b4d1d9b 2506 plasma-wayland-protocols_1.9.0-1.dsc 1f7bfa684d28782c036527cc1dd376b469a43137 42920 plasma-wayland-protocols_1.9.0.orig.tar.xz e833759b0e31c029ecb742037c1f089fb3a5086b 488 plasma-wayland-protocols_1.9.0.orig.tar.xz.asc b79539f978fe9f3c8fea8dc05e6cc1360dc27bcc 5700 plasma-wayland-protocols_1.9.0-1.debian.tar.xz 141900569076a807a5235132f20516388dc75a63 10563 plasma-wayland-protocols_1.9.0-1_amd64.buildinfo Checksums-Sha256: 77c20ec3dd8c4d55af59fedbdd04e0cbe10a005eb52c42a0a72e49c9fbb014f3 2506 plasma-wayland-protocols_1.9.0-1.dsc a4275b9a854716fa5ed9c2ba2d697df2b0749fc45a28ad965e68d0aa36c5d4c8 42920 plasma-wayland-protocols_1.9.0.orig.tar.xz f0ab2815b23c7d252b23390a04187ca7465f3cd9f15090b0aec36f6b4f4e3cd2 488 plasma-wayland-protocols_1.9.0.orig.tar.xz.asc 069d77e84b00e5a6cfb9d89f0fb608084d06ea356acb2153e3cad4a2005be96b 5700 plasma-wayland-protocols_1.9.0-1.debian.tar.xz 5613fb1276d6d949441bf02e58a8339ab91131a9d9bf4121bd02434851f6 10563 plasma-wayland-protocols_1.9.0-1_amd64.buildinfo Files: fcbbcf49f4982dfb8c485a6f050b7ad9 2506 libdevel optional plasma-wayland-protocols_1.9.0-1.dsc 268b9914ef5e4b186f96987e584d4109 42920 libdevel optional plasma-wayland-protocols_1.9.0.orig.tar.xz 5739681fc8a3835c8e745cf0ea1d4da4 488 libdevel optional plasma-wayland-protocols_1.9.0.orig.tar.xz.asc d9e4ec45414f0a2e784652538a5a5793 5700 libdevel optional plasma-wayland-protocols_1.9.0-1.debian.tar.xz d20336176d3446110256e15015b311e9 10563 libdevel optional plasma-wayland-protocols_1.9.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmM0w28ACgkQcaflM/KR oyScqBAAt/2LDmzEA5EBBXPKwF2OS8fsJfTcVBvT0hEyO5A4hJrX7cbR8HMQIH6q YkHH6WMGxD32oa3pxu3t7Vx1DX9B2KpkEWz1zFwFVcwJLYqpdzKurPYdwaIjfEox jQa4cAjkaDwfHh9tkKZTj98vaoQTscDsmSCfYgjMH2X8Q+rOKJj7FGHAB4bHebY7 xlb552E9Cv0Et/K+If3wkleptOHv49PpPnNgtAfWDmUsIKHvi2XMwN5gU20XekRk DajPx+Y+J+yrmhATtY+Mp9u4/IP4NUSVjHWxTruMVq7+ZCrpyTv9bQCFajnzgRBy Z3DmYJgo6pl9I6/yIkBeIhuVGAELFK/6gvApuaVFCscJlZw4kITUWQB90LqVauAE Gv77mb3Ho+17h5E/Qw6acha7Jl3DIi/gQG1jvIgfl5zfZfTyH0MXBq4BfasgR0RQ eYItJ15i29PhOFvm3DoAVUt2cRz8+yWFwjJmAwxfPhoV4aiOKQGiL7LQKzaU1Coc iSeG9rLUDfdo3ePA/ZhZKV/SYpDGo3WF0Mr2j3PxFVJ5iRbrGdyR6pFmt3IQRJt+ ZIL4bL6X3yj3/LqJQqzQFQ+mni8j5HrCxHHTBHJCYkvgrABjYINpxLXu3Sykie+F TUP7Q/1bhn9Qm+YZT6Maf62mIZVV+swbtaivAxUX5Qk50dkhzTc= =CxGo -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of plasma-wayland-protocols_1.9.0-1_source.changes
plasma-wayland-protocols_1.9.0-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.9.0-1.dsc plasma-wayland-protocols_1.9.0.orig.tar.xz plasma-wayland-protocols_1.9.0.orig.tar.xz.asc plasma-wayland-protocols_1.9.0-1.debian.tar.xz plasma-wayland-protocols_1.9.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
plasma-wayland-protocols_1.8.0-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Sep 2022 22:26:21 +0200 Source: plasma-wayland-protocols Architecture: source Version: 1.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: plasma-wayland-protocols (1.8.0-1) unstable; urgency=medium . [ Aurélien COUDERC ] * New upstream release (1.8.0). Checksums-Sha1: 3372d688c3ab6d9b702e811f3feb14528da59762 2506 plasma-wayland-protocols_1.8.0-1.dsc 5e69c6fc87ad5b8204ab3ef29783a04c3359ef26 42916 plasma-wayland-protocols_1.8.0.orig.tar.xz 26cc01fde472d9e8606e830070c3eeca6ea633f1 488 plasma-wayland-protocols_1.8.0.orig.tar.xz.asc 21c23b651d960d88797e491e379dbbb77c013c49 5588 plasma-wayland-protocols_1.8.0-1.debian.tar.xz 02fa23eb19fe862a715ffa8c65792aa417e8d425 11295 plasma-wayland-protocols_1.8.0-1_source.buildinfo Checksums-Sha256: 1aba4457e9a0f216aecf48c46894898770913087f49c6b8394a6beee56fcca5b 2506 plasma-wayland-protocols_1.8.0-1.dsc 5d0fa0c9a0b448001e08425241f235fcfba25bbc62ce43c050ad1d808d57dd7a 42916 plasma-wayland-protocols_1.8.0.orig.tar.xz 84d2cf6b9bc6060d64706db44ac5a607778e8b936c0f79621c6db5e89a7604d6 488 plasma-wayland-protocols_1.8.0.orig.tar.xz.asc ef1130622a98a1ac33a517ed022d055b338a33a0841f82c8844247fd3820e286 5588 plasma-wayland-protocols_1.8.0-1.debian.tar.xz 26d7c5f66f1126538d32a811713bea1da11a0b8d98bb3fb84a82dc54d029d8ba 11295 plasma-wayland-protocols_1.8.0-1_source.buildinfo Files: ba65787bf5c9bc759860c9dbe880b470 2506 libdevel optional plasma-wayland-protocols_1.8.0-1.dsc 8e948c1eddf80badfac83774af5af8f4 42916 libdevel optional plasma-wayland-protocols_1.8.0.orig.tar.xz 6feb159ad9765eeb89bb60fb3e2a748f 488 libdevel optional plasma-wayland-protocols_1.8.0.orig.tar.xz.asc ee8f2798bd52232bba75d1bd507ffe0b 5588 libdevel optional plasma-wayland-protocols_1.8.0-1.debian.tar.xz 139011c696fca12fb3e761c12a72858c 11295 libdevel optional plasma-wayland-protocols_1.8.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmMnf4QACgkQnp96YDB3 /lb8ABAAjRdtzO8GiJKtlkoJjfz+f/mZHSUsTq1iFQq0p5JO3HYyeWx7UlHy7H/R i/JdKuifBGIWx2ob2L/CFtplc+4kY2mlTSwNT6QidM7WoR+/fci0t+PAU4wFe1O6 WBYC9vN7tyNm6d7EfqACKtMSVN+Iwf7y0rn3zHKEwjskNBgWQMA+lIviIgmwJLws CN9VEJRZJyVh/iOfL/v7zm9X3evMToTN/zMOW98ae8FpZYWWEO6QJzSzVJNv9DZY KiYu+urlyIowCjh6lChUjw325SD8is13p82gRSJKiuxgLLUrAhiD/uDNIwtw7XLh s6lqX9FExCAnL4I132euOte9YNT9fnAHvDaMP+LaY4CxIU6JbgzXm2DIvdb0rMur tKgr2jlbqMrpZbZ1HNG0fEkwgGQWriK1Gris5pjrSwsBc9HTv2j0oSyyVwQ7lerk fwcAvDA7QfLKgsuLWCp4RITrGb1nFa361SEIIJ4abPmw/kO1gA+gt9YNyKlHzhF4 h4kdtESSW9GIglmkXZJR4h89Cs0IQ+Yfy/BbfEQz7yCooN5V1asxWplxTGzh1PlY X4RywhTBjdPwI0G58kg5fRgTgZgsaHbwB1IwMGKWHFmN/oSZ31ZLZSRdPLtgpEj9 ZEVHNsrVncoZJ3wIq2ogNAr8B8YO9czm/JsxoTQ92XKhB97Xnug= =qc5E -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of plasma-wayland-protocols_1.8.0-1_source.changes
plasma-wayland-protocols_1.8.0-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.8.0-1.dsc plasma-wayland-protocols_1.8.0.orig.tar.xz plasma-wayland-protocols_1.8.0.orig.tar.xz.asc plasma-wayland-protocols_1.8.0-1.debian.tar.xz plasma-wayland-protocols_1.8.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1019918: plasma-workspace-wayland: xdg-desktop-portal-kde should be a dependence for the KDE Wayland session
Hi Frédéric, xdg-desktop-portal-kde is already a recommendation of the plasma-desktop package. Don't you have that installed as well ? -- Med vänliga hälsningar Patrick Franz
Bug#1019918: plasma-workspace-wayland: xdg-desktop-portal-kde should be a dependence for the KDE Wayland session
Package: plasma-workspace-wayland Version: 4:5.25.4-3 Severity: normal X-Debbugs-Cc: frederic.parre...@univ-grenoble-alpes.fr Dear Maintainer, When installing plasma-workspace-wayland for the KDE wayland session, the xdg- desktop-portal-kde package is not installed by default. As a consequence, the screen sharing functionnality does not work. So I think this package should be a dependence of the KDE Wayland session. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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-workspace-wayland depends on: ii kpackagetool5 5.97.0-1 ii kwayland-integration 5.25.4-1 ii kwin-wayland 4:5.25.4-2 ii libc6 2.34-7 ii libkf5configcore5 5.97.0-2 ii libkf5configgui5 5.97.0-2 ii libkf5configwidgets5 5.97.0-1 ii libkf5coreaddons5 5.97.0-1 ii libkf5guiaddons5 5.97.0-1 ii libkf5kcmutils5 5.97.0+really5.97.0-2 ii libkf5kiogui5 5.97.0-1 ii libkf5notifications5 5.97.0-1 ii libkf5package55.97.0-1 ii libkf5service-bin 5.97.0-1 ii libkf5service55.97.0-1 ii libkworkspace5-5 4:5.25.4-3 ii libphonon4qt5-4 4:4.11.1-4 ii libqt5core5a 5.15.4+dfsg-5 ii libqt5dbus5 5.15.4+dfsg-5 ii libqt5gui55.15.4+dfsg-5 ii libstdc++612.2.0-1 ii phonon4qt54:4.11.1-4 ii plasma-workspace 4:5.25.4-3 ii qtwayland55.15.4-2 plasma-workspace-wayland recommends no packages. plasma-workspace-wayland suggests no packages. -- no debconf information
Processing of plasma-wayland-protocols_1.8.0-1_source.changes
plasma-wayland-protocols_1.8.0-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.8.0-1.dsc plasma-wayland-protocols_1.8.0.orig.tar.xz plasma-wayland-protocols_1.8.0.orig.tar.xz.asc plasma-wayland-protocols_1.8.0-1.debian.tar.xz plasma-wayland-protocols_1.8.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#909636: marked as done (kwin-wayland: kwin_wayland is segfaulting right after login)
Your message dated Thu, 11 Aug 2022 08:15:53 +0200 with message-id <6028f647-f08f-48b9-8782-dfc852467...@coucouf.fr> and subject line Closing as requested has caused the Debian Bug report #909636, regarding kwin-wayland: kwin_wayland is segfaulting right after login 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.) -- 909636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kwin-wayland Version: 4:5.13.5-1 Severity: important Dear Maintainer, When using KWin Wayland session in Debian testing with AMD Vega 56 GPU (connected over DisplayPort), it cores right after log-in and falls back into sddm. I managed to produce a core backtrace - it's happening in the interaction between kwin_wayland and wayland-client. Wayland and KDE developers so far didn't figure out the cause. Mesa developers suggested, that it can be a Debian specific issue, since it doesn't happen on some other up to date distros. See Wayland bug reference below for a backtrace of the crash. * corresponding Wayland bug: https://gitlab.freedesktop.org/wayland/wayland/issues/56 * corresponding KDE bug: https://bugs.kde.org/show_bug.cgi?id=396066 * corresponding Mesa bug: https://bugs.freedesktop.org/show_bug.cgi?id=107213 Configuration: Current Debian testing Linux (x86_64) (kernel: 4.19.0-rc4), KDE Plasma 5.13.5. kwin-wayland 5.13.5 libwayland-client0 1.16.0 GPU: Sapphire Pulse Vega 56 (amdgpu), DisplayPort connection. Mesa: 18.1.7. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-rc4-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kwin-wayland depends on: ii kwayland-integration 5.13.4-1 ii kwin-common 4:5.13.5-1 ii kwin-wayland-backend-drm 4:5.13.5-1 ii libc6 2.27-6 ii libcap2 1:2.25-1.2 ii libcap2-bin 1:2.25-1.2 ii libepoxy0 1.5.2-0.3 ii libfontconfig12.13.0-5 ii libfreetype6 2.8.1-2 ii libkf5coreaddons5 5.49.0-1 ii libkf5i18n5 5.49.0-1 ii libkf5idletime5 5.49.0-1 ii libkf5quickaddons55.49.0-1 ii libkf5waylandclient5 4:5.49.0-1 ii libkf5waylandserver5 4:5.49.0-1 ii libkf5windowsystem5 5.49.0-1 ii libkwineffects11 4:5.13.5-1 ii libqt5core5a [qtbase-abi-5-11-0] 5.11.1+dfsg-8 ii libqt5dbus5 5.11.1+dfsg-8 ii libqt5gui55.11.1+dfsg-8 ii libqt5widgets55.11.1+dfsg-8 ii libstdc++68.2.0-7 ii libwayland-egl1 1.16.0-1 ii libxcb1 1.13-3 ii xwayland 2:1.20.1-1 kwin-wayland recommends no packages. kwin-wayland suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Good to know ans thanks for the follow-up. Closing this bug.--- End Message ---
plasma-wayland-protocols_1.7.0-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Jul 2022 20:59:15 +0200 Source: plasma-wayland-protocols Architecture: source Version: 1.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 1011790 Changes: plasma-wayland-protocols (1.7.0-2) unstable; urgency=medium . * Bump Standards-Version to 4.6.1, no changes required. * Remove inactive Uploaders. * Switch the qt5-qmake build dependency to qtbase5-dev, as newer versions of extra-cmake-modules need all the development bits of Qt5, not only qmake. (Closes: #1011790) Checksums-Sha1: c9ceba5022972410fc0e1dc0b34f63f568983bca 2506 plasma-wayland-protocols_1.7.0-2.dsc 5c3e05eda9953c6aeeeda00df21eac004446ebfe 5628 plasma-wayland-protocols_1.7.0-2.debian.tar.xz 77bf8c01337cd3de4a77519272cb673e39646738 10829 plasma-wayland-protocols_1.7.0-2_source.buildinfo Checksums-Sha256: 38b0875d2f35454ff791bb94bbb5ad75f9878402d46e2ce679c67caba6575386 2506 plasma-wayland-protocols_1.7.0-2.dsc b3526cf657a1e33c1da4e13c472c88733c1f38f4bd62c2e026c4b07437ba939e 5628 plasma-wayland-protocols_1.7.0-2.debian.tar.xz 80311b0708a5f011abb242a5f363120715d800844d712f2663beadedd013610e 10829 plasma-wayland-protocols_1.7.0-2_source.buildinfo Files: 50f7adf78b9117fd2d1e7ad64f18a7a1 2506 libdevel optional plasma-wayland-protocols_1.7.0-2.dsc f1b199ae7a1411dd6365482c7b772c3b 5628 libdevel optional plasma-wayland-protocols_1.7.0-2.debian.tar.xz 3137a1aad759d045c0fa2f733a564c99 10829 libdevel optional plasma-wayland-protocols_1.7.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmLe6B0ACgkQLRkciEOx P001MBAAsGBasHYNhS0p7hNv+Sjpky681AGbsbxeGCrCl4LAvlHJw36mtrQ/sduJ eBhn+eFJfGgUTkMlALK1UHTE0v0L07mtnAgYZUpWGKv6SQ1vzLLEP+PEadJaqHlz P+c715aNErMVLwXErzyQzrvlwOCyfwACupIZZXrdvkhhSlCIWWpfonBauKjOfcGI m4RMTT62l+enc//r3pF558HJUWvfL2Pps5S6/RQxmFCpyPBr5qmFSd4nu87zkAdl tbrS/ysbdjDlwxDvhm/j1fCFsz2WuJH1gEajxeekc1aYSsAdT0smy2ooR9m4FyYX VtyEGQXKFiHm1ycztIswHZw1nnAsCN/AylTs3n7G7ZxzS7HlGlbCb8dkhKTk0jK9 gQ7fan/gkSEZdztcpinEmoQNeRVz6oYZnQL8ZBiYOdkrxrnsz7GPHhmYoEAHEu15 +1Pm4WjOid++sjQ+rQK0p/MPvwqYNsESsR9VzCDi1AJ7bI2PB3NB2+hGZ8+baGlb T3PR3bPp+shCWQD9CsmJ89y1m/j1OcadV/negQPKtmOXaURnRgN9FVn7aHdp5g6c GiPtepNe0KPad+LsQlNIV1zXUlJ3v5KWJ6MC1nNKtWMzONgkxRySWuK7rLTPgYI7 5CjwaIALKHY4Fq9b2eJbK52N1+gjlI8Aknmyv1nDmIK9Pt9y3uc= =TL1B -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#1011790: marked as done (plasma-wayland-protocols: FTBFS: make: *** [debian/rules:6: binary] Error 2)
Your message dated Mon, 25 Jul 2022 19:37:17 + with message-id and subject line Bug#1011790: fixed in plasma-wayland-protocols 1.7.0-2 has caused the Debian Bug report #1011790, regarding plasma-wayland-protocols: FTBFS: make: *** [debian/rules:6: binary] Error 2 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.) -- 1011790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plasma-wayland-protocols Version: 1.7.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > -- The C compiler identification is GNU 11.3.0 > -- The CXX compiler identification is GNU 11.3.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- > > qmake: could not find a Qt installation of '' > CMake Warning at /usr/share/ECM/modules/ECMQueryQt.cmake:96 (message): > Failed call: "QT_INSTALL_PREFIX" > Call Stack (most recent call first): > /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:238 (ecm_query_qt) > /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include) > CMakeLists.txt:13 (include) > > > CMake Error at /usr/share/ECM/modules/ECMQueryQt.cmake:97 (message): > Qt5 qmake call failed: 1 > Call Stack (most recent call first): > /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:238 (ecm_query_qt) > /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include) > CMakeLists.txt:13 (include) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Build against Qt 6 > BUILD_WITH_QT6:BOOL=OFF > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=None > > //Enable/Disable color output during build. > CMAKE_COLOR_MAKEFILE:BOOL=ON > > //CXX compiler > CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ > > //A wrapper around 'ar' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-11 > > //A wrapper around 'ranlib' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-11 > > //Flags used by the CXX compiler during all build types. > CMAKE_CXX_FLAGS
Processing of plasma-wayland-protocols_1.7.0-2_source.changes
plasma-wayland-protocols_1.7.0-2_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.7.0-2.dsc plasma-wayland-protocols_1.7.0-2.debian.tar.xz plasma-wayland-protocols_1.7.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1015627: qt6-wayland: ftbfs with LTO (link time optimization) enabled
Package: src:qt6-wayland Version: 6.2.4-2 Severity: minor Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-lto This package currently fails to build (at least on the amd64 architecture) with link time optimizations enabled. For a background for LTO please see https://wiki.debian.org/ToolChain/LTO The goal is to enable this optimization by default in an upcoming Debian release in dpkg-buildflags for 64bit architectures. The goal is to get this package to build with link time optimizations, or to explicitly disable link time optimizations for this package build. To reproduce the build failure, enable the lto optimization in testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS in the debian/rules file, or if this macro is unset, just set it: export DEB_BUILD_MAINT_OPTIONS = optimize=+lto Please try to fix the build with lto enabled, fixing the packaging or forwarding the issue upstream. If the issue cannot be fixed, explicitly disallow building the package with lto by adding to your rules file: export DEB_BUILD_MAINT_OPTIONS = optimize=-lto or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/dpkglto/qt6-wayland_6.2.4-2_unstable_dpkglto.log The last lines of the build log are at the end of this report. [...] - _ZTVN15QtWaylandServer22zqt_texture_sharing_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer22zqt_texture_sharing_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer22zqt_texture_sharing_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer22zxdg_output_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer22zxdg_output_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer22zxdg_output_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer23qt_hardware_integration8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer23qt_hardware_integration8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer23qt_hardware_integrationE@Base 6.2.2 - _ZTVN15QtWaylandServer23qt_text_input_method_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer23qt_text_input_method_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer23qt_text_input_method_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer25zwp_text_input_manager_v28ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer25zwp_text_input_manager_v28ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer25zwp_text_input_manager_v2E@Base 6.2.2 - _ZTVN15QtWaylandServer26zxdg_decoration_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer26zxdg_decoration_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer26zxdg_decoration_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer27zwp_idle_inhibit_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer27zwp_idle_inhibit_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer27zwp_idle_inhibit_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer27zxdg_toplevel_decoration_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer27zxdg_toplevel_decoration_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer27zxdg_toplevel_decoration_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer31qt_text_input_method_manager_v18ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer31qt_text_input_method_manager_v18ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer31qt_text_input_method_manager_v1E@Base 6.2.2 - _ZTVN15QtWaylandServer6wl_shm8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer6wl_shm8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer6wl_shmE@Base 6.2.2 - _ZTVN15QtWaylandServer7wl_seat8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer7wl_seat8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer7wl_seatE@Base 6.2.2 - _ZTVN15QtWaylandServer8wl_shell8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer8wl_shell8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer8wl_shellE@Base 6.2.2 - _ZTVN15QtWaylandServer8wl_touch8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer8wl_touch8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer8wl_touchE@Base 6.2.2 - _ZTVN15QtWaylandServer9wl_buffer8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer9wl_buffer8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer9wl_bufferE@Base 6.2.2 - _ZTVN15QtWaylandServer9wl_output8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer9wl_output8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer9wl_outputE@Base 6.2.2 - _ZTVN15QtWaylandServer9wl_region8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer9wl_region8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer9wl_regionE@Base 6.2.2 - _ZTVN15QtWaylandServer9wl_scaler8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer9wl_scaler8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer9wl_scalerE@Base 6.2.2 - _ZTVN15QtWaylandServer9xdg_popup8ResourceE@Base 6.2.2 +#MISSING: 6.2.4-2# _ZTVN15QtWaylandServer9xdg_popup8ResourceE@Base 6.2.2 _ZTVN15QtWaylandServer9xdg_p
Bug#1013222: src:qt6-wayland: please package private headers
Source: qt6-wayland Severity: wishlist Dear Maintainer, Please package private QtWaylandClient headers and related CMake config. Telegram authors offer a forked plugin for XDG shell integration. In order to build the telegram-desktop package against Qt6 keeping all features with Wayland, the headers are necessary. signature.asc Description: This is a digitally signed message part.
Bug#1011790: plasma-wayland-protocols: FTBFS: make: *** [debian/rules:6: binary] Error 2
Source: plasma-wayland-protocols Version: 1.7.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > -- The C compiler identification is GNU 11.3.0 > -- The CXX compiler identification is GNU 11.3.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- > > qmake: could not find a Qt installation of '' > CMake Warning at /usr/share/ECM/modules/ECMQueryQt.cmake:96 (message): > Failed call: "QT_INSTALL_PREFIX" > Call Stack (most recent call first): > /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:238 (ecm_query_qt) > /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include) > CMakeLists.txt:13 (include) > > > CMake Error at /usr/share/ECM/modules/ECMQueryQt.cmake:97 (message): > Qt5 qmake call failed: 1 > Call Stack (most recent call first): > /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:238 (ecm_query_qt) > /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include) > CMakeLists.txt:13 (include) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Build against Qt 6 > BUILD_WITH_QT6:BOOL=OFF > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=None > > //Enable/Disable color output during build. > CMAKE_COLOR_MAKEFILE:BOOL=ON > > //CXX compiler > CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ > > //A wrapper around 'ar' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-11 > > //A wrapper around 'ranlib' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-11 > > //Flags used by the CXX compiler during all build types. > CMAKE_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 > > //Flags used by the CXX compiler during DEBUG builds. > CMAKE_CXX_FLAGS_DEBUG:STRING=-g > > //Flags used by the CXX compiler during MINSIZEREL builds. > CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG > > //Flags used by the CXX compiler during NONE builds. > CMAKE_CXX_FLAGS_NONE:STRING= > > //Flags used by the CXX compiler during RELEASE builds. > CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG > > //Flags used by the CXX compiler during RELWITHDEBINFO builds. > CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG > > //C compiler > CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc > > //A wrapper around 'ar' adding the appropriate '--plugin' opt
qt6-wayland is marked for autoremoval from testing
qt6-wayland 6.2.4-2 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
plasma-wayland-protocols is marked for autoremoval from testing
plasma-wayland-protocols 1.7.0-1 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
plasma-wayland-protocols_1.7.0-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 May 2022 13:31:11 +0200 Source: plasma-wayland-protocols Architecture: source Version: 1.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: plasma-wayland-protocols (1.7.0-1) unstable; urgency=medium . [ Aurélien COUDERC ] * New upstream release (1.7.0). * Build with hardening=+all build hardening flag. * Refresh copyright information. Checksums-Sha1: d7800096f28ab5d5f09e244347d8eab1fa4b9095 2575 plasma-wayland-protocols_1.7.0-1.dsc 1586da798680bafc54aafcb757632d1ff4194a30 42000 plasma-wayland-protocols_1.7.0.orig.tar.xz 1745fd3967fe488f1faf5397977e09e673b71269 488 plasma-wayland-protocols_1.7.0.orig.tar.xz.asc 2271c2148440ff076af6483fcaf73b963e9417d5 5464 plasma-wayland-protocols_1.7.0-1.debian.tar.xz 64e24844e0e7346ddb01b470c854c512ec31ae96 6607 plasma-wayland-protocols_1.7.0-1_amd64.buildinfo Checksums-Sha256: b4a84cf334aff5ded5330a480f03a9054a24ed6359d3eb4a2d55963fc6ff8179 2575 plasma-wayland-protocols_1.7.0-1.dsc 084e2685caa61d94c6fe86dce006b22474d7bb4b34c4cb96bd763b97e305fad6 42000 plasma-wayland-protocols_1.7.0.orig.tar.xz d30ed2b2f028af83f3e6e7a5de111c8887d0b842d8cee22035745d1ed86845e3 488 plasma-wayland-protocols_1.7.0.orig.tar.xz.asc 22e6ddd019b09b94f124ae6b96690a26df8b22ab2cd727e0ce83d25982599e72 5464 plasma-wayland-protocols_1.7.0-1.debian.tar.xz cbbb9db4e8ab2af64a574a7e0eca960752d8c0a9842bba123dbcc481aa07b470 6607 plasma-wayland-protocols_1.7.0-1_amd64.buildinfo Files: 800643cab6fd91cdf5898f7838f7a4b1 2575 libdevel optional plasma-wayland-protocols_1.7.0-1.dsc 432387fdf7f8a7d77f34c1932b61295f 42000 libdevel optional plasma-wayland-protocols_1.7.0.orig.tar.xz 0d3a95c728c7e1c1446393e0ce7f27f8 488 libdevel optional plasma-wayland-protocols_1.7.0.orig.tar.xz.asc 5356778b190f3cab80a84a2844639b52 5464 libdevel optional plasma-wayland-protocols_1.7.0-1.debian.tar.xz b61fad1f091c26be445431ea4ba32ee9 6607 libdevel optional plasma-wayland-protocols_1.7.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmJ4+6ITHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJAGNEACHclXEQai/cW4MzXZnSADrjFyDayRP gmFGVxqfhoz8tetUcYnGWdaxEDzv1DcTz8m1FuoOfiKBpqR7ryEDEkYtdIxexEQp IW7XFeqfArek+JKHrs0hdPhX0qfjD7GhZr6TStc42n3HoTpfpXuLMRFwWxsixU0q tLdLver2mUYWuPYmAurn+awBtQNVCLMdRLYyNeyeKWRq/XzY1Lwu5etsllCACZw5 HR3C7xYdlaOIjMWuTsRvyP8KBCI9jCH+XUP54NbLoSB33zYalZYNBFZIc4yGZ9vK Rphrj4oYHD2w5RxAZdf4S7IHH1YCchjOfVddvyc4XtqEmYRJT+K+z2TVgpoG+fxA dy6Ttndo7luO8MTk7E6ZAi+22V++OsM7awG+M9chRS1rlLeb3dig1KWsXd44ByCs QiaZzgzkaxXrmRLa1S9UpmAq7iL1L1fSqNMMJhMPTpcR2exdd9qc1KRH8am3oXjD gcr53Kzs/nKpzsPm0C0A912oUtTQptCBmsCMtNZJvz1aBe4R0OS4/Z47ZUUvU8X/ gK1Q7+r1xxnf3FbeRAfgRNoIYxT1wUuQ5GELM/59DCI+jRs90XAUCjXxzQPEFz0V X/TYDIBQi3jWwUS68xAD6WCbHDHlfvCyg25txNaIOheWzWV2drhqqm0flyc+/93s Fgt6J24b+8Zydg== =mHWQ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of plasma-wayland-protocols_1.7.0-1_source.changes
plasma-wayland-protocols_1.7.0-1_source.changes uploaded successfully to localhost along with the files: plasma-wayland-protocols_1.7.0-1.dsc plasma-wayland-protocols_1.7.0.orig.tar.xz plasma-wayland-protocols_1.7.0.orig.tar.xz.asc plasma-wayland-protocols_1.7.0-1.debian.tar.xz plasma-wayland-protocols_1.7.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: KDE/Wayland just a black screen with a cursor.
Hello Valerio Some very important informations are missing. You totally forgot to tell us which version(s) are in use on your hardware. And which hardware too. ;-) --- Librement, Xavier Brochard xav...@alternatif.org La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre Rosnay) Le 05.05.2022 18:42, Valerio Passini a écrit : Hello, I've difficulties in making KDE+Wayland work . My system is Debian Unstable with Radeon (open source drivers) and the KDE+W combination worked in the past, now all I get is a black screen with a moving cursor and a lot of crashing stuff. Even if I login in a new clean account the problem is the same. On the other side GNOME+Wayland works as it should. Any advice would be appreciated. Valerio
Re: KDE/Wayland just a black screen with a cursor.
Hi, Thank you for your answer. My system is up-to-date to the packages in Unstable. My hardware is a laptop with double Graphic Card but I'm only using the Radeon for running desktop: Computer Summary Computer Processor AMD Ryzen 7 4800H with Radeon Graphics Memory 15801MB (6684MB used) Machine Type Notebook Operating System Debian GNU/Linux bookworm/sid User Name valerio (Unknown) Date/Time gio 5 mag 2022, 19:21:31 Display Resolution 1920x1080 pixels OpenGL Renderer AMD RENOIR (LLVM 14.0.1, DRM 3.44, 5.17.5-hpomen-amd) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA NVidia Audio Adapter HDA-Intel - HD-Audio Generic Audio Adapter acp - acp Operating System Version Kernel Linux 5.17.5-hpomen-amd (x86_64) *(this is a custom kernel but the problem is the same with stock Debian Kernel in Sid)* Version #6 SMP PREEMPT Sat Apr 30 00:57:37 CEST 2022 C Library GNU C Library / (Debian GLIBC 2.33-7) 2.33 Distribution Debian GNU/Linux bookworm/sid Il giorno gio 5 mag 2022 alle ore 18:59 Xavier Brochard < xav...@alternatif.org> ha scritto: > Hello Valerio > > Some very important informations are missing. > You totally forgot to tell us which version(s) are in use on your > hardware. And which hardware too. ;-) > > --- > Librement, > Xavier Brochard xav...@alternatif.org > La liberté est à l'homme ce que les ailes sont à l'oiseau > (Jean-Pierre Rosnay) > > Le 05.05.2022 18:42, Valerio Passini a écrit : > > Hello, > > > > I've difficulties in making KDE+Wayland work . > > My system is Debian Unstable with Radeon (open source drivers) and the > > KDE+W combination worked in the past, now all I get is a black screen > > with > > a moving cursor and a lot of crashing stuff. Even if I login in a new > > clean > > account the problem is the same. > > On the other side GNOME+Wayland works as it should. > > Any advice would be appreciated. > > > > Valerio > --
KDE/Wayland just a black screen with a cursor.
Hello, I've difficulties in making KDE+Wayland work . My system is Debian Unstable with Radeon (open source drivers) and the KDE+W combination worked in the past, now all I get is a black screen with a moving cursor and a lot of crashing stuff. Even if I login in a new clean account the problem is the same. On the other side GNOME+Wayland works as it should. Any advice would be appreciated. Valerio --
Re: Wayland in current KDE
On Monday, 4 April 2022 21:38:35 CEST Marc Haber wrote: > On Mon, Apr 04, 2022 at 04:20:38PM +0200, chris wrote: > > https://oftc.irclog.whitequark.org/wayland/[3]) > Do they know their way aroud KDE Plasma? I suspect that most of my > issues are actually in KDE. No, they don't. I just gave the information in case the issue was related to your GPU, or something not kde specific. My wayland session works very well, but I don't use a 2fa-usb-key, so I wouldn't know. As for `ssh-agent` I always start it from command line.
Re: Wayland in current KDE
On Mon, Apr 04, 2022 at 04:20:38PM +0200, chris wrote: > On Sunday, 3 April 2022 17:59:44 CEST Patrick Franz wrote: > > Hi Marc, > > > > Am Sonntag, 3. April 2022, 13:13:24 CEST schrieb Marc Haber: > > [...] > > > > > If this should work, who needs to know about the bug? > > > > I suggest upstream. They know much better which hardware configurations > > should work and which ones cause trouble under which circumstances. > > There is a friendly and helpful irc channel on OTFC: > ircs://irc.oftc.net/#wayland[1] > (see also: https://wayland.freedesktop.org/[2]) > They've helped me a lot for bug reporting in the past, and the bugs have been > fixed since. > (There is a "whitequark" log: https://oftc.irclog.whitequark.org/wayland/[3]) Do they know their way aroud KDE Plasma? I suspect that most of my issues are actually in KDE. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Re: Wayland in current KDE
On Sunday, 3 April 2022 17:59:44 CEST Patrick Franz wrote: > Hi Marc, > > Am Sonntag, 3. April 2022, 13:13:24 CEST schrieb Marc Haber: > [...] > > > If this should work, who needs to know about the bug? > > I suggest upstream. They know much better which hardware configurations > should work and which ones cause trouble under which circumstances. There is a friendly and helpful irc channel on OTFC: ircs://irc.oftc.net/#wayland[1] (see also: https://wayland.freedesktop.org/[2]) They've helped me a lot for bug reporting in the past, and the bugs have been fixed since. (There is a "whitequark" log: https://oftc.irclog.whitequark.org/wayland/[3]) ---- [1] ircs://irc.oftc.net/#wayland [2] https://wayland.freedesktop.org/ [3] https://oftc.irclog.whitequark.org/wayland/
Re: Wayland in current KDE
Hi Marc, Am Sonntag, 3. April 2022, 13:13:24 CEST schrieb Marc Haber: [...] > > If this should work, who needs to know about the bug? I suggest upstream. They know much better which hardware configurations should work and which ones cause trouble under which circumstances. -- Med vänliga hälsningar Patrick Franz
Re: Wayland in current KDE
Hi, On Mon, Jan 31, 2022 at 11:10:35AM +0100, Marc Haber wrote: > I tried Wayland recently. Looked ok, but was hardly usable. The Panels > show, but don't accept any mouse clicks (neither left nor right). Two months later, this situation is still the same. Panels are unuseable in KDE Plasma in a Wayland session on my machine. > "Leave" in the desktop's right-click menu didn't work either, had to > Ctrl-Alt-Backspace myself out of the session. The desktop right-click menu works now, and one can now leave the Plasma Wayland session. Ctrl-F2 works as well, so I can now start applications which seem to work alright. When I start a konsole, there is no ssh-agent (probably as there is no X session, what is the mechanism to have ssh-agent in a Wayland session?), and when I manually start an ssh-agent, connect it to my yubikey and then ssh to a server, I don't get the prompt asking for my confirmation to use the key. Hence, no connection. I also do not have anything that matches "wayland" in system-settings. My machine was built 2020, has a Ryzen 5 Pro 4650G CPU, I am using the builtin GPU, amdgpu, I have Debian unstable and a recent kernel. The following wayland-related packages are installed in addition to a reasonably complete and current KDE from today: kwayland-data, kwayland-integration, kwin-wayland, kwin-wayland-backend-drm, libkf5waylandclient5, libkf5waylandserver5, libkwaylandserver5, libqt5waylandclient5, libqt5waylandcompositor5, libva-wayland2, libwayland-client0, libwayland-cursor0, libwayland-egl1, libwayland-server0, plasma-wayland-protocols, plasma-workspace-wayland, qtwayland5, and xwayland. If this should work, who needs to know about the bug? Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Re: Wayland in current KDE
On Sunday, 6 March 2022 10:20:22 CET tv.debian wrote: > Le 06/03/2022 à 04:19, chris a écrit : > > Just a small related comment, with upgrade to 5.24 from a week or so ago, > > the panel, wallpapers, etc switched between laptop monitor and external > > monitor. Beside that I've noticed that there now is the possibility to > > select a "primary" monitor in Setting/Wayland, which I think wasn't > > possible before. Anyway, no big deal. But the primary monitor thing could > > mean no more monitor swapping in the future. At the moment, the external > > 4K monitor has been selected as primary: I don't know what would be the > > behavior were I to unplug it. > > > > On Saturday, 19 February 2022 19:49:23 CET Leonid. wrote: > >> 18.02.2022, 20:00, "Luc Castermans" : > >> well... > >> - on a laptop with integrated graphics controller it works :=) > >> - on a desktop with separate NVDIA card it doesn't even start (!) > >> > >> I suppose problem isn't in X-server, I think problem in user :) > >> You should try start "ready to start" distribution for test Xorg, if you > >> aren't sure in your configuration. For example... live-cd ubuntu image. > > Same experience here, the external TV had the desktop attributes (bar, > plasmoïdes...), but manually selecting the laptop screen got things back > in order. After plugin/unplugin the secondary screen the marked primary > screen stays stable. In my case the attribution of screens is the other way around, the external monitor, has been automatically afaik, assigned as primary. It seems legit since I never use the laptop screen. Laptop monitor is TN 1366x768, external monitor is 4K, IPS. In any case I won't try high risk experiment consisting in unplugging external monitor, or changing primary attribute. The prospect of having to spend hours to fix it is way too scary. > On several machines the shortcut that binds the app menu (using the full > screen app launcher) to the "Windows" key was unbinded. Setting it to > something random, then back to "alt+F1" did the trick. Minor stuff, > otherwise good experience so far. My keyboard must be very very old because it doesn't have a windows key, viz no meta key neither. I do and have done Alt + F1 from day one. I've assigned Alt+F11 to overview. Generally Kwin/Wayland experience is the most awesome.
