[Touch-packages] [Bug 1197542] Re: System Info module not integrated with platform

[Lorn Potter]

** Changed in: qtsystems-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1197542

Title:
  System Info module not integrated with platform

Status in Ubuntu UI Toolkit:
  Invalid
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  The DeviceInfo item provides correct information for some functions on both 
desktop and Touch
  The BatteryInfo items do not yield correct results in any case.
  Did not try the other interfaces 

  libqt5systeminfo5:
Installed: 5.0~git20130123-0ubuntu1~test2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1197542/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1545619] Re: Replace qnam-ubuntu-fix6.patch with upstreamed patches

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1545619

Title:
  Replace qnam-ubuntu-fix6.patch with upstreamed patches

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  This is a reminder that for the Ubuntu archive version of qtbase, the
  qnam-ubuntu-fix6.patch should eventually be replaced with merged to
  upstream solution. Vivid-overlay can keep using the patch since it has
  been well tested by now.

  A portion of qnam-ubuntu-fix6.patch is currently being upstreamed at
  https://codereview.qt-project.org/#/c/148280/. Additionally qnam-
  ubuntu-fix6.patch touches src/network/access/qnetworkreplyhttpimpl.cpp
  and the network manager bearer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1545619/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553850] Re: QtSensor testsuite fails on Ubuntu

[Lorn Potter]

** Changed in: qtsensors-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsensors-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1553850

Title:
  QtSensor testsuite fails on Ubuntu

Status in Canonical System Image:
  Confirmed
Status in qtsensors-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Upstream bug:
  https://bugreports.qt.io/browse/QTBUG-34500

  QSensorGesture autotest fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558840] Re: Update downloads hang when connection changes

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1558840

Title:
  Update downloads hang when connection changes

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Downloads that use QNetworkRequest will seemingly hang when the
  connection changes from mobile data to wifi and vice versa.

  It would be nice if they would resume when the connection switch is
  completed.

  This requires changes in the bearer backend to enable forced  session
  roaming, as well as some changes in QNAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1404188

Title:
  QNetworkSession::isOpen() always returns false

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  Confirmed

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print "all is well".
  On a vivid phone however, it'll print "network session not open..."

  This used to work fine at least back in utopic images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560101] Re: /usr/bin/unity8:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngin

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1560101

Title:
  
/usr/bin/unity8:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151208.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9ff17690c744a60f79af6670852868008eb49303
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1560101/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1575744] Re: network disk cache does not take into account the HTTP Vary header

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1575744

Title:
  network disk cache does not take into account the HTTP Vary header

Status in Canonical System Image:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Fix Released

Bug description:
  Switching from English to Polish works as expected
  But then going back to English leaves me with store in Polish

  This survives reboots.

  Steps to reproduce:
  1. Go to Ubuntu Store scope (with your current language).
  2. Go to phone settings, change the language, accept & reboot the phone.
  3. Go to Ubuntu Store scope. Note how scope title and some strings such as 
"installed" changed for the new language (since these are provided locally by 
the scope for current LANG), but strings such as 'Highlight of the week' or 
departments names (hit the search lens icon to reveal departments) which come 
from the store still use the old language.

  See upstream bug at https://bugreports.qt.io/browse/QTBUG-14750

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575744/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1603883] Re: Upstream bearer plugin part of Ubuntu's QNAM fixes

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1603883

Title:
  Upstream bearer plugin part of Ubuntu's QNAM fixes

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  With https://codereview.qt-project.org/#/c/146115/ in Qt 5.6.1

  the following remains to be upstreamed:

  http://paste.ubuntu.com/19873256/

  It's fine to upstream to either 5.6 if suitable or 5.7/5.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1603883/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

** Changed in: qtsystems-opensource-src (Ubuntu)
 Assignee: Lorn Potter (lorn-potter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

[Lorn Potter]

upstream MR https://codereview.qt-project.org/#/c/178521/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1646080

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

[Lorn Potter]

@osomon looks good. I will apply upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1646080

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

[Lorn Potter]

** Changed in: qtsystems-opensource-src (Ubuntu)
   Importance: Undecided => High

** Changed in: qtsystems-opensource-src (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1646080

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

I seem to remember @timo-jyrinki suggesting the 'devices' name at review
time, so I must have not changed the base class. Not sure which one
makes more sense. Suggestions? Opinions??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

@osomon The reason you are seeing this not work correctly, is because
the value for countChanged signal is named 'devices' in the declarative
class, and not 'count' like what is in the base class and that you are
using in your qml example.

This should probably get changed in the declarative class to match the
base class.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

Got this working on my laptop w/ unity8...
Except it does work, still see that thread message, except the count is 
opposite of what it should be.

When I disconnect the keyboard (usb as well as bt) it says count: 2, and
when I connect it count: 1

When I first run the test qml, it reports count: 0
when it should report 1, as the laptop has a keyboard.
The first time I connect a keyboard there is no report, or when I first 
disconnect it.
Subsequent connection I see count: 1 (should be 2)
...

So it does seem to work regardless of the thread message, just not as it
should.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

I can reproduce this on turbo.
Does not happen when running the inputinfo console app in qtsystem examples.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

I meant latest repo for qtsystems-opensource-src.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

where is the latest bzr repo?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

[Lorn Potter]

How can I reproduce this? When I try that qml on qmlscene on my lenovo
yoga running unity8, I get a seg fault in
libunubtu_application_api_desktop_mirclient.so.3.0.0

** Changed in: qtsystems-opensource-src (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1638517

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1637129] [NEW] network-manager suddenly reports ethernet is unmanaged

[Lorn Potter]

Public bug reported:

Using 16.10

ethernet stopped working, network indicator & nmcli reports that my ethernet is 
unmanaged.
ifconfig reports it has no ip address. I turn on wifi and it works fine.

Doing ifconfig  up; dhclient  works for
getting ip address

I did have network-manager snap installed for a brief amount of time,
but have since removed it.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1637129

Title:
  network-manager suddenly reports ethernet is unmanaged

Status in network-manager package in Ubuntu:
  New

Bug description:
  Using 16.10

  ethernet stopped working, network indicator & nmcli reports that my ethernet 
is unmanaged.
  ifconfig reports it has no ip address. I turn on wifi and it works fine.

  Doing ifconfig  up; dhclient  works for
  getting ip address

  I did have network-manager snap installed for a brief amount of time,
  but have since removed it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1637129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1598584] Re: wifi slows to a crawl when bluetooth is enabled

[Lorn Potter]

I have seen this (and similar disconnections) happen on non Ubuntu
related devices where the bluetooth and wifi share the antenna.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1598584

Title:
  wifi slows to a crawl when bluetooth is enabled

Status in arale:
  New
Status in Canonical System Image:
  Confirmed
Status in frieza:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  I am having serious wifi performance issues on my Aquaris M10 (running
  rc-proposed r133). When measuring the wifi speed, I get download
  speeds of less than 1/20 compared to my Pro 5 at the same distance
  from the wifi router. This seems to be consistent through reboots. I
  had similar wifi performance also before recently upgrading to rc-
  proposed, which I thought would have fixed the issue.

  I am in the same place testing 3 different ubuntu devices and these are the 
readings of the wifi download speed:
  Laptop: 4 MB/s
  Pro 5: 3.5 MB/s
  Aquaris M10: 0.16 MB/s

  However, upload speed is about the same on all three devices.

  Turning bluetooth off gets Aquaris M10 wifi speed back to sort of
  normal, 2.5-3.4 MB/s. Bluetooth on, again 0.1-0.2 MB/s. Seems the two
  wireless technologies interfere with each other on the M10, while the
  Pro 5 doesn't have that problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/arale/+bug/1598584/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1603883] Re: Upstream bearer plugin part of Ubuntu's QNAM fixes

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1603883

Title:
  Upstream bearer plugin part of Ubuntu's QNAM fixes

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  With https://codereview.qt-project.org/#/c/146115/ in Qt 5.6.1

  the following remains to be upstreamed:

  http://paste.ubuntu.com/19873256/

  It's fine to upstream to either 5.6 if suitable or 5.7/5.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1603883/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Lorn Potter]

Got a patch from Andreas Pokorny to fix mir crash. Upstreamed at:
https://codereview.qt-project.org/#/c/169262/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Lorn Potter]

--- 
qtsystems-opensource-src-5.0~git20141206~44f70d99.orig/src/systeminfo/linux/qscreensaver_mir_p.h
+++ 
qtsystems-opensource-src-5.0~git20141206~44f70d99/src/systeminfo/linux/qscreensaver_mir_p.h
@@ -63,7 +63,7 @@ private:
 QScreenSaver * const q_ptr;
 Q_DECLARE_PUBLIC(QScreenSaver)
 
-int m_keepDisplayOnRequest;
+int m_keepDisplayOnRequestId;
 QDBusInterface m_iface;
 };
 


