Bug#897338: Downgrading severity of 897338
Control: -1 severity normal As this is apparently does not happen without virtualbox and is fixed by installing virtualbox-guest-dkms and/or virtualbox-guest-x11 I'm downgrading this bug to normal. I let the SDDM maintainers decide if this is a bug at all or if this is expected if the hardware support is not present in virtualbox. I think the last two messages to this bug report are about a different problem with NVIDIA graphics which is not related to this bug report. Gaudenz -- PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5 signature.asc Description: PGP signature
Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel
Source: qtbase-opensource-src
Version: 5.5.0+dfsg-3
Severity: serious
Setting the severity of this bug to serious because it causes another package
to fail to build from source.
This version of Qt breaks the tests of owncloud-sync on mips and mipsel. Test
also break
when compiling version 2.0.0+dfsg-1 of owncloud-client which previously
successfully built against the newer version of Qt. So I suspect this is
a bug in Qt and not in owncloud-client.
See here for the failing build logs:
https://buildd.debian.org/status/fetch.php?pkg=owncloud-client&arch=mipsel&ver=2.0.2%2Bdfsg-1&stamp=1445685652
I tried to debug this on the mipsel porter box but could not resovlve
the problem. This is what I found out:
- The problem is also present when running the tests with Qt
5.5.0+dfsg-3 so setting this version. This is the first version of Qt
5.5 available for mipsel. This is likely a bug introduced with Qt 5.5.
- This is the problematic part of the code in owncloud-client which
triggers the bug (see test/testfilesystem.h in owncloud-client):
https://anonscm.debian.org/cgit/pkg-owncloud/owncloud-client.git/tree/test/testfilesystem.h
26 QByteArray shellSum( const QByteArray& cmd, const QString& file )
27 {
28QProcess md5;
29QStringList args;
30args.append(file);
31md5.start(cmd, args);
32QByteArray sumShell;
33qDebug() << "File: "<< file;
34
35if( md5.waitForFinished() ) {
36
37 sumShell = md5.readAll();
38 sumShell = sumShell.left( sumShell.indexOf(' '));
39}
40return sumShell;
41 }
This is called twice during the test to compute a md5/sha1 sum with the
command
line tool to compare this against owncloud-clients internal implementation.
The
test then fails because this function returns an empty string instead of the
correct result.
- Running the test under strace shows that the md5sum/sha1sum call succeeds and
returns
the correct string. But apparently waitForFinished just hangs for 30s
(default timeout
value) and then returns an error.
At this point I'm out of ideas on how to further debug this. Help by Qt
maintainers or
mips porters would be appreciated.
Gaudenz
-- System Information:
Debian Release: stretch/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (100,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libqt5core5a depends on:
ii libc6 2.19-22
ii libgcc1 1:5.2.1-22
ii libglib2.0-0 2.46.1-1
ii libicu55 55.1-5
ii libpcre16-3 2:8.35-7.2
ii libstdc++65.2.1-22
ii zlib1g1:1.2.8.dfsg-2+b1
Versions of packages libqt5core5a recommends:
ii qttranslations5-l10n 5.5.1-2
Versions of packages libqt5core5a suggests:
ii libthai0 0.1.22-2
-- no debconf information
Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel
Lisandro Damián Nicanor Pérez Meyer writes: > forwarded 803669 https://bugreports.qt.io/browse/QTBUG-49168 > tag 803669 upstream > thanks > > On Monday 02 November 2015 23:07:19 Gaudenz Steinlin wrote: > [snip] >> If I read the strace output right (attached) md5sum only tahkes less >> than 1 second. The long 2x30s delay comes from subsequent pselect calls >> which may be unrelated to waitForFinished, but related to the fact the >> QProcess tries to kill the no longer running md5sum process. > > You are right. My wonderful teammate Dmitry has filed [qtbug] upstream. > > [qtbug] <https://bugreports.qt.io/browse/QTBUG-49168> > > The fix should be already in unstable in 5.5.1+dfsg-6, we are waiting for the > mips/mipsel buildds to pick the package. After that please try again. Now that -6 is on the mirror the porter box uses I retried the build but I still have the same build failure. So something is still missing here. Next I'll try the test program in the upstream bug report to see if that is fixed. Gaudenz signature.asc Description: PGP signature
Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel
Gaudenz Steinlin writes:
> Lisandro Damián Nicanor Pérez Meyer writes:
>
>> forwarded 803669 https://bugreports.qt.io/browse/QTBUG-49168
>> tag 803669 upstream
>> thanks
>>
>> On Monday 02 November 2015 23:07:19 Gaudenz Steinlin wrote:
>> [snip]
>>> If I read the strace output right (attached) md5sum only tahkes less
>>> than 1 second. The long 2x30s delay comes from subsequent pselect calls
>>> which may be unrelated to waitForFinished, but related to the fact the
>>> QProcess tries to kill the no longer running md5sum process.
>>
>> You are right. My wonderful teammate Dmitry has filed [qtbug] upstream.
>>
>> [qtbug] <https://bugreports.qt.io/browse/QTBUG-49168>
>>
>> The fix should be already in unstable in 5.5.1+dfsg-6, we are waiting for
>> the
>> mips/mipsel buildds to pick the package. After that please try again.
>
> Now that -6 is on the mirror the porter box uses I retried the build but
> I still have the same build failure. So something is still missing here.
>
> Next I'll try the test program in the upstream bug report to see if that
> is fixed.
The testcase from the upstream bug report does not work on the porter
box with 5.5.1+dfsg-6 as well. So this fix is either not applied to this
build or it's incomplete.
This is the output from the test program:
(sid_mipsel-dchroot)gaudenz@eder:~/testcase$ ./testcase
24 Calling waitForStarted()
54 waitForStarted() returned true
55 Calling waitForFinished()
30086 waitForFinished() returned false
30086 errorString() is "Process operation timed out"
QProcess: Destroyed while process ("/bin/true") is still running.
The strace output from running the testcase is attached.
Gaudenz
testcase.trace
Description: Binary data
signature.asc
Description: PGP signature
Bug#803669: Breaks QProcess in owncloud-client tests on mips an mipsel
Hi
Dmitry Shachnev writes:
> Hi Gaudenz,
>
> On Wed, 04 Nov 2015 15:51:40 +0100, Gaudenz Steinlin wrote:
>> The testcase from the upstream bug report does not work on the porter
>> box with 5.5.1+dfsg-6 as well. So this fix is either not applied to this
>> build or it's incomplete.
>>
>> This is the output from the test program:
>> (sid_mipsel-dchroot)gaudenz@eder:~/testcase$ ./testcase
>> 24 Calling waitForStarted()
>> 54 waitForStarted() returned true
>> 55 Calling waitForFinished()
>> 30086 waitForFinished() returned false
>> 30086 errorString() is "Process operation timed out"
>> QProcess: Destroyed while process ("/bin/true") is still running.
>
> Are you sure you were testing with 5.5.1+dfsg-6?
>
> This bug is definitely fixed there, here is the output of the same binary on
> the same machine:
>
> (sid_mipsel-dchroot)mitya57@eder:/home/gaudenz/testcase$ ./testcase
> 3 Calling waitForStarted()
> 9 waitForStarted() returned true
> 10 Calling waitForFinished()
> 11 waitForFinished() returned true
> 12 errorString() is "Unknown error"
>
> Tried multiple times to be completely sure.
You are absolutely right. I had the shell I was testing this running in
screen and forgot that I set an LD_LIBRARY_PATH there the other day to
be able to test different Qt versions. So LD_LIBRARY_PATH was still
pointing to the old Qt version. After clearing the variable everything
is fine.
Thanks again for the quick fix and sorry for the noise.
Gaudenz
signature.asc
Description: PGP signature
Bug#804883: QNAM does not report correct NetworkAccessibility (was: Regression: OwnCloud client fails to reconnect when network starts up)
Control: -1 retitle QNAM does not report correct NetworkAccessibility
[ Resending this to the Debian Qt/KDE maintainers as it only made it to
the Owncloud maintainers list. Sorry about my confusion how the BTS
would handle this. This is about Debian bug #804883 ]
Hi
Some context for the QT maintainers: This is about a bug in
owncloud-client which fails to reconnect to the server if the network
connection is lost. This is quite annoying because after every suspend
of your machine you have to restart the client because it does not
reconnect.
This bug in onwcloud-client is caused by a bug in QT. The upstream
bugreport is https://bugreports.qt.io/browse/QTBUG-46323.
There is a patch merged upstream, but it's not in any released version
yet: https://codereview.qt-project.org/#/c/121724/
I locally compiled QT with the fix applied and can confirm that this
fixes the oncloud-client issue for me. To be able to apply the patch I
had to pull in a second patch as a dependency:
https://bugreports.qt.io/browse/QTBUG-47471
https://codereview.qt-project.org/#/c/123087/2
The patch to the Debian package I used is attached. Thanks for
considering this until a fixed version is released upstream. It fixes a
very annoying bug in owncloud-client.
Gaudenz
From bf47964d9f8902dbdaae310786ae8118e2d20fb0 Mon Sep 17 00:00:00 2001
From: Gaudenz Steinlin
Date: Mon, 16 Nov 2015 15:31:37 +0100
Subject: [PATCH] Add patches to fix QT bugs #46323 and #47471
Closes: #804883
---
debian/patches/qtbug-46323.patch | 233 +++
debian/patches/qtbug-47471.patch | 146
debian/patches/series| 4 +
3 files changed, 383 insertions(+)
create mode 100644 debian/patches/qtbug-46323.patch
create mode 100644 debian/patches/qtbug-47471.patch
diff --git a/debian/patches/qtbug-46323.patch b/debian/patches/qtbug-46323.patch
new file mode 100644
index 000..fcc444e
--- /dev/null
+++ b/debian/patches/qtbug-46323.patch
@@ -0,0 +1,233 @@
+From bb281eea179d50a413f4ec1ff172d27ee48d3a41 Mon Sep 17 00:00:00 2001
+From: Lorn Potter
+Date: Fri, 17 Jul 2015 15:32:23 +1000
+Subject: [PATCH] Make sure networkAccessibilityChanged is emitted
+
+Task-number: QTBUG-46323
+Change-Id: I8297072b62763136f457ca6ae15282d1c22244f4
+Reviewed-by: Timo Jyrinki
+Reviewed-by: Alex Blasche
+---
+ src/network/access/qnetworkaccessmanager.cpp | 70 +++---
+ src/network/access/qnetworkaccessmanager_p.h | 14 -
+ .../tst_qnetworkaccessmanager.cpp | 31 +-
+ 3 files changed, 77 insertions(+), 38 deletions(-)
+
+diff --git a/src/network/access/qnetworkaccessmanager.cpp b/src/network/access/qnetworkaccessmanager.cpp
+index 84931cb..f9e9513 100644
+--- a/src/network/access/qnetworkaccessmanager.cpp
b/src/network/access/qnetworkaccessmanager.cpp
+@@ -278,7 +278,8 @@ static void ensureInitialized()
+
+ \snippet code/src_network_access_qnetworkaccessmanager.cpp 4
+
+-Network requests can be reenabled again by calling
++Network requests can be re-enabled again, and this property will resume to
++reflect the actual device state by calling
+
+ \snippet code/src_network_access_qnetworkaccessmanager.cpp 5
+
+@@ -467,16 +468,12 @@ QNetworkAccessManager::QNetworkAccessManager(QObject *parent)
+ qRegisterMetaType >();
+
+ #ifndef QT_NO_BEARERMANAGEMENT
+-if (!d->networkSessionRequired) {
+-// if a session is required, we track online state through
+-// the QNetworkSession's signals
+-connect(&d->networkConfigurationManager, SIGNAL(onlineStateChanged(bool)),
+-SLOT(_q_onlineStateChanged(bool)));
+-}
+-// we would need all active configurations to check for
+-// d->networkConfigurationManager.isOnline(), which is asynchronous
+-// and potentially expensive. We can just check the configuration here
+-d->online = (d->networkConfiguration.state() & QNetworkConfiguration::Active);
++// if a session is required, we track online state through
++// the QNetworkSession's signals if a request is already made.
++// we need to track current accessibility state by default
++//
++connect(&d->networkConfigurationManager, SIGNAL(onlineStateChanged(bool)),
++SLOT(_q_onlineStateChanged(bool)));
+ #endif
+ }
+
+@@ -946,7 +943,8 @@ QNetworkConfiguration QNetworkAccessManager::activeConfiguration() const
+ void QNetworkAccessManager::setNetworkAccessible(QNetworkAccessManager::NetworkAccessibility accessible)
+ {
+ Q_D(QNetworkAccessManager);
+-d->defaultAccessControl = false;
++
++d->defaultAccessControl = accessible == NotAccessible ? false : true;
+
+ if (d->networkAccessible != accessible) {
+ NetworkAccessibility previous = networkAccessible();
+@@ -965,6 +963,10 @@ void QNetworkAccessManager::setNetworkAccessible(QNetworkAccessManager::NetworkA
+ QNetwork
Bug#670185: Facility to disable Autologin with kdm.d files
Package: kde-workspace
Version: 4:4.7.4-2
Severity: wishlist
Tags: patch
Currently it's only possible to activate auto login with a configuration
snippet in /etc/default/kdm.d but it's not possible to deactivate auto
login in the same way. This would be convenient for a package I'm
developing which is an addition to Debian Live to allow users to plug in
their Debian Live system, have it automatically mounted as the home
directory and then login into the system with their account. For this to
work I would like to have a way to deactivate the autologin that was
activated by live-config.
The attached patch implements this with a new variable AUTOLOGINENABLE
but leaves the semantics as they are currently in the absence of this
variable.
Thanks for considering this patch.
Gaudenz
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
commit 83ea84a3b4894ac278bcb1bb5cb0268b5a437a9b
Author: Gaudenz Steinlin
Date: Mon Apr 23 22:14:12 2012 +0200
Facility to disable Autologin with kdm.d files
Enable setting AUTOLOGINENABLE="false" to disable auto login with a file
in /etc/default/kdm.d.
diff --git a/debian/kdm.init b/debian/kdm.init
index 9475ed4..1312af7 100644
--- a/debian/kdm.init
+++ b/debian/kdm.init
@@ -86,10 +86,9 @@ setup_config () {
sed -i "s|@@@ToBeReplacedByDesktopBase@@@|$DEFAULT_KDM_THEME|" ${KDMCFG}
# autologin overrides are useful for live debian environment
-if [ -n "$AUTOLOGINUSER" ]; then
- sed -i "s|^#\?AutoLoginEnable=.*|AutoLoginEnable=true|" $KDMCFG
- sed -i "s|^#\?AutoLoginUser=.*|AutoLoginUser=$AUTOLOGINUSER|" $KDMCFG
-fi
+[ -n "$AUTOLOGINENABLE" ] && sed -i "s|^#\?AutoLoginEnable=.*|AutoLoginEnable=$AUTOLOGINENABLE|" $KDMCFG
+[ -z "$AUTOLOGINENABLE" -a -n "$AUTOLOGINUSER" ] && sed -i "s|^#\?AutoLoginEnable=.*|AutoLoginEnable=true|" $KDMCFG
+[ -n "$AUTOLOGINUSER" ] && sed -i "s|^#\?AutoLoginUser=.*|AutoLoginUser=$AUTOLOGINUSER|" $KDMCFG
[ -n "$AUTOLOGINDELAY" ] && sed -i "s|^#\?AutoLoginDelay=.*|AutoLoginDelay=$AUTOLOGINDELAY|" $KDMCFG
[ -n "$AUTOLOGINAGAIN" ] && sed -i "s|^#\?AutoLoginAgain=.*|AutoLoginAgain=$AUTOLOGINAGAIN|" $KDMCFG
[ -n "$AUTOLOGINLOCKED" ] && sed -i "s|^#\?AutoLoginLocked=.*|AutoLoginLocked=$AUTOLOGINLOCKED|" $KDMCFG
