Bug#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

2023-04-12 Thread Lisandro Damián Nicanor Pérez Meyer
Samuel: do you know if this bug is also applicable to Qt 6?




-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/



qtbase-opensource-src_5.15.8+dfsg-7_source.changes ACCEPTED into unstable

2023-04-12 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Apr 2023 20:24:34 -0300
Source: qtbase-opensource-src
Architecture: source
Version: 5.15.8+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 1033995 1034160 1034271
Changes:
 qtbase-opensource-src (5.15.8+dfsg-7) unstable; urgency=medium
 .
   * Update a11y_root.diff. This time the code waits for Qt loop to process the
 check (Closes: #1033995, #1034160, #1034271).
Checksums-Sha1:
 1a0b9b7c22d41764ece1ded30e697c4e222fb11a 5430 
qtbase-opensource-src_5.15.8+dfsg-7.dsc
 7cf5dd664ac17213cb19b1ffdbad5aec0b05a55a 231232 
qtbase-opensource-src_5.15.8+dfsg-7.debian.tar.xz
 1fb6da1057f67c9277c9d8e40b3e9022f58e95ab 17785 
qtbase-opensource-src_5.15.8+dfsg-7_source.buildinfo
Checksums-Sha256:
 4eaa662ba36e20aad3409a3d41c43e0147fe8fe16338846a722ae1fc1c832241 5430 
qtbase-opensource-src_5.15.8+dfsg-7.dsc
 42f28f3e6094dcf16006dfa158103b4acca0b917f2f93266ca344fcea602da65 231232 
qtbase-opensource-src_5.15.8+dfsg-7.debian.tar.xz
 e5fc2e2af14a08904e0d837f362529084fe53802b00c0a0e2e9eeba9edfcf7c1 17785 
qtbase-opensource-src_5.15.8+dfsg-7_source.buildinfo
Files:
 df895924e04827efb330592ba8d937d7 5430 libs optional 
qtbase-opensource-src_5.15.8+dfsg-7.dsc
 7435869d1a650050539607b3d9f7804a 231232 libs optional 
qtbase-opensource-src_5.15.8+dfsg-7.debian.tar.xz
 2e87a84140a0963d9e31db3c6b2770b6 17785 libs optional 
qtbase-opensource-src_5.15.8+dfsg-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAmQ3PdoUHGxpc2FuZHJv
QGRlYmlhbi5vcmcACgkQq2RfQGKGp9BHOg/7BQ/cET7DLuNDZxwcMsCSf12sdYQD
TTQ2wLnNOxeVU3dDuGbIxXvXvz0pU1lWoWSb1ld5IiOUF0OWhrtPSzO5cuJ7BarC
TFVEeR5CiV5URXUvTelcCV0t+70+V7rE6GC5WE69uKu4g+nFnE5oRgoc/P9tgZRr
aziOQQzp+3541lFt6IlPG6mfzOpFz66rqZkeFFnj+JQ7N6EezX9tLxZqnyA2MowB
KzdXskee2PC/6Vc+fHVwAckR0d6cVtrt95CGaPAyu7KXjcdbPP5XB3+fZLrQlR2a
s5I4TG1GcWc//8XQo3wS6Vvwk6g3WZPSB7JeL1Z90jEe1/oaohlwdOiT/X/NbMKl
8gOlbzlMARn/bubLo26Hd3yX/jhDKEjYbv+94HKvRQK6ZSKFPdoQnUq106nhJO9X
9ZnQKiXqy3i9diFMWDKolPYFMkcpY5lAcFdqRttwgQu4VC2oZWrUzlR/I03LjLmT
br2w7KDEkmdxtsF3FBMJ/3AtFPzjjNKI7leDe7tClILCGcNcqDy26/yNOJxnlZ+E
wxO6U4Yr5U9w5umpQer7xpoVwhNJTdteZkAXHKzXKf4dWDRt96AZLgkbCBjKk5tQ
IaWTJjxmeDop/Qlyse4/1aHmoxgh4LW3ODiyI5V/6LigKsHy2AE7Z83QJ2LynWJu
dlLVQdOlNKpuPfM=
=H43g
-END PGP SIGNATURE-



Bug#1034271: marked as done (libqt5core5a: upgrade to 5.15.8+dfsg-6 causes alt-F2 krunner start to never show dialogue box)

2023-04-12 Thread Debian Bug Tracking System
Your message dated Thu, 13 Apr 2023 00:12:40 +
with message-id 
and subject line Bug#1034271: fixed in qtbase-opensource-src 5.15.8+dfsg-7
has caused the Debian Bug report #1034271,
regarding libqt5core5a: upgrade to 5.15.8+dfsg-6 causes alt-F2 krunner start to 
never show dialogue box
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.)