--- 
qtsystems-opensource-src-5.0~git20141206~44f70d99.orig/src/systeminfo/systeminfo.pro
+++ 
qtsystems-opensource-src-5.0~git20141206~44f70d99/src/systeminfo/systeminfo.pro
@@ -67,7 +67,7 @@ linux-*: !simulator: {
  qinputinfo.h \
  linux/qinputinfomanager_p.h
 
-contains(QT_CONFIG, mirclient) {
+config_mir {
 DEFINES += QT_UNITY8
 PRIVATE_HEADERS += linux/qscreensaver_mir_p.h
 SOURCES += linux/qscreensaver_mir.cpp

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Lorn Potter]

Weird thing is when I load the source into qtcreator and build with same
qmake line (and building mirclient stuff), I don't get segfaults.

I did have to edit source to even get it compiling.
In qscreensaver_mir_p.h there is int m_keepDisplayOnRequest
but it is m_keepDisplayOnRequestId in qscreensaver_mir.cpp 
I don't see how that would even compile when mirclient is enabled

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Lorn Potter]

comment in #26 was my fault, wrong library path used when it ran fine.

Program received signal SIGSEGV, Segmentation fault.
0x77fa0e30 in QInputInfoManagerPrivate::instance () at qinputinfo.cpp:68
68  if 
(QGuiApplication::platformNativeInterface()->nativeResourceForIntegration("mirconnection"))
(gdb) bt
#0  0x77fa0e30 in QInputInfoManagerPrivate::instance () at 
qinputinfo.cpp:68
#1  0x77fa10fc in QInputInfoManager::QInputInfoManager (this=0x423a50, 
parent=) at qinputinfo.cpp:260
#2  0x00402ec6 in Inputtest::Inputtest (this=0x7fffd4a0, 
parent=) at inputtest.cpp:42
#3  0x00402096 in main (argc=1, argv=) at main.cpp:41

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Lorn Potter]

Odd. The first time I built this package on my xenial laptop, inputinfo
crashed, but other builds (clean) it ran fine.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1607217] Re: QSysInfo doesn't work properly with AppArmor confinement

[Lorn Potter]

QSystemInfo has quite a few areas in the system it tries to access
information from, read only. (We've tried hard to keep it read only
access)

Just adding AppArmor to this to hopefully get some comment about this.

I could come up with a policy that would allow QSystemInfo to work, but
it would be up to the security guys to decide whether they would allow
it.

There are a few related bugs regarding wrong or missing information in
QSystemInfo.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1607217

Title:
  QSysInfo doesn't work properly with AppArmor confinement

Status in apparmor package in Ubuntu:
  New
Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Trying to detect platform (OS) name and version on Ubuntu Touch 15.04
  based phones and tablets using QML. On the Ubuntu Desktop QSysInfo
  provides the following _correct_ values:

  QSysInfo::productType(): "ubuntu"
  QSysInfo::productVersion(): "16.04"
  QSysInfo::prettyProductName(): "Ubuntu 16.04 LTS"

  However, in a confined environment (e.g. bq Aquaris E5 HD Ubuntu
  Edition / 15.04 OTA-11) the following _incorrect_ values are provided
  by QSysInfo:

  QSysInfo::productType(): "unknown"
  QSysInfo::productVersion(): "unknown"
  QSysInfo::prettyProductName(): "Linux 3.4.67"

  I suppose it's because QSysInfo tries to (or would need to) access
  such files on the filesystem that are blocked by AppArmor, like /etc
  /os-release or such.

  Ideally, QSysInfo::productVersion() should return not only "15.04" on
  an Ubuntu Touch device, but also the OTA release number. So it should
  be more like: "15.04 OTA-11". That's because "15.04" alone doesn't
  tell much about the actual Ubuntu Touch OS release installed on a
  mobile device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1607217/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1607217] Re: QSysInfo doesn't work properly with AppArmor confinement

[Lorn Potter]

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1607217

Title:
  QSysInfo doesn't work properly with AppArmor confinement

Status in apparmor package in Ubuntu:
  New
Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Trying to detect platform (OS) name and version on Ubuntu Touch 15.04
  based phones and tablets using QML. On the Ubuntu Desktop QSysInfo
  provides the following _correct_ values:

  QSysInfo::productType(): "ubuntu"
  QSysInfo::productVersion(): "16.04"
  QSysInfo::prettyProductName(): "Ubuntu 16.04 LTS"

  However, in a confined environment (e.g. bq Aquaris E5 HD Ubuntu
  Edition / 15.04 OTA-11) the following _incorrect_ values are provided
  by QSysInfo:

  QSysInfo::productType(): "unknown"
  QSysInfo::productVersion(): "unknown"
  QSysInfo::prettyProductName(): "Linux 3.4.67"

  I suppose it's because QSysInfo tries to (or would need to) access
  such files on the filesystem that are blocked by AppArmor, like /etc
  /os-release or such.

  Ideally, QSysInfo::productVersion() should return not only "15.04" on
  an Ubuntu Touch device, but also the OTA release number. So it should
  be more like: "15.04 OTA-11". That's because "15.04" alone doesn't
  tell much about the actual Ubuntu Touch OS release installed on a
  mobile device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1607217/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1521518] Re: No way to invoke OSK when a hardware keyboard is connected

[Lorn Potter]

There is iio-sensor-proxy and an iio-sensor-proxy plugin in QtSensors
that works for device orientation on a variety of laptops.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1521518

Title:
  No way to invoke OSK when a hardware keyboard is connected

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Incomplete
Status in ubuntu-keyboard:
  New
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  There are mice on the market that claim to be keyboards as well. This
  inhibits OSK. We can try and find out how many keys they have and be
  smart about it.

  Regardless, we should have a way of forcing the OSK, especially on
  touch-enabled devices. Whether it's triggered by a touch (as opposed
  to mouse click) on the text area, or with a button in the text field
  (replaced with the clear icon when you start typing). Another option
  is the copy/paste dropdown.

  :
  
  The on-screen keyboard should appear if:
  * no external keyboard is connected, and a text field becomes focused; or
  * an external keyboard is connected, but the most recent text typed anywhere 
was with the OSK, and a text field becomes focused; or
  * an external keyboard is connected, and the most recent text typed was with 
an external keyboard, but you tap in the already-focused text field. (App 
developers are responsible for emulating this behavior in typable areas that 
are not text fields.)
  

  == original description ==

  1. Boot nexus 7
  2. In the login screen, test that OSK works by tapping the password textfield
  3. swipe keyboard back down after testing it works
  4. Turn on Bluetooth mouse to get a mouse cursor
  5. Click on password textfield

  OSK doesn't pop up, touch tapping on the field doesn't bring up the
  OSK anymore either.

  ie. The login screen is not usable with mouse connected - cannot type
  in password via OSK since it doesn't come up when clicking the
  password textfield with mouse.

  See attached screenshot. Focus on textfield. Would expect OSK to show
  up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521518/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

[Lorn Potter]

I am wondering how widespread this bug may be? Does it effect only a few
phones (as in a bad batch of sensors) or is it more widespread?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1493574

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in vegetahd:
  New
Status in powerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560101] Re: /usr/bin/unity8:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngin

[Lorn Potter]

Duplicate of bug #1540679

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1560101

Title:
  
/usr/bin/unity8:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151208.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9ff17690c744a60f79af6670852868008eb49303
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1560101/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

[Lorn Potter]

Looking into the code, nothing jumps out at me as being out of the
ordinary there. Someone with a device would need to look into this
further.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1493574

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in vegetahd:
  New
Status in powerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

[Lorn Potter]

In #46, there is a difference of an ALS entry. (Pat's does not have one, while 
the one containing
an error has one) but the error is contained in the ALS/PS, while LHJ_PS looks 
normal. These functions that look like they pertain to calibration. 

As in the log from #45 seems to point to ALS/PS reading from mt-i2c, it
could originate in the hardware, but the software doesn't recover.
Whether that software is the driver, android sensors or powerd or
something else would require digging through the code. My guess is the
(als) driver doesn't handle this well.

It is interesting that this seems to happen on krillin as well, but
apparently not all devices. I'm not familiar enough with these to
devices to know if they use the same als/ps chip or share driver code.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1493574

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in vegetahd:
  New
Status in powerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1588748] Re: Compass not working on Meizu Pro 5

[Lorn Potter]

I know there was a change to add magnetometer. I am not sure of its
landing.

https://code.launchpad.net/~gerboland/qtubuntu-sensors/add-gyro-magnet-sensors/+merge/282033
https://code.launchpad.net/~gerboland/platform-api/add-magnetic-gyro-sensors/+merge/270389

Compass uses a magnetometer and sometimes of sensors to come up with
azimuth.

** Also affects: qtubuntu-sensors (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: platform-api (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu-sensors in
Ubuntu.
https://bugs.launchpad.net/bugs/1588748

Title:
  Compass not working on Meizu Pro 5

Status in Canonical System Image:
  New
Status in platform-api package in Ubuntu:
  New
Status in qtubuntu-sensors package in Ubuntu:
  New

Bug description:
  On my turbo the compass is not working. This shows in:

  - uNav navigation is always pointing north, even when moving in other 
directions
  - Compass app (https://github.com/andrejcampa/compass) only gives "-1" always

  Not filing under location-service since it probably doesn't deal with
  hardware specific problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588748/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1588748] Re: Compass not working on Meizu Pro 5

[Lorn Potter]

Correction to last comment, compass sometimes uses other sensors (low
level)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1588748

Title:
  Compass not working on Meizu Pro 5

Status in Canonical System Image:
  New
Status in platform-api package in Ubuntu:
  New
Status in qtubuntu-sensors package in Ubuntu:
  New

Bug description:
  On my turbo the compass is not working. This shows in:

  - uNav navigation is always pointing north, even when moving in other 
directions
  - Compass app (https://github.com/andrejcampa/compass) only gives "-1" always

  Not filing under location-service since it probably doesn't deal with
  hardware specific problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588748/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560398] Re: Proximity sensor during call doesn't allow dialing options

[Lorn Potter]

It seems that most of our proximity drivers have only close/far and not the 
full ir reflectance value that would be needed for obtaining a better distance 
indication.
That said, the driver could possibly be changed to toggle at a closer or 
greater distance.

But to me, this seems like it is some undefined behavior related to
#1543948

Sadly, I do not have an arale to test.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1560398

Title:
  Proximity sensor during call doesn't allow dialing options

Status in Canonical System Image:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I'm not sure if this is a duplicate of any of the proximity bugs
  already reported (https://bugs.launchpad.net/canonical-devices-system-
  image/+bug/1512100,  https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1493574, https://bugs.launchpad.net/canonical-
  devices-system-image/+bug/1524648,  https://bugs.launchpad.net
  /canonical-devices-system-image/+bug/1523308 to name a few).

  On arale, rc-proposed I made a call, but at a certain point I needed
  to choose an option on an IVR. When I took the phone off my ear, the
  screen would indeed wake up, but when I wanted to press a key number
  (after some trouble to bring up the keyboard altogether) I wouldn't be
  able because the screen would turn off. Eventually I managed to
  "trick" the phone being quick, but it took me some time. Hanging up
  was somehow less painful.

  Maybe a matter of adjusting the distance from which the screen turns
  off during calls?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560398/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1575744] Re: Language in the Store scope doesn't always change when user switches lang of the phone

[Lorn Potter]

What are the steps to reproduce this?
I tried several times switching system language English->Spanish (reboot) and 
then back to English (reboot) and store scope did the correct thing.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1575744

Title:
  Language in the Store scope doesn't always change when user switches
  lang of the phone

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  Switching from English to Polish works as expected
  But then going back to English leaves me with store in Polish

  This survives reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575744/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1575744] Re: Language in the Store scope doesn't always change when user switches lang of the phone

