Re: Status of Plasma 5.18/5.19?
hi Shmerl When I asked similar a while ago my conclusion was the amount of work, hundreds of packages, on one side and the amount of packagers on the other side. And of course disagreements in this case make the effective packaging capacity even smaller. Luc Op 01-07-2020 om 22:03 schreef Shmerl: > Debian Sid is still on Plasma 5.17, meanwhile 5.18 LTS and 5.19 have already > been released with 5.20 around the corner > ... > What is the status on this now? Did you actually find the answer to your question? From this whole thread, I still don't understand why is Plasma still outdated in Debian testing / unstable. All I got was that there was some disagreement and packaging help was rejected. But that doesn't explain what the disagreement was and why Plasma wasn't updated in such a long time either way. There must be some blockers or issues obviously that prevent it. Can anyone please elaborate on it for the benefit of those who are reading it? Thanks! Shmerl. -- m.vr.gr. Luc Castermans mailto:luc.casterm...@gmail.com
Bug#895718: marked as done (libqt5core5a: Requires Linux kernel 3.17.0 or newer)
Your message dated Thu, 2 Jul 2020 10:56:36 +0800 with message-id and subject line Using new kernel can fix this problem has caused the Debian Bug report #964064, regarding libqt5core5a: Requires Linux kernel 3.17.0 or newer 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.) -- 964064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-pyqt5 Version: 5.9.2+dfsg-1 Severity: grave Justification: renders package unusable Tried this on sid with both pyqt5 5.9.2 and 5.10.1: Unpacking python-pyqt5 (5.10.1+dfsg-1) over (5.9.2+dfsg-1+b1) ... Setting up python-pyqt5 (5.10.1+dfsg-1) ... # python Python 2.7.14+ (default, Apr 2 2018, 04:16:25) [GCC 7.3.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import PyQt5.QtCore Traceback (most recent call last): File "", line 1, in ImportError: libQt5Core.so.5: cannot open shared object file: No such file or directory >>> I checked and libQt5Core.so.5 is installed at the expected location: # ls -l /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 lrwxrwxrwx 1 root root 20 Apr 7 19:35 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -> libQt5Core.so.5.10.1 # ls -l /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.1 -rw-r--r-- 1 root root 5224752 Apr 7 19:35 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.1 The same thing happenson python3 too: Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import PyQt5.QtCore Traceback (most recent call last): File "", line 1, in ImportError: libQt5Core.so.5: cannot open shared object file: No such file or directory Scott K --- End Message --- --- Begin Message --- Thanks for your information--- End Message ---
Bug#902118: marked as done (quassel-core: quasselcore unable to load installed libQt5Core.so.5)
Your message dated Thu, 2 Jul 2020 10:56:36 +0800
with message-id
and subject line Using new kernel can fix this problem
has caused the Debian Bug report #964064,
regarding quassel-core: quasselcore unable to load installed libQt5Core.so.5
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.)
--
964064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quassel-core
Version: 1:0.12.5-2
Severity: important
Dear Maintainer,
I am unable to start the quasselcore systemd service unit. Manually starting
quasselcore results in:
$ sudo -u quasselcore quasselcore
quasselcore: error while loading shared libraries: libQt5Core.so.5: cannot open
shared object file: No such file or directory
If I comment the systemd-option Restart=on-failure in the provided
quasselcore.service
file, I can see the same issue via systemd (otherwise systemd will complain
about too many restart tries):
$ sudo systemctl status quasselcore
● quasselcore.service - distributed IRC client using a central core component
Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-06-22 15:44:18 CEST; 1min
23s ago
Docs: man:quasselcore(1)
Process: 12060 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR}
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN}
(code=exited, status=127)
Main PID: 12060 (code=exited, status=127)
Jun 22 15:44:18 systemd[1]: Started distributed IRC client using a central core
component.
Jun 22 15:44:18 quasselcore[12060]: /usr/bin/quasselcore: error while loading
shared libraries: libQt5Core.so.5: cannot open shared object file: No such file
or directory
Jun 22 15:44:18 systemd[1]: quasselcore.service: Main process exited,
code=exited, status=127/n/a
Jun 22 15:44:18 systemd[1]: quasselcore.service: Failed with result 'exit-code'
LibQt5Core.so.5 is installed, though:
$ sudo updatedb && locate libQt5Core.so.5 | xargs ls -l
lrwxrwxrwx 1 root root 20 May 20 23:57
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -> libQt5Core.so.5.10.1
lrwxrwxrwx 1 root root 20 May 20 23:57
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10 -> libQt5Core.so.5.10.1
-rw-r--r-- 1 root root 5224752 May 20 23:57
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.1
ldd reports the binary cannot find libQt5Core.so.5, but other Qt5 libraries are
found:
$ ldd `which quasselcore`
linux-vdso.so.1 (0x74250a074000)
libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
(0x742509908000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x742509704000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7425094e6000)
libQt5Script.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
(0x74250905)
libQt5Sql.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5
(0x742508e06000)
libqca-qt5.so.2 => /usr/lib/x86_64-linux-gnu/libqca-qt5.so.2
(0x742508b13000)
libQt5Core.so.5 => not found
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x74250879)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7425083d6000)
libQt5Core.so.5 => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7425081b8000)
/lib64/ld-linux-x86-64.so.2 (0x74250a075000)
libQt5Core.so.5 => not found
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x742507e23000)
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x742507c0b000)
Running ldconfig, or setting LD_LIBRARY_PATH does not help, either:
$ sudo -u quasselcore LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu quasselcore
quasselcore: error while loading shared libraries: libQt5Core.so.5: cannot open
shared object file: No such file or directory
Upstream offers a version of the quassel-core, which is statically linked
against Qt, so testing that does not make much sense. I have not tried to build
quassel-core from source myself.
kind regards,
Christoph Terasa
-- System Information:
Debian Release: buster/sid
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14.32--grs-ipv6-64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Bug#964064: marked as done (python3-pyqt5: ImportError when from PyQt5 import QtGui)
Your message dated Thu, 2 Jul 2020 10:56:36 +0800 with message-id and subject line Using new kernel can fix this problem has caused the Debian Bug report #964064, regarding python3-pyqt5: ImportError when from PyQt5 import QtGui 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.) -- 964064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pyqt5 Version: 5.15.0+dfsg-1 Severity: important Dear Maintainer, Running `python3 -c "from PyQt5 import QtGui"` throws importError, says libQt5Core.so not found. To reproduce this error: root@c208a4fd881c:~/ete/ete# python3 Python 3.8.3 (default, May 14 2020, 11:03:12) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from PyQt5 import QtGui Traceback (most recent call last): File "", line 1, in ImportError: libQt5Core.so.5: cannot open shared object file: No such file or directory The file `/usr/lib/x86_64-linux-gnu/libQt5Core.so.5` exists on the system. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10.0-957.1.3.el7.x86_64 (SMP w/56 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages python3-pyqt5 depends on: ii libc6 2.30-8 ii libgcc-s1 10.1.0-4 ii libpython3.8 3.8.3-1 ii libqt5core5a [qtbase-abi-5-12-5] 5.12.5+dfsg-10+b1 ii libqt5dbus5 5.12.5+dfsg-10+b1 ii libqt5designer5 5.12.5-2+b2 ii libqt5gui55.12.5+dfsg-10+b1 ii libqt5help5 5.12.5-2+b2 ii libqt5network55.12.5+dfsg-10+b1 ii libqt5printsupport5 5.12.5+dfsg-10+b1 ii libqt5test5 5.12.5+dfsg-10+b1 ii libqt5widgets55.12.5+dfsg-10+b1 ii libqt5xml55.12.5+dfsg-10+b1 ii libstdc++610.1.0-4 ii python3 3.8.2-3 ii python3-sip [sip-py3api-12.7] 4.19.23+dfsg-1 python3-pyqt5 recommends no packages. Versions of packages python3-pyqt5 suggests: pn python3-pyqt5-dbg -- no debconf information --- End Message --- --- Begin Message --- Thanks for your information--- End Message ---
Bug#961913: marked as done (kmail: the access and reading of the received messages is often very slow)
Your message dated Thu, 02 Jul 2020 00:09:40 +0200 with message-id <3763144.xsRPXWWrgn@merkaba> and subject line Re: kmail: the access and reading of the received messages is often very slow has caused the Debian Bug report #961913, regarding kmail: the access and reading of the received messages is often very slow 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.) -- 961913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kmail Version: 4:20.04.1-1 Severity: important Dear Maintainer, the access and reading of the received messages is often very slow a message appears "Reception of the content of the folder please wait" Same problem for the trashing of messages. The CPU increase to 100% an akonadictl fsck or akonadictl vacuum does not improved . Its new -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:20.04.1-2 ii kdepim-runtime 4:20.04.1-1 ii kio 5.70.1-1 ii libc62.30-8 ii libgcc-s110.1.0-3 ii libgpgmepp6 1.13.1-7+b1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.04] 4:20.04.1-2 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.04] 4:20.04.1-1 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.04]4:20.04.1-2 ii libkf5akonadimime5 [libkf5akonadimime5-20.04]4:20.04.1-1 ii libkf5akonadisearch-bin 4:20.04.1-1 ii libkf5akonadisearch-plugins 4:20.04.1-1 ii libkf5akonadisearchdebug5 [libkf5akonadisearchdebug5-20.04] 4:20.04.1-1 ii libkf5akonadisearchpim5 [libkf5akonadisearchpim5-20.04] 4:20.04.1-1 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.04] 4:20.04.1-2 ii libkf5bookmarks5 5.70.0-1 ii libkf5calendarcore5abi2 5:5.70.0-1 ii libkf5calendarutils5 [libkf5calendarutils5-20.04]4:20.04.1-1 ii libkf5codecs55.70.0-1 ii libkf5completion55.70.0-1 ii libkf5configcore55.70.0-1 ii libkf5configgui5 5.70.0-1 ii libkf5configwidgets5 5.70.0-1 ii libkf5contacts5 5:5.70.0-1 ii libkf5coreaddons55.70.0-1 ii libkf5crash5 5.70.0-1 ii libkf5dbusaddons55.70.0-1 ii libkf5followupreminder5 [libkf5followupreminder5-20.04] 4:20.04.1-1 ii libkf5grantleetheme-plugins 20.04.1-1 ii libkf5gravatar5abi2 [libkf5gravatar5-20.04] 4:20.04.1-1 ii libkf5guiaddons5 5.70.0-1 ii libkf5i18n5 5.70.0-1 ii libkf5iconthemes55.70.0-1 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.04] 20.04.1-1 ii libkf5itemmodels55.70.0-1 ii libkf5itemviews5 5.70.0-1 ii libkf5jobwidgets55.70.0-1 ii libkf5kcmutils5 5.70.0-1 ii libkf5kiocore5 5.70.1-1 ii libkf5kiofilewidgets55.70.1-1 ii libkf5kiowidgets55.70.1-1 ii libkf5kontactinterface5 [libkf5kontactinterface5-20.04] 20.04.1-1 ii
Re: Correction of a Kmail-Akonadi Bug
Hi! MERLIN Philippe - 22.06.20, 18:51:49 CEST: > For the first time, I'm going to be ranting. I have been using Debian > Linux for over 15 years and I appreciate the quality of this system, > the speed of correction by software maintainers in the event of a > major bug. On May 31 I opened a Debian Bug # 961913 entitled "Kmail: > the access and reading of the received messages is often very slow" > on the advice of Martin Steigerwald I opened on June 1 also a Bug on > bugs.kde. org # 422336 The analysis of this Bug was completed by As you reported in upstream bug tracker and I found by testing myself then, the issue somehow appear to have been fixed with Qt 5.14.2 and maybe some other package update. Synchronizing folders is much, much faster now. Maybe Akonadi 20.04 did not like Qt 5.12… but I am not sure whether that is all to it. Best, -- Martin
Re: Bug#879014: gpgme1.0: FTBFS on some arches: Qt needs a compile with -fPIC (PIE is not enough), hardening downgrades to PIE
Control: affects 879014 + dpkg src:qtbase-opensource-src
Control: tags 879014 + patch
Hi folks--
Further conversation about problems compiling and linking against Qt and
GPGME in debian suggest that the problem might be related to dpkg's
default spec files, and confused by Qt's compiler warnings.
I'm attaching a patch to dpkg which (i think) reflects the fix proposed
by Guillem Jover (in cc):
From 8d01f1419c62e24b662abc2e1ec708a7c63fbbfe Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Wed, 1 Jul 2020 17:00:02 -0400
Subject: [PATCH] Use +self_spec: instead of *self_spec:
After discussion with NIIBE Yutaka on https://dev.gnupg.org/T4982 and
Guillem Jover on IRC, I think this is the correct fix for problems
when compiling Qt/GPGME code in debian systems.
I don't fully understand the implications of this change, but i
believe it is related to #870383 and #879014 (in the debian BTS) as
well.
---
data/no-pie-compile.specs | 2 +-
data/no-pie-link.specs| 2 +-
data/pie-compile.specs| 2 +-
data/pie-link.specs | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/data/no-pie-compile.specs b/data/no-pie-compile.specs
index 2277b97ef..70cb36095 100644
--- a/data/no-pie-compile.specs
+++ b/data/no-pie-compile.specs
@@ -1,2 +1,2 @@
-*self_spec:
++self_spec:
+ %{!r:%{!fpie:%{!fPIE:%{!fpic:%{!fPIC:%{!fno-pic:-fno-PIE}}
diff --git a/data/no-pie-link.specs b/data/no-pie-link.specs
index 54db649b1..fa4162793 100644
--- a/data/no-pie-link.specs
+++ b/data/no-pie-link.specs
@@ -1,2 +1,2 @@
-*self_spec:
++self_spec:
+ %{!shared:%{!r:%{!fPIE:%{!pie:-fno-PIE -no-pie
diff --git a/data/pie-compile.specs b/data/pie-compile.specs
index 74d82155c..c1ee08c71 100644
--- a/data/pie-compile.specs
+++ b/data/pie-compile.specs
@@ -1,2 +1,2 @@
-*self_spec:
++self_spec:
+ %{!r:%{!fpie:%{!fPIE:%{!fpic:%{!fPIC:%{!fno-pic:%{!fno-PIE:%{!no-pie:-fPIE
diff --git a/data/pie-link.specs b/data/pie-link.specs
index 94c122fd3..9b401e34a 100644
--- a/data/pie-link.specs
+++ b/data/pie-link.specs
@@ -1,2 +1,2 @@
-*self_spec:
++self_spec:
+ %{!static:%{!shared:%{!r:%{!fno-PIE:%{!no-pie:-fPIE -pie}
--
2.27.0
gniibe also identified a problem in how Qt reports compilation warnings
related to the PIE/PIC mismatch. I've tried to address that in the
following patch to qtbase-opensource-src:
From 107f387ea625a67ef03b916ef965761f36de2bf4 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Wed, 1 Jul 2020 17:15:12 -0400
Subject: [PATCH] Clarify warning message about PIC/PIE
As noted in discussion at https://dev.gnupg.org/T4982#135524, the
warning message produced when there is a mismatch between
position-independence of the Qt library and other compilations, the
warning produced by Qt is confusing.
This is an attempt to express a warning that is more closely aligned
with the actual test used.
---
src/corelib/global/qglobal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/corelib/global/qglobal.h b/src/corelib/global/qglobal.h
index fe8e8e8..971ee56 100644
--- a/src/corelib/global/qglobal.h
+++ b/src/corelib/global/qglobal.h
@@ -1280,7 +1280,7 @@ Q_CORE_EXPORT int qrand();
#if !defined(QT_BOOTSTRAPPED) && defined(QT_REDUCE_RELOCATIONS) && defined(__ELF__) && \
(!defined(__PIC__) || (defined(__PIE__) && defined(Q_CC_GNU) && Q_CC_GNU >= 500))
# error "You must build your code with position independent code if Qt was built with -reduce-relocations. "\
- "Compile your code with -fPIC (-fPIE is not enough)."
+ "Compile your code with -fPIC (and not with -fPIE unless you have a very old version of GCC)."
#endif
namespace QtPrivate {
--
2.27.0
If either of these two fixes are not appropriate to help resolve the
problem, i'd appreciate help in figuring out what the right fixes are.
I am not an expert in either Qt or dpkg, so pointers and explanations
are welcome.
Regards,
--dkg
signature.asc
Description: PGP signature
Re: Status of Plasma 5.18/5.19?
> Debian Sid is still on Plasma 5.17, meanwhile 5.18 LTS and 5.19 have already > been released with 5.20 around the corner > ... > What is the status on this now? Did you actually find the answer to your question? From this whole thread, I still don't understand why is Plasma still outdated in Debian testing / unstable. All I got was that there was some disagreement and packaging help was rejected. But that doesn't explain what the disagreement was and why Plasma wasn't updated in such a long time either way. There must be some blockers or issues obviously that prevent it. Can anyone please elaborate on it for the benefit of those who are reading it? Thanks! Shmerl.
Processed: tagging 963421
Processing commands for cont...@bugs.debian.org: > tags 963421 + pending Bug #963421 [src:calligra] calligra: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 963421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
calligra is marked for autoremoval from testing
calligra 1:3.2.1+dfsg-1 is marked for autoremoval from testing on 2020-07-20 It is affected by these RC bugs: 963421: calligra: FTBFS: dh_install: error: missing files, aborting
Bug#849012: /usr/bin/spectacle: kde-spectacle: no longer works under VNC (ksnapshot did)
In data mercoledì 1 luglio 2020 16:23:49 CEST, Thorsten Glaser ha scritto: > >Anyhow: please report this at https://bugs.kde.org, "spectacle" product, > >so it can be properly tracker and acted upon by spectacle developers. > > Could you please just forward it, as DevRef says… I don’t think > users are happy about having to create accounts on hundreds of > upstream bugtrackers. Considering that: - this is definitely not your first bug related to KDE software - you are a technical person I'm pretty sure you can be helpful and report this bug yourself to upstream, so to ease a bit the work of an already well overloaded packaging team. Right? -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#849012: /usr/bin/spectacle: kde-spectacle: no longer works under VNC (ksnapshot did)
Pino Toscano dixit: >In data mercoledì 1 luglio 2020 14:10:36 CEST, Thorsten Glaser ha scritto: >> $ spectacle >> >> qt.qpa.xcb: XKeyboard extension not present on the X server > >This seems pretty clear to me. Have you tried to fix this? It’s VNC. Also, a screenshot tool does not need a keyboard extension. >Anyhow: please report this at https://bugs.kde.org, "spectacle" product, >so it can be properly tracker and acted upon by spectacle developers. Could you please just forward it, as DevRef says… I don’t think users are happy about having to create accounts on hundreds of upstream bugtrackers. bye, //mirabilos -- "Using Lynx is like wearing a really good pair of shades: cuts out the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL." -- Henry Nelson, March 1999
[bts-link] source package kaccounts-integration
# # bts-link upstream status pull for source package kaccounts-integration # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #962780 (http://bugs.debian.org/962780) # Bug title: kaccounts-integration: [ABI break] 20.04 and 20.04.1 have renamed symbols and needs an upstream ABI bump # * http://bugs.kde.org/show_bug.cgi?id=422191 # * remote status changed: UNCONFIRMED -> REOPENED usertags 962780 - status-UNCONFIRMED usertags 962780 + status-REOPENED thanks
Bug#849012: /usr/bin/spectacle: kde-spectacle: no longer works under VNC (ksnapshot did)
In data mercoledì 1 luglio 2020 14:10:36 CEST, Thorsten Glaser ha scritto: > $ spectacle > > qt.qpa.xcb: XKeyboard extension not present on the X server This seems pretty clear to me. Have you tried to fix this? > QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it > was ':1.99' > kf5.kservice.services: The desktop entry file > "/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec > line > kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/qemu.desktop" > The X11 connection broke: Unsupported extension used (code 2) > XIO: fatal IO error 17 (File exists) on X server ":2" > after 221 requests (213 known processed) with 0 events remaining. Anyhow: please report this at https://bugs.kde.org, "spectacle" product, so it can be properly tracker and acted upon by spectacle developers. Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#849012: /usr/bin/spectacle: kde-spectacle: no longer works under VNC (ksnapshot did)
Package: kde-spectacle Version: 20.04.1-1 Followup-For: Bug #849012 $ spectacle qt.qpa.xcb: XKeyboard extension not present on the X server QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.99' kf5.kservice.services: The desktop entry file "/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/qemu.desktop" The X11 connection broke: Unsupported extension used (code 2) XIO: fatal IO error 17 (File exists) on X server ":2" after 221 requests (213 known processed) with 0 events remaining. -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.5.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages kde-spectacle depends on: ii kio5.70.1-1 ii libc6 2.30-8 ii libkf5configcore5 5.70.0-1 ii libkf5configgui5 5.70.0-1 ii libkf5configwidgets5 5.70.0-1 ii libkf5coreaddons5 5.70.0-1 ii libkf5dbusaddons5 5.70.0-1 ii libkf5globalaccel-bin 5.70.0-1 ii libkf5globalaccel5 5.70.0-1 ii libkf5i18n55.70.0-1 ii libkf5kiocore5 5.70.1-1 ii libkf5kiowidgets5 5.70.1-1 ii libkf5kipi32.0.0 4:19.08.1-1+b1 ii libkf5newstuff55.70.0-1 ii libkf5notifications5 5.70.0-1 ii libkf5purpose-bin 5.70.0-1 ii libkf5purpose5 5.70.0-1 ii libkf5service-bin 5.70.0-1 ii libkf5service5 5.70.0-1 ii libkf5waylandclient5 4:5.70.0-1 ii libkf5widgetsaddons5 5.70.0-1 ii libkf5windowsystem55.70.0-1 ii libkf5xmlgui5 5.70.0-1 ii libqt5core5a 5.12.5+dfsg-10+b1 ii libqt5dbus55.12.5+dfsg-10+b1 ii libqt5gui5 5.12.5+dfsg-10+b1 ii libqt5printsupport55.12.5+dfsg-10+b1 ii libqt5widgets5 5.12.5+dfsg-10+b1 ii libqt5x11extras5 5.12.5-1 ii libstdc++6 10.1.0-3 ii libxcb-cursor0 0.1.1-4 ii libxcb-image0 0.4.0-1+b2 ii libxcb-util0 0.3.8-3+b2 ii libxcb-xfixes0 1.14-2 ii libxcb11.14-2 ii qdbus-qt5 5.12.5-2+b2 kde-spectacle recommends no packages. kde-spectacle suggests no packages. -- no debconf information
Bug#963983: closed by Gianfranco Costamagna (Re: python3-pyside2.qtsvg: segfault on import)
Control: severity -1 important On Tue, Jun 30, 2020 at 12:50:36AM +0200, ydir...@free.fr wrote: > The other pyside2 packages (code, gui etc) were still at 5.15.0-1~exp1. > > If I just update qtsvg to 5.15.0-2 the segfault still happens. > > Update the rest of pyside2 triggers a huge cascading of upgrades to Qt 5.14 > which had not been done when I had installed the exp packages, and when I > updated qtsvg initially. > > Among them: > > Unpacking libqt5svg5:amd64 (5.14.2-2) over (5.12.5-2) ... > > With all this upgraded, I confirm there is no segfault any more. > > Thus, the problem is likely caused by an undeclared versioned dependency on an > underlying lib, and libqt5svg5 looks like a good candidate. I have now bumped Qt build-dependencies in Git, that should help. In the mean time, downgrading the severity of this bug as it should not block Qt migration to testing (especially when we require new Qt). -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#963983: closed by Gianfranco Costamagna (Re: python3-pyside2.qtsvg: segfault on import)
Processing control commands: > severity -1 important Bug #963983 [python3-pyside2.qtsvg] python3-pyside2.qtsvg: segfault on import Severity set to 'important' from 'grave' -- 963983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Really merging 895718 964064 - try 3
Processing commands for cont...@bugs.debian.org: > affects 964064 jenkins.debian.org Bug #964064 [libqt5core5a] python3-pyqt5: ImportError when from PyQt5 import QtGui Added indication that 964064 affects jenkins.debian.org > merge 895718 964064 Bug #895718 [libqt5core5a] libqt5core5a: Requires Linux kernel 3.17.0 or newer Bug #902118 [libqt5core5a] quassel-core: quasselcore unable to load installed libQt5Core.so.5 Bug #902118 [libqt5core5a] quassel-core: quasselcore unable to load installed libQt5Core.so.5 Bug #964064 [libqt5core5a] python3-pyqt5: ImportError when from PyQt5 import QtGui Merged 895718 902118 964064 > thanks Stopping processing here. Please contact me if you need assistance. -- 895718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895718 902118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902118 964064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Really merging
Processing commands for cont...@bugs.debian.org: > severity 964064 normal Bug #964064 [libqt5core5a] python3-pyqt5: ImportError when from PyQt5 import QtGui Severity set to 'normal' from 'important' > merge 895718 964064 Bug #895718 [libqt5core5a] libqt5core5a: Requires Linux kernel 3.17.0 or newer Bug #902118 [libqt5core5a] quassel-core: quasselcore unable to load installed libQt5Core.so.5 Unable to merge bugs because: affects of #964064 is '' not 'jenkins.debian.org' Failed to merge 895718: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 895718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895718 902118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902118 964064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
clazy_1.7-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 01 Jul 2020 10:44:27 +0200 Source: clazy Architecture: source Version: 1.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Changes: clazy (1.7-2) unstable; urgency=medium . * Exclude the inefficient-qlist check again, unfortunately on all the 32bit architectures: https://bugs.kde.org/423728. Checksums-Sha1: b44d66dd4e0359a75e789e3873377cdcc8da748c 2435 clazy_1.7-2.dsc fd0a46ee9a16a1395b8c4297f8b04c33dec1b432 17512 clazy_1.7-2.debian.tar.xz 90c45d6f087e93976a0fce8a4f7c8f224e1d92e5 11349 clazy_1.7-2_source.buildinfo Checksums-Sha256: a2486310ab4c08150ff22f4507fa010ef61f261900ced30591fcf42ac0be860d 2435 clazy_1.7-2.dsc 5f7acc041affbd617c42edb9d55901ad3e9135b723d904943245426d05ab984d 17512 clazy_1.7-2.debian.tar.xz b609d3f1aace87e7a07c52ffdd322fd17d7aa1b5146a8b98513e977f3b7560d3 11349 clazy_1.7-2_source.buildinfo Files: 75b2531cc6caacec4c984ccd08619606 2435 devel optional clazy_1.7-2.dsc 6b87caff08d7f5d99a2f900cc08f4e7d 17512 devel optional clazy_1.7-2.debian.tar.xz 463fef1cf606fdb47f8e99ba20e274e7 11349 devel optional clazy_1.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl78TTQACgkQLRkciEOx P02wRQ//U3Vt1xzxZ6oULehpNOcwrqwXWwetSYwtTR7YWjUqiJLjx9KzA2S+zwp5 begLoZC4+sCgn4JuCR4/YvHHKqDe4r/bF9gY6FsKbCzKgxegUel6rCax0U9tAXHl GBvLYdTnUGXv0qfimqDizaOwRny45QhGE6506iiKu9kJUsfPV9i5OuRhDBekyumI Xrz6JMh+vE5DJbHjblbT4DGMWx1Xt3nDvjLRqXYpX0+yaLMRCD8asxrna6g2hU/L j+jHd4cOA5mILlE4CC8U9UXTUwRwXe+ifu1s6j0+AvGCitYXUmKETXPxZiiwoa7F 3C0lqUm11Qm6kCncB81BY7QatL4iIeSJp5zKz8L465qgZocOYlA3Kh8VfZJjQTaG pXAjP+IAaTy+f+9T0JgAfMgBa2ZBz0b+ci3L3YHUBCuW99RsPkWFX8cXR7xVB3Wm BB9bc0A3bdhfFOQRz6dd7WHGRUorxPBy/V766uDOe7zjNSLmt6Gk4/ZEvdF8s3lW J9kXQw3jfD62la3/hLBwvJz8XcHxMZoeXlsJv3wZqW0CLB1BDvAVfUgGuS7JqljF zYVtOsVIsOEnUy97Zi1FIgO5+dL2AcC1iU3csmdkAWZDfmtDiGdE+TRebQqzLR61 Y9nuimuNQX1wyWpM9kOVKzZnrTL+xQ3ZHoXDmpaOBC6SiCqhTd8= =vTIy -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of clazy_1.7-2_source.changes
clazy_1.7-2_source.changes uploaded successfully to localhost along with the files: clazy_1.7-2.dsc clazy_1.7-2.debian.tar.xz clazy_1.7-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed (with 1 error): Re: Bug#964064: kernel too old
Processing control commands: > reassign -1 libqt5core5a 5.10.1+dfsg-5 Bug #964064 [python3-pyqt5] python3-pyqt5: ImportError when from PyQt5 import QtGui Bug reassigned from package 'python3-pyqt5' to 'libqt5core5a'. No longer marked as found in versions pyqt5/5.15.0+dfsg-1. Ignoring request to alter fixed versions of bug #964064 to the same values previously set Bug #964064 [libqt5core5a] python3-pyqt5: ImportError when from PyQt5 import QtGui Marked as found in versions qtbase-opensource-src/5.10.1+dfsg-5. > severity -1 important Bug #964064 [libqt5core5a] python3-pyqt5: ImportError when from PyQt5 import QtGui Ignoring request to change severity of Bug 964064 to the same value. > merge 895718 -1 Bug #895718 [libqt5core5a] libqt5core5a: Requires Linux kernel 3.17.0 or newer Bug #902118 [libqt5core5a] quassel-core: quasselcore unable to load installed libQt5Core.so.5 Unable to merge bugs because: severity of #964064 is 'important' not 'normal' affects of #964064 is '' not 'jenkins.debian.org' Failed to merge 895718: Did not alter merged bugs. -- 895718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895718 902118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902118 964064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
clazy_1.7-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 01 Jul 2020 08:06:18 +0200 Source: clazy Architecture: source Version: 1.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Changes: clazy (1.7-1) unstable; urgency=medium . [ Pino Toscano ] * New upstream release. * Update the patches: - select-clangpp.diff: refresh * Update lintian overrides. * Add Rules-Requires-Root: no. * Bump Standards-Version to 4.5.0, no changes required. * Run again the inefficient-qlist check on i386, as it was fixed upstream. * Change the python3 build dependency to python3:any, as Python is needed only as build tool. * Update copyright. . [ Alexander Volkov ] * Don't install needless build dependencies when nocheck profile is enabled. Checksums-Sha1: 48e27688c41ae0d1c2e887406902d28d3f53bf3d 2435 clazy_1.7-1.dsc d19c1d5cc72a1632726f5461c43a52e35c6ca9a6 371788 clazy_1.7.orig.tar.xz 0a94ace918c15464e6f6a01294e2668ca08f507a 195 clazy_1.7.orig.tar.xz.asc 8983fd9f88e73a58b78d34c1665ad4ccd3f14e6d 17392 clazy_1.7-1.debian.tar.xz 5da5b3729db15ca771d5129028f6b211712902db 11349 clazy_1.7-1_source.buildinfo Checksums-Sha256: 2217477bf6d47a4d7d1195166458bdb5d0900f8559675192371c977c4041aecd 2435 clazy_1.7-1.dsc 754da5815f769dd6b72a040a2430525c93f294eb7769c78271603df9614f1b21 371788 clazy_1.7.orig.tar.xz 1c7a101d93b6f98cf943e36fadb6a4addd73f91ca31d801cb14c04bec4f23c11 195 clazy_1.7.orig.tar.xz.asc bc47579f63bcdcbd0a9e76e01dc82c4f157d6b81ebbf9dca8b7cd21e7c75a034 17392 clazy_1.7-1.debian.tar.xz a4c0ccefcaffa8856d5b6d8cc5ce4f882ff54a9f32b7887a4e7d0e71ff715f50 11349 clazy_1.7-1_source.buildinfo Files: 00235f24a4120e3db07a391983b0b44c 2435 devel optional clazy_1.7-1.dsc 48daada66981fa3538daadef4e6aa05f 371788 devel optional clazy_1.7.orig.tar.xz 268ad713dfe8b63c50d259fc0649f0af 195 devel optional clazy_1.7.orig.tar.xz.asc f24190a6b9c3f63ef89865be663b7894 17392 devel optional clazy_1.7-1.debian.tar.xz 79c1c3f142859f9d8bbc0472e4848351 11349 devel optional clazy_1.7-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl78KBAACgkQLRkciEOx P01PbA//UtQeVG3dzRqB8eHqKt/nYLvJ99zWhn1HPNJesrOOb+LeJIEhbzCc6duQ DSHzWQnNBRPxn/cjW57uGi3ay+nLVfggohRPZFXd3S6XhBRkzCGBLRvvPMZiHyB1 MH9nQyhhkly9Cte8armh2aS3IW3zji71PJz5d1FCxkyQQYQK89FqHSV5SwAKRGWi H5155EI6SvjPtQ0bdFWHZ/ao/CbDcWsRKBvFGpJiOZjrWIP+WCOJUcLaVDk7+D9+ 7B8lk8AyEoo9fMbIpzB0mG6jkVwYylJLe+mySZOg36n7gsR3HapGdGSuDn7je2O/ 5yMmK1PYniykUYtTixyHRlSa3LDYyrX/ZDmNQOlA+62ds7q812cbeTZkaFnoFXwR ddJjg1h7NJpb5UTiUD09QPsJFnWjtg34TQP3ARUM51KEtQO14CPaHE0+v2jvUTfp pTT7SSH6LycGnNqv4OA4TfROof8N8T9ZtxGYEB4HeVvjIQCunT6E3dmGWk8YAA/m IYbgLQKLCJHcjN/kXQCb0FW4m5vKGmitZJSZWkGG8KeExt8+rgBW/UU92ZW0s1E1 MTSEgyymN+TL4lkMgV9+AYutMAnNlfItBfZHFiNWuGDLQZIG6gLqwNCgopQrwENm W06WRGRa/kDqDP4HuFlM/+YCi50zD/RUpf/5eYy+bURDKUa2AZ0= =xqwu -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of clazy_1.7-1_source.changes
clazy_1.7-1_source.changes uploaded successfully to localhost along with the files: clazy_1.7-1.dsc clazy_1.7.orig.tar.xz clazy_1.7.orig.tar.xz.asc clazy_1.7-1.debian.tar.xz clazy_1.7-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
