Bug#949340: marked as done (sddm should by default install sddm-theme-debian-breeze instead of sddm-theme-debian-maui)
Your message dated Sun, 09 Oct 2022 08:49:16 + with message-id and subject line Bug#949340: fixed in sddm 0.19.0-4 has caused the Debian Bug report #949340, regarding sddm should by default install sddm-theme-debian-breeze instead of sddm-theme-debian-maui 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.) -- 949340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 --- End Message --- --- Begin Message --- Source: sddm Source-Version: 0.19.0-4 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of sddm, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated sddm 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, 09 Oct 2022 10:30:14 +0200 Source: sddm Architecture: source Version: 0.19.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 949340 1013550 Changes: sddm (0.19.0-4) unstable; urgency=medium . * Team upload. . [ Norbert Preining ] * Recommend sddm-theme-debian-breeze instead of maui (Closes: #949340). The alternatives system gives this theme the highest priority, so install it by default. . [ Pino Toscano ] * Remove inactive Uploaders. * Backport upstream commit e93bf95c54ad8c2a1604f8d7be05339164b19308 to fix build with newer versions of Qt 5.15; patch upstream_Fix-compilation-once-QTBUG-88431-gets-fixed.patch. (Closes: #1013550) * Update lintian overrides. * Use /usr/share/dpkg/architecture.mk instead of querying the $DEB_HOST_* variables manually. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.6.1, no changes needed. * Remove the upstream sddm.service in execute_after_dh_auto_install, rather than execute_before_dh_install; same effect, mostly a better place logically. * Use execute_after_dh_fixperms-arch, and execute_after_dh_installpam to avoid invoking dh_fixperms, and dh_installpam manually. Checksums-Sha1: 62aeabbea01a6f7
Bug#1013550: marked as done (sddm: FTBFS: XorgDisplayServer.cpp:68:42: error: use of deleted function ‘QCharRef& QCharRef::operator=(char)’)
Your message dated Sun, 09 Oct 2022 08:49:16 +
with message-id
and subject line Bug#1013550: fixed in sddm 0.19.0-4
has caused the Debian Bug report #1013550,
regarding sddm: FTBFS: XorgDisplayServer.cpp:68:42: error: use of deleted
function ‘QCharRef& QCharRef::operator=(char)’
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.)
--
1013550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sddm
Version: 0.19.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src/daemon && /usr/bin/c++
> -DHAVE_JOURNALD -DHAVE_SYSTEMD -DNDEBUG -DQT_CORE_LIB -DQT_DBUS_LIB
> -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY
> -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_QML_LIB -DUSE_PAM
> -I/<>/obj-x86_64-linux-gnu/src/daemon
> -I/<>/src/daemon
> -I/<>/obj-x86_64-linux-gnu/src/daemon/sddm_autogen/include
> -I/<>/src/common -I/<>/src/auth
> -I/<>/obj-x86_64-linux-gnu/src/common -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQml -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Wall
> -std=c++11 -fPIC -MD -MT src/daemon/CMakeFiles/sddm.dir/PowerManager.cpp.o
> -MF CMakeFiles/sddm.dir/PowerManager.cpp.o.d -o
> CMakeFiles/sddm.dir/PowerManager.cpp.o -c
> /<>/src/daemon/PowerManager.cpp
> /<>/src/daemon/XorgDisplayServer.cpp: In constructor
> ‘SDDM::XorgDisplayServer::XorgDisplayServer(SDDM::Display*)’:
> /<>/src/daemon/XorgDisplayServer.cpp:68:42: error: use of
> deleted function ‘QCharRef& QCharRef::operator=(char)’
>68 | m_cookie[i] = digits[dis(gen)];
> | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
> from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
> from /<>/src/daemon/DisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.cpp:21:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1236:15: note: declared
> here
> 1236 | QCharRef &operator=(char c) = delete;
> | ^~~~
> /<>/src/daemon/XorgDisplayServer.cpp: In member function
> ‘virtual bool SDDM::XorgDisplayServer::start()’:
> /<>/src/daemon/XorgDisplayServer.cpp:174:74: warning:
> ‘QStringList QString::split(QChar, QString::SplitBehavior,
> Qt::CaseSensitivity) const’ is deprecated: Use split(QChar sep,
> Qt::SplitBehavior ...) variant instead [-Wdeprecated-declarations]
> 174 | QStringList args =
> mainConfig.X11.ServerArguments.get().split(QLatin1Char(' '),
> QString::SkipEmptyParts);
> |
> ~~^~~
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
> from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
> from /<>/src/daemon/DisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.cpp:21:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:615:17: note: declared here
> 615 | QStringList split(QChar sep, SplitBehavior behavior,
> | ^
> /<>/src/daemon/XorgDisplayServer.cpp: In member function
> ‘virtual void SDDM::XorgDisplayServer::finished()’:
> /<>/src/daemon/XorgDisplayServer.cpp:288:33: warning: ‘void
> QProcess::start(const QString&, QIODevice::OpenMode)’ is deprecated: Use
> QProcess::start(const QString &program, const QStringList &arguments,OpenMode
> mode = ReadWrite) instead [-Wdeprecated-declarations]
> 288 | displayStopScript->start(displayStopCommand);
> | ^~~~
> In file included from
> /usr/include/x86_64-linux-gnu/qt5/QtCore/QProcessEnvironment:1,
> from /<>/src/auth/Auth.h:28,
> from /<>/src/daemon/Display.h:28,
>
Processing of sddm_0.19.0-4_source.changes
sddm_0.19.0-4_source.changes uploaded successfully to localhost along with the files: sddm_0.19.0-4.dsc sddm_0.19.0-4.debian.tar.xz sddm_0.19.0-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: tagging 949340
Processing commands for cont...@bugs.debian.org:
> tags 949340 + pending
Bug #949340 {Done: Pino Toscano } [sddm] sddm should by
default install sddm-theme-debian-breeze instead of sddm-theme-debian-maui
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 949340
Processing commands for cont...@bugs.debian.org:
> tags 949340 - pending
Bug #949340 {Done: Pino Toscano } [sddm] sddm should by
default install sddm-theme-debian-breeze instead of sddm-theme-debian-maui
Removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
sddm_0.19.0-4_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 09 Oct 2022 10:30:14 +0200 Source: sddm Architecture: source Version: 0.19.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 949340 1013550 Changes: sddm (0.19.0-4) unstable; urgency=medium . * Team upload. . [ Norbert Preining ] * Recommend sddm-theme-debian-breeze instead of maui (Closes: #949340). The alternatives system gives this theme the highest priority, so install it by default. . [ Pino Toscano ] * Remove inactive Uploaders. * Backport upstream commit e93bf95c54ad8c2a1604f8d7be05339164b19308 to fix build with newer versions of Qt 5.15; patch upstream_Fix-compilation-once-QTBUG-88431-gets-fixed.patch. (Closes: #1013550) * Update lintian overrides. * Use /usr/share/dpkg/architecture.mk instead of querying the $DEB_HOST_* variables manually. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.6.1, no changes needed. * Remove the upstream sddm.service in execute_after_dh_auto_install, rather than execute_before_dh_install; same effect, mostly a better place logically. * Use execute_after_dh_fixperms-arch, and execute_after_dh_installpam to avoid invoking dh_fixperms, and dh_installpam manually. Checksums-Sha1: 62aeabbea01a6f74265f9b75312ebb7bac342553 2609 sddm_0.19.0-4.dsc 168b7249c468f5f2523f6f7f0631a4bf62ae943d 59408 sddm_0.19.0-4.debian.tar.xz 8ce64ebab8e01058b407eda88b047c91a806abc3 12695 sddm_0.19.0-4_source.buildinfo Checksums-Sha256: fc190d4c32cb65c7a11f7e600d901dd684ba174301b3cada6041fe84e9359f30 2609 sddm_0.19.0-4.dsc 028e275ad11b131c01b23945e9c15820a127f23d9a2c47a208ccc3744905d9fa 59408 sddm_0.19.0-4.debian.tar.xz 87d4ed211499e545c69f89efed23d89899756d24aae906c0746573d576c8b135 12695 sddm_0.19.0-4_source.buildinfo Files: 6aecb659049881a6bbca4ed3984e55a0 2609 kde optional sddm_0.19.0-4.dsc 5d90beb150cca5c65478444ae48a31b7 59408 kde optional sddm_0.19.0-4.debian.tar.xz 12b769432f21818fd82ee872f9cd8514 12695 kde optional sddm_0.19.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmNChr8ACgkQLRkciEOx P01T0A//T7iBBFwFxKjpRBGE9Jo1Jr2ogGqNpAkAOwB1NoR4DZCYtATxkDsJZ0oP 33hQHilqUIW+j/zuKU0tzfM/rzOEiyB75wvI9cCQXG72ZoSPCT0dwqeGp449XP/E llewpyV/u4twiE5L/5GwUpgrXtJgLx4PRp9CsFjPGwpmWrDwWk0oHAUfY2/ldhuu kJRScfyuAT3RrX6soQSPvNLuOJdsL8lmkj2xAU6iiFgoZKrFbMIOdmM/RYHRpo4X giHbXFHY1xbU0OJ1oi2H4rK0TnLhHhBpX2F1C1gjphO+mm7Qo8LBIS/kAHmlO7eQ VjJoEM2zQxRCxW6eBuc7lBzOUE1sj+Myvi+dxF/wA/0c6TnK//boyvtInJcL0PXG k2F080g/yKVYjA5CiHJIeNvRiRVMFO2dVGa85spDBUR0BvPsexZGyYM+gEpayIPj UFOsWLxpjDgibDxxQun/1Zknf2f1rROIB51mOc8FMGbu+G9pbdvwugFsJpfqfuA7 iaQxF1BQ+zG5r29Oh6sxmUtqAukyCCq/7x5JnhOyfk+1SRr+n64BGWeMxkqTQ2Af pKvp67wW42RPZXZa7PNcdxz/9YF9YpuZfRJ4J1ITQID+S2WVcGxMyMc7/ttI14sw CUDjtoXYKEBeYX/b4viEriDmiSSPHsZCG248wrUgU+34bd/e6P4= =m2nG -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#361898: marked as done (ark: remember archive format for unknown types)
Your message dated Sun, 09 Oct 2022 11:11:08 +0200 with message-id and subject line Fixed upstream has caused the Debian Bug report #361898, regarding ark: remember archive format for unknown types 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.) -- 361898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ark Version: 4:3.5.1-2 Severity: wishlist there should be a way to remember/add an uknown type and associated archive format instead of being prompted each time to choose one. i.e. if I have a file of type application/lwtp I would like to define that as a zip archive only once. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages ark depends on: ii kdelibs4c2a 4:3.5.1-2 core libraries for all KDE applica ii libacl1 2.2.36-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.32-1 Extended attribute shared library ii libaudio2 1.7-6 The Network Audio System (NAS). (s ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libfontconfig12.3.2-1.1 generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgamin0 [libfam0] 0.1.7-3Client library for the gamin file ii libgcc1 1:4.1.0-1 GCC support library ii libice6 6.9.0.dfsg.1-6 Inter-Client Exchange library ii libidn11 0.5.18-2 GNU libidn library, implementation ii libjpeg62 6b-12 The Independent JPEG Group's JPEG ii libpng12-01.2.8rel-5 PNG library - runtime ii libqt3-mt 3:3.3.5-4 Qt GUI Library (Threaded runtime v ii libsm66.9.0.dfsg.1-6 X Window System Session Management ii libstdc++64.1.0-1The GNU Standard C++ Library v3 ii libx11-6 6.9.0.dfsg.1-6 X Window System protocol client li ii libxcursor1 1.1.3-1X cursor management library ii libxext6 6.9.0.dfsg.1-6 X Window System miscellaneous exte ii libxft2 2.1.8.2-5.1FreeType-based font drawing librar ii libxi66.9.0.dfsg.1-6 X Window System Input extension li ii libxinerama1 6.9.0.dfsg.1-6 X Window System multi-head display ii libxrandr26.9.0.dfsg.1-6 X Window System Resize, Rotate and ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii libxt66.9.0.dfsg.1-6 X Toolkit Intrinsics ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages ark recommends: pn arj(no description available) ii bzip2 1.0.3-2high-quality block-sorting file co pn ncompress (no description available) ii unzip 5.52-7 De-archiver for .zip files ii zip 2.31-3 Archiver for .zip files pn zoo(no description available) -- no debconf information --- End Message --- --- Begin Message --- control: fixed -1 4:15.08.1-1--- End Message ---
Processed: fixed 361898 in ark/4:15.08.1-1
Processing commands for cont...@bugs.debian.org:
> fixed 361898 ark/4:15.08.1-1
Bug #361898 {Done: Aurélien COUDERC } [ark] ark: remember
archive format for unknown types
Marked as fixed in versions ark/4:15.08.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
361898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1018003: comment
May also be related to "Plasmashell problems after changing the HDMI output and
KDE does not recognize the new display":
https://bugs.kde.org/show_bug.cgi?id=457755
Currently, it doesn't crash anymore but I often need to go to an alt+f3 (any
number) terminal and run `loginctl unlock-session {id}` and `logout` to resume
the session.
Bug#1018003: comment
In the totally outdated issue tracker I can't edit the text: it doesn't crash anymore because as a workaround I have the monitor HDMI cable disconnected except when I use it. When connecting the HDMI cable, the session ends only when the monitor that the HDMI cable is plugged into is turned off. The wallpaper is changed to a default one nevertheless. Currently, the remaining problem is that when doing one of these things to switch the monitor back again the sessions as well: a) pulling out the HDMI cable b) switching off the active second monitor c) press meta+p and selecting "Unify outputs" (haven't tried the other ones yet). For the workout to be complete, I only need to find out how to switch back to the formerly active display without the session ending. I'll try a few more things later such as going into standby, then pulling out the HDMI cable, and waking it again. If somebody knows a working workaround, please comment.