[Lorn Potter]

I briefly looked into fixing QNetworkRequest/QNetworkAccessManager (I
presume that is what you are using), it looks fairly easy three lines at
most (famous last words) to fix.

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1575744

Title:
  Language in the Store scope doesn't always change when user switches
  lang of the phone

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  Switching from English to Polish works as expected
  But then going back to English leaves me with store in Polish

  This survives reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575744/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Lorn Potter]

I'll make a task for myself to upstream that to qtsystems.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

[Lorn Potter]

LGTM, just a few style changes needed for upstream. Updated upstream
with patchset 24

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1536669

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1571522] Re: Detect captive WiFi hotspots

[Lorn Potter]

There can be many ways captive portals work and it is tricky being able
to support the different ways of detecting this.

I've seen some offer redirects, but others offer different status codes
to indicate the captive portal, and not all captive portals act properly
once things get returned.

I would think this comes from network-manager level and not indicator
level.


** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1571522

Title:
  Detect captive WiFi hotspots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Right now it is very annoying that when you connect to a captive wifi
  portal, the device does not detect that. All other devices open the
  log in page automatically, except ubuntu devices. One needs to
  manually open the browser, type a url and get redirected before being
  able to log in and start e.g. telegram messaging over the wifi
  connection.

  My proposed solution to solve this:
  When a WiFi connection is established, indicator-network should do a http GET 
call to ubuntu.com. If the reply turns out to be a redirect, it should open the 
browser with the redirect url.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1571522/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1569619] Re: Need support for Pressure sensor

[Lorn Potter]

** Also affects: platform-api (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1569619

Title:
  Need support for Pressure sensor

Status in qtubuntu-sensors:
  New
Status in platform-api package in Ubuntu:
  New

Bug description:
  Hi,

  At least in my device (Nexus 4), the pressure sensor doesn't seem to be 
available (OTA-10).
  If it is available, please direct me to the documentation of the available 
APIs to access it.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu-sensors/+bug/1569619/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1564142] Re: Multiple calls to finished/error signals of QNAM object

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1564142

Title:
  Multiple calls to finished/error signals of QNAM object

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Recently I've noticed that some odd issues where the
  QNetworkAccessManager API is being used to communicate with REST APIs
  in some of our code. I've tracked this down as far as it seems that
  the finished/error signals seem to get called multiple times,
  sometimes.

  This has resulted in bug #1552546 in ubuntuone-credentials. When
  logging in, if you enter the wrong password, it should show you an
  error message stating that either the email or password was incorrect.
  However, a generic network error message is being shown instead. When
  examining the logs, it seems that the correct error is sent, and then
  an invalid call to the finished signal was made, and a second error
  sent, resulting in the generic network error displayed to the user.
  This same issue happens when the 2FA code is required as well, and a
  network error message is displayed, rather than the 2FA required
  message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1564142/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552546] Re: Wrong hints showing when signing in Ubuntu One account

[Lorn Potter]

Patch attached to https://bugs.launchpad.net/bugs/1564142

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntuone-credentials in
Ubuntu.
https://bugs.launchpad.net/bugs/1552546

Title:
  Wrong hints showing when signing in Ubuntu One account

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  $ adb shell system-image-cli -i
  current build number: 272
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-03 04:45:02
  version version: 272
  version ubuntu: 20160303
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  Steps to reproduce:
  1. Open Ubuntu One sign in page from System Settings-->Accounts-->Ubuntu One
  2. Enter an account does not exist and with a password more than 8 characters
  Or enter an existed accunt and with a wrong password (more than 8 characters)

  Actual results:
  It always showing the same hints "Network error - please retry"

  Scenario 2:
  If enter an existed account which enabled 2nd factor authentication, tap 
'Sign in" after entered the correct account and password, the field of "Type 
your verification code" reveals, but also appears the hint "Network error - 
please retry"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552546/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1564142] Re: Multiple calls to finished/error signals of QNAM object

[Lorn Potter]

Patch for fixing this.
Partially reverts qnam-ubuntu-fix6.patch

** Patch added: "fix-duplicate-qnam-finished.patch"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1564142/+attachment/4627185/+files/fix-duplicate-qnam-finished.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1564142

Title:
  Multiple calls to finished/error signals of QNAM object

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Recently I've noticed that some odd issues where the
  QNetworkAccessManager API is being used to communicate with REST APIs
  in some of our code. I've tracked this down as far as it seems that
  the finished/error signals seem to get called multiple times,
  sometimes.

  This has resulted in bug #1552546 in ubuntuone-credentials. When
  logging in, if you enter the wrong password, it should show you an
  error message stating that either the email or password was incorrect.
  However, a generic network error message is being shown instead. When
  examining the logs, it seems that the correct error is sent, and then
  an invalid call to the finished signal was made, and a second error
  sent, resulting in the generic network error displayed to the user.
  This same issue happens when the 2FA code is required as well, and a
  network error message is displayed, rather than the 2FA required
  message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1564142/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1564142] Re: Multiple calls to finished/error signals of QNAM object

[Lorn Potter]

ok. it seems the last qnam patch does this. Need to remember why I added that 
one offending line.
Will test against the bug at #1552546

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1564142

Title:
  Multiple calls to finished/error signals of QNAM object

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Recently I've noticed that some odd issues where the
  QNetworkAccessManager API is being used to communicate with REST APIs
  in some of our code. I've tracked this down as far as it seems that
  the finished/error signals seem to get called multiple times,
  sometimes.

  This has resulted in bug #1552546 in ubuntuone-credentials. When
  logging in, if you enter the wrong password, it should show you an
  error message stating that either the email or password was incorrect.
  However, a generic network error message is being shown instead. When
  examining the logs, it seems that the correct error is sent, and then
  an invalid call to the finished signal was made, and a second error
  sent, resulting in the generic network error displayed to the user.
  This same issue happens when the 2FA code is required as well, and a
  network error message is displayed, rather than the 2FA required
  message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1564142/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1564142] Re: Multiple calls to finished/error signals of QNAM object

[Lorn Potter]

I made a simple test app that uses QNetworkRequest, and I am not seeing
duplicated finished signals being called when there are no errors.

If I use a non existent url, I am seeing duplicated
QNetworkAccessManager::finished signals being called, but no duplicated
signals from QNetworkReply.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1564142

Title:
  Multiple calls to finished/error signals of QNAM object

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Recently I've noticed that some odd issues where the
  QNetworkAccessManager API is being used to communicate with REST APIs
  in some of our code. I've tracked this down as far as it seems that
  the finished/error signals seem to get called multiple times,
  sometimes.

  This has resulted in bug #1552546 in ubuntuone-credentials. When
  logging in, if you enter the wrong password, it should show you an
  error message stating that either the email or password was incorrect.
  However, a generic network error message is being shown instead. When
  examining the logs, it seems that the correct error is sent, and then
  an invalid call to the finished signal was made, and a second error
  sent, resulting in the generic network error displayed to the user.
  This same issue happens when the 2FA code is required as well, and a
  network error message is displayed, rather than the 2FA required
  message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1564142/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552546] Re: Wrong hints showing when signing in Ubuntu One account

[Lorn Potter]

Does not need to be wrong password, it gives that 'Network error -
please retry' and then shows the 2 step verification entry, when giving
correct password.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntuone-credentials in
Ubuntu.
https://bugs.launchpad.net/bugs/1552546

Title:
  Wrong hints showing when signing in Ubuntu One account

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  $ adb shell system-image-cli -i
  current build number: 272
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-03 04:45:02
  version version: 272
  version ubuntu: 20160303
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  Steps to reproduce:
  1. Open Ubuntu One sign in page from System Settings-->Accounts-->Ubuntu One
  2. Enter an account does not exist and with a password more than 8 characters
  Or enter an existed accunt and with a wrong password (more than 8 characters)

  Actual results:
  It always showing the same hints "Network error - please retry"

  Scenario 2:
  If enter an existed account which enabled 2nd factor authentication, tap 