-- 
1034271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5core5a
Version: 5.15.8+dfsg-6
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

[UPGRADE] libqt5concurrent5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5core5a:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5dbus5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5gui5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5network5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5opengl5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5opengl5-dev:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5printsupport5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5-mysql:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5-psql:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5sql5-sqlite:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5test5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5widgets5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] libqt5xml5:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qt5-gtk-platformtheme:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qt5-qmake:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qt5-qmake-bin:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qtbase5-dev:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6
[UPGRADE] qtbase5-dev-tools:amd64 5.15.8+dfsg-5 -> 5.15.8+dfsg-6

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

using alt-F2 results in krunner consuming a large amount of CPU time then 
not appearing in the top monitor, but using alt-F2 again repears the same
increasing CPU and eventual dropping out from being the most CPU bound process

Downgrading back to 5.15.8+dfsg-5 resolved the problem.

   * 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: 12.0
  APT prefers experimental
  APT policy: (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-rc6+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libqt5core5a depends on:
ii  libc6  2.36-9
ii  libdouble-conversion3  3.2.1-1
ii  libgcc-s1  13-20230320-1
ii  libglib2.0-0   2.75.2-1
ii  libicu72   72.1-3
ii  libpcre2-16-0  10.42-1
ii  libstdc++6 13-20230320-1
ii  libzstd1   1.5.4+dfsg2-5
ii  shared-mime-info   2.2-1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.15.8-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.29-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.15.8+dfsg-7
Done: Lisandro Damián Nicanor Pérez Meyer 

We believe that the bug you reported is fixed in the latest version of
qtbase-opensource-src, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1034...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtbase-opensource-src package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Apr 2023 20:24:34 -0300
Source: qtbase-opensource-src
Architecture: source
Version: 5.15.8+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 

Bug#1034160: marked as done (libkscreenlocker5: Screen locker crashes asking for loginctl command)

2023-04-12 Thread Debian Bug Tracking System
Your message dated Thu, 13 Apr 2023 00:12:40 +
with message-id 
and subject line Bug#1034160: fixed in qtbase-opensource-src 5.15.8+dfsg-7
has caused the Debian Bug report #1034160,
regarding libkscreenlocker5: Screen locker crashes asking for loginctl command
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.)


-- 
1034160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkscreenlocker5
Version: 5.27.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After some libraries updates, I cannot lock my plasma session anymore.

It shows a black screen with a message asking to go to a virtual terminal and 
run a 'loginctl unlock-session 2' or similar to unlock the screen.

This is happening with my desktop and my notebook. Even with a reboot this 
problem presists.

Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.2.10 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libkscreenlocker5 depends on:
ii  kio5.103.0-1
ii  kpackagetool5  5.103.0-1
ii  libc6  2.36-8
ii  libkf5configcore5  5.103.0-2
ii  libkf5configgui5   5.103.0-2
ii  libkf5configqml5   5.103.0-2
ii  libkf5coreaddons5  5.103.0-1
ii  libkf5crash5   5.103.0-1
ii  libkf5declarative5 5.103.0-1
ii  libkf5globalaccel-bin  5.103.0-1
ii  libkf5globalaccel5 5.103.0-1
ii  libkf5i18n55.103.0-1
ii  libkf5idletime55.103.0-2
ii  libkf5kiocore5 5.103.0-1
ii  libkf5notifications5   5.103.0-1
ii  libkf5package5 5.103.0-1
ii  libkf5quickaddons5 5.103.0-1
ii  libkf5screendpms8  4:5.27.2-1
ii  libkf5waylandclient5   4:5.103.0-1
ii  libkf5windowsystem55.103.0-1
ii  libkf5xmlgui5  5.103.0-1
ii  liblayershellqtinterface5  5.27.2-1
ii  libpam0g   1.5.2-6
ii  libqt5core5a   5.15.8+dfsg-4
ii  libqt5dbus55.15.8+dfsg-4
ii  libqt5gui5 5.15.8+dfsg-4
ii  libqt5network5 5.15.8+dfsg-4
ii  libqt5qml5 5.15.8+dfsg-3
ii  libqt5quick5   5.15.8+dfsg-3
ii  libqt5widgets5 5.15.8+dfsg-4
ii  libqt5x11extras5   5.15.8-2
ii  libstdc++6 12.2.0-14
ii  libwayland-client0 1.21.0-1
ii  libwayland-server0 1.21.0-1
ii  libx11-6   2:1.8.4-2
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb11.15-1
ii  libxi6 2:1.8-1+b1
ii  psmisc 23.6-1

