qtcreator_5.0.0-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Aug 2021 20:32:28 +0200 Source: qtcreator Architecture: source Version: 5.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Changes: qtcreator (5.0.0-1) unstable; urgency=medium . * Team upload. * Upload to unstable. * New upstream release. * Switch watch file back to stable releases. * Bump Standards-Version to 4.6.0, no changes required. Checksums-Sha1: 3c7ebb762fc0a330327884c6875d9cba6c12ff89 2963 qtcreator_5.0.0-1.dsc 4e8e5e52c6272fcebd0abc6bad8994b3b489ab80 45430108 qtcreator_5.0.0.orig.tar.xz b5e634e8063004cae0bd0b8de6adf1d29a56e53c 26336 qtcreator_5.0.0-1.debian.tar.xz 47dc347e6455c1213bd916e0ff7742d92d1ef7ab 14612 qtcreator_5.0.0-1_source.buildinfo Checksums-Sha256: 8a41e449d2a20efd38ccda9549fec46114505fd426de55eb4a7ae0552f970990 2963 qtcreator_5.0.0-1.dsc b24b194a2e96f07baf55815264cd898fa0399673bfedd500575098fdf8d70475 45430108 qtcreator_5.0.0.orig.tar.xz 94b25b1eb7d66e93a08250c8283a7109bf3472337780c0b773aaf6a343da110d 26336 qtcreator_5.0.0-1.debian.tar.xz 2b88e0a2a17ed7b3f80d6b7b2f71f7d181fd4cd8e810db2bd60ae3db58294693 14612 qtcreator_5.0.0-1_source.buildinfo Files: d84da6fe73777eef7513e698afec860d 2963 devel optional qtcreator_5.0.0-1.dsc 2464c38b97e9cc9698243543e56efc15 45430108 devel optional qtcreator_5.0.0.orig.tar.xz 677aace210f9e531bd9a5fb9938fbed1 26336 devel optional qtcreator_5.0.0-1.debian.tar.xz f880759c48b841b39d6461b5b6580ec9 14612 devel optional qtcreator_5.0.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmEn3pcACgkQLRkciEOx P03JZw/5AQ33ph+UI7TQ/KzmICRfuKL7Uch+TexOVdKWgOxiVFBizvEK6rvG57Aa bHNfpN1CdPuZInQ693L2MGJoh/W5k53U2pcY7L1FWRsi16fZ9YXT3gJVj/oern/w DQRlZtz1VPF14F+rt4DcpICyd3sLVIRaycEvy4PtJpeBKYwibTHpv97V4v3VGEIW azt7gg9dn5T8xxFOp952FjfSlACorFqnvaA8L2xfQs9IHcy0g6xURbYWP7TtkMV1 LJloZoF8xMj1Kp4W68PV6+u0o0b07VwWvNQUfeBGXtOxFsaiXxws4PjTYeFmx56u +4meHIF9K5a/N2KCdU2dlnJl2lJo00zoTrdIs2wRVuW5XSjyu0SC//sDHDM7lzdn jeKOTNdNjBOYnGct/NnNC2QIZ5SRoKlaEJgwOrVAppncYRCgTiLDH+KThwFHR+DB THa/ruv1bzgOyMq2vQKbG0f82F5nQoXwY5pm61GGu7WVwp+EYuIH7MQawYKYP3uw gP8Ma+bmoo11rLwTsZQkj008aONF3/U8mt6ialnHtRihlyoA/w16EZtrTWJdKMw1 1L8MULGtlApwaU+RNulNIy/s1q3IDUOLgyMJi1dLts1+X6G7djfDryj8OQfXzRnH ZS8sowHm/SPFJ94v5LB/7DK0u5x6RgVl6LhttddC3QcfQv0tcE8= =KTsa -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of qtcreator_5.0.0-1_source.changes
qtcreator_5.0.0-1_source.changes uploaded successfully to localhost along with the files: qtcreator_5.0.0-1.dsc qtcreator_5.0.0.orig.tar.xz qtcreator_5.0.0-1.debian.tar.xz qtcreator_5.0.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#993036: plasma-workspace: Provide locked sessions
Package: plasma-workspace Version: 5.21.5-3 Severity: wishlist Tags: patch The attached patch creates additional session definitions for X and Wayland that launch Plasma in a locked state. Using them with auto-login makes for a great combination. I had been looking for something like this for years. The patch applies against 5.21.5-3, but I have only tested it with 5.20.5-6. Locked auto-login under X works nicely and it's what I'll be using. Locked auto-login under Wayland works, too, but is a rather rocky experience IMO. I also recommend using throwaway user accounts for testing (to not mess up your saved session) and running top/htop on a separate VT during the familiarization phase and keeping an eye on CPU usage. Notable observations from my testing: * kwin_wayland pegs the CPU to ~385% until you unlock the session (with DRM backend on nouveau). I guess disabling some effects could reduce that, but I haven't looked into that. * Consequently mouse movement is choppy, and you have to put the pointer directly over the password field for it to retain focus. * The window dimensions of the kscreenlocker_greet window change once Plasma launches the Task Manager leaving a black bar at the position where the Task Manager would be. * Also upon logout sometimes stray processes (korgac, kactivitymanager, kded5) stay around which consume ~200 % CPU till killed. I can't reliably reproduce this yet, though, so it might be nothing. Regards, Dennis Filder --- a/debian/rules +++ b/debian/rules @@ -11,6 +11,18 @@ include /usr/share/pkg-kde-tools/qt-kde-team/2/library-packages.mk override_dh_auto_configure: dh_auto_configure -Skf5 -- -DBUILD_TESTING=OFF +override_dh_auto_install: + dh_auto_install --buildsystem=kf5 -i -O--buildsystem=kf5 + rm -f debian/tmp/usr/share/xsessions/plasmalocked.desktop debian/tmp/usr/share/wayland-sessions/plasmawaylandlocked.desktop + cp -a debian/tmp/usr/share/xsessions/plasma.desktop debian/tmp/usr/share/xsessions/plasmalocked.desktop + cp -a debian/tmp/usr/share/wayland-sessions/plasmawayland.desktop debian/tmp/usr/share/wayland-sessions/plasmawaylandlocked.desktop + sed -f debian/genlockedplasma.sed -i debian/tmp/usr/share/xsessions/plasmalocked.desktop + sed -f debian/genlockedplasma.sed -i debian/tmp/usr/share/wayland-sessions/plasmawaylandlocked.desktop +# Test if the above actually took effect and error out if it didn't + grep -q -e DESKTOP_LOCKED=true debian/tmp/usr/share/xsessions/plasmalocked.desktop + grep -q -e --lockscreen debian/tmp/usr/share/wayland-sessions/plasmawaylandlocked.desktop + grep -q -e '^Name=.*(Wayland)$$' debian/tmp/usr/share/wayland-sessions/plasmawaylandlocked.desktop + override_dh_auto_test: # Disable auto tests at build time : --- a/debian/plasma-workspace.install +++ b/debian/plasma-workspace.install @@ -66,3 +66,4 @@ usr/share/kservicetypes5/ usr/share/metainfo/ usr/share/solid/actions/test-predicate-openinwindow.desktop usr/share/xsessions/plasma.desktop +usr/share/xsessions/plasmalocked.desktop --- a/debian/plasma-workspace-wayland.install +++ b/debian/plasma-workspace-wayland.install @@ -1,3 +1,4 @@ usr/bin/startplasma-wayland usr/lib/*/libexec/startplasma-waylandsession usr/share/wayland-sessions/plasmawayland.desktop +usr/share/wayland-sessions/plasmawaylandlocked.desktop --- /dev/null +++ b/debian/genlockedplasma.sed @@ -0,0 +1,26 @@ +# -*- mode: conf; -*- + +# https://github.com/sddm/sddm/issues/306 has some discussion + +s@^Exec=\(/usr/.*/startplasma-x11.*\)$@Exec=/usr/bin/env DESKTOP_LOCKED=true \1@ +# The Plasma devs in their infinite wisdom made startplasma-wayland +# ignore DESKTOP_LOCKED. Also because their approach to command line +# defaults is a bit unorthodox, we have to specify the command line +# in full like so carefully preserving arch-specific paths. +s@^Exec=/usr/\(.*/libexec\)/\(plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland.*\)$@Exec=/usr/\1/\2 --lockscreen --xwayland --exit-with-session /usr/\1/startplasma-waylandsession@ + +# sddm in src/common/Session.cpp:Session::setTo() foolishly expects +# the string "(Wayland)" at the very end of Name= (instead of e.g. +# inspecting Type=), so we must preserve it until they fix the code. +# +# Consider using U+1F510 CLOSED LOCK WITH KEY () or U+1F512 LOCK +# () once Qt supports it. +#s@^Name=\(Plasma\)\(.*\)$@Name=\1 \2@ +#s@^Name=\(Plasma\)\(.*\)$@Name=Locked \1\2@ +#s@^Name=\(Plasma\)\(.*\)$@Name=\1 „-o\2@ +#s@^Name=\(Plasma\)\(.*\)$@Name=\1 o––⃩\2@ +#s@^Name=\(Plasma\)\(.*\)$@Name=\1 o¬\2@ +#s@^Name=\(Plasma\)\(.*\)$@Name=\1 ◯—▄\2@ +s@^Name=\(Plasma\)\(.*\)$@Name=\1 [locked]\2@ + +s@^Comment=\(.*\)$@Comment=\1 (locked)@
Bug#981349: kde/plasma does not start under wayland (solved)
X-Debbugs-CC: Antonio
This happened to me, too. I can't tell what the cause in your case
might have been, but in my case it was because I set DISPLAY to ":0"
via ~/.pam_environment which made kwin_wayland believe it is running
within an X server, so it chose the X11 backend without testing if it
could actually connect to the X server first. Since with SDDM (which
I use, too) the sddm-greeter's X server runs as user sddm, the
logged-in user's .Xauthority file will not match (because it is not
updated when entering a Wayland session) and the connection will fail
with an authentication error.
A remedy would be to actually try to open an X display in
kwin/main_wayland.cpp:automaticBackendSelection() and choose a
different plugin if it fails. The code could look as simple as this:
#include
...
static QString automaticBackendSelection(SpawnMode spawnMode)
{
...
if (qEnvironmentVariableIsSet("DISPLAY")) {
if (qEnvironmentVariableIsSet("KWIN_WAYLAND_SKIP_X11CHECK"))
return s_x11Plugin;
Display *d = XOpenDisplay(NULL);
if (d) {
XCloseDisplay(d);
return s_x11Plugin;
}
}
...
}
Since kwin_wayland already links against libX11.so.6 there would be no
new dependencies.
N.B.: There is another very insidious problem here with how
startplasma-wayland chooses default values. If startplasma-wayland is
called without arguments it unconditionally runs:
kwin_wayland --xwayland
--exit-with-session=/path/to/startplasma-waylandsession
But if a user modifies the Exec= line in
/usr/share/wayland-sessions/plasmawayland.desktop to e.g.
/usr/bin/startplasma-wayland --drm
then it runs only this:
kwin_wayland --drm
The user has no way of knowing (beyond studying the source code) that
he must also specify those other options, too, as otherwise the Plasma
session will not be set up correctly due to a missing X server. The
lack of a manpage does not help exactly either.
Regards.
Bug#993030: plasma-desktop: keyboard layout swaps third level characters
Package: plasma-desktop Version: 4:5.21.5-2 Severity: normal Dear Maintainer, Something strange happened to the keyboard layout treatment and I am not sure where exactly. It manifests in KDE plasma, which I upgraded recently and thus I assume that the issue is with plasma. I do not know the exact package which handles the keybord layout, so feel free to reassign to other package. The issue is with "Lithuanian" kayboard layout with "Lithuanian (US)" variant. Normally the layout is the same as US keyboard, except the 3rd level (accessible by holding Right-AltGr) contains Lithuanian letters on the number keys (the row above the letters, not the numberpad). The issue is that the 3rd level (Lithuanian letters) now work at the 1st level (ie. without Right-AltGr) and the numbers are accessible as 3rd level (while holding the Right-AltGr). The keyboard settings still show the correct layout (1st numbers, 3rd LT letters). I have tried removing and re-adding this layout, and the issue persists. I have tried Danish layout and the issue is not there (i.e. 1st level are numbers and 3rd are currency and other characters), so maybe the issue is specific to this particular variant. * What led up to the situation? apt update && apt upgrade && plasmashell --restart * What exactly did you do (or not do) that was effective (or ineffective)? now I am forced to switch between US and LT layout which is not convenient. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (900, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-desktop depends on: ii accountsservice 0.6.55-3 ii breeze 4:5.21.5-2 ii kactivitymanagerd5.21.5-2 ii kde-cli-tools4:5.21.5-2 ii kded55.83.0-2 ii kio 5.83.0-2 ii kpackagetool55.83.0-2 ii libaccounts-qt5-11.16-2 ii libc62.31-13 ii libcrypt11:4.4.18-4 ii libglib2.0-0 2.68.4-1 ii libibus-1.0-51.5.24-1 ii libkaccounts24:21.08.0-1 ii libkf5activities55.83.0-2 ii libkf5activitiesstats1 5.83.0-2 ii libkf5authcore5 5.83.0-2 ii libkf5baloo5 5.83.0-2 ii libkf5codecs55.83.0-2 ii libkf5completion55.83.0-2 ii libkf5configcore55.83.0-2 ii libkf5configgui5 5.83.0-2 ii libkf5configwidgets5 5.83.0-3 ii libkf5coreaddons55.83.0-2 ii libkf5crash5 5.83.0-2 ii libkf5dbusaddons55.83.0-2 ii libkf5declarative5 5.83.0-2 ii libkf5globalaccel-bin5.83.0-2 ii libkf5globalaccel5 5.83.0-2 ii libkf5guiaddons5 5.83.0-2 ii libkf5i18n5 5.83.0-3 ii libkf5iconthemes55.83.0-2 ii libkf5itemviews5 5.83.0-2 ii libkf5jobwidgets55.83.0-2 ii libkf5kcmutils5 5.83.0-2 ii libkf5kdelibs4support5 5.83.0-2 ii libkf5kiocore5 5.83.0-2 ii libkf5kiofilewidgets55.83.0-2 ii libkf5kiogui55.83.0-2 ii libkf5kiowidgets55.83.0-2 ii libkf5newstuff5 5.83.0-2 ii libkf5notifications5 5.83.0-3 ii libkf5notifyconfig5 5.83.0-2 ii libkf5package5 5.83.0-2 ii libkf5plasma55.83.0-2 ii libkf5plasmaquick5 5.83.0-2 ii libkf5quickaddons5 5.83.0-2 ii libkf5runner55.83.0-3 ii libkf5service-bin5.83.0-2 ii libkf5service5 5.83.0-2 ii libkf5solid5 5.83.0-2 ii libkf5sonnetcore55.83.0-2 ii libkf5sonnetui5 5.83.0-2 ii
Bug#993017: plasma-workspace: Desktop freeze and occupies two CPU core (dead loop)
Package: plasma-workspace Version: 4:5.20.5-6 Severity: important X-Debbugs-Cc: lkphantom1...@gmail.com Dear Maintainer, The plasma desktop were freeze very frequently after i upgrade to this version (4:5.20.5-6). The process 'plasmashell' bring 1 to 2 CPUs trapped into dead loop when problem occurs. I highly doubt the problem were relative to notification module (most cases happens while notification were flood by some apps, but that won't trigger this problem in elder version). I've got some STDOUT log from 'plasmashell' while problem happen: == log begin qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:153: TypeError: Value is undefined and could not be converted to an object qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:153: TypeError: Value is undefined and could not be converted to an object file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" libkcups: Renew-Subscription last error: 0 successful-ok file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:59:9: QML QQuickTextEdit: Binding loop detected for property "width" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:59:9: QML QQuickTextEdit: Binding loop detected for property "width" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:549:39: QML DeviceListItem: Binding loop detected for property "width" qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:494:39: QML StreamListItem: Binding loop detected for property "width" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:314: TypeError: Cannot read property 'width' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" libkcups: Renew-Subscription last error: 0 successful-ok
Bug#987426: juk: Volume slider displays wrong volume level
Package: juk Version: 4:20.12.3-1 Followup-For: Bug #987426 X-Debbugs-Cc: lkphantom1...@gmail.com Dear Maintainer, The volume indicator and slider **always** shows wrong volume level (-2,147,483,648%, equivalent to 0x8000 in int32_t). The problem didn't affect actual volume level, and i could still change the actual volume by swipe the slider(but -2,147,483,648% will appears again on next time). -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.118.anthony.ll (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 Versions of packages juk depends on: ii kio5.78.0-5 ii libc6 2.31-13 ii libgcc-s1 10.2.1-6 ii libkf5completion5 5.78.0-3 ii libkf5configcore5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons5 5.78.0-4 ii libkf5crash5 5.78.0-3 ii libkf5dbusaddons5 5.78.0-2 ii libkf5globalaccel-bin 5.78.0-3 ii libkf5globalaccel5 5.78.0-3 ii libkf5i18n55.78.0-2 ii libkf5iconthemes5 5.78.0-2 ii libkf5jobwidgets5 5.78.0-2 ii libkf5kiocore5 5.78.0-5 ii libkf5kiowidgets5 5.78.0-5 ii libkf5notifications5 5.78.0-2 ii libkf5textwidgets5 5.78.0-2 ii libkf5wallet-bin 5.78.0-2 ii libkf5wallet5 5.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5windowsystem55.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libphonon4qt5-44:4.11.1-4 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5dbus55.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5network5 5.15.2+dfsg-9 ii libqt5svg5 5.15.2-3 ii libqt5widgets5 5.15.2+dfsg-9 ii libqt5xml5 5.15.2+dfsg-9 ii libstdc++6 10.2.1-6 ii libtag1v5 1.11.1+dfsg.1-3 ii phonon4qt5 4:4.11.1-4 juk recommends no packages. Versions of packages juk suggests: ii k3b 20.12.2-1 -- no debconf information