'Sign in" after entered the correct account and password, the field of "Type 
your verification code" reveals, but also appears the hint "Network error - 
please retry"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552546/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1545619] Re: Replace qnam-ubuntu-fix6.patch with upstreamed patches

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1545619

Title:
  Replace qnam-ubuntu-fix6.patch with upstreamed patches

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  This is a reminder that for the Ubuntu archive version of qtbase, the
  qnam-ubuntu-fix6.patch should eventually be replaced with merged to
  upstream solution. Vivid-overlay can keep using the patch since it has
  been well tested by now.

  A portion of qnam-ubuntu-fix6.patch is currently being upstreamed at
  https://codereview.qt-project.org/#/c/148280/. Additionally qnam-
  ubuntu-fix6.patch touches src/network/access/qnetworkreplyhttpimpl.cpp
  and the network manager bearer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1545619/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558840] Re: Update downloads hang when connection changes

[Lorn Potter]

Dug into system-update and it seems it does not use QNetwork to
download, but some python script (system-image)
com.canonical.SystemImage so resuming the download may or may not work.

IN my testing it seems to work sometimes, but other times, it will stop
with an installation error.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1558840

Title:
  Update downloads hang when connection changes

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Downloads that use QNetworkRequest will seemingly hang when the
  connection changes from mobile data to wifi and vice versa.

  It would be nice if they would resume when the connection switch is
  completed.

  This requires changes in the bearer backend to enable forced  session
  roaming, as well as some changes in QNAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1566103] [NEW] accelerometer is running at 200 MHz

[Lorn Potter]

Public bug reported:

The accelerometer seems to be running at the fastest rate possible -
200Mhz, and thus effecting battery life when it is not needed.

This rate should only be used for apps and games requiring a high amount of 
accel precision.
Normal use for orientation/rotation changes in the UI could be slowed down to 
50 MHz or even less, possibly lessening the power requirements.


The Bug https://bugs.launchpad.net/qtubuntu-sensors/+bug/1388654 would need to 
get fixed first.

** Affects: qtubuntu-sensors
 Importance: Undecided
 Status: New

** Affects: platform-api (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: platform-api (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1566103

Title:
  accelerometer is running at 200 MHz

Status in qtubuntu-sensors:
  New
Status in platform-api package in Ubuntu:
  New

Bug description:
  The accelerometer seems to be running at the fastest rate possible -
  200Mhz, and thus effecting battery life when it is not needed.

  This rate should only be used for apps and games requiring a high amount of 
accel precision.
  Normal use for orientation/rotation changes in the UI could be slowed down to 
50 MHz or even less, possibly lessening the power requirements.

  
  The Bug https://bugs.launchpad.net/qtubuntu-sensors/+bug/1388654 would need 
to get fixed first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu-sensors/+bug/1566103/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558840] Re: Update downloads hang when connection changes

[Lorn Potter]

It seems Today scope sometimes behaves...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1558840

Title:
  Update downloads hang when connection changes

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Downloads that use QNetworkRequest will seemingly hang when the
  connection changes from mobile data to wifi and vice versa.

  It would be nice if they would resume when the connection switch is
  completed.

  This requires changes in the bearer backend to enable forced  session
  roaming, as well as some changes in QNAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1564142] Re: Multiple calls to finished/error signals of QNAM object

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1564142

Title:
  Multiple calls to finished/error signals of QNAM object

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Recently I've noticed that some odd issues where the
  QNetworkAccessManager API is being used to communicate with REST APIs
  in some of our code. I've tracked this down as far as it seems that
  the finished/error signals seem to get called multiple times,
  sometimes.

  This has resulted in bug #1552546 in ubuntuone-credentials. When
  logging in, if you enter the wrong password, it should show you an
  error message stating that either the email or password was incorrect.
  However, a generic network error message is being shown instead. When
  examining the logs, it seems that the correct error is sent, and then
  an invalid call to the finished signal was made, and a second error
  sent, resulting in the generic network error displayed to the user.
  This same issue happens when the 2FA code is required as well, and a
  network error message is displayed, rather than the 2FA required
  message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1564142/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558840] Re: Update downloads hang when connection changes

[Lorn Potter]

The test app I wrote that downloads big file:
https://code.launchpad.net/~lorn-potter/+git/test-servicenetwork
Of course, this runs from commandline so is uncontained.

Steps to reproduce:
Landing for testing:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-060

* open system settings->update
* when there is a larger update available, start the download.
* turn off wifi or walk from wifi zone

Known issues:

1. Euronews, Engadget and Today scope to not ever see network
2. Occasionally update check will hang when changing network device(wifi -> 3g)
3. Occasionally update download will not resume properly when network change.

I am fairly certain that #1 can only be fixed by moving QtBearer plugin
to connectivity-api, although I do not see any apparmor denials in the
log, with this change it makes QNetworkRequest require a
QNetworkSession, which in turn I believe fails as the known and
unfixable QtNetwork network-manager backend issues with apparmor. I am
assuming that scopes run in contained space, because other commandline
based tests with QtNetworking access work, but Click apps that use
QtNetworking fail similarly.

#2 and #3 most likely will continue to occur as I believe they are
timing issues with the actual network process and the linux networking
subsystem does not migrate the actual data/sockets and behave like the
Symbian networking backend (which this feature was originally written
for) to have seamless network transitions/migration.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1558840

Title:
  Update downloads hang when connection changes

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Downloads that use QNetworkRequest will seemingly hang when the
  connection changes from mobile data to wifi and vice versa.

  It would be nice if they would resume when the connection switch is
  completed.

  This requires changes in the bearer backend to enable forced  session
  roaming, as well as some changes in QNAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call when proximity sensor triggered

[Lorn Potter]

I can reproduce this.

Start with screen blanked.
Cover top of phone with something., so it covers the proximity sensor.
Call that phone from another one.
While it is ringing, lift the cover off the proximity sensor.

See that screen stays blanked and only way to unblank it is to push
button.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1524648

Title:
  Display doesn't turn on for incoming phone call when proximity sensor
  triggered

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524648/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558840] Re: Update downloads hang when connection changes

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1558840

Title:
  Update downloads hang when connection changes

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Downloads that use QNetworkRequest will seemingly hang when the
  connection changes from mobile data to wifi and vice versa.

  It would be nice if they would resume when the connection switch is
  completed.

  This requires changes in the bearer backend to enable forced  session
  roaming, as well as some changes in QNAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1558840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1560373] [NEW] network indicator shows no connection but browser works

[Lorn Potter]

Public bug reported:

Using nexus 4, wifi is disabled

/bearer# system-image-cli -i
current build number: 391
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-03-16 13:49:10
version version: 391
version ubuntu: 20160316
version device: 20160315
version custom: 20160316

The network indicator shows no connection.
route -n says rmnet_usb1 is default. nmcli c says ril_0 context2 is connected, 
and browser works

~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.65.67.1010.0.0.0 UG60000 
rmnet_usb1
10.65.67.0  0.0.0.0 255.255.255.0   U 60000 
rmnet_usb1

~# nmcli c
NAME   UUID  TYPE   
  DEVICE
/505025500612657/context2  e1a9ae5f-e7f7-cc00-54ed-cb6806086620  gsm
  ril_0
/505025500612657/context1  c56a0ac7-b8b6-8d66-7e7f-6da831c64ea8  gsm
  --
llkcr2 bc7eb95d-1ff0-4f64-b6ea-f63084914945  
802-11-wireless  --
BIGPOND1DE4bfcaf5ac-262e-4c7d-9998-d421022aef18  
802-11-wireless  --
TV 1   ea55c5bd-9156-4283-aade-2b615a352f1a  
802-11-wireless  --
TV 824802a9-9492-44dd-bc8c-01e0b34f8abc  
802-11-wireless  --
llkcr  96382cce-f023-434f-97ee-b1b6c4103b20  
802-11-wireless  --
OPTUSDN1E578A  69e23365-40a4-4c7b-a999-7d568fb5d9f5  
802-11-wireless  --
Telstra1708f6d10847-fa02-4a49-9644-89f9f9d3e935  
802-11-wireless  --

~# nmcli d
DEVICE   TYPE  STATECONNECTION
ril_0gsm   connected/505025500612657/context2
wlan0wifi  unavailable  --
dummy0   dummy unmanaged--
rev_rmnet0   ethernet  unmanaged--
rev_rmnet1   ethernet  unmanaged--
rev_rmnet2   ethernet  unmanaged--
rev_rmnet3   ethernet  unmanaged--
rev_rmnet4   ethernet  unmanaged--
rev_rmnet5   ethernet  unmanaged--
rev_rmnet6   ethernet  unmanaged--
rev_rmnet7   ethernet  unmanaged--
rev_rmnet8   ethernet  unmanaged--
rmnet0   ethernet  unmanaged--
rmnet1   ethernet  unmanaged--
rmnet2   ethernet  unmanaged--
rmnet3   ethernet  unmanaged--
rmnet4   ethernet  unmanaged--
rmnet5   ethernet  unmanaged--
rmnet6   ethernet  unmanaged--
rmnet7   ethernet  unmanaged--
rmnet_smux0  ethernet  unmanaged--
lo   loopback  unmanaged--
sit0 unknown   unmanaged--

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- net indicator shows no connection. route -n says rmnet_usb1 is default.
- nmcli c says ril_0 context2 is connected, and browser works
+ Using nexus 4
  
- 
root@ubuntu-phablet:/home/phablet/qtbase-opensource-src-5.4.1+dfsg/plugins/bearer#
 route -n
