Bug#1072338: syndication: fix building with nocheck

[Samuel Thibault]

Source: syndication
Version: 5.115.0-2
Severity: important

Hello,

syndication currently fails to build with DEB_BUILD_OPTIONS=nocheck:

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5syndication5abi1/DEBIAN/symbols doesn't 
match completely debian/libkf5syndication5abi1.symbols
--- debian/libkf5syndication5abi1.symbols 
(libkf5syndication5abi1_1:5.115.0-2_amd64)
+++ dpkg-gensymbolsscli3z   2024-06-01 08:16:49.0 +
@@ -1,7 +1,7 @@
 libKF5Syndication.so.5abi1 libkf5syndication5abi1 #MINVER#
 * Build-Depends-Package: libkf5syndication-dev
  ABI_5_1@ABI_5_1 18.07.90
- _ZN11Syndication10LoaderUtil9parseFeedERK10QByteArrayRK4QUrl@ABI_5_1 1:5.69.0
+#MISSING: 1:5.115.0-2# 
_ZN11Syndication10LoaderUtil9parseFeedERK10QByteArrayRK4QUrl@ABI_5_1 1:5.69.0
  _ZN11Syndication10PersonImplC1ERK7QStringS3_S3_@ABI_5_1 18.07.90
  _ZN11Syndication10PersonImplC1Ev@ABI_5_1 18.07.90
  _ZN11Syndication10PersonImplC2ERK7QStringS3_S3_@ABI_5_1 18.07.90

Indeed, with tests disabled, ./src/syndication_private_export.h defines
SYNDICATION_TESTS_EXPORT to empty, and thus this declaration hides the
symbol:

./src/loaderutil_p.h:Q_REQUIRED_RESULT SYNDICATION_TESTS_EXPORT QUrl 
parseFeed(const QByteArray , const QUrl );