Versions of packages libkscreenlocker5 recommends:
ii  kde-config-screenlocker  5.27.2-1

libkscreenlocker5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.15.8+dfsg-7
Done: Lisandro Damián Nicanor Pérez Meyer 

We believe that the bug you reported is fixed in the latest version of
qtbase-opensource-src, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1034...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtbase-opensource-src package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Apr 2023 20:24:34 -0300
Source: qtbase-opensource-src
Architecture: source
Version: 5.15.8+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 1033995 1034160 1034271
Changes:
 qtbase-opensource-src (5.15.8+dfsg-7) unstable; urgency=medium
 .
   * Update a11y_root.diff. This time the code waits for Qt loop to process the
 check (Closes: #1033995, #1034160, #1034271).
Checksums-Sha1:
 

Bug#1033995: marked as done (qtbase-opensource-src: Fix accessibility of qt5 applications run as root)

2023-04-12 Thread Debian Bug Tracking System
Your message dated Thu, 13 Apr 2023 00:12:40 +
with message-id 
and subject line Bug#1033995: fixed in qtbase-opensource-src 5.15.8+dfsg-7
has caused the Debian Bug report #1033995,
regarding qtbase-opensource-src: Fix accessibility of qt5 applications run as 
root
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.)


-- 
1033995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtbase-opensource-src
Version: 5.15.8+dfsg-3
Severity: important
Tags: patch upstream
Forwarded: https://bugreports.qt.io/browse/QTBUG-43674

Hello,

Currently, qt5 applications, when run in sudo, are not accessible to
screen readers. This is because the accessibility layer does not manage
to connect to the accessibility bus to export the application content:

https://bugreports.qt.io/browse/QTBUG-43674

Most of the support was merged into qt5, but there is a little fix
missing, that was missed by upstream. I have attached the fix, it is
very simple: the ordering in QSpiAccessibleBridge::QSpiAccessibleBridge
used to be

- new DBusConnection() creates the dbusConnection object
  - the DBusConnection::DBusConnection constructor connects to the atspi
bus
- connect the enabledChanged signal

and this patch changes it to:

- new DBusConnection() creates the dbusConnection object
- connect the enabledChanged signal
- the DBusConnection::init method connects to the atspi bus

This is needed in the root case because since in that case it
cannot access the user session dbus, it uses a synchronous method,
in which case the enabledChanged signal is emitted from the
DBusConnection::DBusConnection constructor, and thus lost forever since
it was not connected yet at that time. So we need to connect the signal
before connecting to the atspi bus (and get the enabledChanged event).


This is particularly important because the calamares installer is based
on qt5 and runs as root, and it currently is completely inaccessible to
blind users, and this fix makes it possible for blind users to use it.


I have confirmed that this fixes the issue for bookworm, would it be
possible to upload to unstable? I'll then handle requesting the unblock
from the release team.

Samuel

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.2.0 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From: Frederik Gladhorn 
Date: Tue, 12 Sep 2017 09:22:30 + (+0200)
Subject: Fix accessibility on XCB when running as root
X-Git-Url: 
https://codereview.qt-project.org/gitweb?p=qt%2Fqtbase.git;a=commitdiff_plain;h=4ee3703ffaf063047285247016ee9e5c07ef3b53;hp=689606de91faecf91f1f92e8d355789d9be62d2f
Forwarded: https://bugreports.qt.io/browse/QTBUG-43674

Fix accessibility on XCB when running as root

Accessibility actually works when running applications as root, but we
would never properly connect, since the enabledChanged signal would be
emitted from the constructor in this case.
Only applications running as root would be affected, because all other
applications would go through the asynchronous pattern of getting the
bus address from dbus instead.
Since running apps as root won't let them access the session bus, the
xatom is the way to go.

[ChangeLog][QtGui][Accessibility] On XCB applications running as root are
now accessible.