+ /bearer# system-image-cli -i
+ current build number: 391
+ device name: mako
+ channel: ubuntu-touch/rc-proposed/ubuntu
+ last update: 2016-03-16 13:49:10
+ version version: 391
+ version ubuntu: 20160316
+ version device: 20160315
+ version custom: 20160316
+ 
+ The network indicator shows no connection. 
+ route -n says rmnet_usb1 is default. nmcli c says ril_0 context2 is 
connected, and browser works
+ 
+ ~# route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 10.65.67.1010.0.0.0 UG60000 
rmnet_usb1
  10.65.67.0  0.0.0.0 255.255.255.0   U 60000 
rmnet_usb1
  
  
- 
root@ubuntu-phablet:/home/phablet/qtbase-opensource-src-5.4.1+dfsg/plugins/bearer#
 nmcli c
- NAME   UUID  TYPE 
DEVICE 
- /505025500612657/context2  e1a9ae5f-e7f7-cc00-54ed-cb6806086620  gsm  
ril_0  
- /505025500612657/context1  c56a0ac7-b8b6-8d66-7e7f-6da831c64ea8  gsm  
-- 
- llkcr2 bc7eb95d-1ff0-4f64-b6ea-f63084914945  
802-11-wireless  -- 
- BIGPOND1DE4bfcaf5ac-262e-4c7d-9998-d421022aef18  
802-11-wireless  -- 
- TV 1   ea55c5bd-9156-4283-aade-2b615a352f1a  
802-11-wireless  -- 
- TV 824802a9-9492-44dd-bc8c-01e0b34f8abc  
802-11-wireless  -- 
- llkcr  96382cce-f023-434f-97ee-b1b6c4103b20  
802-11-wireless  -- 
- OPTUSDN1E578A  69e23365-40a4-4c7b-a999-7d568fb5d9f5  
802-11-wireless  -- 
- Telstra1708f6d10847-fa02-4a49-9644-89f9f9d3e935  
802-11-wireless  --   
+ ~# nmcli c
+ NAME   UUID  TYPE 
DEVICE
+ /505025500612657/context2  e1a9ae5f-e7f7-cc00-54ed-cb6806086620  gsm  
ril_0
+ /505025500612657/context1  c56a0ac7-b8b6-8d66-7e7f-6da831c64ea8  gsm  
--
+ llkcr2 

[Touch-packages] [Bug 1560101] Re: /usr/bin/unity8:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngin

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1560101

Title:
  
/usr/bin/unity8:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151208.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9ff17690c744a60f79af6670852868008eb49303
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1560101/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false

[Lorn Potter]

So the solution to this is using connectivity-api in a new bearer
plugin.

The connectivity-api based bearer plugin is blocked by the bandwidthLimitations 
property not working correctly
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1362592

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1404188

Title:
  QNetworkSession::isOpen() always returns false

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  Confirmed

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print "all is well".
  On a vivid phone however, it'll print "network session not open..."

  This used to work fine at least back in utopic images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558840] [NEW] Update downloads hang when connection changes

[Lorn Potter]

Public bug reported:

Downloads that use QNetworkRequest will seemingly hang when the
connection changes from mobile data to wifi and vice versa.

It would be nice if they would resume when the connection switch is
completed.

This requires changes in the bearer backend to enable forced  session
roaming, as well as some changes in QNAM.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1558840

Title:
  Update downloads hang when connection changes

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Downloads that use QNetworkRequest will seemingly hang when the
  connection changes from mobile data to wifi and vice versa.

  It would be nice if they would resume when the connection switch is
  completed.

  This requires changes in the bearer backend to enable forced  session
  roaming, as well as some changes in QNAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1558840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'

[Lorn Potter]

This same crash happens on turbo when:

1.Open Browser app and Message app (or two apps - gallery, etc), then swipe up 
in Browser --Tap New tab
2.Turn your device in landscape mode
3.Swipe from right side to switch to Message app and wait a while ,maybe tap on 
the messages will help to reproduce

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1554635

Title:
  Importing contacts trigger unity restart - Mir crashed with exception
  'failed to add sync point to command buffer'

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in Mir 0.20 series:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Steps:

  Open Dekko or Telegram
  Go to import contacts
  Make sure you have a substantial amount of contacts in your phone
  When the contacts app is open in import mode, select all contact and press 
Tick

  Expected:
  contacts are imported succesfully

  Actual:
  Unity restarts (goes back to the ubuntu dot screen) and the contact import is 
interrupted

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1555751] Re: Some apps require a restart after switching to/from Wifi/Cellular to reconnect to the network

[Lorn Potter]

It could very well be these apps are doing something that is causing this 
behaviour.
I am not convinced this is an issue with QNAM.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1555751

Title:
  Some apps require a restart after switching to/from Wifi/Cellular to
  reconnect to the network

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Some apps require a restart after switching to/from Wifi/Cellular to
  reconnect to the network

  What happened:
  1) Ensure wifi is connected
  2) Start Dekko
  3) Refresh the inbox (notice the bouncing/loading bar stops eventually)
  4) Disable wifi so you are on cellular
  5) Refresh the inbox (notice the bouncing/loading bar stays continuously)

  Note
  - if after step 5 you restart the app it is fine
  - this only occurs on certain apps, specifically Dekko and Telegram are the 
ones that i've noticed so far. (Both of which i assume try to have a long 
running open network connection?)

  What I expected to happen:
  At step 5) for the connection to automatically change to using Cellular and 
not require an app restart

  $ system-image-cli -i
  current build number: 258
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-10 15:48:08
  version version: 258
  version ubuntu: 20160310
  version device: 20160304.2
  version custom: 20160201-5-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1555751/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553850] [NEW] QtSensor testsuite fails on Ubuntu

[Lorn Potter]

Public bug reported:

Upstream bug:
https://bugreports.qt.io/browse/QTBUG-34500

QSensorGesture autotest fail

** Affects: qtsensors-opensource-src (Ubuntu)
 Importance: Undecided
 Assignee: Lorn Potter (lorn-potter)
 Status: Confirmed

** Changed in: qtsensors-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

** Changed in: qtsensors-opensource-src (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsensors-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1553850

Title:
  QtSensor testsuite fails on Ubuntu

Status in qtsensors-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Upstream bug:
  https://bugreports.qt.io/browse/QTBUG-34500

  QSensorGesture autotest fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsensors-opensource-src/+bug/1553850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552860] Re: [MIR] qtsystems-opensource-src

[Lorn Potter]

Also maintained by me. I also maintain upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1552860

Title:
  [MIR] qtsystems-opensource-src

Status in qtsystems-opensource-src package in Ubuntu:
  New

Bug description:
  This is a MIR for qtsystems-opensource-src, which is currently in
  universe.

  1. Availability: the package has been in universe since Trusty, and it
  builds on all supported architectures.

  2. Rationale: In Ubuntu Touch applications, the recommended way of
  enumerating input devices (physical keyboards, mice, touchpads, etc…)
  is the QInputDeviceInfo API. We would like to start using that API in
  webbrowser-app, which is in main.

  3. Security: nothing to highlight, but the security team might want to
  acknowledge that. Note that a preliminary review was already done a
  couple of years ago, see Jamie’s comments at
  https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-
  src/+bug/1217001/comments/10.

  4. QA: the package comes with automated unit tests as well as manual
  tests. The unit tests are run as part of the package build. Bugs in
  ubuntu: https://bugs.launchpad.net/ubuntu/+source/qtsystems-
  opensource-src. The package is not in debian (see
  https://wiki.debian.org/Mobile/Ubuntu).

  5. UI standards: N/A

  6. Dependencies: all build and runtime dependencies are in main.

  7. Standards compliance: complies with debian packaging standards.

  8. Maintenance: actively maintained by Timo Jyrinki .

  9. Background information: package descriptions are meaningful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1552860/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta

[Lorn Potter]

awe is currently working on getting the update to 1.2 working. Work is
ongoing, and needs a few more improvements and patches ported.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1552424

Title:
  [FFE] NetworkManager 1.2-beta

Status in network-manager package in Ubuntu:
  New

Bug description:
  We really should update NetworkManager to 1.2 (or some other updated
  stable release) for the LTS, this will allow us to better deal with
  any bugs that might come up post-release.

  This new release will also much improve interop with LXC, which has
  recently been an issue.

  Other FFEs will be opened for NM VPN plugins and for NetworkManager-
  applet.

  
  
  
  NetworkManager-1.2
  Overview of changes since NetworkManager-1.0
  

  This is a new stable release of NetworkManager.  Notable changes
  include:

  * Added an option to enable use of random MAC addresses for Wi-Fi access
  point scanning (defaults to disabled).  Controlled with
  'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key 
in
  ifcfg files).
  * Wi-Fi scanning now utilizes wpa_supplicant's AP list.
  * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
  files.
  * Added support for creation of more types of software devices: tun & tap,
  macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
  * The software devices (bond, bridge, vlan, team, ...) can now be stacked
  arbitrarily.  The nmcli interface for creating master-slave relationships
  has been significantly improved by the use of 'master' argument to
  all link types.
  * RFC7217 stable privacy addressing is now used by default to protect from
  address-based host tracking. The IPv6 addressing mode is configured with
  IPV6_ADDR_GEN_MODE key in ifcfg files.
  * Improved route management code to avoid clashes between conflicting
  routes in multiple connections.
  * Refactored platform code resulting in more robust interface to platform,
  less overhead and reduced memory footprint.
  * Improved interoperability with other network management tools.  The
  externally created software devices are not managed until they're
  activated.
  * The Device instances now exist for all software connections and the platform
  devices are now only created when the device is activated.  This makes it
  possible for connections with device of same name not to clash unless
  they're activated concurrently.  The links are now not unnecessarily 