So it's effectively an optional symbol, could you apply the attached
patch to fix this?

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'), 
(500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (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.9.0 (SMP w/8 CPU threads; PREEMPT)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- debian/libkf5syndication5abi1.symbols.orig  2024-06-01 09:52:19.0 
+
+++ debian/libkf5syndication5abi1.symbols   2024-06-01 09:52:21.0 
+
@@ -2,7 +2,7 @@
 libKF5Syndication.so.5abi1 libkf5syndication5abi1 #MINVER#
 * Build-Depends-Package: libkf5syndication-dev
  ABI_5_1@ABI_5_1 18.07.90
- _ZN11Syndication10LoaderUtil9parseFeedERK10QByteArrayRK4QUrl@ABI_5_1 1:5.69.0
+ 
(optional)_ZN11Syndication10LoaderUtil9parseFeedERK10QByteArrayRK4QUrl@ABI_5_1 
1:5.69.0
  _ZN11Syndication10PersonImplC1ERK7QStringS3_S3_@ABI_5_1 18.07.90
  _ZN11Syndication10PersonImplC1Ev@ABI_5_1 18.07.90
  _ZN11Syndication10PersonImplC2ERK7QStringS3_S3_@ABI_5_1 18.07.90

Bug#1034623: unblock: qtbase-opensource-src/5.15.8+dfsg-7

[Samuel Thibault]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: qtbase-opensource-...@packages.debian.org
Control: affects -1 + src:qtbase-opensource-src

Please unblock package qtbase-opensource-src, thanks!

[ Reason ]
This upload fixes the accessibility of Qt5 application started as root.
Bug#1033995

[ Impact ]
Normally users wouldn't run applications as root, but one notable
exception is the calamares installer, which 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.

[ Tests ]
This was tested by hand, as well as by upstream.

[ Risks ]
The code is quite simple. It went through a few iterations because of
the complexity of the initialization of Qt applications. In the end, the
solution that was commited upstream (using QMetaObject::invokeMethod
to delay initialization of accessibility) is very similar to another
upstream fix that had gone in in july 2022 and hasn't met any problems
since then.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

unblock qtbase-opensource-src/5.15.8+dfsg-7
diff -Nru qtbase-opensource-src-5.15.8+dfsg/debian/changelog 
qtbase-opensource-src-5.15.8+dfsg/debian/changelog
--- qtbase-opensource-src-5.15.8+dfsg/debian/changelog  2023-02-27 
09:28:53.0 +0100
+++ qtbase-opensource-src-5.15.8+dfsg/debian/changelog  2023-04-13 
01:24:34.0 +0200
@@ -1,3 +1,31 @@
+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).
+
+ -- Lisandro Damián Nicanor Pérez Meyer   Wed, 12 Apr 
2023 20:24:34 -0300
+
+qtbase-opensource-src (5.15.8+dfsg-6) unstable; urgency=medium
+
+  * Use the new, fixed version of a11y_root.diff from Samuel Thibault
+(again closes: #1033995).
+
+ -- Dmitry Shachnev   Tue, 11 Apr 2023 14:25:22 +0300
+
+qtbase-opensource-src (5.15.8+dfsg-5) unstable; urgency=medium
+
+  * Revert the last upload. Unfortunately, it caused regressions
+(closes: #1034160, #1034169, #1034191).
+
+ -- Dmitry Shachnev   Mon, 10 Apr 2023 23:58:16 +0300
+
+qtbase-opensource-src (5.15.8+dfsg-4) unstable; urgency=medium
+
+  * Add a patch to fix accessibility on XCB when running as root
+(closes: #1033995).
+
+ -- Dmitry Shachnev   Sun, 09 Apr 2023 21:23:36 +0300
+
 qtbase-opensource-src (5.15.8+dfsg-3) unstable; urgency=medium
 
   * Use ${DEB_HOST_GNU_TYPE} substitution in debian/qt5-qmake.install.
diff -Nru qtbase-opensource-src-5.15.8+dfsg/debian/patches/a11y_root.diff 
qtbase-opensource-src-5.15.8+dfsg/debian/patches/a11y_root.diff
--- qtbase-opensource-src-5.15.8+dfsg/debian/patches/a11y_root.diff 
1970-01-01 01:00:00.0 +0100
+++ qtbase-opensource-src-5.15.8+dfsg/debian/patches/a11y_root.diff 
2023-04-13 00:50:31.0 +0200
@@ -0,0 +1,33 @@
+Description: 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. So after connecting the
+ signal, check the value by hand to make sure not to miss the
+ notification.
+ .
+ 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.
+Origin: https://codereview.qt-project.org/c/qt/qtbase/+/205196
+Bug: https://bugs.debian.org/1033995
+Last-Update: 2023-04-12
+
+--- 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)
diff -Nru qtbase-opensource-src-5.15.8+dfsg/debian/patches/series 
qtbase-opensource-src-5.15.8+dfsg/debian/patches/series
--- qtbase-opensource-src-5.15.8+dfsg/debian/patches/series 2023-02-27 
09:28:53.0 +0100
+++ qtbase-opensource-src-5.15.8+dfsg/debian/patches/series 2023-04-13 
00:57:07.0 +0200
@@ -29,3 +29,4 @@
 cross_build_mysql.diff
 cast_types_for_egl_x11_test.diff
 revert_startBlocking_removal.d

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

[Samuel Thibault]

Lisandro Damián Nicanor Pérez Meyer, le mer. 12 avril 2023 21:54:03 -0300, a 
ecrit:
> Samuel: do you know if this bug is also applicable to Qt 6?

Yes it is. The patch I have sent upstream should apply fine on debian's
qt6.

Samuel

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

[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

[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#1034169: libqt5core5a: upgrade to 5.15.8+dfsg-4 stops krunner shortcut from working

[Samuel Thibault]

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#1033995: qtbase-opensource-src: Fix accessibility of qt5 applications run as root

[Samuel Thibault]

Control: reopen -1
Control: found -1 5.15.8+dfsg-5

Hello,

So the patch that was submitted upstream is indeed posing
problems: #1034160, #1034169, #1034191. AIUI, I guess that connecting
the enabledChanged signal too early is problematic because the code is
not actually ready to handle it because initialization is not finished.

I however came up with another way to fix the issue, that is way simpler
and should really not pose any problem since that's the way it's
happening in the normal case. I have submitted it upstream, and here is
the change.

Samuel
Description: 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. So after connecting the
 signal, check the value by hand to make sure not to miss the
 notification.
 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.
Origin: https://codereview.qt-project.org/c/qt/qtbase/+/205196
Bug: https://bugs.debian.org/1033995
Last-Update: 2023-04-09

--- a/src/platformsupport/linuxaccessibility/bridge.cpp
+++ b/src/platformsupport/linuxaccessibility/bridge.cpp
@@ -65,6 +65,10 @@ 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.
+if (dbusConnection->isEnabled())
+enabledChanged(true);
 }
 
 void QSpiAccessibleBridge::enabledChanged(bool enabled)

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

[Samuel Thibault]

Antonio, le lun. 10 avril 2023 21:13:59 +0200, a ecrit:
> Thread 1 "krunner" received signal SIGSEGV, Segmentation fault.
> 0x74a9814a in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> (gdb) bt
> #0  0x74a9814a in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> #1  0x74a982d2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> #2  0x74a982d2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> #3  0x74a982d2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> #4  0x74a98608 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> #5  0x74a98743 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> #6  0x74a98a40 in _dbus_type_reader_set_basic () from /lib/
> x86_64-linux-gnu/libdbus-1.so.3
> #7  0x74a9604b in _dbus_header_set_field_basic () from /lib/
> x86_64-linux-gnu/libdbus-1.so.3
> #8  0x74a9a92d in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
> #9  0x74a9c793 in dbus_message_iter_append_basic () from /lib/
> x86_64-linux-gnu/libdbus-1.so.3
> #10 0x769c990b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
> #11 0x769cb8f1 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
> #12 0x7699e8b0 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
> #13 0x7699854d in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
> #14 0x7699b2a8 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5

Could you re-run with libdbus-1-3-dbgsym and libqt5dbus5-dbgsym
installed?

Samuel

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

[Samuel Thibault]

Antonio, le lun. 10 avril 2023 20:40:12 +0200, a ecrit:
> I confirm this problem,

Ok, but I'd need a way to reproduce it to be able to fix the change...

Samuel

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

[Samuel Thibault]

Hello,

Arthur Marsh, le mar. 11 avril 2023 00:43:16 +0930, a ecrit:
> krunner alt-F2 shortcut worked again

I cannot reproduce the issue.  What I did was:

- install bookworm with the KDE desktop task
- upgrade libqt5core5a to 5.15.8+dfsg-4, that upgraded all other
  libraries from qt5base.
- rebooted
- logged into the KDE session
- pressed alt-f2, and krunner showed up.

I tried both with Xorg and wayland, in both cases it worked.

Is there something specific in your desktop environment, compared to
that situation?

The change included in 5.15.8+dfsg-4 is really not related to shortcuts
at all so this issue is very surprising.

Samuel

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

[Samuel Thibault]

Hello,

Dmitry Shachnev, le jeu. 06 avril 2023 22:15:01 +0300, a ecrit:
> On Thu, Apr 06, 2023 at 06:20:04PM +0200, Samuel Thibault wrote:
> > Oh, I didn't notice that there was a recorded test failure.
> >
> > I don't see how the failure can be related to the change...
> >
> > Cc-ing Frederik, in case he remembers / realizes something.
> 
> I just want to add some context. We are talking about this change:
> 
> https://codereview.qt-project.org/c/qt/qtbase/+/205196
> 
> Frederik, perhaps you can rebase and see if the tests still fail?

Not sure Frederik is still working for KDE, I have pushed the rebase,
let's see.

Samuel

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

[Samuel Thibault]

Dmitry Shachnev, le jeu. 06 avril 2023 19:10:28 +0300, a ecrit:
> I don't like that this change has not been merged upstream because of
> test failures,

Oh, I didn't notice that there was a recorded test failure.

I don't see how the failure can be related to the change...

Cc-ing Frederik, in case he remembers / realizes something.

> But I looked at the KDE branch, and the last three commits they have there [1]
> seem to be related to the same problem. At least, the comment talks about the
> the same thing as your description:
> 
> // Only connect on next loop run, connections to our enabled signal are
> // only established after the ctor returns.
> 
> But these changes depend on AT_SPI_BUS_ADDRESS environment variable. Can we
> rely on it in Debian?

No, that variable is not usually set. root-owned applications get the
bus address from the X11 root window property.

It's unfortunate that this fix didn't see Frederik's patch which should
be way more straightforward to fix things.

Samuel

> --
> Dmitry Shachnev

> diff --git a/src/platformsupport/linuxaccessibility/dbusconnection.cpp 
> b/src/platformsupport/linuxaccessibility/dbusconnection.cpp
> index 45ddc8e496..cc734abc63 100644
> --- a/src/platformsupport/linuxaccessibility/dbusconnection.cpp
> +++ b/src/platformsupport/linuxaccessibility/dbusconnection.cpp
> @@ -69,6 +69,21 @@ QT_BEGIN_NAMESPACE
>  DBusConnection::DBusConnection(QObject *parent)
>  : QObject(parent), m_a11yConnection(QString()), m_enabled(false)
>  {
> +// If the bus is explicitly set via env var it overrides everything else.
> +QByteArray addressEnv = qgetenv("AT_SPI_BUS_ADDRESS");
> +if (!addressEnv.isEmpty()) {
> +// Only connect on next loop run, connections to our enabled signal 
> are
> +// only established after the ctor returns.
> +QMetaObject::invokeMethod(
> +this,
> +[this, addressEnv] {
> +m_enabled = true;
> +connectA11yBus(QString::fromLocal8Bit(addressEnv));
> +},
> +Qt::QueuedConnection);
> +return;
> +}
> +
>  // Start monitoring if "org.a11y.Bus" is registered as DBus service.
>  QDBusConnection c = QDBusConnection::sessionBus();
>  if (!c.isConnected()) {

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

[Samuel Thibault]

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, 
SLOT(enabledChanged(bool)));
+dbusConnection->init();
 }
 
 void QSpiAccessibleBridge::enabledChanged(bool enabled)
--- a/src/platformsupport/linuxaccessibility/dbusconnection.cpp
+++ b/src/platformsupport/linuxaccessibility/dbusconnection.cpp
@@ -69,6 +69,14 @@ QT_BEGIN_NAMESPACE
 DBusConnection::DBusConnection(QObject *parent)
 : QObject(parent), m_a11yConnection(QString()), m_enabled(false)
 {
+}
+
+/**
+\internal
+Connect to the accessibility dbus service.
+*/
+void DBusConnection::init()
+{
 // Start monitoring if "org.a11y.Bus" is registered as DBus service.
 QDBusConnection c = QDBusConnection::sessionBus();
 if (!c.isConnected()) {
--- a/src/platformsupport/linuxaccessibility/dbusconnection_p.h
+++ b/src/platformsupport/linuxaccessibility/dbusconnection_p.h
@@ -67,6 +67,7 @@ class DBusConnection : public QObject
 

Bug#993719: plasma-framework: missing symbol on hurd-i386

[Samuel Thibault]

Norbert Preining, le dim. 05 sept. 2021 22:00:50 +0900, a ecrit:
> > Version: 5.81.0
> ...
> > It seems hurd-i386 also needs ignoring the missing
> > _ZNK12KConfigGroup9readEntryI6QSizeFEET_PKcRKS2_@Base symbol, as the
> > attached patch fixes like on i386.
> 
> Do you really mean 5.81.0?

Since the symbol was marked as supposed to be appearing in 5.81.0, yes.
Version 5.83.0-2 was already failing with that issue.

> You also have a wild mixture of 5.83 nd 5.85, seem your system is not
> completely uptodate.

I'm not actually reporting the bug from by testbox, sorry.

Samuel

Bug#993719: plasma-framework: missing symbol on hurd-i386

[Samuel Thibault]

Package: plasma-framework
Version: 5.81.0
Severity: important
Tags: patch

Hello,

It seems hurd-i386 also needs ignoring the missing
_ZNK12KConfigGroup9readEntryI6QSizeFEET_PKcRKS2_@Base symbol, as the
attached patch fixes like on i386.

Samuel

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

Kernel: Linux 5.14.0 (SMP w/8 CPU threads)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-framework depends on:
ii  kio  5.83.0-2
ii  kpackagetool55.85.0-2
ii  libc62.31-17
ii  libegl1  1.3.2-1
ii  libgcc-s111.2.0-3
ii  libglx0  1.3.2-1
ii  libkf5activities55.85.0-2
ii  libkf5calendarevents55.83.0-2
ii  libkf5configcore55.85.0-2
ii  libkf5configgui5 5.85.0-2
ii  libkf5coreaddons55.85.0-2
ii  libkf5declarative5   5.83.0-2
ii  libkf5i18n5  5.85.0-2
ii  libkf5iconthemes55.85.0-2
ii  libkf5kiocore5   5.83.0-2
ii  libkf5kiowidgets55.83.0-2
ii  libkf5notifications5 5.85.0-3
ii  libkf5package5   5.85.0-2
ii  libkf5plasma55.83.0-2
ii  libkf5plasmaquick5   5.83.0-2
ii  libkf5quickaddons5   5.83.0-2
ii  libkf5widgetsaddons5 5.85.0-2
ii  libkf5windowsystem5  5.85.0-2
ii  libkf5xmlgui55.85.0-3
ii  libopengl0   1.3.2-1
ii  libqt5core5a 5.15.2+dfsg-10
ii  libqt5gui5   5.15.2+dfsg-10
ii  libqt5qml5   5.15.2+dfsg-8
ii  libqt5quick5 5.15.2+dfsg-8
ii  libqt5widgets5   5.15.2+dfsg-10
ii  libqt5x11extras5 5.15.2-2
ii  libstdc++6   11.2.0-3
ii  libx11-6 2:1.7.2-1
ii  libxcb-composite01.14-3
ii  libxcb-damage0   1.14-3
ii  libxcb-render0   1.14-3
ii  libxcb1  1.14-3
ii  qml-module-org-kde-kconfig   5.83.0-2
ii  qml-module-org-kde-kquickcontrols5.83.0-2
ii  qml-module-org-kde-kquickcontrolsaddons  5.83.0-2
ii  qml-module-qtqml-models2 5.15.2+dfsg-8
ii  qml-module-qtquick-controls  5.15.2-2
ii  qml-module-qtquick-controls2 5.15.2+dfsg-4
ii  qml-module-qtquick-templates25.15.2+dfsg-4

plasma-framework recommends no packages.

plasma-framework suggests no packages.

-- no debconf information

-- 
Samuel
/*
 * [...] Note that 120 sec is defined in the protocol as the maximum
 * possible RTT.  I guess we'll have to use something other than TCP
 * to talk to the University of Mars.
 * PAWS allows us longer timeouts and large windows, so once implemented
 * ftp to mars will work nicely.
 */
(from /usr/src/linux/net/inet/tcp.c, concerning RTT [retransmission timeout])
--- debian/libkf5plasma5.symbols.original   2021-09-05 12:26:40.0 
+
+++ debian/libkf5plasma5.symbols2021-09-05 12:26:56.0 +
@@ -483,7 +483,7 @@
  _ZN6Plasma8FrameSvgD1Ev@Base 4.96.0
  _ZN6Plasma8FrameSvgD2Ev@Base 4.96.0
  (optional=templinst|arch=arm64 armel armhf hurd-i386 i386 kfreebsd-i386 m68k 
mips mipsel powerpc powerpcspe ppc64el 
sparc64)_ZNK12KConfigGroup9readEntryI6QRectFEET_PKcRKS2_@Base 4.100.0
- (arch=!i386 !m68k !mipsel !ppc64 
!s390x)_ZNK12KConfigGroup9readEntryI6QSizeFEET_PKcRKS2_@Base 5.81.0
+ (arch=!hurd-i386 !i386 !m68k !mipsel !ppc64 
!s390x)_ZNK12KConfigGroup9readEntryI6QSizeFEET_PKcRKS2_@Base 5.81.0
  (optional=templinst)_ZNK12KConfigGroup9readEntryIbEET_PKcRKS1_@Base 5.61.0
  (optional=templinst)_ZNK12KConfigGroup9readEntryIdEET_PKcRKS1_@Base 5.17.0
  (optional=templinst)_ZNK12KConfigGroup9readEntryIiEET_PKcRKS1_@Base 4.100.0

Bug#993682: kio: Fix non-linux builds

[Samuel Thibault]

Package: kio
Version: 5.85.0-1
Severity: important
Tags: patch

Hello,

Version 5.85.0-1 of kio added the libmount-dev build-dep, but this is
linux-only. I have attached a patch that disables it on non-linux, thus
fixing the build.

Samuel

-- System Information:
Debian Release: bookworm/sid
  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-debug'), (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

Kernel: Linux 5.14.0 (SMP w/8 CPU threads)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kio depends on:
ii  kded5 5.85.0-2
ii  libacl1   2.3.1-1
ii  libc6 2.31-17
ii  libgcc-s1 11.2.0-3
ii  libgssapi-krb5-2  1.18.3-7
ii  libkf5archive55.85.0-2
ii  libkf5authcore5   5.85.0-2
ii  libkf5codecs5 5.85.0-2
ii  libkf5configcore5 5.85.0-2
ii  libkf5configwidgets5  5.85.0-2
ii  libkf5coreaddons5 5.85.0-2
ii  libkf5dbusaddons5 5.85.0-2
ii  libkf5doctools5   5.85.0-2
ii  libkf5i18n5   5.85.0-2
ii  libkf5itemviews5  5.85.0-2
ii  libkf5kiocore55.83.0-2
ii  libkf5kiogui5 5.83.0-2
ii  libkf5kiontlm55.83.0-2
ii  libkf5kiowidgets5 5.83.0-2
ii  libkf5notifications5  5.85.0-3
ii  libkf5service-bin 5.85.0-2
ii  libkf5service55.85.0-2
ii  libkf5solid5  5.85.0-2
ii  libkf5textwidgets55.85.0-2
ii  libkf5wallet-bin  5.83.0-2
ii  libkf5wallet5 5.83.0-2
ii  libkf5widgetsaddons5  5.85.0-2
ii  libkf5windowsystem5   5.85.0-2
ii  libqt5core5a  5.15.2+dfsg-10
ii  libqt5dbus5   5.15.2+dfsg-10
ii  libqt5gui55.15.2+dfsg-10
ii  libqt5network55.15.2+dfsg-10
ii  libqt5qml55.15.2+dfsg-8
ii  libqt5widgets55.15.2+dfsg-10
ii  libqt5x11extras5  5.15.2-2
ii  libqt5xml55.15.2+dfsg-10
ii  libstdc++611.2.0-3
ii  libxml2   2.9.10+dfsg-6.7
ii  libxslt1.11.1.34-4

kio recommends no packages.

kio suggests no packages.

-- no debconf information

-- 
Samuel
 > Quelqu'un aurait-il une solution pour réinitialiser un MBR
 Si tu veux qu'il soit complètement blanc (pas souhaitable, à mon avis) :
 dd if=/dev/zero of=/dev/hda bs=512 count=1 (sous Linux)
 -+- OT in Guide du linuxien (très) pervers - "Pour les K difficiles" -+-
--- debian/control.original 2021-09-04 17:42:04.0 +
+++ debian/control  2021-09-04 17:42:09.0 +
@@ -34,7 +34,7 @@
libkf5windowsystem-dev (>= 5.85.0~),
libkf5xmlgui-dev (>= 5.85.0~),
libkrb5-dev,
-   libmount-dev,
+   libmount-dev [linux-any],
libqt5sql5-sqlite,
libqt5x11extras5-dev (>= 5.15.0~),
libxml2-dev,

Bug#978164: kguiaddons: FTBFS on non-linux

[Samuel Thibault]

Pino Toscano, le sam. 26 déc. 2020 22:04:14 +0100, a ecrit:
> Yes, I know. I already fixed it few days ago:
> https://salsa.debian.org/qt-kde-team/kde/kguiaddons/-/commit/1130cd0d8f0c95c9536a74034826fbb0ed5f0d8c

Cool, thanks!

Samuel

Bug#978164: kguiaddons: FTBFS on non-linux

[Samuel Thibault]

Source: kguiaddons
Version: 5.77.0-3
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

kguiaddons currently doesn't build on non-Linux, where Wayland is not
available. The attached patch fixes this.

Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'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

Kernel: Linux 5.10.0 (SMP w/8 CPU threads)
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 not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Samuel
 KK1 a 1 conseil de comment s'attaquer a du code java ou ya plus de 50 
classes ? par kel bout ?
 le troisième
 -+- #ens-mim en stage -+-
--- debian/control.original 2020-12-26 20:33:59.0 +
+++ debian/control  2020-12-26 20:34:21.0 +
@@ -10,9 +10,9 @@
extra-cmake-modules (>= 5.77.0~),
graphviz,
libqt5sql5-sqlite:native,
-   libqt5waylandclient5-dev (>= 5.13.0~),
+   libqt5waylandclient5-dev (>= 5.13.0~) [linux-any],
libqt5x11extras5-dev (>= 5.13.0~),
-   libwayland-dev (>= 1.9~),
+   libwayland-dev (>= 1.9~) [linux-any],
libx11-dev,
libxcb1-dev,
pkg-config,
@@ -21,7 +21,7 @@
qtbase5-private-dev,
qttools5-dev,
qttools5-dev-tools (>= 5.4),
-   qtwayland5-dev-tools (>= 5.13.0~),
+   qtwayland5-dev-tools (>= 5.13.0~) [linux-any],
 Standards-Version: 4.5.1
 Homepage: https://invent.kde.org/frameworks/kguiaddons
 Vcs-Browser: https://salsa.debian.org/qt-kde-team/kde/kguiaddons
--- debian/rules.original   2020-12-26 20:42:47.0 +
+++ debian/rules2020-12-26 20:43:55.0 +
@@ -2,11 +2,15 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+ifneq ($(DEB_BUILD_ARCH_OS),linux)
+WAYLAND=-DWITH_WAYLAND=OFF
+endif
+
 %:
dh $@ --with kf5,pkgkde_symbolshelper --buildsystem kf5 --without 
build_stamp
 
 override_dh_auto_configure:
-   dh_auto_configure -- -DBUILD_QCH=ON -DBUILD_TESTING=OFF
+   dh_auto_configure -- -DBUILD_QCH=ON -DBUILD_TESTING=OFF $(WAYLAND)
 
 override_dh_auto_test:
# Disable auto tests at build time
--- debian/libkf5guiaddons5.symbols.original2020-12-26 20:49:28.0 
+
+++ debian/libkf5guiaddons5.symbols 2020-12-26 20:49:33.0 +
@@ -184,5 +184,5 @@
  _ZTV19KeySequenceRecorder@Base 5.77.0
  _ZTV24KModifierKeyInfoProvider@Base 5.61.0
  _ZTV30KLocalImageCacheImplementation@Base 4.96.0
- zwp_keyboard_shortcuts_inhibit_manager_v1_interface@Base 5.77.0
- zwp_keyboard_shortcuts_inhibitor_v1_interface@Base 5.77.0
+ (arch=linux-any)zwp_keyboard_shortcuts_inhibit_manager_v1_interface@Base 
5.77.0
+ (arch=linux-any)zwp_keyboard_shortcuts_inhibitor_v1_interface@Base 5.77.0

Bug#948676: at-spi2-core: /etc/X11/Xsession.d/90qt-a11y does not enable Qt5 support as the Wiki indicates

[Samuel Thibault]

Control: forwarded -1 https://codereview.qt-project.org/c/qt/qtbase/+/286336

Dmitry Shachnev, le dim. 12 janv. 2020 22:31:14 +0300, a ecrit:
> On Sun, Jan 12, 2020 at 07:54:22PM +0100, Samuel Thibault wrote:
> > Could we at least restore looking at IsEnabled in Qt, as the attached
> > patch does? Actually, that is needed for proper focus tracking in Qt
> > applications for zoom support in compiz when Orca is not used. The
> > comment there says that IsEnabled is always true, but that's not what I
> > am observing with e.g. Debian 8's gnome 3.14, Debian 9's gnome 3.22, and
> > Debian 10's 3.30... Ideally, we'd backport this fix to buster too.
> 
> Any chance you can submit the patch to Qt Gerrit [1]?

Here it is.

Samuel

Bug#948676: at-spi2-core: /etc/X11/Xsession.d/90qt-a11y does not enable Qt5 support as the Wiki indicates

[Samuel Thibault]

Thorsten Glaser, le dim. 12 janv. 2020 19:37:03 +, a ecrit:
> Samuel Thibault dixit:
> 
> >I guess in your case what you expected was that at the very least
> >applications started after orca got started should be accessible, even
> >if orca is only started by hand. This would work if Qt was not only
> >looking at org.a11y.Status ScreenReaderEnabled (the control panel
> >configuration), but also at org.a11y.Status IsEnabled (set by Orca on
> >startup). This would not be enough for making existing applications
> >accessible when you first start Orca, Bug#874054 mentions that it's
> >because Qt currently doesn't monitor the dbus IsEnabled variable.
> 
> Ooh, interesting. From what the MuseScore people say, after start
> of orca would be enough (also, AIUI, orca starts with the desktop
> session or can be made to).

Starting orca only wouldn't be enough. But enabling Orca startup in the
control panel would be enough. My patch is for the former case.

> >Could we at least restore looking at IsEnabled in Qt, as the attached
> >patch does? Actually, that is needed for proper focus tracking in Qt
> >applications for zoom support in compiz when Orca is not used. The
> 
> Would this have the effect of losing keyboard input in MuseScore
> when orca is used, which is what one tester reported?

That shouldn't happen, but that could be an effect indeed.

> I’m under plain X11 with evilwm, no desktop environment, and did
> not have that issue.

Getting Orca to access the content of the application would be enough to
get the same situation as the users.

Samuel

Bug#948676: at-spi2-core: /etc/X11/Xsession.d/90qt-a11y does not enable Qt5 support as the Wiki indicates

[Samuel Thibault]

Dmitry Shachnev, le dim. 12 janv. 2020 22:31:14 +0300, a ecrit:
> Any chance you can submit the patch to Qt Gerrit [1]?

I'll have a look at it.

Samuel

Bug#947735: qtlocation-opensource-src: Fix build on hurd-i386

[Samuel Thibault]

Control: reopen -1

Hello,

Version 5.12.5+dfsg-3 added the build of the mapbox plugin, which has a
portability issue. The attached patch was commited upstream, could you
apply it?
https://github.com/mapbox/mapbox-gl-native/pull/16085

Thanks,
Samuel
commit e4cab3f37fda236339d40a0de291cd75c9b1a51e
Author: Samuel Thibault 
Date:   Sun Dec 29 15:27:58 2019 +0100

[util] fix thread.cpp portability

diff --git a/src/3rdparty/mapbox-gl-native/platform/default/thread.cpp 
b/src/3rdparty/mapbox-gl-native/platform/default/thread.cpp
index 28772d956..58a7c12bc 100644
--- a/src/3rdparty/mapbox-gl-native/platform/default/thread.cpp
+++ b/src/3rdparty/mapbox-gl-native/platform/default/thread.cpp
@@ -12,26 +12,32 @@ namespace platform {
 
 std::string getCurrentThreadName() {
 char name[32] = "unknown";
+#ifdef __linux__
 pthread_getname_np(pthread_self(), name, sizeof(name));
+#endif
 
 return name;
 }
 
 void setCurrentThreadName(const std::string& name) {
+#ifdef __linux__
 if (name.size() > 15) { // Linux hard limit (see manpages).
 pthread_setname_np(pthread_self(), name.substr(0, 15).c_str());
 } else {
 pthread_setname_np(pthread_self(), name.c_str());
 }
+#endif
 }
 
 void makeThreadLowPriority() {
+#ifdef SCHED_IDLE
 struct sched_param param;
 param.sched_priority = 0;
 
 if (sched_setscheduler(0, SCHED_IDLE, ) != 0) {
 Log::Warning(Event::General, "Couldn't set thread scheduling policy");
 }
+#endif
 }
 
 } // namespace platform

Bug#947735: qtlocation-opensource-src: Fix build on hurd-i386

[Samuel Thibault]

Source: qtlocation-opensource-src
Version: 5.12.5+dfsg-2
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

qtlocation-opensource-src currently can't build on hurd-i386 because it
does not enable the geoclue modules. The attach patch fixes this.

Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (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

Kernel: Linux 5.4.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
c> [ ] morning [ ] afternoon [ ] evening [ ] night , everyone (choose as 
applicable)
Index: qtlocation-opensource-src-5.12.5+dfsg/src/plugins/position/position.pro
===
--- qtlocation-opensource-src-5.12.5+dfsg.orig/src/plugins/position/position.pro
+++ qtlocation-opensource-src-5.12.5+dfsg/src/plugins/position/position.pro
@@ -2,8 +2,8 @@ TEMPLATE = subdirs
 
 QT_FOR_CONFIG += positioning-private
 
-linux|freebsd|openbsd|netbsd:qtHaveModule(dbus):SUBDIRS += geoclue
-linux|freebsd|openbsd|netbsd:qtHaveModule(dbus):SUBDIRS += geoclue2
+linux|freebsd|openbsd|netbsd|hurd:qtHaveModule(dbus):SUBDIRS += geoclue
+linux|freebsd|openbsd|netbsd|hurd:qtHaveModule(dbus):SUBDIRS += geoclue2
 qtConfig(gypsy):SUBDIRS += gypsy
 qtConfig(winrt_geolocation):SUBDIRS += winrt
 qtHaveModule(simulator):SUBDIRS += simulator

Bug#947675: qtbase-opensource-src: please do not build-dep on libdrm-dev on hurd-any

[Samuel Thibault]

Source: qtbase-opensource-src
Version: 5.12.5+dfsg-4
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

qtbase-opensource-src currently can't be builton hurd-any because it
build-depends on libdrm-dev. Making the build-dep optional as the
attached patch does fixes this.

Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (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

Kernel: Linux 5.4.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- debian/control.original 2019-12-28 23:40:22.0 +
+++ debian/control  2019-12-28 23:40:32.0 +
@@ -19,7 +19,7 @@
libcups2-dev,
libdbus-1-dev,
libdouble-conversion-dev,
-   libdrm-dev,
+   libdrm-dev [linux-any kfreebsd-any],
libfontconfig1-dev,
libfreetype6-dev,
libgbm-dev [linux-any kfreebsd-any],

Bug#944031: qtsensors-opensource-src: FTBFS on !linux

[Samuel Thibault]

Source: qtsensors-opensource-src
Version: 5.12.5-2
Severity: important
Tags: patch

Hello,

qtsensors-opensource-src currently FTBFS on !linux archs, because the
libqt5sensors5 package doesn't even contain the libQt5Sensors.so.5
library.

Indeed, even if the source package contains libqt5sensors5.install, that
file gets dropped during the build, because debian/clean contains its
name. Could you apply the attached patch to fix this?

Thanks,
Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (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

Kernel: Linux 5.3.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
 what the fuck is wtf
--- debian/clean.original   2019-11-03 01:07:55.0 +
+++ debian/clean2019-11-03 01:07:56.0 +
@@ -1,4 +1,3 @@
-debian/libqt5sensors5.install
 doc/qtsensors.qch
 doc/qtsensors/
 examples/sensors/grue/detect_grue

Bug#922771: qtbase-opensource-src: Not accessible in wayland mode

[Samuel Thibault]

Lisandro Damián Nicanor Pérez Meyer, le mer. 20 févr. 2019 11:12:05 -0300, a 
ecrit:
> El miércoles, 20 de febrero de 2019 10:56:33 -03 Samuel Thibault escribió:
> > Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-73945
> > 
> > Samuel Thibault, le mer. 20 févr. 2019 14:46:45 +0100, a ecrit:
> > > This can be checked with
> > > 
> > > git clone http://salsa.debian.org/a11y-team/check-a11y
> > > 
> > > cd check-a11y
> > > make check_qt5
> > 
> > I meant
> > 
> > QT_QPA_PLATFORM=wayland make check_qt5
> > 
> > to actually enable wayland, of course.
> > 
> > I have forwarded the issue upstream.
> 
> You've been faster than me. I really don't know if there is a11y support in 
> wayland, so maybe this bug might actually be a wishlist one :-(

Gnome is accessible on Wayland. There are issues with keyboard snooping
& synthesis, but accessible applications just works.

Actually I'm really wondering why it shouldn't just work with Qt5. There
shouldn't really be much specific to be done. Perhaps Qt5 just doesn't
manage to find the dbus session bus.

> Of course we will do our best, but really sounds as an upstream issue :-/

Sure, I'd just rather track it in Debian too, to make sure it is known
and tracked so we know it gets fixed in Debian.

Samuel

Bug#922771: qtbase-opensource-src: Not accessible in wayland mode

[Samuel Thibault]

Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-73945

Samuel Thibault, le mer. 20 févr. 2019 14:46:45 +0100, a ecrit:
> This can be checked with
> 
> git clone http://salsa.debian.org/a11y-team/check-a11y
> 
> cd check-a11y
> make check_qt5

I meant

QT_QPA_PLATFORM=wayland make check_qt5

to actually enable wayland, of course.

I have forwarded the issue upstream.

Samuel

Bug#922771: qtbase-opensource-src: Not accessible in wayland mode

[Samuel Thibault]

Source: qtbase-opensource-src
Version: 5.11.3+dfsg-2
Severity: important
Tags: a11y

Hello,

While surveying accessibility, I noticed that qt5 is not accessible at
all when running in wayland mode, i.e. with QT_QPA_PLATFORM=wayland
Since this is not a default yet, this will not pose problems to
our users yet, but when it becomes a default, we will have to have
this fixed, otherwise all qt5 applications will suddenly become
non-accessible (qt4 is unaffected)

This can be checked with

git clone http://salsa.debian.org/a11y-team/check-a11y

cd check-a11y
make check_qt5

Samuel

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'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

Kernel: Linux 4.20.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#920613: qtbase-opensource-src: kio FTBFS on hurd-i386

[Samuel Thibault]

Source: qtbase-opensource-src
Version: 5.11.3+dfsg-3
Severity: important
Tags: patch

Hello,

kio currently FTBFS on hurd-i386 due to a missing include in
qplatforms.h:

https://buildd.debian.org/status/fetch.php?pkg=kio=hurd-i386=5.54.1-1=1547906241=0

See the attached patch which adds #include  (just like on
Linux). Without this include, __REDIRECT does not get defined, and then
open gets #defined to open64, leading to bogus MOC output.
Could you apply the attached patch in the next upload (along with the
patch for #920236?
(missing kio build prevents a lot of packages from being able to build)

Samuel

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'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

Kernel: Linux 4.20.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
 bon comment on fait de l'investigation pour savoir qui est le vilain ?
 on débranche le routeur et on regarde qui s'affole
 -+- #ens-mim administre -+-
Index: qtbase-opensource-src-5.11.3+dfsg/mkspecs/hurd-g++/qplatformdefs.h
===
--- qtbase-opensource-src-5.11.3+dfsg.orig/mkspecs/hurd-g++/qplatformdefs.h
+++ qtbase-opensource-src-5.11.3+dfsg/mkspecs/hurd-g++/qplatformdefs.h
@@ -58,7 +58,7 @@
 
 // We are hot - unistd.h should have turned on the specific APIs we requested
 
-
+#include 
 #include 
 #include 
 #include 

Bug#920236: qtbase-opensource-src: FTBFS on hurd-i386/kfreebsd-any: fix installed files list

[Samuel Thibault]

Source: qtbase-opensource-src
Version: 5.11.3+dfsg-3
Severity: important
Tags: patch

Hello,

I have fixed an issue in glibc that was making qtbase-opensource-src
fail to build on hurd-i386.  The 5.11.3+dfsg-3 build however still fails
(and on kfreebsd) because qtbase5-private-dev.install now explicits some
files which are not available on hurd-i386, or even on kfreebsd-any.  I
have attached a patch fixing this.

Samuel

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'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

Kernel: Linux 4.20.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
  bien sûr que ça convient mieux à tout le monde
  enfin, dans la mesure où tout le monde c'est comme moi
 -+- le consensus, c'est facile -+-
--- qtbase5-private-dev.install.original2019-01-23 00:54:09.0 
+
+++ qtbase5-private-dev.install 2019-01-23 00:55:32.0 +
@@ -130,14 +130,14 @@
 usr/lib/*/qt5/mkspecs/modules/qt_lib_devicediscovery_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_edid_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_egl_support_private.pri
-usr/lib/*/qt5/mkspecs/modules/qt_lib_eglfs_kms_support_private.pri
-usr/lib/*/qt5/mkspecs/modules/qt_lib_eglfsdeviceintegration_private.pri
+[!hurd-i386] usr/lib/*/qt5/mkspecs/modules/qt_lib_eglfs_kms_support_private.pri
+[!hurd-i386] 
usr/lib/*/qt5/mkspecs/modules/qt_lib_eglfsdeviceintegration_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_eventdispatcher_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_fb_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_fontdatabase_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_gui_private.pri
-usr/lib/*/qt5/mkspecs/modules/qt_lib_input_support_private.pri
-usr/lib/*/qt5/mkspecs/modules/qt_lib_kms_support_private.pri
+[linux-i386] usr/lib/*/qt5/mkspecs/modules/qt_lib_input_support_private.pri
+[!hurd-i386] usr/lib/*/qt5/mkspecs/modules/qt_lib_kms_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_linuxaccessibility_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_network_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_opengl_private.pri
@@ -148,7 +148,7 @@
 usr/lib/*/qt5/mkspecs/modules/qt_lib_sql_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_testlib_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_theme_support_private.pri
-usr/lib/*/qt5/mkspecs/modules/qt_lib_vulkan_support_private.pri
+[linux-i386] usr/lib/*/qt5/mkspecs/modules/qt_lib_vulkan_support_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_widgets_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_xcb_qpa_lib_private.pri
 usr/lib/*/qt5/mkspecs/modules/qt_lib_xml_private.pri

Bug#912628: kfilemetadata-kf5: FTBFS on hurd-i386

[Samuel Thibault]

Source: kfilemetadata-kf5
Version: 5.49.0-1
Severity: important
Tags: patch

Hello,

kfilemetadata-kf5 currently FTBFS on hurd-i386 because it uses an
undefined errno value, ENOATTR. Could you apply the attached patch to
fix this just like on Linux?

Thanks,
Samuel

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

Kernel: Linux 4.19.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
`When you say "I wrote a program that crashed Windows", people just stare at
you blankly and say "Hey, I got those with the system, *for free*".'
(By Linus Torvalds)
Index: kfilemetadata-kf5-5.49.0/src/xattr_p.h
===
--- kfilemetadata-kf5-5.49.0.orig/src/xattr_p.h
+++ kfilemetadata-kf5-5.49.0/src/xattr_p.h
@@ -32,7 +32,7 @@
 #include 
 #include 
 
-#if defined(Q_OS_ANDROID) || defined(Q_OS_LINUX)
+#if defined(Q_OS_ANDROID) || defined(Q_OS_LINUX) || defined(Q_OS_HURD)
 // attr/xattr.h is not available in the Android NDK so we are defining ENOATTR 
ourself
 #ifndef ENOATTR
 # define ENOATTR ENODATA/* No such attribute */

Re: [Pkg-cmake-team] Bug#912475: qtmultimedia-opensource-src: FTBFS on hurd: no qtaudioengine

[Samuel Thibault]

Control: reassign -1 sndio
Control: forcemerge 912453 -1

Felix Geyer, le jeu. 01 nov. 2018 01:31:55 +0100, a ecrit:
> The build failure is most likely caused by a bug in sndio, see #912443 and 
> #912453

Indeed, thanks!

Samuel

Re: Bug#912475: qtmultimedia-opensource-src: FTBFS on hurd: no qtaudioengine

[Samuel Thibault]

Samuel Thibault, le jeu. 01 nov. 2018 00:38:55 +0100, a ecrit:
> The link line contains /usr/lib/i386-gnu/libsndio.so in one case, and
> -lsndio in the other case. I don't know why cmake makes a difference. In
> both cases we have absolute paths in
> 
> ./build-tree/CMakeFiles/OpenAL.dir/build.make:libopenal.so.1.19.1: 
> /usr/lib/i386-gnu/libsndio.so
> ./build-tree/CMakeCache.txt:OpenAL_LIB_DEPENDS:STATIC=general;-pthread;general;common;general;/usr/lib/i386-gnu/libsndio.so;general;rt;general;pthread;general;dl;general;atomic;general;m;
> ./build-tree/CMakeCache.txt:SOUNDIO_LIBRARY:FILEPATH=/usr/lib/i386-gnu/libsndio.so
> ./build-tree/CMakeCache.txt:FIND_PACKAGE_MESSAGE_DETAILS_SoundIO:INTERNAL=[/usr/lib/i386-gnu/libsndio.so][/usr/include][v()]
> 
> 
> ./build-tree/CMakeFiles/OpenAL.dir/build.make:libopenal.so.1.19.1: 
> /usr/lib/x86_64-linux-gnu/libsndio.so
> ./build-tree/CMakeCache.txt:OpenAL_LIB_DEPENDS:STATIC=general;-pthread;general;common;general;/usr/lib/x86_64-linux-gnu/libsndio.so;general;rt;general;pthread;general;dl;general;atomic;general;m;
> ./build-tree/CMakeCache.txt:SOUNDIO_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libsndio.so
> ./build-tree/CMakeCache.txt:FIND_PACKAGE_MESSAGE_DETAILS_SoundIO:INTERNAL=[/usr/lib/x86_64-linux-gnu/libsndio.so][/usr/include][v()]
> 
> cmake maintainers, do you have any idea why
> /usr/lib/i386-gnu/libsndio.so does not get turned into -lsndio while
> /usr/lib/x86_64-linux-gnu/libsndio.so does?

Notably, ./build-tree/CMakeFiles/CMakeOutput.log says

implicit dirs: 
[/usr/lib/gcc/i686-gnu/8;/usr/lib/i386-gnu;/usr/lib;/lib/i386-gnu]

implicit dirs: 
[/usr/lib/gcc/x86_64-linux-gnu/8;/usr/lib/x86_64-linux-gnu;/usr/lib;/lib/x86_64-linux-gnu;/lib]

(I don't know what implicit dirs means exactly, but it seems to be
alright here).

Samuel

Re: Bug#912475: qtmultimedia-opensource-src: FTBFS on hurd: no qtaudioengine

[Samuel Thibault]

reassign -1 cmake

Pino Toscano, le mer. 31 oct. 2018 23:44:36 +0100, a ecrit:
> The issue comes from the fact that libopenal seems to not have all the
> proper dependencies, and thus the linking test fails with all the sio_*
> symbols (provided by libsndio) undefined.

Oh, indeed.

> I tried taking a quick look, and I did not find yet why apparently
> there is a behaviour change between Linux and Hurd. I did not have a
> lot of time to spend on it, though.

I see that there is at least:

€ objdump -x debian/libopenal1/usr/lib/i386-gnu/libopenal.so.1.19.1 | grep NEED
  NEEDED   /usr/lib/i386-gnu/libsndio.so
  ...

€ objdump -x ./tmp/usr/lib/x86_64-linux-gnu/libopenal.so.1.19.1 | grep NEED
  NEEDED   libsndio.so.7.0
  ...

The link line contains /usr/lib/i386-gnu/libsndio.so in one case, and
-lsndio in the other case. I don't know why cmake makes a difference. In
both cases we have absolute paths in

./build-tree/CMakeFiles/OpenAL.dir/build.make:libopenal.so.1.19.1: 
/usr/lib/i386-gnu/libsndio.so
./build-tree/CMakeCache.txt:OpenAL_LIB_DEPENDS:STATIC=general;-pthread;general;common;general;/usr/lib/i386-gnu/libsndio.so;general;rt;general;pthread;general;dl;general;atomic;general;m;
./build-tree/CMakeCache.txt:SOUNDIO_LIBRARY:FILEPATH=/usr/lib/i386-gnu/libsndio.so
./build-tree/CMakeCache.txt:FIND_PACKAGE_MESSAGE_DETAILS_SoundIO:INTERNAL=[/usr/lib/i386-gnu/libsndio.so][/usr/include][v()]


./build-tree/CMakeFiles/OpenAL.dir/build.make:libopenal.so.1.19.1: 
/usr/lib/x86_64-linux-gnu/libsndio.so
./build-tree/CMakeCache.txt:OpenAL_LIB_DEPENDS:STATIC=general;-pthread;general;common;general;/usr/lib/x86_64-linux-gnu/libsndio.so;general;rt;general;pthread;general;dl;general;atomic;general;m;
./build-tree/CMakeCache.txt:SOUNDIO_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libsndio.so
./build-tree/CMakeCache.txt:FIND_PACKAGE_MESSAGE_DETAILS_SoundIO:INTERNAL=[/usr/lib/x86_64-linux-gnu/libsndio.so][/usr/include][v()]

cmake maintainers, do you have any idea why
/usr/lib/i386-gnu/libsndio.so does not get turned into -lsndio while
/usr/lib/x86_64-linux-gnu/libsndio.so does?

Samuel

Bug#912475: qtmultimedia-opensource-src: FTBFS on hurd: no qtaudioengine

[Samuel Thibault]

Source: qtmultimedia-opensource-src
Version: 5.11.2-2
Severity: important
Tags: patch

Hello,

qtmultimedia-opensource-src currently FTBFS on hurd because
qtaudioengine doesn't get built.

https://buildd.debian.org/status/fetch.php?pkg=qtmultimedia-opensource-src=hurd-i386=5.11.2-2=1540905856=0

Could you apply the attached patch to just disable the resulting
package?

(kio indirectly depends on it, and thus a big lot of kde packages too).

Thanks,
Samuel

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

Kernel: Linux 4.19.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
"And the next time you consider complaining that running Lucid Emacs
19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to
get the background colors right, you'll know who to thank."
(By Matt Welsh)
--- debian/control.original 2018-10-31 22:21:09.0 +
+++ debian/control  2018-10-31 22:21:14.0 +
@@ -93,7 +93,7 @@
  This package contains the Multimedia QML module for QtDeclarative.
 
 Package: qml-module-qtaudioengine
-Architecture: any
+Architecture: linux-any kfreebsd-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, ${shlibs:Depends}

Bug#911618: qttools-opensource-src: FTBFS on !linux

[Samuel Thibault]

Source: qttools-opensource-src
Version: 5.11.2-3
Severity: important
Tags: patch

Hello,

The qttools-opensource-src package can not build on non-Linux archs due
to the libvulkan-dev dependency, could you drop it as the attached patch
does?

Thanks
Samuel

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'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

Kernel: Linux 4.18.5 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
/* Amuse the user in a SPARC fashion */
if (err) printk(
KERN_CRIT "  ___ \n"
KERN_CRIT " < Your System ate a SPARC! Gah! >\n"
KERN_CRIT "  --- \n"
KERN_CRIT " \\   ^__^\n"
KERN_CRIT "  \\  (xx)\\___\n"
KERN_CRIT " (__)\\   )\\/\\\n"
KERN_CRIT "  U  ||w |\n"
KERN_CRIT " || ||\n");
(From linux/arch/parisc/kernel/traps.c:die_if_kernel())
--- debian/control.orig 2018-10-21 09:02:32.0 +
+++ debian/control  2018-10-21 09:02:35.0 +
@@ -14,7 +14,7 @@
libqt5opengl5-dev (>= 5.11.2+dfsg~),
libqt5sql5-sqlite (>= 5.11.2+dfsg~),
libqt5webkit5-dev (>= 5.212.0~alpha2-16~) [!m68k !sparc64],
-   libvulkan-dev,
+   libvulkan-dev [linux-any],
llvm-dev (>= 1:3.9~),
pkg-kde-tools,
qtbase5-private-dev (>= 5.11.2+dfsg~),

Bug#911422: qtbase-opensource-src: FTBFS on !linux due to vulkan dependency

[Samuel Thibault]

Source: qtbase-opensource-src
Version: 5.11.2+dfsg-3
Severity: important
Tags: patch

Hello,

qtbase-opensource-src was recently made to depend on Vulkan, but this is
not available on non-Linux ports. Could you apply the attached patch to
fix this?

Thanks,
Samuel

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'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

Kernel: Linux 4.18.5 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
> C'est vrai. FreeBSD pourrait être bien s'il avait une licence
> correcte.
Oh, mon troll-ô-meter vient d'exploser...
-+- OR in Guide du linuxien pervers - "Bien regler son troll-ô-meter"
--- debian/control.orig 2018-10-19 17:50:12.0 +
+++ debian/control  2018-10-19 17:00:36.0 +
@@ -40,7 +40,7 @@
libsqlite3-dev,
libssl-dev,
libudev-dev [linux-any],
-   libvulkan-dev,
+   libvulkan-dev [linux-any],
libx11-dev,
libx11-xcb-dev,
libxcb-icccm4-dev,
--- debian/qtbase5-private-dev.install.orig 2018-10-19 22:38:32.0 
+
+++ debian/qtbase5-private-dev.install  2018-10-19 22:38:53.0 +
@@ -90,7 +90,7 @@
 usr/include/*/qt5/QtThemeSupport/QtThemeSupportDepends
 usr/include/*/qt5/QtThemeSupport/QtThemeSupportVersion
 usr/include/*/qt5/QtThemeSupport/qtthemesupportversion.h
-usr/include/*/qt5/QtVulkanSupport/5.*/*
+[linux-any] usr/include/*/qt5/QtVulkanSupport/5.*/*
 usr/include/*/qt5/QtWidgets/5.*/*
 usr/include/*/qt5/QtXml/5.*/*
 usr/lib/*/libQt5AccessibilitySupport.a
@@ -115,5 +115,5 @@
 usr/lib/*/libQt5ServiceSupport.prl
 usr/lib/*/libQt5ThemeSupport.a
 usr/lib/*/libQt5ThemeSupport.prl
-usr/lib/*/libQt5VulkanSupport.a
-usr/lib/*/libQt5VulkanSupport.prl
+[linux-any] usr/lib/*/libQt5VulkanSupport.a
+[linux-any] usr/lib/*/libQt5VulkanSupport.prl
--- debian/qtbase5-dev.install.orig 2018-10-19 23:46:18.0 +
+++ debian/qtbase5-dev.install  2018-10-19 23:46:26.0 +
@@ -1208,10 +1208,10 @@
 usr/include/*/qt5/QtTest/qttestlib-config.h
 usr/include/*/qt5/QtTest/qttestglobal.h
 usr/include/*/qt5/QtTest/qttestversion.h
-usr/include/*/qt5/QtVulkanSupport/qtvulkansupportversion.h
-usr/include/*/qt5/QtVulkanSupport/QtVulkanSupportDepends
-usr/include/*/qt5/QtVulkanSupport/QtVulkanSupport
-usr/include/*/qt5/QtVulkanSupport/QtVulkanSupportVersion
+[linux-any] usr/include/*/qt5/QtVulkanSupport/qtvulkansupportversion.h
+[linux-any] usr/include/*/qt5/QtVulkanSupport/QtVulkanSupportDepends
+[linux-any] usr/include/*/qt5/QtVulkanSupport/QtVulkanSupport
+[linux-any] usr/include/*/qt5/QtVulkanSupport/QtVulkanSupportVersion
 usr/include/*/qt5/QtWidgets/QAbstractButton
 usr/include/*/qt5/QtWidgets/QAbstractGraphicsShapeItem
 usr/include/*/qt5/QtWidgets/QAbstractItemDelegate
--- debian/libqt5gui5.symbols.orig  2018-10-20 00:25:08.0 +
+++ debian/libqt5gui5.symbols   2018-10-20 00:31:00.0 +
@@ -1396,30 +1396,30 @@
  _ZN13QTextDocumentD0Ev@Qt_5 5.0.2
  _ZN13QTextDocumentD1Ev@Qt_5 5.0.2
  _ZN13QTextDocumentD2Ev@Qt_5 5.0.2
- _ZN13QVulkanWindow10frameReadyEv@Qt_5 5.11.1
- _ZN13QVulkanWindow11exposeEventEP12QExposeEvent@Qt_5 5.11.1
- _ZN13QVulkanWindow11qt_metacallEN11QMetaObject4CallEiPPv@Qt_5 5.11.1
- _ZN13QVulkanWindow11qt_metacastEPKc@Qt_5 5.11.1
- _ZN13QVulkanWindow11resizeEventEP12QResizeEvent@Qt_5 5.11.1
- _ZN13QVulkanWindow12frameGrabbedERK6QImage@Qt_5 5.11.1
- _ZN13QVulkanWindow14createRendererEv@Qt_5 5.11.1
- _ZN13QVulkanWindow14setSampleCountEi@Qt_5 5.11.1
- _ZN13QVulkanWindow16staticMetaObjectE@Qt_5 5.11.1
- _ZN13QVulkanWindow19setDeviceExtensionsERK5QListI10QByteArrayE@Qt_5 5.11.1
- _ZN13QVulkanWindow20clipCorrectionMatrixEv@Qt_5 5.11.1
- _ZN13QVulkanWindow21supportedSampleCountsEv@Qt_5 5.11.1
- _ZN13QVulkanWindow22setPhysicalDeviceIndexEi@Qt_5 5.11.1
- _ZN13QVulkanWindow24availablePhysicalDevicesEv@Qt_5 5.11.1
- _ZN13QVulkanWindow24setPreferredColorFormatsERK7QVectorI8VkFormatE@Qt_5 5.11.1
- _ZN13QVulkanWindow25supportedDeviceExtensionsEv@Qt_5 5.11.1
- _ZN13QVulkanWindow4grabEv@Qt_5 5.11.1
- _ZN13QVulkanWindow5eventEP6QEvent@Qt_5 5.11.1
- _ZN13QVulkanWindow8setFlagsE6QFlagsINS_4FlagEE@Qt_5 5.11.1
- _ZN13QVulkanWindowC1EP7QWindow@Qt_5 5.11.1
- _ZN13QVulkanWindowC2EP7QWindow@Qt_5 5.11.1
- _ZN13QVulkanWindowD0Ev@Qt_5 5.11.1
- _ZN13QVulkanWindowD1Ev@Qt_5 5.11.1
- _ZN13QVulkanWindowD2Ev@Qt_5 5.11.1
+ (arch=linux-any)_ZN13QVulkanWindow10frameReadyEv@Qt_5 5.11.1

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Samuel Thibault]

Samuel Thibault, le jeu. 06 sept. 2018 11:44:45 +0200, a ecrit:
> Paul Gevers, le jeu. 06 sept. 2018 11:22:46 +0200, a ecrit:
> > On 06-09-18 11:19, Samuel Thibault wrote:
> > > It'd be useful for the abi-compliance-checker test to actually output
> > > error messages,
> > > 
> > > https://ci.debian.net/data/autopkgtest/testing/amd64/k/kf5-kdepim-apps-libs/944759/log.gz
> > > 
> > > it not very talkative :)
> > 
> > I agree, but I found that there are more logs in the artifacts.
> 
> Ah, right. They seem to only point at c++ headers, so it'd rather be a
> g++ issue?

All the passed artifacts I can find have libc++-dev 6.0.1-1, not
libc++-8-dev 1:8~svn340819-1.

Samuel

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Samuel Thibault]

Paul Gevers, le jeu. 06 sept. 2018 11:22:46 +0200, a ecrit:
> On 06-09-18 11:19, Samuel Thibault wrote:
> > It'd be useful for the abi-compliance-checker test to actually output
> > error messages,
> > 
> > https://ci.debian.net/data/autopkgtest/testing/amd64/k/kf5-kdepim-apps-libs/944759/log.gz
> > 
> > it not very talkative :)
> 
> I agree, but I found that there are more logs in the artifacts.

Ah, right. They seem to only point at c++ headers, so it'd rather be a
g++ issue?

Samuel

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Samuel Thibault]

Hello,

Paul Gevers, le jeu. 06 sept. 2018 10:55:30 +0200, a ecrit:
> the autopkgtest of libkf5calendarsupport, kf5-kdepim-apps-libs and
> akonadi-calendar started to fail when run in testing with either glibc
> or abi-compliance-checker from unstable.

It'd be useful for the abi-compliance-checker test to actually output
error messages,

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kf5-kdepim-apps-libs/944759/log.gz

it not very talkative :)

On Linux, the glibc 2.27-6 change only contains two additional static
functions, so at best it'd be an issue with the toolchain.

Samuel

Re: Removing Qt4 in Buster

[Samuel Thibault]

Hello,

Lisandro Damián Nicanor Pérez Meyer, on mar. 05 sept. 2017 15:29:31 -0300, 
wrote:
> Debian Accessibility Team 
>qt-at-spi

FTR, this package is only needed for Qt4, to it shall just go away along
with Qt4 :)

Samuel

Re: [Development] Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Hello,

It seems my mails don't reach the developm...@qt-project.org mailing
list. Could somebody who got them forward them to it?

Frederik Gladhorn, on mar. 05 sept. 2017 10:32:43 +0200, wrote:
> And then Allan is right, by setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON you ask 
> for it. All the stuff unconditionally. Please don't, why do you need it in 
> the 
> first place?

Because it would just not work at all in non-kde desktops in Debian 9
otherwise (and I didn't notice performance regression). AIUI, qt 5.7 was
only looking at the "accessibility enabled" checkbox in kde
configuration.

> Right now Qt is trying to emulate Gnome's way, except since we don't 
> listen to the change signal, we never dynamically enable/disable a11y.

With Debian testing (qt 5.9), I don't need to set
QT_LINUX_ACCESSIBILITY_ALWAYS_ON, and accessibility seems to get enabled
dynamically, so it seems something changed between 5.7 and 5.9.

Samuel

Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Lisandro Damián Nicanor Pérez Meyer, on dim. 03 sept. 2017 19:08:38 -0300, 
wrote:
> So you mean that something changed between 5.7 and 5.9?

It seems so.

Samuel

Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Control: clone -1 -2
Control: reassign -2 at-spi2-core
Control: retitle -2 Should not set QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 any more
Control: found -1 5.7.1+dfsg-3+b1
Control: done -1 5.9.1+dfsg-9

Samuel

Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Samuel Thibault, on dim. 03 sept. 2017 21:17:12 +0200, wrote:
> I have checked with a vanilla reinstall of Debian 9, using the Mate
> desktop, and Qt 5.7.1.
> 
> When QT_LINUX_ACCESSIBILITY_ALWAYS_ON is not set, I don't see Qt
> applications in accerciser, only the Mate applications. If I set
> QT_LINUX_ACCESSIBILITY_ALWAYS_ON, I do see them.
> 
> On my current desktop, I have Qt 5.9.1, I made quick tests, it seems
> it behaves as I expect, so perhaps we can indeed avoid setting
> QT_LINUX_ACCESSIBILITY_ALWAYS_ON now. I'll retest with a vanilla
> reinstall of debian testing, to be sure.

Yes, a vanilla reinstall behaves as expected.  So we can drop that
variable, good :)

Samuel

Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Samuel Thibault, on dim. 03 sept. 2017 20:23:30 +0200, wrote:
> Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:19:31 +0200, wrote:
> > On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> > > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> > > 
> > > That's Qt's fault for not taking care of EventListenerRegistered
> > > signals to determine whether someone is listening.
> > 
> > So it is Qt's fault that is doing what you have told it to do? You have set 
> > the environment variable to ignore the absence of listeners. That is what 
> > QT_LINUX_ACCESSIBILITY_ALWAYS_ON does.
> 
> Ah?  That's not what I had gotten in my tests.  I'll check again, then.

I have checked with a vanilla reinstall of Debian 9, using the Mate
desktop, and Qt 5.7.1.

When QT_LINUX_ACCESSIBILITY_ALWAYS_ON is not set, I don't see Qt
applications in accerciser, only the Mate applications. If I set
QT_LINUX_ACCESSIBILITY_ALWAYS_ON, I do see them.

On my current desktop, I have Qt 5.9.1, I made quick tests, it seems
it behaves as I expect, so perhaps we can indeed avoid setting
QT_LINUX_ACCESSIBILITY_ALWAYS_ON now. I'll retest with a vanilla
reinstall of debian testing, to be sure.

Samuel

Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:31:58 +0200, wrote:
> Note, the case where I saw the largest performance impact was not moving 
> the cursor, it was self-modifying web-content, it would send every text 
> change 
> in the active focus. [...]
> But it is what Chrome would send on macOS and Windows when a
> screen-reader is detected as active.

Uh. While it can be necessary to get such information. Getting every
text change is the kind of spurious event I'm referring to. It should
throttle the sends, to avoid the flurry that the screen reader won't be
able to render as speech or braille anyway, and just make sure that the
last version is sent.

Samuel

Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:19:31 +0200, wrote:
> On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> > 
> > That's Qt's fault for not taking care of EventListenerRegistered
> > signals to determine whether someone is listening.
> 
> So it is Qt's fault that is doing what you have told it to do? You have set 
> the environment variable to ignore the absence of listeners. That is what 
> QT_LINUX_ACCESSIBILITY_ALWAYS_ON does.

Ah?  That's not what I had gotten in my tests.  I'll check again, then.

The question of flurry of events is still there, and does matter for
screen readers.  Avoiding to expose the issue to users without a screen
reader is a bit hiding it under the carpet.

Samuel

Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> On Sonntag, 3. September 2017 18:15:15 CEST Samuel Thibault wrote:
> > On the long run, it really should.  Just hiding issues is not the way
> > forward :)
> > 
> > Also, note that if the performance is so bad, it means something *needs*
> > to be fixed, otherwise blind users will get the bad performance, and
> > nobody will be there to fix it, because nobody notices it except blind
> > users, who are left with little hope to fix it by themselves.
> 
> It is not a issue or a bug. The performance impact comes from sending 
> everything the mouse hovers over to the accessibility framework (for instance 
> to be spoken aloud), when there is not any accessibility tools running.

Well, if just moving mouse over windows does send a flurry of events,
that's already a bug.  There is no need to send all of that to a
screen reader, the user won't be able to grasp everything anyway, only
not-too-short hovers would be useful (the final destination of the
movement, basically).  And that's particularly a problem if that makes
the interface slow: it's already difficult to use a computer when one
has to use a screen reader.  If that makes the interface much slower,
that's even more difficult, so it is still a bug for that reason.

> You are deliberately crippling Qt to always send dbus events even when no one 
> is listening.

That's Qt's fault for not taking care of EventListenerRegistered
signals to determine whether someone is listening.

> Note the performance impact is the same in all applications regardless of 
> framework.

No. Gtk sends only basic events (application creation notification,
basically) when there is no screen reader.

> Running accessibility tools has a substantional performance cost on 
> mouse movements, but a mouse rendered or text scrolling at 60 fps is 
> completely pointless to blind people, but rather important to everybody else.

Sure, but fps is not the only consequence. Responsiveness of the
interface is also a consequence.  If the performance is really hurt,
that's probably because there are too many messages, and so many
messages can't be useful for a screen reader either.  We do have seen
screen readers overflowed with flurries of useless notifications.

Really, looking at the whole picture: there are tons of messages needed
to get all the tiny movements of the mouse, and render the 60fps. On the
other hand, the refresh rates of screen readers are *much* slower. So
the message bandwidth needed for it should be much lower. If that's not
the case, it means there is spurious information that should be dropped.

Samuel

Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Samuel Thibault]

Control: reassign -1 libqt5core5a
Control: retitle -1 Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge 
negative performance impact, qt accessibility should not always send all 
messages

Hello,

Lisandro Damián Nicanor Pérez Meyer, on sam. 02 sept. 2017 11:02:15 -0300, 
wrote:
> According to [upstream] setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a
> huge negative performace impact on Qt,

Upstream said "big", not "huge" :)

> so it should not be enabled by default.

On the long run, it really should.  Just hiding issues is not the way
forward :)

Also, note that if the performance is so bad, it means something *needs*
to be fixed, otherwise blind users will get the bad performance, and
nobody will be there to fix it, because nobody notices it except blind
users, who are left with little hope to fix it by themselves.

> Upstream suggested that maybe we should try to only set this variable if
> the appropriate hardware is found.

Sebastian Humenda, on sam. 02 sept. 2017 16:18:16 +0200, answered:
> This is not a good idea, because not all screen reader users have dedicated
> hardware. Users only using speech for navigation would be without Qt a11y.

Exactly.

> Couldn't we detect whether a screen reader (Orca) is installed, or is this a
> default on Desktop systems, these days?

It is a default, and that is on purpose.

Lisandro Damián Nicanor Pérez Meyer, on sam. 02 sept. 2017 11:28:51 -0300, 
wrote:
> On the other hand people needing a11y really need to get this on as
> simple as possible.

And that's precisely the issue.

If at-spi is not installed and enabled by default, it's a real pain to
make a system accessible with a screen reader: you first have to divine
which package should be installed, then enable accessibility in some
control panel, and log out / re login, so that at-spi gets started. That
just can not work.  While having it enabled by default, ready to be
activated, it's just a matter of pressing e.g. ctrl-alt-s to start
speech.  That's a *huge* difference for blind people.  This is discussed
in more details in my talk at DC15.

https://summit.debconf.org/debconf15/meeting/290/thanks-for-maintaining-a-desktop-environment-but-is-it-accessible/

Lisandro Damián Nicanor Pérez Meyer, on sam. 02 sept. 2017 14:34:01 -0300, 
wrote:
> Basically: Qt issuing all the necessary messages for a11y in machines
> not needing a11y makes a lot of cpu power waste, whether you notice it
> or not.

Ok, so it seems Qt does not implement the optimization that Gtk did.
Normally Qt should only send events that were requested by a screen
reader.

See the notification part of

https://www.freedesktop.org/wiki/Accessibility/Walkthrough/

It'd be useful if you could contribute text for the Qt part, btw :)

Samuel

Bug#812752: phonon: please depend on phonon-backend-gstreamer on hurd

[Samuel Thibault]

Hello,

Maximiliano Curia, on mer. 12 juil. 2017 09:43:38 +0200, wrote:
> It seems to me that libldb is needed for the vlc samba plugin, which is
> optional for vlc, also phonon4qt5-backend-vlc is only the recommended
> backend, but it should be replaceable with phonon4qt5-backend-gstreamer or
> phonon4qt5-backend-null at package resolution time if phonon4qt5-backend-vlc
> is uninstallable.

Sure, but buildds don't do that automatically.

> Anyway, I think this issue should be solved by now, but I don't have a hurd
> machine to test this, could you please recheck if this issue is still
> affecting hurd?

It is still a problem:

# apt-get build-dep akonadi
...
 builddeps:akonadi : Depends: kdesignerplugin (>= 5.16.0~) but it is not going 
to be installed
 Depends: kio-dev (>= 5.16.0~) but it is not going to be 
installed
...
# apt-get install kio-dev libkf5kio-dev kio libkf5notifications5
 libkf5notifications5 : Depends: phonon4qt5 but it is not going to be installed
# apt-get install kio-dev libkf5kio-dev kio libkf5notifications5 phonon4qt5
...
The following NEW packages will be installed:
...
  phonon-backend-gstreamer-common phonon4qt5 phonon4qt5-backend-gstreamer

so apt manages to pick up the gstreamer version. But that's not what the
buildd resolver does: it always picks the first alternative, so as to
get deterministic behavior.

For those KDE applications, I do add the dep by hand to get things
built, but that's not how it is to be done.

Samuel

Bug#799619: kio: FTBFS on hurd-i386: warning about posix_fadvise

[Samuel Thibault]

Hello,

Unless somebody complains, I plan to NMU these changes, which are
completely harmless on non-Hurd, around 8th May.

Samuel

Samuel Thibault, on Sun 24 Apr 2016 13:00:44 +0200, wrote:
> Index: kio-5.16.0/src/ioslaves/file/file.cpp
> ===
> --- kio-5.16.0.orig/src/ioslaves/file/file.cpp
> +++ kio-5.16.0/src/ioslaves/file/file.cpp
> @@ -333,7 +333,7 @@ void FileProtocol::get(const QUrl )
>  return;
>  }
>  
> -#if HAVE_FADVISE
> +#if HAVE_FADVISE && !defined(__GNU__)
>  //TODO check return code
>  posix_fadvise(f.handle(), 0, 0, POSIX_FADV_SEQUENTIAL);
>  #endif
> Index: kio-5.16.0/src/ioslaves/file/file_unix.cpp
> ===
> --- kio-5.16.0.orig/src/ioslaves/file/file_unix.cpp
> +++ kio-5.16.0/src/ioslaves/file/file_unix.cpp
> @@ -128,7 +128,7 @@ void FileProtocol::copy(const QUrl 
>  return;
>  }
>  
> -#if HAVE_FADVISE
> +#if HAVE_FADVISE && !defined(__GNU__)
>  posix_fadvise(src_file.handle(), 0, 0, POSIX_FADV_SEQUENTIAL);
>  #endif
>  
> @@ -144,7 +144,7 @@ void FileProtocol::copy(const QUrl 
>  return;
>  }
>  
> -#if HAVE_FADVISE
> +#if HAVE_FADVISE && !defined(__GNU__)
>  posix_fadvise(dest_file.handle(), 0, 0, POSIX_FADV_SEQUENTIAL);
>  #endif
>  

> --- debian/libkf5kiocore5.symbols.original2016-04-24 10:55:11.0 
> +
> +++ debian/libkf5kiocore5.symbols 2016-04-24 10:55:15.0 +
> @@ -901,12 +901,12 @@
>   _ZN3KIO8UDSEntry6insertEjRK7QString@Base 4.96.0
>   _ZN3KIO8UDSEntry6insertEjx@Base 4.96.0
>   _ZN3KIO8UDSEntry7reserveEi@Base 5.5.0+git20141229.0049+15.04
> - (arch=kfreebsd-any)_ZN3KIO8UDSEntryC1ERK4statRK7QString@Base 5.11.0
> - (arch=!kfreebsd-any)_ZN3KIO8UDSEntryC1ERK6stat64RK7QString@Base 4.100.0
> + (arch=kfreebsd-any hurd-i386)_ZN3KIO8UDSEntryC1ERK4statRK7QString@Base 
> 5.11.0
> + (arch=!kfreebsd-any !hurd-i386)_ZN3KIO8UDSEntryC1ERK6stat64RK7QString@Base 
> 4.100.0
>   _ZN3KIO8UDSEntryC1ERKS0_@Base 4.96.0
>   _ZN3KIO8UDSEntryC1Ev@Base 4.96.0
> - (arch=kfreebsd-any)_ZN3KIO8UDSEntryC2ERK4statRK7QString@Base 5.11.0
> - (arch=!kfreebsd-any)_ZN3KIO8UDSEntryC2ERK6stat64RK7QString@Base 4.100.0
> + (arch=kfreebsd-any hurd-i386)_ZN3KIO8UDSEntryC2ERK4statRK7QString@Base 
> 5.11.0
> + (arch=!kfreebsd-any !hurd-i386)_ZN3KIO8UDSEntryC2ERK6stat64RK7QString@Base 
> 4.100.0
>   _ZN3KIO8UDSEntryC2ERKS0_@Base 4.96.0
>   _ZN3KIO8UDSEntryC2Ev@Base 4.96.0
>   _ZN3KIO8UDSEntryD1Ev@Base 4.96.0

Bug#799619: kio: FTBFS on hurd-i386: warning about posix_fadvise

[Samuel Thibault]

Samuel Thibault, on Sun 24 Apr 2016 13:00:44 +0200, wrote:
> In the meanwhile, the hurd-i386 port looks in terribly bad shape due to
> all the not-rebuilt KDE packages.

(it would be good to have a kio upload before the migration to the
newer qt/kio/etc. currently in experimental, so we get to see possible
unrelated build failures of KDE packages.)

Samuel

Bug#799619: kio: FTBFS on hurd-i386: warning about posix_fadvise

[Samuel Thibault]

Hello,

Samuel Thibault, on Sun 20 Sep 2015 22:53:07 +0200, wrote:
> kio FTBFS on hurd-i386:
> 
> /«PKGBUILDDIR»/obj-i586-gnu/src/ioslaves/file/../../../../src/ioslaves/file/file.cpp:338:
>  warning: posix_fadvise64 is not implemented and will always fail

This is still a problem with 5.16.0, making basically the whole KDE world
unbuildable on hurd-i386.

> which turns into an error due to -Wl,--fatal-warnings
> 
> This function is actually probed by the CMakefiles, but only with
> check_function_exists.  It happens that the posix_fadvise function is
> provided by glibc as a stub, which always returns ENOSYS.  The fact that
> the function is actually not implemented is announced by the presence
> of #define __stub_posix_fadvise in /usr/include/i386-gnu/gnu/stubs.h
> Autoconf automatically detects that in its ac_fn_c_check_func()
> function, but it seems that cmake unfortunately didn't integrate that
> kind of detection yet into check_function_exists, and thus wrongly
> believes the support is available.  It happens that cmake has a proper
> check_function_exists_glibc function defined in
> ./Utilities/cmlibarchive/build/cmake/CheckFuncs.cmake
> but it doesn't seem to be shipped in the standard cmake. So the
> solutions I see would be:
> 
> - avoid -Wl,--fatal-warnings, since it may actually bring other kinds of
>   unexpected FTBFS along upgrades of gcc or binutils in the future.
> - either to integrate ./Utilities/cmlibarchive/build/cmake/CheckFuncs.cmake
>   into kio's cmake/ directory to be able to call the proper
>   check_function_exists_glibc detection function
> - or to patch over src/ioslaves/file/file.cpp and file_unix.cpp's
>   #if HAVE_FADVISE into #if HAVE_FADVISE && !defined(__hurd__) (but once
>   hurd-i386 gets posix_fadvise support it should get reverted).

So what do you think, how do you prefer to proceed?  The simplest would
be the third solution, as attached.

Also, the symbols file needs to be update, see attached patch.

In the meanwhile, the hurd-i386 port looks in terribly bad shape due to
all the not-rebuilt KDE packages.

Samuel
Kio's check_function_exists_glibc does not actually detect for the presence of
posix_fadvise: it ignores the stubs.h provided by glibc. See #799619 for the
details.

Index: kio-5.16.0/src/ioslaves/file/file.cpp
===
--- kio-5.16.0.orig/src/ioslaves/file/file.cpp
+++ kio-5.16.0/src/ioslaves/file/file.cpp
@@ -333,7 +333,7 @@ void FileProtocol::get(const QUrl )
 return;
 }
 
-#if HAVE_FADVISE
+#if HAVE_FADVISE && !defined(__GNU__)
 //TODO check return code
 posix_fadvise(f.handle(), 0, 0, POSIX_FADV_SEQUENTIAL);
 #endif
Index: kio-5.16.0/src/ioslaves/file/file_unix.cpp
===
--- kio-5.16.0.orig/src/ioslaves/file/file_unix.cpp
+++ kio-5.16.0/src/ioslaves/file/file_unix.cpp
@@ -128,7 +128,7 @@ void FileProtocol::copy(const QUrl 
 return;
 }
 
-#if HAVE_FADVISE
+#if HAVE_FADVISE && !defined(__GNU__)
 posix_fadvise(src_file.handle(), 0, 0, POSIX_FADV_SEQUENTIAL);
 #endif
 
@@ -144,7 +144,7 @@ void FileProtocol::copy(const QUrl 
 return;
 }
 
-#if HAVE_FADVISE
+#if HAVE_FADVISE && !defined(__GNU__)
 posix_fadvise(dest_file.handle(), 0, 0, POSIX_FADV_SEQUENTIAL);
 #endif
 
--- debian/libkf5kiocore5.symbols.original  2016-04-24 10:55:11.0 
+
+++ debian/libkf5kiocore5.symbols   2016-04-24 10:55:15.0 +
@@ -901,12 +901,12 @@
  _ZN3KIO8UDSEntry6insertEjRK7QString@Base 4.96.0
  _ZN3KIO8UDSEntry6insertEjx@Base 4.96.0
  _ZN3KIO8UDSEntry7reserveEi@Base 5.5.0+git20141229.0049+15.04
- (arch=kfreebsd-any)_ZN3KIO8UDSEntryC1ERK4statRK7QString@Base 5.11.0
- (arch=!kfreebsd-any)_ZN3KIO8UDSEntryC1ERK6stat64RK7QString@Base 4.100.0
+ (arch=kfreebsd-any hurd-i386)_ZN3KIO8UDSEntryC1ERK4statRK7QString@Base 5.11.0
+ (arch=!kfreebsd-any !hurd-i386)_ZN3KIO8UDSEntryC1ERK6stat64RK7QString@Base 
4.100.0
  _ZN3KIO8UDSEntryC1ERKS0_@Base 4.96.0
  _ZN3KIO8UDSEntryC1Ev@Base 4.96.0
- (arch=kfreebsd-any)_ZN3KIO8UDSEntryC2ERK4statRK7QString@Base 5.11.0
- (arch=!kfreebsd-any)_ZN3KIO8UDSEntryC2ERK6stat64RK7QString@Base 4.100.0
+ (arch=kfreebsd-any hurd-i386)_ZN3KIO8UDSEntryC2ERK4statRK7QString@Base 5.11.0
+ (arch=!kfreebsd-any !hurd-i386)_ZN3KIO8UDSEntryC2ERK6stat64RK7QString@Base 
4.100.0
  _ZN3KIO8UDSEntryC2ERKS0_@Base 4.96.0
  _ZN3KIO8UDSEntryC2Ev@Base 4.96.0
  _ZN3KIO8UDSEntryD1Ev@Base 4.96.0

Bug#812752: phonon: please depend on phonon-backend-gstreamer on hurd

[Samuel Thibault]

Package: phonon
Version: 4:4.8.3-2
Severity: important

Hello,

Most of KDE is currently not buildable on hurd-i386 because phonon tries
to pull phonon-backend-vlc, which is currently not installable due to
the missing libldb-dev support on hurd for now (the person working on
this is still working on this, but it seems to be taking months).

Could you change the dependencies to phonon-backend-gstreamer on hurd
to avoid the issue so we can get to build kde again?  I have attached a
proposed patch.

Thanks,
Samuel

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (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

Kernel: Linux 4.4.0 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages phonon depends on:
ii  debconf [debconf-2.0]1.5.58
ii  libphonon4   4:4.8.3-2
ii  phonon-backend-vlc [phonon-backend]  0.8.2-1

phonon recommends no packages.

Versions of packages phonon suggests:
pn  phonon-backend-gstreamer  
ii  phonon-backend-vlc0.8.2-1

-- debconf information excluded

-- 
Samuel
 Moralité : le modem et le cablerouteur font comme les filles, ils
 papotent toute la journée.
 -+- RB in NPC : Et en plus, ils ne parlent que de bits -+-
--- debian/rules.orig   2016-01-26 10:55:18.426115433 +0100
+++ debian/rules2016-01-26 10:56:11.575941501 +0100
@@ -8,8 +8,15 @@
 libpkgs_gen_strict_local_shlibs = $(libpkgs_all_packages)
 include /usr/share/pkg-kde-tools/qt-kde-team/2/library-packages.mk
 
+DEB_HOST_ARCH_OS := $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
+
+ifeq ($(DEB_HOST_ARCH_OS),hurd)
+RECOMMENDED_PHONON4_QT4_BACKEND := phonon-backend-gstreamer
+RECOMMENDED_PHONON4_QT5_BACKEND := phonon4qt5-backend-gstreamer
+else
 RECOMMENDED_PHONON4_QT4_BACKEND := phonon-backend-vlc
 RECOMMENDED_PHONON4_QT5_BACKEND := phonon4qt5-backend-vlc
+endif
 
 override_dh_auto_clean:
$(overridden_command)

Bug#808389: on an XFCE System KDE-Zugangshilfe don't close btw. runs again shortly after close

[Samuel Thibault]

Hello,

Pino Toscano, on Thu 07 Jan 2016 19:51:18 +0100, wrote:
> In data sabato 19 dicembre 2015 13:47:41, Jörg Frings-Fürst ha scritto:
> > Since the last update the "KDE-Zugangshilfe" is running every time.

Uh.

> > Shortly after closing the program is running again.
> 
> Do you have qt-at-spi installed? I guess it has something do with the
> recent change that enabled accessibility by default for Qt4
> applications. Samuel, do you have any hint?

I don't see why it accessibility help should get triggered, there is no
reason why disabled people would need that behavior.

Jörg, you can cross-check whether that's my change which
triggers this behavior by trying to comment the definitions in
/etc/X11/Xsession.d/90qt-a11y

We need to fix that anyway, disabled people really don't want that
either anyway.

Samuel

Bug#801266: libkdecore5: Please make libkdecore5 multiarch

[Samuel Thibault]

Pino Toscano, on Thu 07 Jan 2016 19:44:50 +0100, wrote:
> So I'm setting this bug as wontfix, sorry.

That should be fine, since:

> (I see the latest version of qt-at-spi does not depend on libkdecore5
> anymore, so this bug is left open as reference.)

so qt-at-spi is multiarch-installable. And what's more, libqtgui4 now
recommends it, so that if a user has a 32bit qt4 app, she'll probably
get the 32bit qt-at-spi installed automatically to make it accessible.

Samuel

Bug#798408: Bug#797816: openscad FTBFS in armhf due to conflict declaration of headers gl3.h and glew.h

[Samuel Thibault]

Hello,

I'm getting the same issue with the "vite" package now that I have
migrated it from qt4 to qt5:

https://buildd.debian.org/status/fetch.php?pkg=vite=armel=1.2%2Bsvn1430-5=1450824398

In file included from /usr/include/arm-linux-gnueabi/qt5/QtGui/qopengl.h:97:0,
 from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qgl.h:39,
 from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/QGLWidget:1,
 from 
/«BUILDDIR»/vite-1.2+svn1430/src/render/Render_opengl.hpp:56,
 from 
/«BUILDDIR»/vite-1.2+svn1430/src/render/Render_opengl.cpp:67:
/usr/include/GLES3/gl3.h:69:25: error: conflicting declaration 'typedef
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;

In file included from /usr/include/GL/gl.h:2055:0,
 from /usr/include/GL/glu.h:38,
 from 
/«BUILDDIR»/vite-1.2+svn1430/src/render/Render_opengl.cpp:52:
/usr/include/GL/glext.h:468:19: note: previous declaration as 'typedef 
ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;

vite just happens to be using both QGLWidget and GL.

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Lisandro Damián Nicanor Pérez Meyer, on Fri 11 Dec 2015 18:11:40 -0300, wrote:
> Ah, now I get it. Please go ahead.

Good, now done!

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

Lisandro Damián Nicanor Pérez Meyer, on Wed 09 Dec 2015 22:27:51 -0300, wrote:
> On Tuesday 08 December 2015 20:28:29 Samuel Thibault wrote:
> [snip] 
> > So, how is it going?  Can we proceeed?
> 
> I pushed the necessary changes to qt4 on Nov 17th, qt4-x11 (4:4.8.7+dfsg-4). 
> If I'm missing something please do not heasitate in replying :)

The additional dependency is useful to make sure that the bridge is
there, but it is not activated by default, i.e. one can not just start
the screen reader to get access to already-running applications.  We
need to set QT_ACCESSIBILITY to 1 for that, which will enable some parts
of qt-at-spi so that the screen reader can access already-running
applications.  I planned to do that in the at-spi2-core package once Qt
people tell me it's OK to do it.

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

Lisandro Damián Nicanor Pérez Meyer, on Tue 01 Sep 2015 18:50:43 -0300, wrote:
> On Tuesday 01 September 2015 01:39:51 Samuel Thibault wrote:
> > As discussed at DebConf [1,2,3], we would like to make the accessibility
> > stack enabled by default, so that all a user who needs it has to do is
> > just to start orca

> > Considering that we
> > are just at the beginning of the Stretch development, perhaps we can
> > try to enable accessibility by default in both Qt4 and Qt5, see how
> > well this goes, and at worse not enable it by default for Qt4 if the
> > possibly-revealed bugs become really not solvable?
> 
> I like the idea, but ~1 month after the gcc5 transition ends. We are also 
> pushing KDE+Qt5 to the archive and have quite some problems with the 
> transition, so it would be better to let the transition "dust" settle down 
> before adding yet more sources of bugs. After that we should definitely give 
> it a try IMO.

So, how is it going?  Can we proceeed?

Samuel

Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

[Samuel Thibault]

Hello,

Ritesh Raj Sarraf, on Mon 23 Nov 2015 17:11:46 +0530, wrote:
> On Sun, 2015-11-22 at 19:49 +0100, Samuel Thibault wrote:
> > Ritesh Raj Sarraf, on Sun 22 Nov 2015 21:57:12 +0530, wrote:
> > > I'm also curious to know if KDE5/Qt5 apps really support the at-spi
> > > bridge.
> > 
> > Qt5 actually embeds its own at-spi bridge.
> 
> That was my impression too, but it does not seem to be working, at
> least on Debian.

It is working, at least basically. the
ssh://git.debian.org/git/pkg-a11y/check-a11y tool shows that both qt4
and qt5 applications are accessible at the same time.

> Perhaps the Debian KDE Team (CCed) can confirm if it
> is supposed to work with KDE5/Qt5, or not.

It is supposed to work (and much better than Qt4)

Samuel

Bug#801266: libkdecore5: Please make libkdecore5 multiarch

[Samuel Thibault]

Package: libkdecore5
Version: 4:4.14.12-2
Severity: normal

Hello,

The latest version of qt-at-spi now depends on libkdecore5. People often
need to install the i386 version of qt-at-spi on an amd64 machine so
as to be able to run e.g. proprietary 32bit applications using the QT
toolkit. qt-at-spi thus needs to be multiarch, but currently that does
not work because libkdecore5 (now a dependency) is not multiarch. AIUI,
the libraries in libkdecore5 should not be a problem to move to the
multiarch path. lnusertemp may be a bit more difficult to move, but that
should be feasible.

Samuel

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.2 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libkdecore5 depends on:
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.19-22
ii  libdlrestrictions1  0.15.19
ii  libfam0 2.7.0-17.1+b1
ii  libgcc1 1:5.2.1-17
ii  liblzma55.1.1alpha+20120614-2.1
ii  libqt4-dbus 4:4.8.7+dfsg-3
ii  libqt4-network  4:4.8.7+dfsg-3
ii  libqtcore4  4:4.8.7+dfsg-3
ii  libstdc++6  5.2.1-17
ii  zlib1g  1:1.2.8.dfsg-2+b1

libkdecore5 recommends no packages.

libkdecore5 suggests no packages.

-- no debconf information

-- 
Samuel
  mr  -  remove the home of correct users who accidentally enter mr
instead of rm

Bug#799619: kio: FTBFS on hurd-i386: warning about posix_fadvise

[Samuel Thibault]

Source: kio
Version: 5.14.0-1
Severity: important
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

kio FTBFS on hurd-i386:

/«PKGBUILDDIR»/obj-i586-gnu/src/ioslaves/file/../../../../src/ioslaves/file/file.cpp:338:
 warning: posix_fadvise64 is not implemented and will always fail

which turns into an error due to -Wl,--fatal-warnings

This function is actually probed by the CMakefiles, but only with
check_function_exists.  It happens that the posix_fadvise function is
provided by glibc as a stub, which always returns ENOSYS.  The fact that
the function is actually not implemented is announced by the presence
of #define __stub_posix_fadvise in /usr/include/i386-gnu/gnu/stubs.h
Autoconf automatically detects that in its ac_fn_c_check_func()
function, but it seems that cmake unfortunately didn't integrate that
kind of detection yet into check_function_exists, and thus wrongly
believes the support is available.  It happens that cmake has a proper
check_function_exists_glibc function defined in
./Utilities/cmlibarchive/build/cmake/CheckFuncs.cmake
but it doesn't seem to be shipped in the standard cmake. So the
solutions I see would be:

- avoid -Wl,--fatal-warnings (which may actually bring other kinds of
  unexpected FTBFS along upgrades of gcc or binutils in the future).
- either to integrate ./Utilities/cmlibarchive/build/cmake/CheckFuncs.cmake
  into kio's cmake/ directory to be able to call the proper
  check_function_exists_glibc detection function
- or to patch over src/ioslaves/file/file.cpp and file_unix.cpp's
  #if HAVE_FADVISE into #if HAVE_FADVISE && !defined(__hurd__) (but once
  hurd-i386 gets posix_fadvise support it should get reverted).

There are also symbols differences, see the attached output from
dpkg-gensymbols.

Samuel

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
 la vraie vie, c'est quand le prompt passe de $ à #
--- debian/libkf5kiocore5.symbols (libkf5kiocore5_5.14.0-1_hurd-i386)
+++ dpkg-gensymbols0UZGn9   2015-09-20 20:32:35.0 +
@@ -177,10 +177,10 @@
  _ZN14KCoreDirLister7Private14CachedItemsJob6doKillEv@Base 4.96.0
  _ZN14KCoreDirLister7Private14CachedItemsJobC1EPS_RK4QUrlb@Base 4.96.0
  _ZN14KCoreDirLister7Private14CachedItemsJobC2EPS_RK4QUrlb@Base 4.96.0
- (optional=gccinternal)_ZN14KCoreDirLister7Private14CachedItemsJobD0Ev@Base 
4.96.0
- (optional=gccinternal)_ZN14KCoreDirLister7Private14CachedItemsJobD1Ev@Base 
4.96.0
- (optional=gccinternal)_ZN14KCoreDirLister7Private14CachedItemsJobD2Ev@Base 
4.96.0
- (optional=private)_ZN14KCoreDirLister7Private14FilterSettingsaSERKS1_@Base 
5.10.0
+#MISSING: 5.14.0-1# 
(optional=gccinternal)_ZN14KCoreDirLister7Private14CachedItemsJobD0Ev@Base 
4.96.0
+#MISSING: 5.14.0-1# 
(optional=gccinternal)_ZN14KCoreDirLister7Private14CachedItemsJobD1Ev@Base 
4.96.0
+#MISSING: 5.14.0-1# 
(optional=gccinternal)_ZN14KCoreDirLister7Private14CachedItemsJobD2Ev@Base 
4.96.0
+#MISSING: 5.14.0-1# 
(optional=private)_ZN14KCoreDirLister7Private14FilterSettingsaSERKS1_@Base 
5.10.0
  _ZN14KCoreDirLister7Private14_k_slotPercentEP4KJobm@Base 4.96.0
  _ZN14KCoreDirLister7Private14addRefreshItemERK4QUrlRK9KFileItemS6_@Base 4.96.0
  _ZN14KCoreDirLister7Private16_k_slotTotalSizeEP4KJoby@Base 4.96.0
@@ -774,9 +774,9 @@
  _ZN3KIO6DavJob8slotDataERK10QByteArray@Base 4.96.0
  _ZN3KIO6DavJobC1ERNS_13DavJobPrivateEiRK7QString@Base 4.96.0
  _ZN3KIO6DavJobC2ERNS_13DavJobPrivateEiRK7QString@Base 4.96.0
- (optional=gccinternal)_ZN3KIO6DavJobD0Ev@Base 4.96.0
- (optional=gccinternal)_ZN3KIO6DavJobD1Ev@Base 4.96.0
- (optional=gccinternal)_ZN3KIO6DavJobD2Ev@Base 4.96.0
+#MISSING: 5.14.0-1# (optional=gccinternal)_ZN3KIO6DavJobD0Ev@Base 4.96.0
+#MISSING: 5.14.0-1# (optional=gccinternal)_ZN3KIO6DavJobD1Ev@Base 4.96.0
+#MISSING: 5.14.0-1# (optional=gccinternal)_ZN3KIO6DavJobD2Ev@Base 4.96.0
  _ZN3KIO6copyAsERK4QUrlS2_6QFlagsINS_7JobFlagEE@Base 4.96.0
  _ZN3KIO6linkAsERK4QUrlS2_6QFlagsINS_7JobFlagEE@Base 4.96.0
  _ZN3KIO6mkpathERK4QUrlS2_6QFlagsINS_7JobFlagEE@Base 5.3.0+git20141016.0314
@@ -907,12 +907,12 @@
  _ZN3KIO8UDSEntry6insertEjRK7QString@Base 4.96.0
  _ZN3KIO8UDSEntry6insertEjx@Base 4.96.0
  _ZN3KIO8UDSEntry7reserveEi@Base 5.5.0+git20141229.0049+15.04
- (arch=kfreebsd-any)_ZN3KIO8UDSEntryC1ERK4statRK7QString@Base 5.11.0
- (arch=!kfreebsd-any)_ZN3KIO8UDSEntryC1ERK6stat64RK7QString@Base 4.100.0
+ _ZN3KIO8UDSEntryC1ERK4statRK7QString@Base 5.11.0
+#MISSING: 5.14.0-1# 
(arch=!kfreebsd-any)_ZN3KIO8UDSEntryC1ERK6stat64RK7QString@Base 4.100.0
  _ZN3KIO8UDSEntryC1ERKS0_@Base 4.96.0
  

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

BTW, we'd like to enable speech synthesis by default when speech was
used during installation. AIUI, it is a matter of running this

qdbus org.kde.kaccessibleapp /Adaptor setSpeechEnabled true

but during installation we don't have an X session, and dbus tells me

Error: org.freedesktop.DBus.Error.NoReply
Message did not receive a reply (timeout by message bus)

In the gconf/gsettings case we could go around this kind of issue by
rather leaving a schema file in an appropriate place. Is there this kind
of possibility with kdbus?

Samuel

Re: Enabling accessibility stack by default in Qt4/Qt5

[Samuel Thibault]

Hello,

Lisandro Damián Nicanor Pérez Meyer, le Tue 01 Sep 2015 18:50:43 -0300, a écrit 
:
> On Tuesday 01 September 2015 01:39:51 Samuel Thibault wrote:
> > For Qt4, this is implemented in the qt-at-spi package, which has been
> > developped mostly between 2009 and 2013.  There doesn't seem to be much
> > activity there since early 2013.
> 
> Kind of. See the last part of the first message in:
> 
> <https://bugreports.qt.io/browse/QTBUG-47653?focusedCommentId=288544=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-288544>

I remember this well ;)

> And the following comments. I'll try to get at it as soon as possible, but 
> not 
> before the gcc5 transition ends.

Sure.

> Now we should also consider Wayland and even pure console. Qt5 has been 
> improving in this side (yes, it can draw a GUI without X and without the need 
> to recompile anything). I don't know if a11y is present in those cases, but 
> if 
> it is it would also be good to check them.

AT-SPI is actually independent from the actual rendering, so it should
be already working.

Samuel

Re: Bug#792208: qt-at-spi: does not show up in KDE/Qt apps

[Samuel Thibault]

Control: clone -1 -2
Control: reassign -2 qtbase-opensource-src

Hello,

The issue reported below and the corresponding patch also concern the
copy of qt-at-spi embedded in qtbase-opensource-src, could you please
apply the proposed patch there too?

Thanks,
Samuel

Ritesh Raj Sarraf, le Sun 12 Jul 2015 23:12:40 +0530, a écrit :
 Package: qt-at-spi
 Version: 0.3.1-5
 Severity: normal
 Tags: patch
 
 While trying to figure out why the Caribou On-Screen keyboard does not
 show up for KDE/Qt apps, I stumbled upon this patch from Fedora/Red Hat.
 
 If applied on top of the current qt-at-spi package in Debian, it shows
 the Caribou on-screen keyboard, for both KDE and Qt apps.
 
 -- System Information:
 Debian Release: stretch/sid
   APT prefers testing
   APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 4.1.2+ (SMP w/4 CPU cores)
 Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)
 
 Versions of packages qt-at-spi depends on:
 ii  libatspi2.0-0  2.16.0-1
 ii  libc6  2.19-18
 ii  libdbus-1-31.8.18-1
 ii  libgcc11:5.1.1-12
 ii  libglib2.0-0   2.44.1-1.1
 ii  libqt4-dbus4:4.8.7+dfsg-1
 ii  libqtcore4 4:4.8.7+dfsg-1
 ii  libqtgui4  4:4.8.7+dfsg-1
 ii  libstdc++6 5.1.1-12
 
 qt-at-spi recommends no packages.
 
 qt-at-spi suggests no packages.
 
 -- no debconf information
Picked up from: https://bugzilla.redhat.com/attachment.cgi?id=865746

This fixes issues with KDE/Qt apps, i.e. the Caribou keyboard now pops up in 
applications from those toolkits
--- a/src/atspiadaptor.cpp
+++ b/src/atspiadaptor.cpp
@@ -1831,7 +1831,13 @@
 } else if (function == GetCharacterExtents) {
 int offset = message.arguments().at(0).toInt();
 int coordType = message.arguments().at(1).toUInt();
-connection.send(message.createReply(getCharacterExtents(interface, 
offset, coordType)));
+// connection.send(message.createReply(getCharacterExtents(interface, 
offset, coordType)));
+   
+// There is probably a better way to create the list from the rect.
+QRect rect = getCharacterExtents(interface, offset, coordType);
+QListQVariant variantList = QListQVariant();
+variantList  rect.x()  rect.y()  rect.width()  rect.height();
+connection.send(message.createReply(variantList));
 } else if (function == GetDefaultAttributeSet || function == 
GetDefaultAttributes) {
 // GetDefaultAttributes is deprecated in favour of 
GetDefaultAttributeSet.
 // Empty set seems reasonable. There is no default attribute set.

Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr_GError(_GError*)'

[Samuel Thibault]

Lisandro Damián Nicanor Pérez Meyer, le Sun 07 Sep 2014 15:32:38 -0300, a écrit 
:
 This is clearly a bug that only happens on !linux and it reduces to:
 
 /«PKGBUILDDIR»/WebKitBuild/Release/lib/libQtWebKit.so: undefined reference to 
 `void WTF::freeOwnedGPtr_GError(_GError*)'
 
 which happens to be declared in:
 
 Source/autotools/symbols.filter:11:_ZN3WTF13freeOwnedGPtrI7_GErrorEEvPT_;

But this is only a declaration, is the definition in
./Source/WTF/wtf/gobject/GOwnPtr.cpp really built?

Also, you need to make sure that the mangled c++ name (as see with an nm
on GOwnPtr.o) is exactly the same, perhaps the type is a bit different
on !linux.

Samuel


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140907185305.gi20...@type.youpi.perso.aquilenet.fr

Bug#760727: qtwebkit: FTBFS on kfreebsd-*: libQtWebKit.so: undefined reference to `void WTF::freeOwnedGPtr_GError(_GError*)'

[Samuel Thibault]

Steven Chamberlain, le Sun 07 Sep 2014 22:22:21 +0100, a écrit :
  which happens to be declared in:
  Source/autotools/symbols.filter:11:_ZN3WTF13freeOwnedGPtrI7_GErrorEEvPT_;
 
 I wonder if there's some significance that it was templated for
 _GError whereas I think that should be a typedef to GError (without
 underscore)?

An underscore in the type makes a difference, yes.

Samuel


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140907215909.gs20...@type.youpi.perso.aquilenet.fr

Bug#760519: qtwebkit: Uses unbound parallelism on unknown platforms

[Samuel Thibault]

Source: qtwebkit
Version: 2.3.2.dfsg-2
Severity: important
User: debian-h...@lists.debian.org
Usertags: hurd
Tags: patch

Hello,

qtwebkit currently puts hurd buildds on their knees because its
build systems uses make -j, i.e. without specifying the requested
parallelism level, which means unbound parallelism, which when building
c++ code basically means filling dozens of gigabytes of memory.

This apparently comes from ./Tools/Scripts/webkitdirs.pm which for
unknown platforms makes numberOfCPUs() return an empty string, which
thus ends up with make -j.

The attached patch makes qtwebkit default to 1 instead of defaulting to
unbound parallelism.

Perhaps upstream will also prefer to try to use the portable way,
sysconf(_SC_NPROCESSORS_ONLN) (I don't know the perl equivalent).

Samuel

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel
AUTHOR
 FvwmM4 is the result of a random  bit  mutation  on  a  hard
 disk,  presumably  a  result  of  a  cosmic-ray or some such
 thing.
(extrait de la page de man de FvwmM4)
--- ./Tools/Scripts/webkitdirs.pm.original  2014-09-05 00:09:09.0 
+0200
+++ ./Tools/Scripts/webkitdirs.pm   2014-09-05 00:10:34.0 +0200
@@ -362,6 +362,10 @@
 } elsif (isDarwin() || isFreeBSD()) {
 chomp($numberOfCPUs = `sysctl -n hw.ncpu`);
 }
+if (!defined($numberOfCPUs) or $numberOfCPUs eq )
+{
+  $numberOfCPUs = 1;
+}
 }
 
 sub jscPath($)

Bug#676957: libqt4-dev: including qtconcurrentfilter.h generates a gcc warning

[Samuel Thibault]

Hello,

Control: tags 701343 + pending

Євгеній Мещеряков wrote:
 During compilation of one of my programs the following warning is
 generated:
...
 /usr/include/qt4/QtCore/qtconcurrentfilter.h:108:47: warning: typedef 
 'Iterator' locally defined but not used [-Wunused-local-typedefs]
  typedef typename Sequence::const_iterator Iterator;

This affects the qt-at-spi build, which uses -Werror (which I'll
disable).

Samuel


--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130305000902.gf6...@type.youpi.perso.aquilenet.fr

Bug#669878: Could not perform immediate configuration on 'phonon-backend-vlc'

[Samuel Thibault]

Petter Reinholdtsen, le Wed 12 Dec 2012 21:07:20 +0100, a écrit :
 I guess changes to one of these packages caused the upgrade to break.
 After checking the package changelogs, I suspect the changes in
 python-pyatspi2 version 2.5.3+dfsg-3 is the cause.  See changelog at
 URL: http://packages.qa.debian.org/p/pyatspi/news/20121118T004749Z.html :
 
* Fix typo in Breaks/Replaces relation. Closes: Bug#693490.
 
 This package is the only one with changes to package meta information
 of the ones listed above.  Did not quite understand why after reading
 URL: http://bugs.debian.org/693490 .  Anyone got a clue to spare?

See the previous upload. As the changelog says, the upload you mention
is just a typo-fixing upload, there's no bug there. The previous upload
was meant to fix #691160 by doing some renaming. I guess _that_ might
have introduced a dependency loop, but I fail to see how that could go
through phonon-backend-vlc. What is a way to determine the actual loop?

Samuel


--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20121213001124.gs7...@type.youpi.perso.aquilenet.fr

Bug#689265: qt4-x11: FTBFS due to glib _GMutex type discrepancy

[Samuel Thibault]

Source: qt4-x11
Version: 4:4.8.2+dfsg-2
Severity: important
Tags: patch

Hello,

I've tried to rebuild qt4-x11, but got an error about _GMutex: it has a
different type in glib:

union _GMutex
{
  /* private */
  gpointer p; 
  guint i[2];
};

and in qt4-x11's GTypedefs.h:

typedef struct _GMutex GMutex;

so that I had to apply the attached patch to fix the build.

Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel
 C'est vrai. FreeBSD pourrait être bien s'il avait une licence
 correcte.
Oh, mon troll-ô-meter vient d'exploser...
-+- OR in Guide du linuxien pervers - Bien regler son troll-ô-meter
--- src/3rdparty/webkit/Source/JavaScriptCore/wtf/gobject/GTypedefs.h   
2012-10-01 01:08:44.613545773 +0200
+++ src/3rdparty/webkit/Source/JavaScriptCore/wtf/gobject/GTypedefs.h   
2012-10-01 01:08:01.178469875 +0200
@@ -52,7 +52,7 @@
 typedef struct _GHashTable GHashTable;
 typedef struct _GInputStream GInputStream;
 typedef struct _GList GList;
-typedef struct _GMutex GMutex;
+typedef union _GMutex GMutex;
 typedef struct _GPatternSpec GPatternSpec;
 typedef struct _GPollableOutputStream GPollableOutputStream;
 typedef struct _GSocketClient GSocketClient;

Bug#673429: qtcreator: FTBFS in sid: sleep' was not declared

[Samuel Thibault]

Package: qtcreator
Version: 2.2.1-2
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.7

Hello,

qtcreator currently FTBFS in sid, most probably due to the switch to
gcc-4.7:

outputgenerator.cpp:110:21: error: 'sleep' was not declared in this scope

Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages qtcreator depends on:
ii  libc6  2.13-32
ii  libgcc11:4.7.0-7
ii  libqt4-help4:4.8.1-1
ii  libqt4-network 4:4.8.1-1
ii  libqt4-sql-sqlite  4:4.8.1-1
ii  libqtcore4 4:4.8.1-1
ii  libqtgui4  4:4.8.1-1
ii  libstdc++6 4.7.0-7

Versions of packages qtcreator recommends:
ii  aterm [x-terminal-emulator]   1.0.1-8
ii  eterm [x-terminal-emulator]   0.9.5-3
ii  gdb   7.4.1-1
ii  gnome-terminal [x-terminal-emulator]  3.4.1.1-1
ii  konsole [x-terminal-emulator] 4:4.7.4-2
ii  kterm [x-terminal-emulator]   6.2.0-46
ii  make  3.81-8.2
ii  mlterm [x-terminal-emulator]  3.0.11-1
ii  pterm [x-terminal-emulator]   0.62-6
ii  qt4-demos 4:4.8.1-1
ii  qt4-dev-tools 4:4.8.1-1
ii  qt4-doc   none
ii  qtcreator-doc 1.3.1-3
ii  rxvt [x-terminal-emulator]1:2.6.4-14
ii  rxvt-ml [x-terminal-emulator] 1:2.6.4-14
ii  rxvt-unicode [x-terminal-emulator]9.15-1
ii  wterm [x-terminal-emulator]   6.2.9-8.1
ii  xterm [x-terminal-emulator]   278-1

Versions of packages qtcreator suggests:
ii  cmake   2.8.8-3
ii  git [git-core]  1:1.7.10-1
ii  git-core1:1.7.10-1
ii  subversion  1.6.17dfsg-3

-- no debconf information

-- 
Samuel Thibault samuel.thiba...@fnac.net
c xlnt comme sujet de stage je peux essayer de donner une description 
formelle de automake
 -+- #ens-mim -+-



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120518165042.ga3...@type.famille.thibault.fr

Bug#672624: kalgebra: FTBFS in sid: No rule to make target `/usr/lib/libphonon.so'

[Samuel Thibault]

Package: kalgebra
Version: 4:4.7.4-2
Severity: serious
Justification: FTBFS

Hello,

kalgebra currently FTBFS in sid:

make[4]: *** No rule to make target `/usr/lib/libphonon.so', needed by 
`src/kalgebra'.  Stop.

This is most probably due to kde moving to multi-arch.

Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kalgebra depends on:
ii  kalgebra-common   4:4.7.4-2
ii  kde-runtime   4:4.7.4-2
ii  libanalitza4  4:4.7.4-2
ii  libanalitzagui4   4:4.7.4-2
ii  libc6 2.13-32
ii  libgl1-mesa-glx [libgl1]  7.11.2-1
ii  libglu1-mesa [libglu1]7.11.2-1
ii  libkdecore5   4:4.7.4-4
ii  libkdeui5 4:4.7.4-4
ii  libkhtml5 4:4.7.4-4
ii  libkio5   4:4.7.4-4
ii  libkparts44:4.7.4-4
ii  libqt4-opengl 4:4.8.1-1
ii  libqt4-xml4:4.8.1-1
ii  libqtcore44:4.8.1-1
ii  libqtgui4 4:4.8.1-1
ii  libstdc++64.7.0-7

kalgebra recommends no packages.

kalgebra suggests no packages.

-- no debconf information

-- 
Samuel Thibault samuel.thiba...@fnac.net
 Les roots ne sont plus ce qu'ils étaient...Maintenant il sont dioxinés,
 c'est de la m... ! Avant on les élevaient avec du bon unix mais ça été
 remplacé par des farines industrielles nouvelles technologies (NT).
 -+- JdK in NPC : Exigez un root élevé sous la mère ! -+-



--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120512134238.GA3589@type

Bug#672674: kdegames: FTBFS in sid: usleep' was not declared in this scope

[Samuel Thibault]

Package: kdegames
Version: 4:4.7.4-2
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.7

Hello,

kdegames currently FTBFS on sid: 

../../kblocks/KBlocksPlayNetwork.cpp:102:22: error: 'usleep' was not declared 
in this scope

Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kdegames depends on:
ii  bomber4:4.7.4-2
ii  bovo  4:4.7.4-2
ii  granatier 4:4.7.4-2
ii  kapman4:4.7.4-2
ii  katomic   4:4.7.4-2
ii  kbattleship   4:4.7.4-2
ii  kblackbox 4:4.7.4-2
ii  kblocks   4:4.7.4-2
ii  kbounce   4:4.7.4-2
ii  kbreakout 4:4.7.4-2
ii  kdiamond  4:4.7.4-2
ii  kfourinline   4:4.7.4-2
ii  kgoldrunner   4:4.7.4-2
ii  kigo  4:4.7.4-2
ii  killbots  4:4.7.4-2
ii  kiriki4:4.7.4-2
ii  kjumpingcube  4:4.7.4-2
ii  klickety  4:4.7.4-2
ii  klines4:4.7.4-2
ii  kmahjongg 4:4.7.4-2
ii  kmines4:4.7.4-2
ii  knetwalk  4:4.7.4-2
ii  kolf  4:4.7.4-2
ii  kollision 4:4.7.4-2
ii  konquest  4:4.7.4-2
ii  kpat  4:4.7.4-2
ii  kreversi  4:4.7.4-2
ii  kshisen   4:4.7.4-2
ii  ksirk 4:4.7.4-2
ii  kspaceduel4:4.7.4-2
ii  ksquares  4:4.7.4-2
ii  ksudoku   4:4.7.4-2
ii  ktron 4:4.7.4-2
ii  ktuberling4:4.7.4-2
ii  kubrick   4:4.7.4-2
ii  lskat 4:4.7.4-2
ii  palapeli  4:4.7.4-2

Versions of packages kdegames recommends:
ii  kajongg  4:4.7.4-2

kdegames suggests no packages.

-- no debconf information

-- 
Samuel Thibault samuel.thiba...@fnac.net
...very few phenomena can pull someone out of Deep Hack Mode, with two
noted exceptions: being struck by lightning, or worse, your *computer*
being struck by lightning.
(By Matt Welsh)



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120512185022.GA21735@type

Dropping HAL? [Was: Bits from the Release Team - Kicking off Wheezy]

[Samuel Thibault]

Cc-ing debian-bsd, else they may simply not be aware of the thread...

Michael Biebl, le Thu 31 Mar 2011 14:30:06 +0200, a écrit :
 Am 31.03.2011 07:26, schrieb Reinhard Tartler:
  On Wed, Mar 30, 2011 at 19:51:17 (CEST), Michael Biebl wrote:
  
  HAL removal is already in progress, see [1]. Actually I've been working on 
  that
  for some time already. I wouldn't object obviously making that a release 
  goal.
  
  How well does kFreeBSD cope with HAL gone missing? AFAIUI udev isn't
  available there. 
 
 I ran apt-cache rdepends on an up-to-date kfreebsd sid VM.
 Attached are the rdeps for libhal1, libhal-storage1 and hal.
 
 As you can see, xserver-xorg still uses hal on kfreebsd, but iirc KiBi did 
 some
 work in that regard.

AFAIK, it was agreed that hal is needed for now. FreeBSD's devd should
be a long-term replacement.

 Then there is GNOME/gvfs/gnome-mount using hal on kfreebsd: I don't know if 
 hal
 support can be disabled in gvfs for kfreebsd and what consequences that would
 have. Most likely stuff like automounting wouldn't work anymore.
 
 Xfce 4.8 (for the most part) doesn't rely on hal anymore, at least on Linux.
 Yves-Alexis, what is the fallback on kfreebsd? Does Xfce 4.8 on kfreebsd still
 require hal or will it just have reduced functionality?
 
 KDE 4.6 respectively Solid in KDE SC 4.6 will use the newer interface like
 upower on Linux.
 I don't know what the KDE team plans for the kfreebsd ports. Will Solid still
 use hal there?

 hal
 Reverse Depends:
   xserver-xorg
   xfce4-session
   xfce4-power-manager
   xfburn
   wiican
   virt-manager
   thunar
   thunar-volman
   synce-hal
   rhythmbox
   pulseaudio-module-hal
   pitivi
   pcscd
   openct
   moovida-plugins-good
   kde-plasma-netbook
   kde-plasma-desktop
   lxde
   laptop-mode-tools
   kdebase-runtime
   halevt
   hal-info
   hal-info
   gvfs
   guidance-power-manager
   gnome-mount
   gnome-device-manager
   flumotion
   awn-applets-python-core
   apcupsd

 libhal1
 Reverse Depends:
   xprint
   xserver-xorg-core
   xfburn
   libthunar-vfs-1-2
   thunar-volman
   synce-trayicon
   synce-hal
   synce-gnomevfs
   rhythmbox
   rhythmbox-plugins
   pulseaudio-module-hal
   pcscd
   nut-hal-drivers
   libsynce0
   python-rra
   librra0
   librra-tools
   librapi2
   halevt
   libhal-storage1
   libhal-dev
   hal
   gxine
   gvfs
   gvfs-backends
   gtkpod
   gnome-mount
   libgnome-device-manager0
   gnome-device-manager
   libexo-0.3-0
   exo-utils
   collectd
   collectd-core

 libhal-storage1
 Reverse Depends:
   xfburn
   libthunar-vfs-1-2
   thunar-volman
   libhal-storage-dev
   hal
   gnome-mount
   libexo-0.3-0
   exo-utils


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110331133345.gt10...@const.bordeaux.inria.fr

Bug#533526: qt4-x11: FTBFS on hurd-i386

[Samuel Thibault]

Hello,

Could you please apply the patch?

Samuel



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#533526: qt4-x11: FTBFS on hurd-i386

[Samuel Thibault]

Package: qt4-x11
Version: 4.5.1-2
Severity: important
Tags: patch

Hello,

qt4-x11 currently FTBFS on hurd-i386 because since clock_gettime is not
available there qt4-x11 reverts to using gettimeofday, but it doesn't
include sys/time.h where the latter is defined, see attached patch.

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- src/corelib/concurrent/qtconcurrentiteratekernel.cpp.orig   2009-06-16 
22:11:11.0 +
+++ src/corelib/concurrent/qtconcurrentiteratekernel.cpp2009-06-16 
22:11:19.0 +
@@ -49,6 +49,7 @@
 
 #elif defined(Q_OS_UNIX)
 
+#include sys/time.h
 #include time.h
 #include unistd.h
 

Bug#438952: kdelibs: FTBFS on hurd-i386

[Samuel Thibault]

Package: kdelibs
Version: 4:3.5.7.dfsg.1-4
Severity: important
Tags: patch

Hi,

Kdelibs currently FTBFS because 

- on hurd-i386, the optional macro MAXPATHLEN is not defined since
there's no such hard global limit. readdir_r(), however, is known to be
limited to UCHAR_MAX on GNU/Hurd.
- on hurd-i386, the optional macro PATH_MAX is not defined either for
the same reason. The glibc version of getcwd(), however, can actually
allocate as much room as is required.

Here is a patch.

Samuel

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-xen
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel
 Allez, soyez sympa ... traduisez-lui linux
Linux, c'est comme le miel : c'est vachement bon mais ça attire les
mouches. En plus, ça colle aux doigts et on a du mal à s'en défaire.
-+- TP in: Guide du linuxien pervers - Barrez vous les mouches !
--- kdelibs-3.5.7.dfsg.1/kio/kio/kurlcompletion.cpp.orig2007-08-21 
01:20:27.125594000 +0200
+++ kdelibs-3.5.7.dfsg.1/kio/kio/kurlcompletion.cpp 2007-08-21 
01:28:02.002981000 +0200
@@ -231,6 +231,9 @@
while ( !terminationRequested() 
(dirEntry = ::readdir( dir)))
 #else
+#if !defined(MAXPATHLEN)  defined(__GNU__)
+#define MAXPATHLEN UCHAR_MAX
+#endif
struct dirent *dirPosition = (struct dirent *) malloc( sizeof( 
struct dirent ) + MAXPATHLEN + 1 );
struct dirent *dirEntry = 0;
while ( !terminationRequested() 
--- kdelibs-3.5.7.dfsg.1/kdoctools/meinproc.cpp.orig2007-08-21 
01:40:47.688059000 +0200
+++ kdelibs-3.5.7.dfsg.1/kdoctools/meinproc.cpp 2007-08-21 01:46:17.83361 
+0200
@@ -136,9 +136,18 @@
 }
 
 if ( args-isSet( check ) ) {
+#if !defined(PATH_MAX)  defined(__GLIBC__)
+char *pwd_buffer;
+#else
 char pwd_buffer[PATH_MAX];
+#endif
 QFileInfo file( QFile::decodeName(args-arg( 0 )) );
-if ( !getcwd( pwd_buffer, sizeof(pwd_buffer) - 1 ) ) {
+#if !defined(PATH_MAX)  defined(__GLIBC__)
+if ( !(pwd_buffer = getcwd( NULL, 0 ) ) )
+#else
+if ( !getcwd( pwd_buffer, sizeof(pwd_buffer) - 1 ) )
+#endif
+   {
 kdError()  getcwd failed.  endl;
  return 2;
}
@@ -175,11 +184,18 @@
 }
 pclose( xmllint );
 chdir( pwd_buffer );
-if ( !noout )
+if ( !noout ) {
+#if !defined(PATH_MAX)  defined(__GLIBC__)
+free( pwd_buffer );
+#endif
 return 1;
+}
 } else {
 kdWarning()  couldn't find xmllint  endl;
 }
+#if !defined(PATH_MAX)  defined(__GLIBC__)
+free( pwd_buffer );
+#endif
 }
 
 xmlSubstituteEntitiesDefault(1);
--- kdelibs-3.5.7.dfsg.1/kioslave/file/file.cc.orig 2007-08-21 
01:51:36.702504000 +0200
+++ kdelibs-3.5.7.dfsg.1/kioslave/file/file.cc  2007-08-21 01:55:39.362966000 
+0200
@@ -1234,8 +1234,13 @@
directories we keep as active directory. And
as the slave runs in the background, it's hard
to see for the user what the problem would be */
+#if !defined(PATH_MAX)  defined(__GLIBC__)
+char *path_buffer;
+path_buffer = getcwd(NULL, 0);
+#else
 char path_buffer[PATH_MAX];
 (void) getcwd(path_buffer, PATH_MAX - 1);
+#endif
 if ( chdir( _path.data() ) )  {
 if (errno == EACCES)
 error(ERR_ACCESS_DENIED, _path);
@@ -1261,6 +1266,9 @@
 kdDebug(7101)  = COMPLETED LIST   endl;
 
 chdir(path_buffer);
+#if !defined(PATH_MAX)  defined(__GLIBC__)
+free(path_buffer);
+#endif
 
 finished();
 }
--- kdelibs-3.5.7.dfsg.1/libkmid/fmout.cc.orig  2007-08-21 02:05:03.032474000 
+0200
+++ kdelibs-3.5.7.dfsg.1/libkmid/fmout.cc   2007-08-21 02:08:08.281128000 
+0200
@@ -127,8 +127,8 @@
 void FMOut::loadFMPatches(void)
 {
 #ifdef HAVE_OSS_SUPPORT
-  char patchesfile[PATH_MAX];
-  char drumsfile[PATH_MAX];
+  char patchesfile[strlen(FMPatchesDirectory)+7+1];
+  char drumsfile[strlen(FMPatchesDirectory)+9+1];
   int size;
   struct sbi_instrument instr;
   char tmp[60];
@@ -141,12 +141,12 @@
 
   if (opl==3)
   {
-snprintf(patchesfile, PATH_MAX, %s/std.o3,FMPatchesDirectory);
+snprintf(patchesfile, sizeof(patchesfile), %s/std.o3,FMPatchesDirectory);
 size=60;
   }
   else
   {
-snprintf(patchesfile, PATH_MAX, %s/std.sb,FMPatchesDirectory);
+snprintf(patchesfile, sizeof(patchesfile), %s/std.sb,FMPatchesDirectory);
 size=52;
   }
   fh=fopen(patchesfile,rb);
@@ -171,11 +171,11 @@
 
   if (opl==3)
   {
-snprintf(drumsfile, PATH_MAX, %s/drums.o3,FMPatchesDirectory);
+snprintf(drumsfile, sizeof(drumsfile), %s/drums.o3,FMPatchesDirectory);
   }
   else
   {
-snprintf(drumsfile, PATH_MAX, %s/drums.sb,FMPatchesDirectory);

Bug#375803: libartsc0-dev: artsc-config --libs shouldn't include -ldl -lpthread -lgmodule-2.0 -lgthread-2.0 -lglib-2.0

[Samuel Thibault]

Package: libartsc0-dev
Version: 1.5.3-2
Severity: wishlist

Hi,

There are spurious dependencies in the output of artsc-config --libs:
-L/usr/lib -ldl -lartsc -lpthread -lgmodule-2.0 -ldl -lgthread-2.0 -lglib-2.0

-ldl -lpthread -lgmodule-2.0 -ldl -lgthread-2.0 -lglib-2.0 are _not_
needed here (since the artsc _interface_ doesn't depend on these
libraries) and just bring unneeded dependencies. They should be used
only for linking libartsc.so itself, and put in artsc-config --libs
--static (for static linking).

Samuel

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages libartsc0-dev depends on:
ii  libartsc0 1.5.3-2aRts sound system C support librar
ii  libglib2.0-dev2.10.2-1   Development files for the GLib lib

libartsc0-dev recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#368883: qt4-x11: FTBFS on alpha

[Samuel Thibault]

Hi,

Could this be fixed any time soon?  qt4-x11 is currently blocking no
less than 83 packages.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]