Bug#804883: QNAM does not report correct NetworkAccessibility

2016-01-09 Thread Mirko Vogt
This problem is gone in the 5.6.0 beta version of Qt, but still present in the 5.5.1-versions available for stretch/sid.

Bug#804883: QNAM does not report correct NetworkAccessibility

2015-12-09 Thread Mirko Vogt
On Sun, 22 Nov 2015 15:16:09 +0100 Ralf Jung wrote: > unfortunately, this bug is not fixed. I updated all the packages built > from qtbase to version 5.5.1+dfsg-8, and did a reboot - but the ownCloud > client is still not reconnecting to the server after I switching from > wired to wireless connec

Bug#804883: QNAM does not report correct NetworkAccessibility

2015-11-23 Thread Dmitry Shachnev
Hi Ralf, On Sun, Nov 22, 2015 at 03:16:09PM +0100, Ralf Jung wrote: > Hi all, > > unfortunately, this bug is not fixed. I updated all the packages built > from qtbase to version 5.5.1+dfsg-8, and did a reboot - but the ownCloud > client is still not reconnecting to the server after I switching fro

Bug#804883: QNAM does not report correct NetworkAccessibility

2015-11-22 Thread Ralf Jung
Hi all, unfortunately, this bug is not fixed. I updated all the packages built from qtbase to version 5.5.1+dfsg-8, and did a reboot - but the ownCloud client is still not reconnecting to the server after I switching from wired to wireless connection. I am unsure now whether this means that there

Bug#804883: QNAM does not report correct NetworkAccessibility (was: Regression: OwnCloud client fails to reconnect when network starts up)

2015-11-17 Thread Gaudenz Steinlin
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 main