present
  unless the connection is active, avoiding pollution of the link namespace.
  * NetworkManager now correctly manages connectivity in namespace-based
  containers such as LXC and Docker.
  * Support for configuring ethernet Wake-On-Lan has been added.
  * Added LLDP listener functionality and related CLI client commands. Enabled 
via
  LLDP option in ifcfg files.
  * CLI secret agent has been extended with support for VPN secrets.
  * The command line client now utilizes colors for its output.
  * The command line client now sorts the devices and properties for better
  clarity.
  * Numerous improvements to Bash command completion for nmcli.
  * NetworkManager relies on less external libraries.  The use of dbus-glib
  has been replaced with gio's native D-Bus support and libnl-route is no
  longer used.
  * Dependency on avahi-autoipd has been dropped.  Native IPv4 link-local
  addressing configuration based on systemd network library is now used
  instead.
  * Hostname is now managed via systemd-hostnamed on systemd-based systems.
  * Management of resolv.conf management can be changed at runtime, private
  resolv.conf is always written in /run.
  * NetworkManager can now write DNS options to resolv.conf.
  * Updated version of systemd network library used for internal DHCP and
  IPv4 link-local support.
  * Support for event logging via audit subsystem has been added.
  * Support for native logging via systemd-journald has been added taking
  advantage of its structured logging.
  * Live reconfiguration of IP configuration after changing the settings without
  reactivation of the device with "nmcli device reapply" command and via
  D-Bus API.
  * The API for VPN plugins now supports multiple simultaneous connections.
  Most popular VPN plugins have been updated to support this functionality.
  * The libnm library now provides API to access VPN service definitions.
  * New DHCP_FQDN key in ifcfg files to configure the full FQDN to be sent to
  the DHCP servers.
  * The timeout for DHCP requests can now be modified using the
  'ipv4.dhcp-timeout' property.
  * Added multicast_snooping option to BRIDGING_OPTS ifcfg key.
  * Added support 

[Touch-packages] [Bug 1197542] Re: System Info module not integrated with platform

[Lorn Potter]

Related bugs:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1525879
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1549314

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1197542

Title:
  System Info module not integrated with platform

Status in Ubuntu UI Toolkit:
  Invalid
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  The DeviceInfo item provides correct information for some functions on both 
desktop and Touch
  The BatteryInfo items do not yield correct results in any case.
  Did not try the other interfaces 

  libqt5systeminfo5:
Installed: 5.0~git20130123-0ubuntu1~test2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1197542/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1470700] Re: QNetworkAccessManager hangs when in flight mode

[Lorn Potter]

Just verified using the test app that this is fixed on:

phablet@ubuntu-phablet:~/1470700$ system-image-cli -i
current build number: 377
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-03-01 09:20:40
version version: 377
version ubuntu: 20160227
version device: 20160112
version custom: 20160227

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1470700

Title:
  QNetworkAccessManager hangs when in flight mode

Status in Canonical System Image:
  Fix Committed
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Testing the fix:

  - Update rc-proposed (vivid) to citrain device-upgrade 32 
  - Optional: If you want to test using the 'generic' bearer plugin instead of 
the Network Manager bearer, either do not upgrade ubuntu-touch-session or move 
away the file /etc/profile.d/qt_networkmanager_bearer.sh
  - Reboot

  ---

  When my phone is in flight mode, HTTP requests made using
  QNetworkAccessManager seem to hang rather than erroring out
  immediately.

  From my tests, it looks like the HTTP request is blocked until the
  flight mode is disabled and a network connection is reestablished.
  This is contrary to the documentation, which states:

  """If the network is not accessible the network access manager will
  not process any new network requests, all such requests will fail with
  an error. Requests with URLs with the file:// scheme will still be
  processed."""

  http://doc.qt.io/qt-5/qnetworkaccessmanager.html#networkAccessible-
  prop

  By running strace on my test program, it doesn't even look like it
  attempts to open a TCP connection when blocked in flight mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470700/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1545619] Re: Replace qnam-ubuntu-fix6.patch with upstreamed patches

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1545619

Title:
  Replace qnam-ubuntu-fix6.patch with upstreamed patches

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  This is a reminder that for the Ubuntu archive version of qtbase, the
  qnam-ubuntu-fix6.patch should eventually be replaced with merged to
  upstream solution. Vivid-overlay can keep using the patch since it has
  been well tested by now.

  A portion of qnam-ubuntu-fix6.patch is currently being upstreamed at
  https://codereview.qt-project.org/#/c/148280/. Additionally qnam-
  ubuntu-fix6.patch touches src/network/access/qnetworkreplyhttpimpl.cpp
  and the network manager bearer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1545619/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1540679] Re: /usr/bin/signonpluginprocess:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetwor

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1540679

Title:
  
/usr/bin/signonpluginprocess:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding signon.  This problem was most recently seen with version
  8.58+15.04.20151106-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/042703ee27820c1e5507e140ffbdf520d3c5dff2
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1540679/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1538755] Re: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkMana

[Lorn Potter]

Yes. They have landed as well.
And this one is a duplication of this bug.

https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1540679

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1538755

Title:
  /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-
  
service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding thumbnailer.  This problem was most recently seen with
  version 2.3+15.04.20151102.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/4d8506d5cef09939bd7de656ced14576d34f1e9a
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1538755/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1404188

Title:
  QNetworkSession::isOpen() always returns false

Status in Canonical System Image:
  Fix Committed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print "all is well".
  On a vivid phone however, it'll print "network session not open..."

  This used to work fine at least back in utopic images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1288777] Re: Qt bearer thread requires otherwise unneeded internet access

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1288777

Title:
  Qt bearer thread requires otherwise unneeded internet access

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  When comparing Qt5.0 denials with Qt5.2 denials on test runs that popey did, 
it looks like Qt5.2 changed its behavior such that the Qt bearer thread 
requires otherwise unneeded internet access. Eg, 'permy' from the appstore does 
not (and should not) use the "networking" policy group. On 5.0, launching it 
causes no apparmor denials. On 5.2, it does:
  Feb 25 REDACT ubuntu-phablet kernel [REDACT] type=1400 audit(REDACT) 
apparmor="DENIED" operation="create" parent= 
profile="com.ubuntu.developer.jdstrand.permy_permy_0.5" pid= 
comm=517420626561726572207468726561 family="inet" sock_type="dgram" protocol=0

  Permy's source is at lp:permy. Note, one other application besides permy had 
similar denials:
  Feb 25 REDACT ubuntu-phablet kernel [REDACT] type=1400 audit(REDACT) 
apparmor="DENIED" operation="create" parent= 
profile="org.sambull.eo-dict_eo-dict_0.2" pid= 
comm=517420626561726572207468726561 family="inet" sock_type="dgram" protocol=0

  This may seem like it isn't important-- the apparmor policy doesn't
  say it is allowed to connect to the network and apparmor correctly
  blocks it. I don't know if the app is adversely affected though (these
  aren't my logs). It might be, and even if it isn't, the noisy denial
  will lead to confusion (we can't explicitly deny networking in its
  policy to silence the denial due to how apparmor policy works).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1288777/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1541686] Re: apparmor denials with using XMLHttpRequest

[Lorn Potter]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1541686

Title:
  apparmor denials with using XMLHttpRequest

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  I just tried an example app with code from:
  http://doc.qt.io/qt-5/qtqml-xmlhttprequest-get-qml.html

  
  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.DBus.Properties" member="GetAll" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.NetworkManager" member="GetDevices" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
  "Object path cannot be empty"
  file:///opt/click.ubuntu.com/get.lorn-potter/0.1/Main.qml:61: TypeError: 
Cannot read property 'documentElement' of null

  The calls GetAll and GetDevices are used in the QtBearer network
  manager backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1541686/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1547194] [NEW] cannot connect to limitationsUpdated signal

[Lorn Potter]

Public bug reported:

In connectivity.h, the limitationsUpdated signal is declared as such:
  void limitationsUpdated(const QVector&);