Task-number: QTBUG-43674
Change-Id: I82cdc35f00693a8366dfcdab2f2c3c6dc5f5b783
---

---
 src/platformsupport/linuxaccessibility/bridge.cpp |1 +
 src/platformsupport/linuxaccessibility/dbusconnection.cpp |8 
 src/platformsupport/linuxaccessibility/dbusconnection_p.h |1 +
 3 files changed, 10 insertions(+)

--- a/src/platformsupport/linuxaccessibility/bridge.cpp
+++ b/src/platformsupport/linuxaccessibility/bridge.cpp
@@ -65,6 +65,7 @@ QSpiAccessibleBridge::QSpiAccessibleBrid
 {
 dbusConnection = new DBusConnection();
 connect(dbusConnection, SIGNAL(enabledChanged(bool)), this, 

Processing of qtbase-opensource-src_5.15.8+dfsg-7_source.changes

2023-04-12 Thread Debian FTP Masters
qtbase-opensource-src_5.15.8+dfsg-7_source.changes uploaded successfully to 
localhost
along with the files:
  qtbase-opensource-src_5.15.8+dfsg-7.dsc
  qtbase-opensource-src_5.15.8+dfsg-7.debian.tar.xz
  qtbase-opensource-src_5.15.8+dfsg-7_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

2023-04-12 Thread Lisandro Damián Nicanor Pérez Meyer
On Wed, 12 Apr 2023 at 19:56, Lisandro Damián Nicanor Pérez Meyer
 wrote:
>
> Uups, I wrongly tested this without re enabling the patch, my bad!
> Building and testing again!

Patch tested, everything looks fine! I am now pushing the package to
the archive.



Bug#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

2023-04-12 Thread Lisandro Damián Nicanor Pérez Meyer
Uups, I wrongly tested this without re enabling the patch, my bad!
Building and testing again!

On Wed, 12 Apr 2023 at 19:50, Samuel Thibault  wrote:
>
> Lisandro Damián Nicanor Pérez Meyer, le mer. 12 avril 2023 19:49:00 -0300, a 
> ecrit:
> > In the meantime I'll be preparing the upload, if everything is OK I'll
> > push to the repo and upload the packages.
>
> Thanks for your patience on this!
>
> Samuel



-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/



Bug#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

2023-04-12 Thread Lisandro Damián Nicanor Pérez Meyer
Hi again,

On Wed, 12 Apr 2023 at 19:19, Lisandro Damián Nicanor Pérez Meyer
 wrote:
>
> Hi,
>
> On Wed, 12 Apr 2023 at 19:03, Samuel Thibault  wrote:
> >
> > And again it's posing problem. As advised by svuorela on irc, here is a
> > version that defers the trigger. This is probably even safer since
> > that's what is committed upstream for the AT_SPI_BUS_ADDRESS environment
> > variable case.
>
> It makes sense, let me try the patch.

krunner works as expected. I am now waiting for the automatic screen
locker to pop in and check it works as expected too (this were two
symptoms of his issue).

In the meantime I'll be preparing the upload, if everything is OK I'll
push to the repo and upload the packages.

-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/



Bug#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

2023-04-12 Thread Samuel Thibault
Lisandro Damián Nicanor Pérez Meyer, le mer. 12 avril 2023 19:49:00 -0300, a 
ecrit:
> In the meantime I'll be preparing the upload, if everything is OK I'll
> push to the repo and upload the packages.

Thanks for your patience on this!

Samuel



Bug#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

2023-04-12 Thread Lisandro Damián Nicanor Pérez Meyer
Hi,

On Wed, 12 Apr 2023 at 19:03, Samuel Thibault  wrote:
>
> And again it's posing problem. As advised by svuorela on irc, here is a
> version that defers the trigger. This is probably even safer since
> that's what is committed upstream for the AT_SPI_BUS_ADDRESS environment
> variable case.

It makes sense, let me try the patch.



-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/



Bug#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

2023-04-12 Thread Samuel Thibault
And again it's posing problem. As advised by svuorela on irc, here is a
version that defers the trigger. This is probably even safer since
that's what is committed upstream for the AT_SPI_BUS_ADDRESS environment
variable case.

Samuel
--- a/src/platformsupport/linuxaccessibility/bridge.cpp
+++ b/src/platformsupport/linuxaccessibility/bridge.cpp
@@ -65,6 +65,16 @@ QSpiAccessibleBridge::QSpiAccessibleBrid
 {
 dbusConnection = new DBusConnection();
 connect(dbusConnection, SIGNAL(enabledChanged(bool)), this, 
SLOT(enabledChanged(bool)));
+// Now that we have connected the signal, make sure we didn't miss a 
change,
+// e.g. when running as root or when AT_SPI_BUS_ADDRESS is set by hand.
+// But do that only on next loop, once dbus is really settled.
+QMetaObject::invokeMethod(
+this,
+[this] {
+if (dbusConnection->isEnabled())
+enabledChanged(true);
+},
+Qt::QueuedConnection);
 }
 
 void QSpiAccessibleBridge::enabledChanged(bool enabled)


Bug#1034191: regression -6 broke what -5 fixed

2023-04-12 Thread Ivan Sergio Borgonovo
Same problem with 5.15.8+dfsg-6, downgrading to 5.15.8+dfsg-5 fixed the 
problem.


thanks

--
Ivan Sergio Borgonovo
https://www.webthatworks.it https://www.borgonovo.net



Bug#1034215: drkonqi: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

2023-04-12 Thread Andreas Henriksson
Hello again,

On Wed, Apr 12, 2023 at 01:19:52PM +0200, Andreas Henriksson wrote:
> On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> > Package: drkonqi
> > Version: 5.27.2-1  
> > Severity: serious
> > Tags: sid bookworm
> > User: debhel...@packages.debian.org
> > Usertags: systemd-files-in-usr-bookworm
> > 
> > Dear Maintainer,
> > 
> > It seems that your package drkonqi is shipping files (.service, .socket or
> > .timer) in /usr/lib/systemd/system.
> [...]
> 
> ```
> $ apt-file show drkonqi | grep systemd/system
> drkonqi: /usr/lib/systemd/system/drkonqi-coredump-processor@.service
> ```

I forgot to mention that since this is a template unit (@.service)
maybe the severity should not be RC.
As far as I know debhelper will not enable any instance of a template
unit by default anyway, so the consequences that bigon warned about
probably doesn't apply here?


> 
> From ./src/coredump/processor/CMakeLists.txt :
> 
> ```
> configure_file(
> drkonqi-coredump-processor@.service.cmake
> ${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
> )
> install(
> FILES ${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
> DESTINATION ${KDE_INSTALL_SYSTEMDUNITDIR}/system
> )
> ```
> 
> So apparently KDE_INSTALL_SYSTEMDUNITDIR is not set correctly.
> 
> I'm not sure where this variable comes from. The above line is the
> only hit on
> https://codesearch.debian.net/search?q=KDE_INSTALL_SYSTEMDUNITDIR=1
> 
> Maybe someone with better understanding of KDE and CMake can help figure this 
> out.
> 
> If not, I guess you can always add a hack that appends to dh_install to move
> the file into the correct directory as returned by
> `pkg-config --variable=systemdsystemunitdir systemd`.
> (Note: make sure to have systemd.pc available by build-dep on systemd)
 
 
Regards,
Andreas Henriksson



Bug#1034215: drkonqi: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

2023-04-12 Thread Andreas Henriksson
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: drkonqi
> Version: 5.27.2-1  
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
> 
> Dear Maintainer,
> 
> It seems that your package drkonqi is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]

```
$ apt-file show drkonqi | grep systemd/system
drkonqi: /usr/lib/systemd/system/drkonqi-coredump-processor@.service
```

>From ./src/coredump/processor/CMakeLists.txt :

```
configure_file(
drkonqi-coredump-processor@.service.cmake
${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
)
install(
FILES ${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
DESTINATION ${KDE_INSTALL_SYSTEMDUNITDIR}/system
)
```

So apparently KDE_INSTALL_SYSTEMDUNITDIR is not set correctly.

I'm not sure where this variable comes from. The above line is the
only hit on
https://codesearch.debian.net/search?q=KDE_INSTALL_SYSTEMDUNITDIR=1

Maybe someone with better understanding of KDE and CMake can help figure this 
out.

If not, I guess you can always add a hack that appends to dh_install to move
the file into the correct directory as returned by
`pkg-config --variable=systemdsystemunitdir systemd`.
(Note: make sure to have systemd.pc available by build-dep on systemd)


Regards,
Andreas Henriksson



Bug#1034271: libqt5core5a: Update also causes segfault during startup in linphone

2023-04-12 Thread Fiona Klute

Package: libqt5core5a
Version: 5.15.8+dfsg-6
Followup-For: Bug #1034271

The update from 5.15.8+dfsg-5 to 5.15.8+dfsg-6 also causes a segfault in
linphone (package linphone-desktop) during startup, making linphone
unusable (command line output attached). Downgrading makes linphone work
again.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqt5core5a depends on:
ii  libc6  2.36-9
ii  libdouble-conversion3  3.2.1-1
ii  libgcc-s1  12.2.0-14
ii  libglib2.0-0   2.74.6-2
ii  libicu72   72.1-3
ii  libpcre2-16-0  10.42-1
ii  libstdc++6 12.2.0-14
ii  libzstd1   1.5.4+dfsg2-5
ii  shared-mime-info   2.2-1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.15.8-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.29-1

-- no debconf information
[09:41:47:734][0x55902e0a4330][Info]"Starting Linphone (bin: linphone)"
[09:41:47:734][0x55902e0a4330][Info]"Use locale: de_DE"
[09:41:47:749][0x55902e0a4330][Info]Available fonts :  ("Bitstream Charter", "C059 [UKWN]", "C059 [urw]", "Cantarell", "Cantarell Extra Bold", "Cantarell Light", "Cantarell Thin", "cmex10", "cmmi10", "cmr10", "cmsy10", "Courier", "Courier 10 Pitch", "D05L [urw]", "D05L [URW ]", "DejaVu Math TeX Gyre", "DejaVu Sans", "DejaVu Sans Condensed", "DejaVu Sans Mono", "DejaVu Serif", "DejaVu Serif Condensed", "Droid Sans Fallback", "dsrom10", "esint10", "eufm10", "FontAwesome", "Latin Modern Math", "Latin Modern Mono", "Latin Modern Mono Caps", "Latin Modern Mono Light", "Latin Modern Mono Light Cond", "Latin Modern Mono Prop", "Latin Modern Mono Prop Light", "Latin Modern Mono Slanted", "Latin Modern Roman", "Latin Modern Roman Caps", "Latin Modern Roman Demi", "Latin Modern Roman Dunhill", "Latin Modern Roman Slanted", "Latin Modern Roman Unslanted", "Latin Modern Sans", "Latin Modern Sans Demi Cond", "Latin Modern Sans Quotation", "Lato", "Lato Black", "Lato Hairline", "Lato Heavy", "Lato Light", "Lato Medium", "Lato Semibold", "Lato Thin", "Liberation Mono", "Liberation Sans", "Liberation Sans Narrow", "Liberation Serif", "LM Mono 10", "LM Mono 12", "LM Mono 8", "LM Mono 9", "LM Mono Caps 10", "LM Mono Light 10", "LM Mono Light Cond 10", "LM Mono Prop 10", "LM Mono Prop Light 10", "LM Mono Slanted 10", "LM Roman 10", "LM Roman 12", "LM Roman 17", "LM Roman 5", "LM Roman 6", "LM Roman 7", "LM Roman 8", "LM Roman 9", "LM Roman Caps 10", "LM Roman Demi 10", "LM Roman Dunhill 10", "LM Roman Slanted 10", "LM Roman Slanted 12", "LM Roman Slanted 17", "LM Roman Slanted 8", "LM Roman Slanted 9", "LM Roman Unslanted 10", "LM Sans 10", "LM Sans 12", "LM Sans 17", "LM Sans 8", "LM Sans 9", "LM Sans Demi Cond 10", "LM Sans Quot 8", "MathJax_AMS", "MathJax_Caligraphic", "MathJax_Fraktur", "MathJax_Main", "MathJax_Math", "MathJax_SansSerif", "MathJax_Script", "MathJax_Size1", "MathJax_Size2", "MathJax_Size3", "MathJax_Size4", "MathJax_Typewriter", "MathJax_Vector", "MathJax_Vector-Bold", "MathJax_WinChrome", "MathJax_WinIE6", "Monospace", "msam10", "msbm10", "Nimbus Mono PS [urw]", "Nimbus Mono PS [UKWN]", "Nimbus Roman [urw]", "Nimbus Roman [UKWN]", "Nimbus Sans [urw]", "Nimbus Sans [URW ]", "Nimbus Sans [UKWN]", "Nimbus Sans Narrow [urw]", "Nimbus Sans Narrow [UKWN]", "Noto Color Emoji", "Noto Kufi Arabic", "Noto Looped Lao", "Noto Looped Lao UI", "Noto Looped Thai", "Noto Looped Thai UI", "Noto Mono", "Noto Music", "Noto Naskh Arabic", "Noto Naskh Arabic UI", "Noto Nastaliq Urdu", "Noto Rashi Hebrew", "Noto Sans", "Noto Sans Adlam", "Noto Sans Adlam Unjoined", "Noto Sans Anatolian Hieroglyphs", "Noto Sans Arabic", "Noto Sans Arabic UI", "Noto Sans Armenian", "Noto Sans Avestan", "Noto Sans Balinese", "Noto Sans Bamum", "Noto Sans Bassa Vah", "Noto Sans Batak", "Noto Sans Bengali", "Noto Sans Bengali UI", "Noto Sans Bhaiksuki", "Noto Sans Brahmi", "Noto Sans Buginese", "Noto Sans Buhid", "Noto Sans Canadian Aboriginal", "Noto Sans Carian", "Noto Sans Caucasian Albanian", "Noto Sans Chakma", "Noto Sans Cham", "Noto Sans Cherokee", "Noto Sans CJK HK", "Noto Sans CJK JP", "Noto Sans CJK KR", "Noto Sans CJK SC", "Noto Sans CJK TC", "Noto Sans Coptic", "Noto Sans Cuneiform", "Noto Sans Cypriot", "Noto Sans Deseret", "Noto Sans Devanagari", "Noto Sans Devanagari UI", "Noto Sans Display", "Noto Sans Duployan", "Noto Sans Egyptian Hieroglyphs", "Noto Sans Elbasan", "Noto Sans Elymaic", "Noto Sans Ethiopic", "Noto Sans Georgian", "Noto Sans Glagolitic", "Noto Sans Gothic", "Noto Sans Grantha", "Noto Sans 

Processed: fixed 1034160 in qtbase-opensource-src/5.15.8+dfsg-5 ...

2023-04-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 1034160 qtbase-opensource-src/5.15.8+dfsg-5
Bug #1034160 [libqt5gui5] libkscreenlocker5: Screen locker crashes asking for 
loginctl command
Marked as fixed in versions qtbase-opensource-src/5.15.8+dfsg-5.
> found 1034160 qtbase-opensource-src/5.15.8+dfsg-6
Bug #1034160 [libqt5gui5] libkscreenlocker5: Screen locker crashes asking for 
loginctl command
Marked as found in versions qtbase-opensource-src/5.15.8+dfsg-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1034160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1034169: libqt5core5a: upgrade to 5.15.8+dfsg-4 stops krunner shortcut from working

2023-04-12 Thread Antonio
The block screen is also back and requires to perform "loginctl 
unlock-session n"



Il 12/04/23 07:58, Antonio ha scritto:


Hi Samuel,
after update to version 5.15.8+DFSG-6 krunner does not respond to Alt-F2.

Compared to before, the program is active in memory without errors.

The program runs but does not show activities.


$ gdb krunner
...
Starting program: /usr/bin/krunner
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

[New Thread 0x703ff6c0 (LWP 4954)]
[New Thread 0x7fffef9e76c0 (LWP 4955)]
[New Thread 0x7fffecdff6c0 (LWP 4957)]
[New Thread 0x7fffe59ff6c0 (LWP 4958)]


Il 11/04/23 01:32, Samuel Thibault ha scritto:

Hello,

Thanks for the backtrace, I believe I understand what is happening.  I
came up with another solution that should be way safer.

Thanks,
Samuel

Bug#1034169: libqt5core5a: upgrade to 5.15.8+dfsg-4 stops krunner shortcut from working

2023-04-12 Thread Antonio

Hi Samuel,
after update to version 5.15.8+DFSG-6 krunner does not respond to Alt-F2.

Compared to before, the program is active in memory without errors.

The program runs but does not show activities.


$ gdb krunner
...
Starting program: /usr/bin/krunner
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x703ff6c0 (LWP 4954)]
[New Thread 0x7fffef9e76c0 (LWP 4955)]
[New Thread 0x7fffecdff6c0 (LWP 4957)]
[New Thread 0x7fffe59ff6c0 (LWP 4958)]


Il 11/04/23 01:32, Samuel Thibault ha scritto:

Hello,

Thanks for the backtrace, I believe I understand what is happening.  I
came up with another solution that should be way safer.

Thanks,
Samuel