Bug#1079395: kdenlive: Please update kdenlive to use Qt 6 / KF 6
Package: kdenlive Version: 24.08.0-1 Severity: wishlist X-Debbugs-Cc: shtetldik+shm...@gmail.com Dear Maintainer, Kdenlive should be usable with Qt 6 and KF 6 but latest uploaded source still depends on Qt 5 and KF 5. Qt 6 and KF6 are already available in unstable. Please repackage it to use that. Thank you! -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.6 (SMP w/32 CPU threads; 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 kdenlive depends on: ii breeze 4:6.1.4-2 ii breeze-icon-theme 4:5.115.0-2 ii ffmpeg 7:7.0.2-3 ii gstreamer1.0-plugins-bad 1.24.6-1 ii kded5 5.115.0-2 ii kdenlive-data 24.05.2-1 ii kinit 5.115.0-2 ii kio5.115.0-6 ii libc6 2.39-6 ii libkf5archive5 5.115.0-2 ii libkf5bookmarks5 5.115.0-2 ii libkf5codecs5 5.115.0-2 ii libkf5completion5 5.115.0-2 ii libkf5configcore5 5.115.0-2 ii libkf5configgui5 5.115.0-2 ii libkf5configwidgets5 5.115.0-2 ii libkf5coreaddons5 5.115.0-2 ii libkf5crash5 5.115.0-2 ii libkf5dbusaddons5 5.115.0-2 ii libkf5filemetadata35.115.0-2+b1 ii libkf5guiaddons5 5.115.0-4 ii libkf5i18n55.115.1-2+b1 ii libkf5iconthemes5 5.115.0-2+b1 ii libkf5itemviews5 5.115.0-2 ii libkf5jobwidgets5 5.115.0-2 ii libkf5kiocore5 5.115.0-6 ii libkf5kiofilewidgets5 5.115.0-6 ii libkf5kiogui5 5.115.0-6 ii libkf5kiowidgets5 5.115.0-6 ii libkf5newstuffcore55.115.0-2 ii libkf5newstuffwidgets5 5.115.0-2 ii libkf5notifications5 5.115.0-2 ii libkf5notifyconfig55.115.0-2 ii libkf5purpose-bin 5.115.0-4 ii libkf5purpose5 5.115.0-4 ii libkf5solid5 5.115.0-3 ii libkf5textwidgets5 5.115.0-2 ii libkf5widgetsaddons5 5.115.0-2 ii libkf5xmlgui5 5.115.0-2+b1 ii libmlt++7 7.24.0-1+b3 ii libmlt77.24.0-1+b3 ii libqt5core5t64 5.15.13+dfsg-4 ii libqt5dbus5t64 5.15.13+dfsg-4 ii libqt5gui5t64 5.15.13+dfsg-4 ii libqt5multimedia5 5.15.13-2 ii libqt5network5t64 5.15.13+dfsg-4 ii libqt5networkauth5 5.15.13-3 ii libqt5qml5 5.15.13+dfsg-2 ii libqt5quick5 5.15.13+dfsg-2 ii libqt5quickcontrols2-5 5.15.13+dfsg-2 ii libqt5quickwidgets55.15.13+dfsg-2 ii libqt5svg5 5.15.13-2 ii libqt5widgets5t64 5.15.13+dfsg-4 ii libqt5xml5t64 5.15.13+dfsg-4 ii libstdc++6 14.2.0-1 ii melt 7.24.0-1+b3 ii qml-module-org-kde-kcm 5.115.0-3 ii qml-module-org-kde-newstuff5.115.0-2 ii qml-module-qtgraphicaleffects 5.15.13-2 ii qml-module-qtqml-models2 5.15.13+dfsg-2 ii qml-module-qtquick-controls5.15.13-2 ii qml-module-qtquick-controls2 5.15.13+dfsg-2 ii qml-module-qtquick-dialogs 5.15.13-2 ii qml-module-qtquick-layouts 5.15.13+dfsg-2 ii qml-module-qtquick-window2 5.15.13+dfsg-2 ii qml-module-qtquick25.15.13+dfsg-2 Versions of packages kdenlive recommends: ii dvdauthor 0.7.2-2+b1 ii dvgrab 3.5+git20160707.1.e46042e-1+b3 ii frei0r-plugins 1.8.0-1+b2 ii genisoimage9:1.1.11-3.5 ii oxygen-icon-theme 5:5.115.0-2 ii recordmydesktop0.4.0-1+b2 ii swh-plugins0.4.17-3 Versions of packages kdenlive suggests: ii khelpcenter 4:23.08.3-1+b1 ii vlc 3.0.21-2 -- no debconf information
Bug#1074550: gdb: Package new version 14.2
Package: gdb Version: 13.2-1+b2 Severity: wishlist X-Debbugs-Cc: shtetldik+shm...@gmail.com Dear Maintainer, please package version 14.2, it has major features like native DAP protocol support. Thank you! Shmerl. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.7-dirty (SMP w/32 CPU threads; 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 gdb depends on: ii libbabeltrace1 1.5.11-3+b6 ii libc62.38-13 ii libdebuginfod1t640.191-1+b1 ii libexpat12.6.2-1 ii libgcc-s114-20240330-1 ii libgmp10 2:6.3.0+dfsg-2+b1 ii libipt2 2.0.6-1 ii liblzma5 5.6.2-1 ii libmpfr6 4.2.1-1+b1 ii libncursesw6 6.5-2 ii libpython3.12t64 3.12.4-1 ii libreadline8t64 8.2-4 ii libsource-highlight4t64 3.1.9-4.3 ii libstdc++6 14-20240330-1 ii libtinfo66.5-2 ii libxxhash0 0.8.2-2+b1 ii libzstd1 1.5.6+dfsg-1 ii zlib1g 1:1.3.dfsg+really1.3.1-1 Versions of packages gdb recommends: ii libc6-dbg [libc-dbg] 2.38-13 Versions of packages gdb suggests: pn gdb-doc ii gdbserver 13.2-1+b2 -- no debconf information
Bug#1072887: konsole: Please package version 24.05.0 it has important features
Package: konsole Version: 4:23.08.1-1+b1 Severity: wishlist X-Debbugs-Cc: shtetldik+shm...@gmail.com Dear Maintainer, please package konsole 24.5.0. It has support for using resizeable tokens: https://invent.kde.org/utilities/konsole/-/commit/1b075680f07665b300fc755766ffef7958094a20 That allows applying a well functioning patch for OSC52 support on top of it. See: * https://invent.kde.org/utilities/konsole/-/merge_requests/767 * https://bugs.kde.org/show_bug.cgi?id=372116 Current outdated version of konsole in Debian doesn't let it work with osc52 well even when patched. Thanks! Shmerl. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.3-dirty (SMP w/32 CPU threads; 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 konsole depends on: ii kio5.115.0-6 ii konsole-kpart 4:23.08.1-1+b1 ii libc6 2.38-12 ii libkf5configcore5 5.115.0-2 ii libkf5configwidgets5 5.115.0-2 ii libkf5coreaddons5 5.115.0-2 ii libkf5crash5 5.115.0-2 ii libkf5dbusaddons5 5.115.0-2 ii libkf5globalaccel-bin 5.115.0-2 ii libkf5globalaccel5 5.115.0-2 ii libkf5guiaddons5 5.115.0-2 ii libkf5i18n55.115.1-2+b1 ii libkf5kiowidgets5 5.115.0-6 ii libkf5notifyconfig55.115.0-2 ii libkf5service-bin 5.115.0-2 ii libkf5service5 5.115.0-2 ii libkf5widgetsaddons5 5.115.0-2 ii libkf5windowsystem55.115.0-2 ii libkf5xmlgui5 5.115.0-2+b1 ii libqt5core5t64 5.15.13+dfsg-2 ii libqt5gui5t64 5.15.13+dfsg-2 ii libqt5widgets5t64 5.15.13+dfsg-2 ii libstdc++6 14-20240330-1 konsole recommends no packages. Versions of packages konsole suggests: pn lrzsz -- no debconf information
Bug#1072499: vice: Provide SDL based version of vice
Package: vice Version: 3.7.1+dfsg1-2+b3 Severity: wishlist X-Debbugs-Cc: shtetldik+shm...@gmail.com Dear Maintainer, Vice has an option to use SDL as a backend rather than GTK. Having that could allow running it in the Wayland session without relying on XWayland backend, since forcing Wayland for GTK doesn't really work for it due to it forcing X11 in its GTK code somehow. Please provide an SDL based variant of vice in addition to GTK one. Thanks! -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.3-dirty (SMP w/32 CPU threads; 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 vice depends on: ii libasound2t641.2.11-1+b1 ii libatk1.0-0t64 2.52.0-1 ii libc62.38-11 ii libcairo21.18.0-3+b1 ii libfontconfig1 2.15.0-1.1 ii libgcc-s114-20240330-1 ii libgdk-pixbuf-2.0-0 2.42.12+dfsg-1 ii libgl1 1.7.0-1+b1 ii libglew2.2 2.2.0-4+b1 ii libglib2.0-0t64 2.80.2-2 ii libgtk-3-0t643.24.42-1 ii libpango-1.0-0 1.52.2+ds-1 ii libpangocairo-1.0-0 1.52.2+ds-1 ii libpng16-16t64 1.6.43-5 ii libpulse016.1+dfsg1-5 ii libreadline8t64 8.2-4 ii libstdc++6 14-20240330-1 ii libx11-6 2:1.8.7-1+b1 ii zlib1g 1:1.3.dfsg+really1.3.1-1 vice recommends no packages. vice suggests no packages. -- no debconf information
Bug#1069382: libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t'
Is there any way to fix or work around this? It's been blocking new version of obs-studio from entering testing for a while. Thanks! Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Mon, 6 May 2024 01:28:47 +0300 Jussi Pakkanen wrote: > Filed: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070470 > Thanks! Do you think it's worth it it to file the bug to rust upstream too: https://github.com/rust-lang/rust/issues May be wider Rust developers can have an insight. Or it's something very Debian specific? Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Sat, 4 May 2024 21:10:10 +0300 Jussi Pakkanen wrote: > The script runs fine on x64_64 but fails on arm64 (and probably also > x86, but I did not test it). This would imply something wonky going on > in the toolchain. The question then becomes where this should be > reported to. May be for rustc? It's worth filing the bug if it's not clear what the root cause is. If it's not really rustc, developers will point that out. Regards, Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Thu, 2 May 2024 19:05:22 +0300 Jussi Pakkanen wrote: > > Along the way I found other bugs, such as bindgen not working at all > out of the box. I filed > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070241 for that. > > All in all this is getting into very deep Debian toolchain magic, of > which I have little knowledge. :( > If real solution for this requires upstream involvement, may be it's worth disabling these tests, until upstream is actually not broken? That would at least move things forward, otherwise it might be stuck for who knows how long? I don't know what's the usual recommended approach for handling such cases. Regards, Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Mon, 26 Feb 2024 19:53:49 +0100 Fabio Pedretti wrote: > Ubuntu fixed it with this patch: > https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz > Can this fix be added to Debian? Meson has been stuck without moving to testing for a very long time and now it seems to be stalling Mesa in result too. Shmerl.
Bug#1069952: Resolved
Actually I was able to resolve it after the recent updates, so it looks all good now. Regards, Shmerl.
Bug#1069952: upgrade from 2.78.4-1 to 2.78.4-7 breaks over 200 packages in testing distribution
On Sat, 27 Apr 2024 10:08:34 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?= < jeremy.bi...@canonical.com> wrote: > On Sat, Apr 27, 2024 at 9:33 AM js wrote: > >Wanted to see the effect of upgrading libglib2.0-dev by a minor > >version number, 2.78.4-1 to 2.78.4-7 and that would have caused over > >200 packages to break in the **testing** distribution. > > Try > sudo apt dist-upgrade > > It is not a "minor" update. It is part of the t64 transition which is > a huge change. > > Thank you, > Jeremy Bícha > That doesn't help. New libglib2.0 is breaking a bunch of things in testing. For example libglib2.0-bin is not co-nisntallable with a bunch of things in KDE Plasma and almost broke a whole installation for me. I managed to somewhat recover it, but for instance *packagekit* and *plasma-discover *got removed. Can you please take a look. sudo apt install libglib2.0-bin Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: plasma-workspace : Depends: gdb-minimal but it is not going to be installed or gdb Error: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Regards, Shmerl.
Bug#1053665: libavif mismatch?
I see that during the build the package is installed, but it's somehow not compatible? Does KDE expect an older version or it's cmake not doing it right? Does it need an upstream bug report or may be Plasma 6 is handling this better? See: https://buildd.debian.org/status/fetch.php?pkg=kimageformats&arch=amd64&ver=5.107.0-3.1&stamp=1698015010&raw=0 Regards, Shmerl. CMake Warning at CMakeLists.txt:54 (find_package): Could not find a configuration file for package "libavif" that is compatible with requested version "0.8.2". The following configuration files were considered but not accepted: /usr/lib/x86_64-linux-gnu/cmake/libavif/libavif-config.cmake, version: 1.0.1 /lib/x86_64-linux-gnu/cmake/libavif/libavif-config.cmake, version: 1.0.1
Bug#1063373: mc-data: modarin thin mc skins are incorrect / behind upstream modarin
Package: mc-data Version: 3:4.8.30-1 Severity: normal X-Debbugs-Cc: shtetldik+shm...@gmail.com Dear Maintainer, I noticed that modarin256-defbg-thin.ini, modarin256-thin.ini (and both root variants of them) are outdated and and also have typos which results in some interface elements being not set. If you compare it to upstream suppprted skins like modarin256-defbg.ini, you'll notice differences in these sections: [widget-panel], [widget-scrollbar], [widget-editor]. They should simply be synced up with non thin ones, keeping only differences in [Lines] section. See below patch for for an example how modarin256-defbg.ini can be fixed. Regards, Shmerl. --- a/modarin256-defbg-thin.ini +++ b/modarin256-defbg-thin.ini @@ -28,7 +28,7 @@ # modarcon16root # modarcon16root-defbg # - like everything running in a 16-color terminal, these skins look ugly -# and are no subsitute for the 256-color versions. As some terminals don't +# and are no substitute for the 256-color versions. As some terminals don't # support using dark gray as background color, i used a black background # and adjusted the remaining colors accordingly. # @@ -81,6 +81,7 @@ disabled = color246;color239 #inputhistory = #commandhistory = +shadow = color240;color0 [dialog] _default_ = color252;color239 @@ -164,21 +165,23 @@ removed = ;color234 error = color231;color160 -[widget-common] -sort-sign-up = ↑ -sort-sign-down = ↓ - [widget-panel] -hiddenfiles-sign-show = • -hiddenfiles-sign-hide = ○ -history-prev-item-sign = « -history-next-item-sign = » -history-show-list-sign = ^ +sort-up-char = ↑ +sort-down-char = ↓ +hiddenfiles-show-char = • +hiddenfiles-hide-char = ○ +history-prev-item-char = « +history-next-item-char = » +history-show-list-char = ^ -[widget-scollbar] +[widget-scrollbar] first-vert-char = ↑ last-vert-char = ↓ first-horiz-char = « last-horiz-char = » current-char = ■ background-char = ▒ + +[widget-editor] +window-state-char = * +window-close-char = X -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.4-dirty (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN 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 -- no debconf information
Bug#924862: shaderc isn't needed
I asked mpv developers, and apparently libplacebo indeed now can handle shader compilation without need for shaderc. So this seems to be not even needed at all on Linux. See: https://github.com/mpv-player/mpv/issues/12982 Regards, Shmerl.
Bug#924862: mpv with Vulkan without shaderc
I just noticed that mpv somehow managed to work with Vulkan without shaderc!
Here is my configuration in $HOME/.config/mpv/config
[gpu-vulkan]
vo=gpu-next
gpu-api=vulkan
hwdec=vaapi
gpu-context=waylandvk
[default]
profile=gpu-vulkan
Here is some of what I see when running with --msg-level=all=debug
[vo/gpu-next/vulkan] Initializing GPU context 'waylandvk'
...
[vo/gpu-next/libplacebo] Spent 2.067 ms creating vulkan instance
...
[vo/gpu-next/libplacebo] Requested alpha compositing mode:
VK_COMPOSITE_ALPHA_PRE_MULTIPLIED_BIT_KHR
[vo/gpu-next/libplacebo] Requested surface transform:
VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR
...
[vo/gpu-next] Loading hwdec driver 'vaapi'
...
[vo/gpu-next/libplacebo] vertex shader source:
[vo/gpu-next/libplacebo] [ 1] #version 450
...
[vo/gpu-next/libplacebo] [ 38]
[vo/gpu-next/libplacebo] [ 39] void main() {
[vo/gpu-next/libplacebo] [ 40] out_color = _1();
[vo/gpu-next/libplacebo] [ 41] }
[vo/gpu-next/libplacebo] Spent 0.796 ms translating SPIR-V
[vo/gpu-next/libplacebo] Spent 0.802 ms translating SPIR-V
[vo/gpu-next/libplacebo] Spent 0.004 ms compiling shader
[vo/gpu-next/libplacebo] Spent 0.070 ms creating pipeline
[vo/gpu-next/libplacebo] Pass statistics: size 0, SPIR-V: vert 0 frag 0
comp 0
...
So it clearly somehow manages to compile shaders to SPIR-V without shaderc!
May be libplacebo has some built in compiler?
Just wanted to share if anyone was waiting to start using Vulkan with your
mpv.
Regards,
Shmerl.
Bug#1042050: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to `hidden_function'
On Tue, 1 Aug 2023 22:55:02 +0300 Jussi Pakkanen wrote: > On Wed, 26 Jul 2023 at 00:16, Lucas Nussbaum wrote: > > This is actually a bug in gobject-introspection. It has already been > fixed upstream. Dunno what the schedule is for getting that into a > release and on to Debian. > Can this be applied for now as a patch until upstream makes a new tag (which can be a while)? https://gitlab.gnome.org/GNOME/gobject-introspection/-/commit/bf96a92ef263820d40e233814a46932cae00db41 Stuck Meson is blocking a bunch of packages from being updated in testing. Regards, Shmerl.
Bug#1029939: shaderc support for mpv
Any news on this? In general, it seems these kind of issues are common for shaderc - glslang integration. Some similar bugs were reported elsewhere. For the reference: * https://bugs.archlinux.org/task/70990 * https://github.com/mpv-player/mpv/issues/8945 * https://github.com/KhronosGroup/glslang/issues/1484 And etc. Shmerl.
Bug#787911: New patch
Not sure if anyone has proposed updated ways to do it, but I made a minimal
patch that implements it
with fallback to legacy config. It's not trying to move anything, just
using XDG base dir if it's a new installation
and picking legacy config if it already exists. It allows to start using it
for fresh installs and not breaking it for old
ones which is a simple temporary compromise.
See attached.
Regards,
Shmerl.
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -1421,6 +1421,10 @@
USERFILE = os.path.expanduser('~/.reportbugrc')
+# Use XDG base directory compliant config file and support legacy one if it already exists.
+if not os.path.isfile(USERFILE):
+USERFILE = (os.environ.get('XDG_CONFIG_HOME') or os.environ.get('HOME') + '/.config') + '/reportbugrc'
+
FILES = ('/etc/reportbug.conf', USERFILE)
CONFIG_ARGS = (
Bug#924862: Enable shaderc support in mpv
Now that shaderc was added to Debian unstable / testing, can you please enable building mpv with it? See: https://tracker.debian.org/pkg/shaderc Thanks! Shmerl.
Bug#1025659: libgl1-mesa-dri: mesa causes xorg segfault; regression against 22.2.0-1
On Fri, 23 Dec 2022 14:53:02 +0100 Fabio Pedretti wrote: > Is this still an issue with 22.3.1-1? If that helps, I have one Intel laptop with Haswell GPU and it works fine with Mesa 22.3.1 (KDE Plasma). Shmerl.
Bug#909636: Fixed upstream
This isn't happening anymore and can be closed.
Bug#1013896: qtbase-opensource-src: Use KDE Qt as upstream instead of qt.io
On Tue, 28 Jun 2022 23:10:24 +0300 Dmitry Shachnev wrote: > Hi Shmerl! > Because KDE does not make any releases, and because some patches break ABI, > we decided to cherry-pick only individual patches that our users request. > > However, we made an exception for Qt Wayland, and the current Qt Wayland > package in testing includes all patches from KDE up to 2022-05-14. This should > fix the issues with Wayland session. > > Are there any other patches you want to have? > > -- > Dmitry Shachnev I know Wayland Qt patches are critical for stable Plasma experience, but I'm not an expert on all of these. May be some communication between upstream KDE developers and Debian team would be good here? Expecting users to know what patches are important isn't a very reliable method. Thanks! Shmerl.
Bug#1013896: qtbase-opensource-src: Use KDE Qt as upstream instead of qt.io
Source: qtbase-opensource-src Version: 5.15.4+dfsg-3 Severity: wishlist X-Debbugs-Cc: shtetl...@gmail.com Dear Maintainer, KDE team maintains important patchset over official Qt that has a lot of bug fixes especially for the Wayland session use case. May be you can switch upstream directly to KDE Qt instead of pulling it from qt.io and then trying to add some patches? See: https://invent.kde.org/qt/qt/qt5/-/tree/kde/5.15 Thanks! -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.7 (SMP w/24 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
Bug#979407: amd64-microcode: Amd64 microcode is not being loaded by the kernel from early initramfs.
On Wed, 06 Jan 2021 10:39:38 + Philip Armstrong wrote: > if I trigger a microcode > load from the shell with > > echo 1 > /sys/devices/system/cpu/microcode/reload > > after booting then the microcode is updated to that newer version. How do you check the current version of microcode in use? Since amd64-microcode package is so outdated in Debian, I updated microcode files manually from the upstream Linux firmware repo, putting them in /usr/lib/firmware/amd-ucode. Then I ran sudo dpkg-recoconfigure amd64-microcode hoping it will update it. On next reboot I have the same version as before (basically what's in my UEFI) according to dmesg. Doing echo 1 > /sys/devices/system/cpu/microcode/reload and checking /proc/cpuinfo I also don't see any change. Thanks, Shmerl.
Bug#890472: Clarification
I contacted LunarG about this, and they clarified the current situation. While they maintain their own repo with Ubuntu packages, they don't have resources to allocate for working on packaging it for Debian. So I'm not sure what's the right way forward for this. Does this need another maintainer or Debian developer to be packaged? Shmerl.
Bug#1002872: Can this be unblocked now?
Looks like it should be just a build time config switch fix. Shmerl.
Bug#890472: Status for Vulkan development tools?
Hi! Any news on this submission? Is anything blocking it or is it lack of maintainers? Thanks! On Mon, 13 Jul 2020 09:57:25 -0600 John Zupin wrote: > Hello, > > Brett is no longer with LunarG and I'll be making updates to his ITP bug > submissions about the status of these packages. > > The current status for the shaderc package is that it has been out for > 1+ years now and is hosted by LunarG. > > I am LunarG's curator for these packages, please check > https://vulkan.lunarg.com/sdk/home under the "ubuntu packages" tab for > more information about our repository.
Bug#998719: calamares: No option to use XFS in filesystem selection
Package: calamares Version: 3.2.44.3-1 Severity: normal X-Debbugs-Cc: shtetl...@gmail.com Dear Maintainer, I tried installing Debian using live image with Calamares and noticed that XFS isn't available in the list of filesystems options when partitioning. May be it's due to missing needed tools related to XFS filesystem? Please configure it to allow using XFS in that step. Thanks! -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0 (SMP w/24 CPU threads) 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 calamares depends on: ii kpackagetool5 5.87.0-1~np1 pn libboost-python1.74.0 pn libboost-python1.74.0-py39 ii libc6 2.32-4 ii libcrypt1 1:4.4.25-2 ii libgcc-s1 11.2.0-10 ii libkf5configcore5 5.87.0-1~np1 ii libkf5coreaddons5 5.87.0-1~np1 ii libkf5package5 5.87.0-1~np1 ii libkf5parts55.87.0-1~np1 ii libkf5service-bin 5.87.0-1~np1 ii libkf5service5 5.87.0-1~np1 ii libkpmcore1121.08.2-1~np2 ii libparted2 3.4-1 pn libpwquality1 ii libpython3.93.9.7-4 ii libqt5core5a5.15.2+dfsg-12 ii libqt5dbus5 5.15.2+dfsg-12 ii libqt5gui5 5.15.2+dfsg-12 ii libqt5network5 5.15.2+dfsg-12 ii libqt5qml5 5.15.2+dfsg-8 ii libqt5quick55.15.2+dfsg-8 ii libqt5quickwidgets5 5.15.2+dfsg-8 ii libqt5svg5 5.15.2-3 ii libqt5webkit5 5.212.0~alpha4-13 ii libqt5widgets5 5.15.2+dfsg-12 ii libqt5xml5 5.15.2+dfsg-12 ii libstdc++6 11.2.0-10 ii libyaml-cpp0.6 0.6.3-10 ii os-prober 1.79 Versions of packages calamares recommends: ii btrfs-progs 5.14.1-1 pn squashfs-tools calamares suggests no packages.
Bug#972323: libllvm11 and libllvm11:i386 aren't coinstallable
Package: libllvm11 Version: 1:11.0.0~+rc6-1 Severity: important X-Debbugs-Cc: shtetl...@gmail.com Dear Maintainer, Recent update to libllvm11 in unstable made libllvm11:amd64 package not coinstallable with libllvm11:i386. According to the build logs: https://buildd.debian.org/status/package.php?p=llvm-toolchain-11 they have a version mismatch: libllvm11:amd64 - 1:11.0.0-2 libllvm11:i386 - 1:11.0.0-2+b1 That makes it impossible to install latest Mesa with both 64 and 32-bit. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0 (SMP w/24 CPU threads) Kernel taint flags: TAINT_WARN, 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 libllvm11 depends on: ii libc6 2.31-3 ii libedit23.1-20191231-1 ii libffi7 3.3-4 ii libgcc-s1 10.2.0-13 ii libstdc++6 10.2.0-13 ii libtinfo6 6.2+20200918-1 ii libz3-4 4.8.9-1 ii zlib1g 1:1.2.11.dfsg-2 libllvm11 recommends no packages. libllvm11 suggests no packages. -- no debconf information
Bug#958151: linux-source-5.6: Please enable hwmon for nvme drives in the kernel config (CONFIG_NVME_HWMON)
Package: linux-source-5.6 Severity: wishlist Dear Maintainer, I just tested kernel 5.6.4 from experimental, and noticed that it doesn't enable hwmon sensors for nvme drives which have been available for some time already. I'm not sure why upstream doesn't enable it by default, but it works very well in general. Please enable CONFIG_NVME_HWMON=y to expose that to Debian build of the kernel. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.3 (SMP w/24 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-source-5.6 depends on: ii binutils 2.34-5 ii xz-utils 5.2.4-1+b1 Versions of packages linux-source-5.6 recommends: ii bc1.07.1-2+b2 pn bison pn flex ii gcc 4:9.2.1-3.1 ii libc6-dev [libc-dev] 2.30-4 pn linux-config-5.6 pn make Versions of packages linux-source-5.6 suggests: pn libncurses-dev | ncurses-dev pn pkg-config pn qtbase5-dev
Bug#939835: This bug is gone now
Just FYI, this bug is gone in Debian testing, due to libvirt updates that happened not long ago.
Bug#956004: mesa: Please build Mesa agaisng llvm 10
Source: mesa Severity: wishlist Dear Maintainer, llvm 10 has various fixes that affect AMD Navi cards, that apparently were not backported to llvm 9 series. llvm 9 is causing desktop hangs on Navi cards even with Mesa 20.x. Please build Mesa in Debian unstable / testing using llvm 10. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.2 (SMP w/24 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#955500: faudio: Please update to latest upstream version
Source: faudio Severity: wishlist Dear Maintainer, faudio in Debian unstable / testing got pretty outdated. In general, upstream releases new versions every month with various bug fixes and features. See: https://github.com/FNA-XNA/FAudio/releases Currently the latest version is 20.04. Please update it in Debian repos. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0 (SMP w/24 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#949340: sddm should by default install sddm-theme-debian-breeze instead of sddm-theme-debian-maui
Package: sddm Version: 0.18.0-1+b2 Severity: normal Dear Maintainer, Currently, when selecting KDE during Debian installation, it by default installs sddm-theme-debian-maui (through sddm installation). It should instead install sddm-theme-debian-breeze, which is much better integrated with KDE's default Breeze theme. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-rc6 (SMP w/24 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) 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.118 ii debconf [debconf-2.0] 1.5.73 ii libc6 2.29-7 ii libgcc1 1:9.2.1-22 ii libpam0g1.3.1-5 ii libqt5core5a5.12.5+dfsg-2 ii libqt5dbus5 5.12.5+dfsg-2 ii libqt5gui5 5.12.5+dfsg-2 ii libqt5network5 5.12.5+dfsg-2 ii libqt5qml5 5.12.5-5 ii libqt5quick55.12.5-5 ii libstdc++6 9.2.1-22 ii libsystemd0 244-3 ii libxcb-xkb1 1.13.1-2 ii libxcb1 1.13.1-2 ii qml-module-qtquick2 5.12.5-5 ii x11-common 1:7.7+20 ii xserver-xorg [xserver] 1:7.7+20 Versions of packages sddm recommends: pn haveged ii libpam-systemd 244-3 ii sddm-theme-breeze [sddm-theme] 4:5.14.5.1-5+b1 Versions of packages sddm suggests: ii libpam-kwallet5 5.14.5-1 pn qtvirtualkeyboard-plugin -- debconf information: sddm/daemon_name: /usr/bin/sddm * shared/default-x-display-manager: sddm
Bug#945846: task-kde-desktop: Use print-manager instead of system-config-printer for KDE installation task
Package: task-kde-desktop Version: 3.55 Severity: wishlist Dear Maintainer, Currently, when selecting KDE in Debian installer, task-kde-desktop pulls in system-config-printer for printer settings, which is part of Gnome project and isn't well integrated with KDE Plasma. Instead, it should use print-manager, which provides printer settings in KDE's own System Settings interface, and as well allows printer queue access for active jobs in notifications area (system tray). Thanks! -- 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-rc7+ (SMP w/24 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages task-kde-desktop depends on: ii kde-standard 5:104 ii sddm 0.18.0-1 ii task-desktop 3.55 ii tasksel 3.55 Versions of packages task-kde-desktop recommends: pn apper ii dragonplayer4:17.08.3-1 ii gimp2.10.12-1 ii hunspell-en-us 1:2018.04.16-1 ii hyphen-en-us2.8.8-7 ii k3b 18.08.1-1 ii k3b-i18n18.08.1-1 ii kdeaccessibility4:17.08.3+5.104 ii libreoffice 1:6.3.3-3 ii libreoffice-help-en-us 1:6.3.3-3 ii libreoffice-kde51:6.3.3-3 ii mythes-en-us1:6.3.1-1 ii orca3.34.0-2 ii plasma-nm 4:5.14.5-2 pn system-config-printer task-kde-desktop suggests no packages. -- no debconf information
Bug#945258: qemu: Filesystem corruption caused by qemu in qcow2 images
Source: qemu Severity: important Dear Maintainer, Currently qemu 4.1 periodically corrupts vm images (qcow2), due to this bug: https://bugs.launchpad.net/qemu/+bug/1846427 Please temporarily apply the provided patches, until upstream will release the fixed version: https://patchwork.kernel.org/cover/11207161/ https://patchwork.kernel.org/patch/11207167/ https://patchwork.kernel.org/patch/11207139/ https://patchwork.kernel.org/patch/11207171/ Thanks! -- 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-rc7+ (SMP w/24 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#943623: Latest llvm10 snapshot still fails with Mesa master
On Tue, 12 Nov 2019 18:11:10 +0100 Sylvestre Ledru wrote: > > https://github.com/llvm/llvm-project/commit/343597789eba1e6482e130b0c1b0818b1432d311 > This is unrelated. Thanks for the clarification, I followed one of the links you posted above, and thought it was related. > I am aware of the issue. No resend the same content as the bug. > It was a long week end here and I have a $$$ job. > > Don't hesitate to step in to help, this is opensource ;) Thanks! Do you have any hints about what to experiment with to address it? I'm quite a loss at what could be the source of this. Best regards, Shmerl.
Bug#943623: Latest llvm10 snapshot still fails with Mesa master
To follow up. According to https://bugs.llvm.org/show_bug.cgi?id=43722#c5, the issue was fixed 5 days ago in https://github.com/llvm/llvm-project/commit/343597789eba1e6482e130b0c1b0818b1432d311 But latest snapshot from http://apt.llvm.org/unstable/pool/main/l/llvm-toolchain-snapshot/ (from 2019-11-11), still fails to work with Mesa master / gcc 9 like this: /usr/bin/ld: /usr/lib/llvm-10/lib/libLLVMAMDGPUDisassembler.a: error adding symbols: archive has no index; run ranlib to add one collect2: error: ld returned 1 exit status Is there something still missing?
Bug#939835: Any update on this?
I'm also affected by this bug. Are there any workarounds?
Bug#943623: Any idea how to fix this?
This issue currently breaks building Mesa master with llvm10 snapshot from http://apt.llvm.org/unstable (in Debian testing).
Bug#890472: Any plans?
It would be good to package shaderc for example for something like mpv to be able to use Vulkan.
Bug#940203: Bugs in the outdated version
Also, current outdated version of faudio in Debian actually has bugs that break games like Dragon Age: Origins in Wine. That should be fixed in the newest upstream.
Bug#940203: faudio: Update faudio to latest upstream version
Source: faudio Severity: wishlist Dear Maintainer, Please update faudio to latest upstream version. They normally come out once a month, so it would be good if they could be packaged in Debian as well. Latest available version at the time of writing is 19.09: https://github.com/FNA-XNA/FAudio/releases -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-rc8+ (SMP w/24 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#939536: qemu-system-data: qemu.desktop is missing Exec entry
Package: qemu-system-data Version: 1:4.1-1 Severity: normal Dear Maintainer, New qemu.desktop file provided by upstream is missing an Exec entry, which according to the spec should be present. See: https://specifications.freedesktop.org/desktop-entry- spec/latest/ar01s06.html > The Exec key is required if DBusActivatable is not set to true. > Even if DBusActivatable is true, Exec should be specified for > compatibility with implementations that do not understand DBusActivatable. For example, running kbuildsycoca5 which checks desktop files correctness, produces this warning: The desktop entry file "/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line I tried to submit the bug upstream, but I can't access launchpad bug tracker used by Qemu, their log-in system is broken (at least now). Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-rc7+ (SMP w/24 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#935768: mesa: Please build Mesa 19.2.0 in experimental against libllvm9 for Navi support
Source: mesa Version: 19.2.0~rc1-1 Severity: wishlist Dear Maintainer, New AMD Navi GPUs (gfx10) need llvm 9 features for amdgpu backend, so please build Mesa 19.2.0 in experimental against libllvm9, to be able to use that Mesa with Navi cards. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-rc5-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#934834: konsole: Update konsole to latest upstream version
Package: konsole Version: 4:18.04.0-1 Severity: normal Dear Maintainer, Konsole in Debian repos got quite outdated, and upstream accumulated a lot of bug fixes and major features like support for extended DECSCUSR escape sequences (helps for nvim) and proper window splitting. See: * https://bugs.kde.org/show_bug.cgi?id=347323 * https://bugs.kde.org/show_bug.cgi?id=178320 Please upload the latest upstream version (at the time of writing - 19.08.0). Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-rc2 (SMP w/16 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages konsole depends on: ii kio 5.54.1-1 ii konsole-kpart 4:18.04.0-1 ii libc6 2.28-10 ii libkf5completion5 5.54.0-1 ii libkf5configcore5 5.54.0-2 ii libkf5configgui5 5.54.0-2 ii libkf5configwidgets5 5.54.0-1 ii libkf5coreaddons5 5.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons5 5.54.0-1 ii libkf5globalaccel55.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes5 5.54.0-1 ii libkf5kiowidgets5 5.54.1-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui5 5.54.0-1 ii libqt5core5a 5.11.3+dfsg1-2+b1 ii libqt5gui55.11.3+dfsg1-2+b1 ii libqt5widgets55.11.3+dfsg1-2+b1 ii libstdc++69.1.0-10 konsole recommends no packages. konsole suggests no packages. -- no debconf information
Bug#909636: kwin-wayland: kwin_wayland is segfaulting right after login
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