When I use this syntax to connect:
connect(ns.data(),SIGNAL(limitationsUpdated(const QVector&)),
 this,SLOT(limitationsUpdated(const 
QVector&));

I get this error when building:

tstconnectivity.h:21:43: error: ‘Limitations’ was not declared in this scope
 void limitationsUpdated(const QVector&);

When I try:
connect(ns.data(),SIGNAL(limitationsUpdated(const 
QVector&)),
 this,SLOT(limitationsUpdated(const 
QVector&));
It builds, but I get this error when running:
2016-02-18T17:52:55 (unknown:0) - QObject::connect: No such signal 
connectivityqt::Connectivity::limitationsUpdated(const 
QVector&)


The signal should probably be declared:
  void limitationsUpdated(const 
QVector&);

with connectivityqt::Connectivity:: just as the statusUpdated

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "connectivityqt-limitations.patch"
   
https://bugs.launchpad.net/bugs/1547194/+attachment/4574827/+files/connectivityqt-limitations.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1547194

Title:
  cannot connect to limitationsUpdated signal

Status in indicator-network package in Ubuntu:
  New

Bug description:
  In connectivity.h, the limitationsUpdated signal is declared as such:
void limitationsUpdated(const QVector&);

  When I use this syntax to connect:
  connect(ns.data(),SIGNAL(limitationsUpdated(const QVector&)),
   this,SLOT(limitationsUpdated(const 
QVector&));

  I get this error when building:

  tstconnectivity.h:21:43: error: ‘Limitations’ was not declared in this scope
   void limitationsUpdated(const QVector&);

  When I try:
  connect(ns.data(),SIGNAL(limitationsUpdated(const 
QVector&)),
   this,SLOT(limitationsUpdated(const 
QVector&));
  It builds, but I get this error when running:
  2016-02-18T17:52:55 (unknown:0) - QObject::connect: No such signal 
connectivityqt::Connectivity::limitationsUpdated(const 
QVector&)

  
  The signal should probably be declared:
void limitationsUpdated(const 
QVector&);

  with connectivityqt::Connectivity:: just as the statusUpdated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1547194/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

** Changed in: connectivity-api (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Fix Committed
Status in Today Scope:
  Invalid
Status in connectivity-api package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1545673] Re: detect network switch

[Lorn Potter]

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1545673

Title:
  detect network switch

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New

Bug description:
  Having in device connected 3G and WIFI at the same time and using
  connectivity api as described here [1] If I'm not wrong it should be
  emiting some sort of bandwidth signal when WIFI gets disconnected for
  an application to know that the connection is now 3G instead of WIFI.
  However, i don't receive any NetworkingStatus::limitationsChanged. Is
  it working properly?. I tested on Krillin and Arale with same result.

  [1] https://developer.ubuntu.com/api/devel/ubuntu-14.10/cplusplus
  /connectivity-
  
api/classubuntu_1_1connectivity_1_1NetworkingStatus.html#a8f5c697c65d6f742f86f21c654aca0a8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545673/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1541210] Re: Photos are displayed as 90 degree rotated in photo roll

[Lorn Potter]

Sent a private email of photos of the device to Florian detailing the
problem with photoroll.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1541210

Title:
  Photos are displayed as 90 degree rotated in photo roll

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  On some devices where the camera is such that the Orientation exif
  data gets written  "Orientation |Right-top", as on Turbo.

  The camera app has problems showing the photo in the photo roll. Gallery also 
has this problem. Other apps will show it normally.
  The camera app view finder shows it as it should.

  When taking photo is portrait mode, the photo roll shows it rotated
  wrong.

  When taking photo in landscape mode, the photo roll shows it properly.

  The "My Photos" scope shows both portrait and landscape taken photos
  properly.

  ---

  This also affects photos transferred from elsewhere to the phone and
  viewed in Gallery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1541210/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1197542] Re: System Info module not integrated with platform

[Lorn Potter]

** Changed in: qtsystems-opensource-src (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1197542

Title:
  System Info module not integrated with platform

Status in Ubuntu UI Toolkit:
  Invalid
Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  The DeviceInfo item provides correct information for some functions on both 
desktop and Touch
  The BatteryInfo items do not yield correct results in any case.
  Did not try the other interfaces 

  libqt5systeminfo5:
Installed: 5.0~git20130123-0ubuntu1~test2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1197542/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1131765] Re: QML Accelerometer is always (useless) dummy.accelerometer

[Lorn Potter]

This actually might be a packaging issue, if the device does not get a
real /etc/xdg/QtProject/Sensors.conf that tells QtSensors to use the
dummy sensor backend.

Bug is 3 years old, so I assume it has been fixed.


** Changed in: qtsensors-opensource-src (Ubuntu)
   Status: New => Invalid

** Changed in: qtsensors-opensource-src (Ubuntu)
   Status: Invalid => New

** Changed in: qtsensors-opensource-src (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsensors-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1131765

Title:
  QML Accelerometer is always (useless) dummy.accelerometer

Status in qtsensors-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Tested on gnex, nex4 phones. Using QML to create the Accelerometer,
  the identified device is "dummy.accelerometer" and it returns no
  useful data (static x:0, y:g (aka 9.81m/s), z:0).

  Snippet:

  Row {
  Label {
  text: "Accel: "
  fontSize: "large"
  }
  Label {
  id: sensor
  text: "..."
  fontSize: "large"
  }
  }
  Accelerometer {
  id: accel
  onReadingChanged: { sensor.text = accel.identifier; stop() }
  active: true
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsensors-opensource-src/+bug/1131765/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1545619] Re: Replace qnam-ubuntu-fix6.patch with upstreamed patches

[Lorn Potter]

Upstream Qt version will be at least 5.6.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1545619

Title:
  Replace qnam-ubuntu-fix6.patch with upstreamed patches

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is a reminder that for the Ubuntu archive version of qtbase, the
  qnam-ubuntu-fix6.patch should eventually be replaced with merged to
  upstream solution. Vivid-overlay can keep using the patch since it has
  been well tested by now.

  A portion of qnam-ubuntu-fix6.patch is currently being upstreamed at
  https://codereview.qt-project.org/#/c/148280/. Additionally qnam-
  ubuntu-fix6.patch touches src/network/access/qnetworkreplyhttpimpl.cpp
  and the network manager bearer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1545619/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

Alrighty then! patch #6
This seems to work with Today, euronews scopes, and doesn't hang!

** Patch added: "qnam-ubuntu-fix6.patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1528886/+attachment/4566541/+files/qnam-ubuntu-fix6.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  In Progress
Status in Today Scope:
  New
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

The Euronews scope also seems to have network issues, so maybe the scope
scope-aggregator  has issues with this. I'll dig into that code to see
if I can find something. At least a way to test this condition.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  In Progress
Status in Today Scope:
  New
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1288777] Re: Qt bearer thread requires otherwise unneeded internet access

[Lorn Potter]

Fixes in QtBearer network-manager backend in the OTA 8.5 release should
have fixed apparmor denials when using QtNetwork & friends.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1288777

Title:
  Qt bearer thread requires otherwise unneeded internet access

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  When comparing Qt5.0 denials with Qt5.2 denials on test runs that popey did, 
it looks like Qt5.2 changed its behavior such that the Qt bearer thread 
requires otherwise unneeded internet access. Eg, 'permy' from the appstore does 
not (and should not) use the "networking" policy group. On 5.0, launching it 
causes no apparmor denials. On 5.2, it does:
  Feb 25 REDACT ubuntu-phablet kernel [REDACT] type=1400 audit(REDACT) 
apparmor="DENIED" operation="create" parent= 
profile="com.ubuntu.developer.jdstrand.permy_permy_0.5" pid= 
comm=517420626561726572207468726561 family="inet" sock_type="dgram" protocol=0

  Permy's source is at lp:permy. Note, one other application besides permy had 
similar denials:
  Feb 25 REDACT ubuntu-phablet kernel [REDACT] type=1400 audit(REDACT) 
apparmor="DENIED" operation="create" parent= 
profile="org.sambull.eo-dict_eo-dict_0.2" pid= 
comm=517420626561726572207468726561 family="inet" sock_type="dgram" protocol=0

  This may seem like it isn't important-- the apparmor policy doesn't
  say it is allowed to connect to the network and apparmor correctly
  blocks it. I don't know if the app is adversely affected though (these
  aren't my logs). It might be, and even if it isn't, the noisy denial
  will lead to confusion (we can't explicitly deny networking in its
  policy to silence the denial due to how apparmor policy works).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1288777/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false

[Lorn Potter]

If this is still an issue Silo 032 currently has a fix for this. Using
this set of patches I do not recall having any issues with isOpen

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1404188

Title:
  QNetworkSession::isOpen() always returns false

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print "all is well".
  On a vivid phone however, it'll print "network session not open..."

  This used to work fine at least back in utopic images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1541686] [NEW] apparmor denials with using XMLHttpRequest

[Lorn Potter]

Public bug reported:

I just tried an example app with code from:
http://doc.qt.io/qt-5/qtqml-xmlhttprequest-get-qml.html


QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.DBus.Properties" member="GetAll" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.NetworkManager" member="GetDevices" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
"Object path cannot be empty"
file:///opt/click.ubuntu.com/get.lorn-potter/0.1/Main.qml:61: TypeError: Cannot 
read property 'documentElement' of null

The calls GetAll and GetDevices are used in the QtBearer network manager
backend.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1541686

Title:
  apparmor denials with using XMLHttpRequest

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  I just tried an example app with code from:
  http://doc.qt.io/qt-5/qtqml-xmlhttprequest-get-qml.html

  
  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.DBus.Properties" member="GetAll" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.NetworkManager" member="GetDevices" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
  "Object path cannot be empty"
  file:///opt/click.ubuntu.com/get.lorn-potter/0.1/Main.qml:61: TypeError: 
Cannot read property 'documentElement' of null

  The calls GetAll and GetDevices are used in the QtBearer network
  manager backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1541686/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1541686] Re: apparmor denials with using XMLHttpRequest

[Lorn Potter]

This could be fixed by moving to using a QtBearer backend based on
connectivity-api.

But I think that API is too sparse at the moment for a completely
working QtBearer.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1541686

Title:
  apparmor denials with using XMLHttpRequest

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  I just tried an example app with code from:
  http://doc.qt.io/qt-5/qtqml-xmlhttprequest-get-qml.html

  
  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.DBus.Properties" member="GetAll" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.107" (uid=32011 pid=7239 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ M") 
interface="org.freedesktop.NetworkManager" member="GetDevices" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1309 comm="NetworkManager ")"
  "Object path cannot be empty"
  file:///opt/click.ubuntu.com/get.lorn-potter/0.1/Main.qml:61: TypeError: 
Cannot read property 'documentElement' of null

  The calls GetAll and GetDevices are used in the QtBearer network
  manager backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1541686/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1470700] Re: QNetworkAccessManager hangs when in flight mode

[Lorn Potter]

Tested this using 032 and with the attached code and no longer hangs:

phablet@ubuntu-phablet:~/1470700$ ./1470700 http://google.com
2016-02-04T04:23:50 (unknown:0) - Starting request
2016-02-04T04:23:50 (unknown:0) - QNAM finished: 
QNetworkReplyHttpImpl(0x19910b8)
2016-02-04T04:23:50 (unknown:0) - Error state: 0 "Unknown error"

302 Moved
302 Moved
The document has moved
http://www.google.com.au/?gfe_rd=crei=tkWyVq7xG6_u8weY775I;>here.


2016-02-04T04:23:50 (unknown:0) - Done. Sleeping 5 seconds
2016-02-04T04:23:55 (unknown:0) - Starting request
2016-02-04T04:23:55 (unknown:0) - "Method "GetAll" with signature "s" on 
interface "org.freedesktop.DBus.Properties" doesn't exist
"
2016-02-04T04:23:55 (unknown:0) - QNAM finished: 
QNetworkReplyHttpImpl(0x19a8a80)
2016-02-04T04:23:55 (unknown:0) - QNAM finished: 
QNetworkReplyHttpImpl(0x19a8a80)
2016-02-04T04:23:55 (unknown:0) - Error state: 8 "Network session error."

2016-02-04T04:23:55 (unknown:0) - QNetworkReplyImplPrivate::error: Internal 
problem, this method must only be called once.
2016-02-04T04:23:55 (unknown:0) - Done. Sleeping 5 seconds
2016-02-04T04:23:55 (unknown:0) - "Method "GetAll" with signature "s" on 
interface "org.freedesktop.DBus.Properties" doesn't exist
"
2016-02-04T04:24:00 (unknown:0) - Starting request
2016-02-04T04:24:00 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198da88)
2016-02-04T04:24:00 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198da88)
2016-02-04T04:24:00 (unknown:0) - Error state: 99 "Network access is disabled."
2016-02-04T04:24:00 (unknown:0) - QIODevice::read: device not open

2016-02-04T04:24:00 (unknown:0) - Done. Sleeping 5 seconds
2016-02-04T04:24:05 (unknown:0) - Starting request
2016-02-04T04:24:05 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198da88)
2016-02-04T04:24:05 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198da88)
2016-02-04T04:24:05 (unknown:0) - Error state: 99 "Network access is disabled."
2016-02-04T04:24:05 (unknown:0) - QIODevice::read: device not open

2016-02-04T04:24:05 (unknown:0) - Done. Sleeping 5 seconds
2016-02-04T04:24:10 (unknown:0) - Starting request
2016-02-04T04:24:10 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198da88)
2016-02-04T04:24:10 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198da88)
2016-02-04T04:24:10 (unknown:0) - Error state: 99 "Network access is disabled."
2016-02-04T04:24:10 (unknown:0) - QIODevice::read: device not open

2016-02-04T04:24:10 (unknown:0) - Done. Sleeping 5 seconds
2016-02-04T04:24:15 (unknown:0) - Starting request
2016-02-04T04:24:15 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198c000)
2016-02-04T04:24:15 (unknown:0) - QNAM finished: 
QDisabledNetworkReply(0x198c000)
2016-02-04T04:24:15 (unknown:0) - Error state: 99 "Network access is disabled."
2016-02-04T04:24:15 (unknown:0) - QIODevice::read: device not open

2016-02-04T04:24:15 (unknown:0) - Done. Sleeping 5 seconds
2016-02-04T04:24:20 (unknown:0) - Starting request
2016-02-04T04:24:20 (unknown:0) - QNAM finished: 
QNetworkReplyHttpImpl(0x1992938)
2016-02-04T04:24:20 (unknown:0) - Error state: 0 "Unknown error"

302 Moved
302 Moved
The document has moved
http://www.google.com.au/?gfe_rd=crei=1EWyVvaAO7Hu8wfFj6DQCA;>here.


-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1470700

Title:
  QNetworkAccessManager hangs when in flight mode

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Triaged
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  Testing the fix:

  - Update rc-proposed (vivid) to citrain device-upgrade 32 
  - Optional: If you want to test using the 'generic' bearer plugin instead of 
the Network Manager bearer, either do not upgrade ubuntu-touch-session or move 
away the file /etc/profile.d/qt_networkmanager_bearer.sh
  - Reboot

  ---

  When my phone is in flight mode, HTTP requests made using
  QNetworkAccessManager seem to hang rather than erroring out
  immediately.

  From my tests, it looks like the HTTP request is blocked until the
  flight mode is disabled and a network connection is reestablished.
  This is contrary to the documentation, which states:

  """If the network is not accessible the network access manager will
  not process any new network requests, all such requests will fail with
  an error. Requests with URLs with the file:// scheme will still be
  processed."""

  http://doc.qt.io/qt-5/qnetworkaccessmanager.html#networkAccessible-
  prop

  By running strace on my test program, it doesn't even look like it
  attempts to open a TCP connection when blocked in flight mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1470700/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

Still working for me!

How to test this:

Open system settings and click on Updates and then quickly switch wifi
off or on

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  In Progress
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

One more time...
This one works better in that is doesn't sit and spin. It will at least say 
"connect to the internet" when the connection changes.

** Patch added: "qnam-ubuntu-fix5.patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1528886/+attachment/4561759/+files/qnam-ubuntu-fix5.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  In Progress
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1197542] Re: System Info module not integrated with platform

[Lorn Potter]

another note to self: /etc/machine-info

** Changed in: qtsystems-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
in Ubuntu.
https://bugs.launchpad.net/bugs/1197542

Title:
  System Info module not integrated with platform

Status in Ubuntu UI Toolkit:
  Invalid
Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  The DeviceInfo item provides correct information for some functions on both 
desktop and Touch
  The BatteryInfo items do not yield correct results in any case.
  Did not try the other interfaces 

  libqt5systeminfo5:
Installed: 5.0~git20130123-0ubuntu1~test2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1197542/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

grrr... At least I can reliably reproduce this:

Start with wifi off and system settings open.
have adb shell or ssh into device.

check for updates
quickly run the command: nmcli radio wifi on

Update should either complete or have an error and should not get stuck
at "checking for updates..."

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

Just tested fix2 package, does not seem to be working entirely correct yet. 
Maybe I missed something in that patch.
It seems to report isOnline is false, quickly followed by true, which seems to 
confuse things...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

alright, attached is yet another fixup. I used quilt this time, so it
should be about good to go.

The only thing I have not really tested is when only connected to mobile data, 
and the connection is bad or weak, and it keeps disconnecting and disconnects 
in the middle of an update request.
It seems when I want to test it this way, I will have good reception. I will 
keep trying and test it when the opportunity arrives.

** Patch added: "qnam-ubuntu-fix3.patch"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+attachment/4554516/+files/qnam-ubuntu-fix3.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

2nd patch here that I am fairly certain fixes this in QNAM as well as in
the nm bearer plugin (making the defaultConfiguration switch when
default connection actually changes). It also optimizes the bearer
plugin a bit.

I have an auto test to be run on a phone to test for this, but I haven't
put it anywhere just yet.


** Patch added: "qnam-ubuntu-fix2.patch"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+attachment/4553861/+files/qnam-ubuntu-fix2.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false

[Lorn Potter]

I tried a working connectivity-api bearer plugin (verified with
unconfined test app) with the attached example app, and I still got app
armor errors:

Syslog> Jan 21 06:55:34 ubuntu-phablet dbus[1809]: apparmor="DENIED"
operation="dbus_method_call"  bus="session"
path="/com/ubuntu/connectivity1/NetworkingStatus"
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send"
name="com.ubuntu.connectivity1" pid=11241
label="com.ubuntu.developer.mzanetti.nmsessiontest_myapp_0.1"
peer_pid=2631 peer_label="unconfined"

Even if we wanted to move to connectivity-api, we would need to fix
those.

After looking further atks the connectivity-api, it is quite limited and
cannot even detect when network is using mobile data or wifi.

We could:
* Use connectivity-api knowing that bearer functionality will be mostly broken, 
but should allow basic bearer use, and allow QNAM & friends to function 
unhindered.

* add some functionality to connectivity-api

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1404188

Title:
  QNetworkSession::isOpen() always returns false

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print "all is well".
  On a vivid phone however, it'll print "network session not open..."

  This used to work fine at least back in utopic images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1404188] Re: QNetworkSession::isOpen() always returns false

[Lorn Potter]

After adding 'connectivity' to the manifest, it is working with
connectivity-api plugin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1404188

Title:
  QNetworkSession::isOpen() always returns false

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print "all is well".
  On a vivid phone however, it'll print "network session not open..."

  This used to work fine at least back in utopic images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1404188/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

seems #2 in comment #34 still is not fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

1) QNAM was only being signalled when the online state of nm changed. Since 
mobile data remains online when wifi connects, the online state never changes 
when the default route moves to wifi. Thus QNAM/QNetworkRequest was not 
following the correct configuration/session. The session would never signal the 
connected state (because it was already connected and didn't change) This means 
that the request would never migrate/resume to new connection, and would wait 
for proper session state to actually start the operation, which would never 
come. 

Haven't looked into why it would not timeout in a reasonable amount of
time.

2) Sometimes QNAM would get confused by #1 and set itself to
NotAccessible, thus blocking the request and issuing error 99
(UnknownNetworkError)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

[Lorn Potter]

I believe I have fixed this against landing-032, patch attached

It needs more testing, including upstream autotests.




** Patch added: "qnam-ubuntu-fix.diff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1528886/+attachment/4548354/+files/qnam-ubuntu-fix.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1528886

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp