[Touch-packages] [Bug 1629782] Re: Hotspot crashes the device and reboots

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

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

-- 
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/1629782

Title:
  Hotspot crashes the device and reboots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  The device hangs and reboots after some tasks related to hotspot.

  There are a couple of ways that this bug occurred.

  1. While the hotspot is on, try to change hotspot settings like
  requiring passwords. Upon clicking the Change button, the bug occurs.
  (happens always)

  2. Turning on the hotspot from the settings app while the wifi is off
  the bug occurs. (happened once)

  
  Not sure what log will be helpful. Please let me know and I'll attach them.

  Device:
  bq E5 HD (OTA 13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629782/+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 1447748] Re: SIM unlock screen unusable when launched from indicator

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

-- 
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/1447748

Title:
  SIM unlock screen unusable when launched from indicator

Status in indicator-network package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The SIM lock screen behaves differently during boot and launching it
  from indicator network. Mostly unusable from indicator to unlock PIN
  (those were the failures reported below).

  Test case.
  - Reboot the phone with a valid SIM card.
  - Unlock the device.
  - Dismiss the PIN unlock screen.
  - Open the network indicator.
  - Tap on unlock SIM card.
  - Introduce incorrect PINs.

  Expected result.
  - The behaviour is the same as when the SIM unlock page is run on boot time.

  Actual result.
  - The number of remaining PIN trials is not correctly shown.
  - When the PIN is locked, no PUK lock screen is shown. Must be closed and 
opened (tap on unlock SIM card in indicator) to be shown.
  - After PUK has been correctly introduced, PIN screen should be shown. It is 
not.
  - Close and re-open the screen does show the PIN screen to introduce the new 
one.

  Tested with vivid-proposed 183 / Arale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447748/+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 1589149] Re: the two Hotspots buttons seem to disagree

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/1589149

Title:
  the two Hotspots buttons seem to disagree

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  When i try to activate the hotspot using the menu that you can make appear 
from above (the black-background one) it seems not to work (no hotspot and no 
hotspot symbol on the top menu appearing).
  If I open setting->hotspot, there the hotspot button is deactivated (not 
green) while the hotspot button in the black menu is green.
  It seems the button in the Settings if activated can really make the hotspot 
work (and make the hotspot button in the black menu green) but the hotspot 
button in the black menu seems to just do nothing (except cutting wifi)

  
  On the meizu 4 with ota 11. I think the problem came with ota 11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589149/+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 1412716] Re: [dash] Make Soundcloud scope background "waveform" lighter

[Pete Woods]

** Changed in: unity-scope-soundcloud
 Assignee: Pete Woods (pete-woods) => (unassigned)

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

Title:
  [dash] Make Soundcloud scope background "waveform" lighter

Status in Ubuntu UX:
  Fix Committed
Status in Unity SoundCloud Scope:
  New
Status in unity-scope-soundcloud package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  We would love to change the color of the design in the streaming as
  the image attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1412716/+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 1280372] Re: Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

[Pete Woods]

** No longer affects: hud

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

Title:
  Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

Status in libdbusmenu-qt:
  Fix Released
Status in hud package in Ubuntu:
  Fix Released
Status in libdbusmenu-qt package in Ubuntu:
  Fix Released

Bug description:
  See the following debug output:
  * http://paste.ubuntu.com/6931329/
  * http://paste.ubuntu.com/6931331/
  * http://paste.ubuntu.com/6931338/
  * http://paste.ubuntu.com/7151579/

  14:09:09 QVariantMap DBusMenuExporterDBus::getProperties(int, const 
QStringList&) const: Condition failed: action
  14:09:09 bool DBusMenuExporterDBus::AboutToShow(int): Condition failed: menu

  Was also seen in the console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libdbusmenu-qt/+bug/1280372/+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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1425172

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in Canonical System Image:
  Fix Released
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+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 1567250] Re: ssh signin problem since OTA-10

[Pete Woods]

** Changed in: gnome-keyring (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: indicator-network (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

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

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Incomplete
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+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 1452567] Re: Wifi icon disappears at the first connection with a hidden network

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

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

-- 
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/1452567

Title:
  Wifi icon disappears at the first connection with a hidden network

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  $ system-image-cli -i
  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-05-07 02:27:02
  version version: 274
  version ubuntu: 20150505
  version device: 20150505-db7b5bd
  version custom: 20150505-682-29-215

  Steps to reproduce the issue:
  1.Tap Wifi settings
  2.Select 'Connect to hidden network…
  3.Enter the SSID and correct password for the network

  Expected results:
  The icon should be shown in the network indicator even if a hidden network is 
connected

  Actual results:
  Wifi icon disappears when connecting to a hidden network on the first try, 
and the SSID is invisible too,
  Both the wifi icon and SSID will appear after forget and re-connect.

  Not sure if it is a regression of issue
  https://bugs.launchpad.net/barajas/+bug/1404195

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452567/+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 1339792] Re: Panel network icon - too much latency when network type changes

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: indicator-network (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

** Changed in: indicator-network (Ubuntu RTM)
   Status: Confirmed => Won't Fix

** Changed in: ofono (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ofono (Ubuntu Utopic)
   Status: Confirmed => Won't Fix

** Changed in: ofono (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

-- 
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/1339792

Title:
  Panel network icon - too much latency when network type changes

Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ofono package in Ubuntu:
  Won't Fix
Status in indicator-network source package in Utopic:
  Won't Fix
Status in ofono source package in Utopic:
  Won't Fix
Status in indicator-network source package in Vivid:
  Won't Fix
Status in ofono source package in Vivid:
  Won't Fix
Status in indicator-network package in Ubuntu RTM:
  Won't Fix

Bug description:
  Testing image #u122 this morning, I ran into two separate scenarios
  where the panel network icon didn't always accurately reflect the
  current network technology due to some kind of latency detecting
  network changes ( ie. WiFi -> 3G -> WiFi ).

  Both scenarios were reproduced on mako.

  Scenario 1:

  3G: online
  WiFi: enabled; connected to AP 1

  - display network menu
  - tap another secure network
  - tap cancel when Password dialog is displayed

  At this point the indicator shows '3G' whereas the network menu still
  shows the original AP 1 as connected.  After some period of time ( 10s
  - 1m ), the icon will change back to show that WiFi is connected.

  Scenario 2:

  3G: online
  WiFi: connected to AP 1

  - go to System Settings::WiFi
  - click "Previous Networks"
  - select the currently connected AP/network
  - click Forget Network
  - go back to WiFi settings

  The WiFi settings correctly shows the AP is no longer connected,
  however again the network icon takes some time ( 10s - 1m ) to reflect
  the change back to "3G".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop

[Pete Woods]

** Changed in: ufrs-apt
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: hud (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

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

Title:
  hud-service is eating up 100% of one of my CPUs in a poll loop

Status in unbuntu-fr Scripts - apt:
  Confirmed
Status in hud package in Ubuntu:
  In Progress

Bug description:
  hud-service is polling like crazy:

  Context Switches:
PID  ProcessVoluntary   Involuntary Total
   Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
2295 hud-service  46084.6342.94 46127.58 (very high)
2325 hud-service  0.09 0.00 0.09 (very low)
2329 hud-service  0.07 0.00 0.07 (very low)
2340 hud-service  0.05 0.00 0.05 (very low)
   Total  46084.8442.94 46127.78

  File I/O operations:
   No file I/O operations detected.

  System calls traced:
PID  Process  Syscall   CountRate/Sec
2295 hud-service  poll 83   23124.8503
2295 hud-service  write10   0.2313
2295 hud-service  sendmsg   4   0.0925
2325 hud-service  restart_syscall   1   0.0231
2329 hud-service  restart_syscall   1   0.0231
2340 hud-service  restart_syscall   1   0.0231
   Total  100   23125.2435

  (gdb) where
  #0  0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #2  0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #3  0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #4  0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #5  0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #6  0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #7  0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #8  0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2
  #9  0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() ()
  #17 0x00441e43 in hud::service::WindowImpl::activate() ()
  #18 0x00439f6a in 
hud::service::QueryImpl::updateToken(QSharedPointer) ()
  #19 0x0043a672 in hud::service::QueryImpl::refresh() ()
  #20 0x0044b115 in ?? ()
  #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #22 0x0045662a in 
hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString 
const&, unsigned int) ()
  #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #24 0x00467361 in 
ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, 
QString const&, unsigned int) ()
  #25 0x004678bd in ?? ()
  #26 0x00467c63 in 
ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, 
void**) ()
  #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #28 0x7fda8435e22e in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadDa

[Touch-packages] [Bug 1280372] Re: Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

[Pete Woods]

** Changed in: hud
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: libdbusmenu-qt
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: hud (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: libdbusmenu-qt (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

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

Title:
  Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

Status in Unity HUD:
  In Progress
Status in libdbusmenu-qt:
  Fix Released
Status in hud package in Ubuntu:
  Fix Released
Status in libdbusmenu-qt package in Ubuntu:
  Fix Released

Bug description:
  See the following debug output:
  * http://paste.ubuntu.com/6931329/
  * http://paste.ubuntu.com/6931331/
  * http://paste.ubuntu.com/6931338/
  * http://paste.ubuntu.com/7151579/

  14:09:09 QVariantMap DBusMenuExporterDBus::getProperties(int, const 
QStringList&) const: Condition failed: action
  14:09:09 bool DBusMenuExporterDBus::AboutToShow(int): Condition failed: menu

  Was also seen in the console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1280372/+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 1327419] Re: Infographic's language not updated until the metric value is changed

[Pete Woods]

** Changed in: canonical-devices-system-image
 Assignee: Thomas Strehl (strehl-t) => (unassigned)

** Changed in: camera-app (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: music-app
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: libusermetrics (Ubuntu RTM)
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: libusermetrics (Ubuntu)
     Assignee: Pete Woods (pete-woods) => (unassigned)

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

Title:
  Infographic's language not updated until the metric value is changed

Status in Canonical System Image:
  Fix Released
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in camera-app package in Ubuntu:
  In Progress
Status in libusermetrics package in Ubuntu:
  Fix Released
Status in libusermetrics package in Ubuntu RTM:
  Fix Released

Bug description:
  1) Start the music app
  2) Play a track for more than 10 seconds to trigger the metric update
  3) Lock and unlock to show the infographic
  4) Note, for example, "1 song played today" appears (double tap to cycle 
through to find music if required)
  5) Goto system settings and change the language
  6) Restart the device
  7) Note the infographic's language has not been updated and it still states 
'1 song played today'
  8) Start the music app
  9) Play a track for more than 10 seconds to trigger the metric update
  10) Lock and unlock to show the infographic
  11) Now notice the infographic's language is now correct, for example "2 
Morceaux joues aujourd'hui"

  It was expected that step 7 the infographic would show the correct
  language.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1327419/+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 1597681] Re: [CTA] Enable WAPI support

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

-- 
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/1597681

Title:
  [CTA] Enable WAPI support

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+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 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

** Changed in: indicator-session (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in Canonical System Image:
  Fix Released
Status in indicator-session package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670657/+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 1672398] Re: Newly launched Ubuntu Terminal doesn't have keyboard focus

[Pete Woods]

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

** No longer affects: unity8 (Ubuntu)

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

Title:
  Newly launched Ubuntu Terminal doesn't have keyboard focus

Status in Canonical System Image:
  In Progress
Status in ubuntu-terminal-app package in Ubuntu:
  In Progress

Bug description:
  After entering your password at the prompt, you cannot type in the
  Ubuntu Terminal because it doesn't have focus.

  Visually the terminal appears to have focus, but the reality is it
  doesn't.

  As soon as you click on the terminal, you can type normally.

  Unsure if the fault lies with the terminal app or unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672398/+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 1670671] Re: At login, the scopes window sometimes appears outside the screen area

[Pete Woods]

Doesn't seem to happen any more.

** Changed in: unity8 (Ubuntu)
   Status: New => Fix Released

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

Title:
  At login, the scopes window sometimes appears outside the screen area

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unsure as to the trigger, but this happened often after login on a
  fresh Zesty install in Qemu.

  You can't move or resize the window without knowing the super-alt-
  arrow shortcuts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670671/+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 1557716] Re: Support 'phone' profile for indicator-session

[Pete Woods]

** Branch linked: lp:~pete-woods/indicator-session/add-phone-menus

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

Title:
  Support 'phone' profile for indicator-session

Status in indicator-session package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When enabling indicator-session support in unity8, we noticed that it
  doesn't have a phone profile?  And in our haste, we kind of worked one
  together unity8-side by stripping some menu items as they came in.

  But it should be done properly upstream.

  Adding a unity8 task so that we know we can drop our hacks when it's
  fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1557716/+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 1672657] Re: unity::util::unique_gobject() and friends have ambiguous ownership semantics

[Pete Woods]

** Changed in: unity-api (Ubuntu)
   Status: New => In Progress

** Changed in: unity-api (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-api (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  unity::util::unique_gobject() and friends have ambiguous ownership
  semantics

Status in unity-api package in Ubuntu:
  In Progress

Bug description:
  The unique_gobject() helper has ownership semantics that are likely to
  introduce bugs in code using it.  It's current logic is essentially:

   1. if the object passed as an argument has a floating reference, increment 
its ref count.
   2. if not, steal the caller's reference.

  So we can't tell statically whether this function steals a reference
  or creates its own.  This makes it more difficult to reason about code
  using this helper.

  It would be better to choose one of the following:

   1. Always create your own reference, using ref_sink() to sink any floating 
reference.
   2. Always steal the caller's reference.  Treat the presence of a floating 
reference as an
  error, since it indicates that the caller doesn't know if it owns the 
object.

  (1) can be a pain because the caller will need to do a manual unref if
  they pass a newly constructed object to unique_gobject() that doesn't
  have a floating reference.

  (2) means that the caller will need to do their own ref_sink() call if
  they are passing an object they don't actually own a reference to.

  We picked (2) for thumbnailer's gobj_ptr smart pointer class.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-api/+bug/1672657/+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 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

** Branch linked: lp:~pete-woods/unity8/fix-unity-platform-ispc-
lp1670657

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in Canonical System Image:
  Triaged
Status in indicator-session package in Ubuntu:
  In Progress
Status in qmenumodel package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670657/+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 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

** Changed in: qmenumodel (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: unity8 (Ubuntu)
   Status: Triaged => In Progress

** Changed in: indicator-session (Ubuntu)
   Status: Invalid => In Progress

** Changed in: indicator-session (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in Canonical System Image:
  Triaged
Status in indicator-session package in Ubuntu:
  In Progress
Status in qmenumodel package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670657/+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 1672797] Re: indicators-client broken as of r2752

[Pete Woods]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Changed in: unity8 (Ubuntu)
   Status: New => In Progress

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

Title:
  indicators-client broken as of r2752

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Seems there was a bunch of refactoring in the indicator panel that
  didn't include the indicators-client code in
  "qml/Panel/Indicators/client".

  The error is:

  qml: Error:
  
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
  IndicatorPage is not a type

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672797/+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 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

I'm pointing the finger at: http://bazaar.launchpad.net/~unity-
team/unity8/trunk/view/head:/qml/Panel/Indicators/IndicatorMenuItemFactory.qml#L69

** Changed in: indicator-session (Ubuntu)
   Status: New => Invalid

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

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => New

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+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 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

This is starting to look like it's somewhere in unity8 stack - see
attached screenshot of unity7 + indicators-client under Zesty

** Attachment added: "Screenshot_ubuntu-17.04_2017-03-14_16&%53&%43.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+attachment/4837721/+files/Screenshot_ubuntu-17.04_2017-03-14_16%26%2553%26%2543.png

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+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 1672797] [NEW] indicators-client broken as of r2752

[Pete Woods]

Public bug reported:

Seems there was a bunch of refactoring in the indicator panel that
didn't include the indicators-client code in
"qml/Panel/Indicators/client".

The error is:

qml: Error:
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
IndicatorPage is not a type

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- ind
+ indicators-client broken as of r2752

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

Title:
  indicators-client broken as of r2752

Status in unity8 package in Ubuntu:
  New

Bug description:
  Seems there was a bunch of refactoring in the indicator panel that
  didn't include the indicators-client code in
  "qml/Panel/Indicators/client".

  The error is:

  qml: Error:
  
file:///usr/share/unity8//Panel/Indicators/client/IndicatorRepresentation.qml:80
  IndicatorPage is not a type

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672797/+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 1672651] Re: Logging out stuck in a loop (looks like it's trying to kill the terminal)

[Pete Woods]

The weird thing is that the terminal looked like it had actually closed.

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

Title:
  Logging out stuck in a loop (looks like it's trying to kill the
  terminal)

Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I had terminal running, and the dash minimised.

  Then I used the ctrl-alt-del shortcut to bring up the logout menu.

  Then clicked logout.

  

  [2017-03-14:09:06:01.311] qtmir.surfaces: 
MirSurface[0x55ba4f943130,"unity8-dash"]::unregisterView(94258687984992) 
after=0 live=true
  [2017-03-14:09:06:01.312] toplevelwindowmodel: removeAt after 
  [2017-03-14:09:06:01.312] void LauncherModel::applicationRemoved(const 
QModelIndex&, int) appIndex not found
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1672651/+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 1672651] Re: Logging out stuck in a loop (looks like it's trying to kill the terminal)

[Pete Woods]

I guess that's possible. The shell was totally non-responsive.

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

Title:
  Logging out stuck in a loop (looks like it's trying to kill the
  terminal)

Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I had terminal running, and the dash minimised.

  Then I used the ctrl-alt-del shortcut to bring up the logout menu.

  Then clicked logout.

  

  [2017-03-14:09:06:01.311] qtmir.surfaces: 
MirSurface[0x55ba4f943130,"unity8-dash"]::unregisterView(94258687984992) 
after=0 live=true
  [2017-03-14:09:06:01.312] toplevelwindowmodel: removeAt after 
  [2017-03-14:09:06:01.312] void LauncherModel::applicationRemoved(const 
QModelIndex&, int) appIndex not found
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1672651/+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 1672401] Re: Screen goes black for ~13 seconds during login with no indication of progress

[Pete Woods]

I'm not convinced this is a duplicate of that other bug. It takes about
13 seconds for the login here. Which is not the 25 second DBus timeout
you mention.

** Description changed:

  This makes me worry there's something gone wrong on every login.
+ 
+ It's only this slow on a cold boot. It's somewhat faster on a second
+ login.
  
  It'd be nice for there to be something like:
  
  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)
  
  during this time.
  
  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

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

Title:
  Lacks animated transition between greeter and session

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

Bug description:
  This makes me worry there's something gone wrong on every login.

  It's only this slow on a cold boot. It's somewhat faster on a second
  login.

  It'd be nice for there to be something like:

  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)

  during this time.

  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

  == Note ==

  The experience might differ depending on whether you use unity-greeter
  (X11-based, default in 17.04) or unity8-greeter (not installed by
  default yet), which is better suited for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672401/+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 1672651] Re: Logging out stuck in a loop (looks like it's trying to kill the terminal)

[Pete Woods]

** Description changed:

  I had terminal running, and the dash minimised.
  
  Then I used the ctrl-alt-del shortcut to bring up the logout menu.
  
  Then clicked logout.
+ 
+ 
+ 
+ [2017-03-14:09:06:01.311] qtmir.surfaces: 
MirSurface[0x55ba4f943130,"unity8-dash"]::unregisterView(94258687984992) 
after=0 live=true
+ [2017-03-14:09:06:01.312] toplevelwindowmodel: removeAt after 
+ [2017-03-14:09:06:01.312] void LauncherModel::applicationRemoved(const 
QModelIndex&, int) appIndex not found
+ [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
+ [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
+ [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()

** Also affects: ubuntu-app-launch (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

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

Title:
  Logging out stuck in a loop (looks like it's trying to kill the
  terminal)

Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I had terminal running, and the dash minimised.

  Then I used the ctrl-alt-del shortcut to bring up the logout menu.

  Then clicked logout.

  

  [2017-03-14:09:06:01.311] qtmir.surfaces: 
MirSurface[0x55ba4f943130,"unity8-dash"]::unregisterView(94258687984992) 
after=0 live=true
  [2017-03-14:09:06:01.312] toplevelwindowmodel: removeAt after 
  [2017-03-14:09:06:01.312] void LauncherModel::applicationRemoved(const 
QModelIndex&, int) appIndex not found
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()
  [2017-03-14:09:06:01.322] qtmir.applications: 
Application["com.ubuntu.terminal"]::close()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1672651/+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 1672401] Re: Screen goes black for ~13 seconds during login with no indication of progress

[Pete Woods]

*** This bug is a duplicate of bug 1663106 ***
https://bugs.launchpad.net/bugs/1663106

Just to be clear. I don't expect the login to be instantaneous - it
never will be on a slow machine. It just looks bad for the screen to be
black for the whole process.

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

Title:
  Screen goes black for ~13 seconds during login with no indication of
  progress

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  This makes me worry there's something gone wrong on every login.

  It'd be nice for there to be something like:

  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)

  during this time.

  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672401/+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 1672401] Re: Screen goes black for ~13 seconds during login with no indication of progress

[Pete Woods]

*** This bug is a duplicate of bug 1663106 ***
https://bugs.launchpad.net/bugs/1663106


** Summary changed:

- Screen goes black for several seconds during login with no indication of 
progress
+ Screen goes black for ~13 seconds during login with no indication of progress

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672401/+attachment/4837506/+files/unity8.log

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

Title:
  Screen goes black for ~13 seconds during login with no indication of
  progress

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  This makes me worry there's something gone wrong on every login.

  It'd be nice for there to be something like:

  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)

  during this time.

  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672401/+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 1672651] Re: Logging out stuck in a loop (looks like it's trying to kill the terminal)

[Pete Woods]

** Attachment added: "logout freeze.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672651/+attachment/4837505/+files/logout%20freeze.png

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

Title:
  Logging out stuck in a loop (looks like it's trying to kill the
  terminal)

Status in unity8 package in Ubuntu:
  New

Bug description:
  I had terminal running, and the dash minimised.

  Then I used the ctrl-alt-del shortcut to bring up the logout menu.

  Then clicked logout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672651/+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 1672651] Re: Logging out stuck in a loop (looks like it's trying to kill the terminal)

[Pete Woods]

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672651/+attachment/4837504/+files/unity8.log

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

Title:
  Logging out stuck in a loop (looks like it's trying to kill the
  terminal)

Status in unity8 package in Ubuntu:
  New

Bug description:
  I had terminal running, and the dash minimised.

  Then I used the ctrl-alt-del shortcut to bring up the logout menu.

  Then clicked logout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672651/+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 1672651] [NEW] Logging out stuck in a loop (looks like it's trying to kill the terminal)

[Pete Woods]

Public bug reported:

I had terminal running, and the dash minimised.

Then I used the ctrl-alt-del shortcut to bring up the logout menu.

Then clicked logout.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Logging out stuck in a loop (looks like it's trying to kill the
  terminal)

Status in unity8 package in Ubuntu:
  New

Bug description:
  I had terminal running, and the dash minimised.

  Then I used the ctrl-alt-del shortcut to bring up the logout menu.

  Then clicked logout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1672651/+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 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Pete Woods]

** Summary changed:

- No log out option in unity8 in Qemu VM
+ No log out option in session indicator in unity8 in Qemu VM

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+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 1670657] Re: No log out option in unity8 in Qemu VM

[Pete Woods]

I'm looking through the indicator-session code now, to try and figure
out what determines the visibility of this option, but it's not leapt
out at my yet.

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

Title:
  No log out option in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+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 1670657] Re: No log out option in unity8 in Qemu VM

[Pete Woods]

That's true, but the indicator doesn't show a log out option. It does
inside unity7, running exactly the same code, and presumably exporting
the exact same menu.

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

Title:
  No log out option in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+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 1670657] Re: No log out option in unity8 in Qemu VM

[Pete Woods]

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

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

Title:
  No log out option in unity8 in Qemu VM

Status in indicator-session package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1670657/+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 1672398] [NEW] Newly launched Ubuntu Terminal doesn't have focus

[Pete Woods]

Public bug reported:

After entering your password at the prompt, you cannot type in the
Ubuntu Terminal because it doesn't have focus.

Visually the terminal appears to have focus, but the reality is it
doesn't.

As soon as you click on the terminal, you can type normally.

Unsure if the fault lies with the terminal app or unity8.

** Affects: ubuntu-terminal-app (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: unity8-desktop

** Also affects: ubuntu-terminal-app (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

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

Title:
  Newly launched Ubuntu Terminal doesn't have focus

Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  After entering your password at the prompt, you cannot type in the
  Ubuntu Terminal because it doesn't have focus.

  Visually the terminal appears to have focus, but the reality is it
  doesn't.

  As soon as you click on the terminal, you can type normally.

  Unsure if the fault lies with the terminal app or unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-terminal-app/+bug/1672398/+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 1672392] [NEW] Install an app from Ubuntu Terminal and it doesn't show up in the app drawer

[Pete Woods]

Public bug reported:

On a fresh Zesty Qemu VM, I installed dconf-editor from the archive
using the terminal.

  sudo apt install dconf-editor

and it didn't show up in the app drawer, either in the scrollable list
or searching by name.

After a reboot (can't logout due to bug #1670657) dconf-editor is there.

** Affects: ubuntu-app-launch (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: unity8-desktop

** Also affects: ubuntu-app-launch (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

** Description changed:

  On a fresh Zesty Qemu VM, I installed dconf-editor from the archive
  using the terminal.
  
-   sudo apt install dconf-editor
+   sudo apt install dconf-editor
  
  and it didn't show up in the app drawer, either in the scrollable list
  or searching by name.
+ 
+ After a reboot (can't logout due to bue #1670657) dconf-editor is there.

** Description changed:

  On a fresh Zesty Qemu VM, I installed dconf-editor from the archive
  using the terminal.
  
    sudo apt install dconf-editor
  
  and it didn't show up in the app drawer, either in the scrollable list
  or searching by name.
  
- After a reboot (can't logout due to bue #1670657) dconf-editor is there.
+ After a reboot (can't logout due to bug #1670657) dconf-editor is there.

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

Title:
  Install an app from Ubuntu Terminal and it doesn't show up in the app
  drawer

Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  On a fresh Zesty Qemu VM, I installed dconf-editor from the archive
  using the terminal.

    sudo apt install dconf-editor

  and it didn't show up in the app drawer, either in the scrollable list
  or searching by name.

  After a reboot (can't logout due to bug #1670657) dconf-editor is
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1672392/+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 1671095] Re: Indicator menus difficult to navigate on desktop [design]

[Pete Woods]

Ha. It just hides the left-most stuff. Clearly Apple think this scenario
is so unlikely they don't try and handle it too cleverly.

To be fair I did have to set the resolution to 720p (the lowest it will
go) and spend 10 minutes finding new indicators to add, and showing
"full date, including seconds" in the time indicator.

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

Title:
  Indicator menus difficult to navigate on desktop [design]

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space due to having large fonts, and lots of padding. The black menu 
background also extends right to the bottom of the screen, which is likely to 
look a bit ridiculous on e.g. a 27" 4K monitor. Opinion: I would definitely be 
in favor of the indicator menus only taking as much vertical screen space as 
they require - like traditional drop-down menus. Or, indeed, Gnome 3's 
indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671095/+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 1671095] Re: Indicator menus difficult to navigate on desktop [design]

[Pete Woods]

I like those designs :)

May we could have clickable arrows to scroll the region left and right
in the case the screen resolution was too low to show them all?

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

Title:
  Indicator menus difficult to navigate on desktop [design]

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space due to having large fonts, and lots of padding. The black menu 
background also extends right to the bottom of the screen, which is likely to 
look a bit ridiculous on e.g. a 27" 4K monitor. Opinion: I would definitely be 
in favor of the indicator menus only taking as much vertical screen space as 
they require - like traditional drop-down menus. Or, indeed, Gnome 3's 
indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671095/+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 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_m

[Pete Woods]

** Tags added: unity8-desktop

-- 
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/1560498

Title:
  Unity8 using vmwgfx_dri.so crashed in
  mir::graphics::nested::detail::DisplayBuffer::make_current() ->
  eglMakeCurrent() -> ... -> dri2_image_get_buffers()
  [platform_mir.c:138]

Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

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+16.04.20160310.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1560498/+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 1670679] Re: Lock screen only becomes visible after moving the pointer

[Pete Woods]

** Tags added: vm

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

Title:
  Lock screen only becomes visible after moving the pointer

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This means you can see the screen contents until you move the pointer.

  Presumably nothing is triggering a screen redraw when the lock screen
  becomes active (at least in a qemu VM).

  This has the potential to leave personal information if an attacker
  knows not to touch the pointer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670679/+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 1671095] Re: Indicator menus difficult to navigate on desktop

[Pete Woods]

** Description changed:

  I've tried to include some screenshots here, to illustrate my point.
- 
  
  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.
  
  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.
  
  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.
  
  Menu size:
- As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.
+ As you can see in #4, the indicator menu entries take up large amounts of 
screen space due to having large fonts, and lots of padding. The black menu 
background also extends right to the bottom of the screen, which is likely to 
look a bit ridiculous on e.g. a 27" 4K monitor. Opinion: I would definitely be 
in favor of the indicator menus only taking as much vertical screen space as 
they require - like traditional drop-down menus. Or, indeed, Gnome 3's 
indicators.

** Attachment added: "Gnome 3 indicator"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+attachment/4833817/+files/oTntk.png

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

Title:
  Indicator menus difficult to navigate on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space due to having large fonts, and lots of padding. The black menu 
background also extends right to the bottom of the screen, which is likely to 
look a bit ridiculous on e.g. a 27" 4K monitor. Opinion: I would definitely be 
in favor of the indicator menus only taking as much vertical screen space as 
they require - like traditional drop-down menus. Or, indeed, Gnome 3's 
indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+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 1661557] Re: Touch tutorial is inescapable on desktop (without a touchscreen)

[Pete Woods]

Would it also be possible to make the tutorial dismissable with the
escape key, or by clicking a close button. Just because I might have a
touchscreen, doesn't mean I don't have a keyboard, for example.

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

Title:
  Touch tutorial is inescapable on desktop (without a touchscreen)

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The touch tutorial is inescapable on desktop (without a touchscreen).

  I somehow accidentally started Unity8 in touch mode and could use it
  with a mouse. However after a short while (bug 1607176) the tutorial
  starts, and there I'm stuck.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1661557/+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 1671095] Re: Indicator menus difficult to navigate on desktop

[Pete Woods]

** Description changed:

- _
+ I've tried to include some screenshots here, to illustrate my point.
+ 
+ 
+ Pointer displacement:
+ First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.
+ 
+ Horizontal scrolling:
+ As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.
+ 
+ Hidden indicators:
+ Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.
+ 
+ Menu size:
+ As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

** Tags added: u8-desktop

** Tags removed: u8-desktop
** Tags added: unity8-desktop

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

Title:
  Indicator menus difficult to navigate on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  
  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+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 1671095] Re: Indicator menus difficult to navigate on desktop

[Pete Woods]

** Attachment added: "Screenshot_ubuntu-17.04_2017-03-08_13&%34&%59.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+attachment/4833775/+files/Screenshot_ubuntu-17.04_2017-03-08_13%26%2534%26%2559.png

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

Title:
  Indicator menus difficult to navigate on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  
  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+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 1671095] Re: Indicator menus difficult to navigate on desktop

[Pete Woods]

** Attachment added: "Screenshot_ubuntu-17.04_2017-03-08_13&%34&%29.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+attachment/4833774/+files/Screenshot_ubuntu-17.04_2017-03-08_13%26%2534%26%2529.png

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

Title:
  Indicator menus difficult to navigate on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  
  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+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 1671095] Re: Indicator menus difficult to navigate on desktop

[Pete Woods]

** Attachment added: "Screenshot_ubuntu-17.04_2017-03-08_13&%33&%36.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+attachment/4833773/+files/Screenshot_ubuntu-17.04_2017-03-08_13%26%2533%26%2536.png

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

Title:
  Indicator menus difficult to navigate on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  
  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+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 1671095] Re: Indicator menus difficult to navigate on desktop

[Pete Woods]

** Attachment added: "Screenshot_ubuntu-17.04_2017-03-08_13&%33&%02.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+attachment/4833772/+files/Screenshot_ubuntu-17.04_2017-03-08_13%26%2533%26%2502.png

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

Title:
  Indicator menus difficult to navigate on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  
  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+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 1671095] [NEW] Indicator menus difficult to navigate on desktop

[Pete Woods]

Public bug reported:

I've tried to include some screenshots here, to illustrate my point.


Pointer displacement:
First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

Horizontal scrolling:
As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

Hidden indicators:
Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind the 
horizontal scrolling region.

Menu size:
As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: unity8-desktop

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

Title:
  Indicator menus difficult to navigate on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I've tried to include some screenshots here, to illustrate my point.

  
  Pointer displacement:
  First I click on the network indicator in #1, then I end up in #2. In this 
case, while I have clicked on the network indicator, what is now under my 
pointer is the battery indicator.

  Horizontal scrolling:
  As you can see in #3, to see all the indicators I must scroll horizontally by 
revving the trackpad left to right. This is a rather uncomfortable and 
unfamiliar gesture.

  Hidden indicators:
  Finding, e.g. the bluetooth indicator, is rather fiddly when hidden behind 
the horizontal scrolling region.

  Menu size:
  As you can see in #4, the indicator menu entries take up large amounts of 
screen space, and also extend right to the bottom of the screen. Opinion: I 
would definitely be in favor of the indicator menus only taking as much 
vertical screen space as they require - like traditional drop-down menus. Or, 
indeed, Gnome 3's indicators.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1671095/+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 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input

[Pete Woods]

I'm not totally convinced that this bug is about relative pointer
movement. For example, if I leave the pointer at one corner of the
virtual screen, then move it outside and all the way around the edge,
then move it back inside the virtual screen at the opposite corner, the
virtual pointer moves more or less to the bottom right.

Also, given that the pointers gradually calibrate and move more closely
in sync with each other, it feels like there's some "estimate" for the
mapping between the size of the graphics tablet and the screen that is
improving as you increase the range of coordinates that U8 has sampled.

-- 
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/1670670

Title:
  Unity8 pointer does not stay in sync with Qemu VM tablet input

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Each time you login, or come back from the lock screen, you need to
  "recalibrate" the pointer by carefully moving the pointer into each
  corner.

  Contrast this with unity7, where the absolute position of the virtual
  tablet pointer is tracked, and sync is never lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670670/+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 1670679] Re: Lock screen only becomes visible after moving the pointer

[Pete Woods]

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => New

** Changed in: canonical-devices-system-image
   Status: Incomplete => New

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

Title:
  Lock screen only becomes visible after moving the pointer

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This means you can see the screen contents until you move the pointer.

  Presumably nothing is triggering a screen redraw when the lock screen
  becomes active (at least in a qemu VM).

  This has the potential to leave personal information if an attacker
  knows not to touch the pointer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670679/+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 1670655] Re: Launcher hidden by default on desktop

[Pete Woods]

** Tags added: unity8-desktop

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

Title:
  Launcher hidden by default on desktop

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  This makes it tough for a new user to know how to start an app (have
  to know to use the left edge gesture, or use super-a).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670655/+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 1670652] Re: No way to contain pointer in VM window

[Pete Woods]

Well, for example when you run fullscreen, your pointer *is* locked to
the edges. Unfortunately I can't test this works in those cases, as the
VM screen resolution doesn't match the aspect ratio of the real screen
4:3 instead of 16:10 (due to a different bug), so there are black bars
down the sides.

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

Title:
  No way to contain pointer in VM window

Status in Canonical System Image:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  In a Qemu VM, the unity8 side gestures (for the launcher and app
  switcher) cannot be activated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670652/+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 1670717] [NEW] Unity8/mir working on VMware due to bypass not working

[Pete Woods]

Public bug reported:

Related to this bug (bug #1480755) - this is the issue preventing
unity8/mir working in VMware.

Bringing it out into its own issue to improve visibility.

Choice quotes from previous bug:

The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell)
returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them
have EGL_ALPHA_SIZE == 8 set.

Added a Mesa task. RAOF has suggested we should just fix Mesa. When
asking for RGBA of 8880 it should provide at least one EGLConfig that is
8880 instead of always .

This should be possible. It's not entirely clear why we're not getting
XRGB visuals currently, but it's fixable.

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Related to this bug (#1480755) - this is the issue preventing unity8/mir
  working in VMware.
  
  Bringing it out into its own issue to improve visibility.
+ 
+ Choice quotes from previous bug:
  
  The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell)
  returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them
  have EGL_ALPHA_SIZE == 8 set.
  
  Added a Mesa task. RAOF has suggested we should just fix Mesa. When
  asking for RGBA of 8880 it should provide at least one EGLConfig that is
  8880 instead of always .
  
  This should be possible. It's not entirely clear why we're not getting
  XRGB visuals currently, but it's fixable.

** Summary changed:

- Mesa returning incorrect EGLConfigs preventing unity8/mir working on VMware
+ Unity8/mir working on VMware due to bypass not working

** Description changed:

- Related to this bug (#1480755) - this is the issue preventing unity8/mir
- working in VMware.
+ Related to this bug (bug #1480755) - this is the issue preventing
+ unity8/mir working in VMware.
  
  Bringing it out into its own issue to improve visibility.
  
  Choice quotes from previous bug:
  
  The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell)
  returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them
  have EGL_ALPHA_SIZE == 8 set.
  
  Added a Mesa task. RAOF has suggested we should just fix Mesa. When
  asking for RGBA of 8880 it should provide at least one EGLConfig that is
  8880 instead of always .
  
  This should be possible. It's not entirely clear why we're not getting
  XRGB visuals currently, but it's fixable.

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

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

Title:
  Unity8/mir working on VMware due to bypass not working

Status in mesa package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Related to this bug (bug #1480755) - this is the issue preventing
  unity8/mir working in VMware.

  Bringing it out into its own issue to improve visibility.

  Choice quotes from previous bug:

  The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell)
  returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them
  have EGL_ALPHA_SIZE == 8 set.

  Added a Mesa task. RAOF has suggested we should just fix Mesa. When
  asking for RGBA of 8880 it should provide at least one EGLConfig that
  is 8880 instead of always .

  This should be possible. It's not entirely clear why we're not getting
  XRGB visuals currently, but it's fixable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1670717/+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 1670713] Re: Automatic screen resizing for virtual machines

[Pete Woods]

** Description changed:

- Currently in when you resize the virtual display in qemu (with QXL/spice
+ Currentl when you resize the virtual display in qemu (with QXL/spice
  display) the unity8 screen resolution stays the same. However in e.g.
  Gnome3, the shell is informed of a suggestion to change size, and
  complies.
  
  There appears to be an emerging de-facto standard in virtual display
  resizing, as described below by Thomas Hellstrom 
  from VMware, which is supported by both qemu and VMware.

** Description changed:

- Currentl when you resize the virtual display in qemu (with QXL/spice
+ Currently when you resize the virtual display in qemu (with QXL/spice
  display) the unity8 screen resolution stays the same. However in e.g.
  Gnome3, the shell is informed of a suggestion to change size, and
  complies.
  
  There appears to be an emerging de-facto standard in virtual display
  resizing, as described below by Thomas Hellstrom 
  from VMware, which is supported by both qemu and VMware.

-- 
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/1670713

Title:
  Automatic screen resizing for virtual machines

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Currently when you resize the virtual display in qemu (with QXL/spice
  display) the unity8 screen resolution stays the same. However in e.g.
  Gnome3, the shell is informed of a suggestion to change size, and
  complies.

  There appears to be an emerging de-facto standard in virtual display
  resizing, as described below by Thomas Hellstrom
   from VMware, which is supported by both qemu
  and VMware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670713/+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 1670713] Re: Automatic screen resizing for virtual machines

[Pete Woods]

** Description changed:

  Currently in when you resize the virtual display in qemu (with QXL/spice
  display) the unity8 screen resolution stays the same. However in e.g.
  Gnome3, the shell is informed of a suggestion to change size, and
  complies.
  
- There appears to be an emerging de-facto standard in virtual displays as
- described below by Thomas Hellstrom  from VMware.
+ There appears to be an emerging de-facto standard in virtual display
+ resizing, as described below by Thomas Hellstrom 
+ from VMware, which is supported by both qemu and VMware.

-- 
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/1670713

Title:
  Automatic screen resizing for virtual machines

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Currently in when you resize the virtual display in qemu (with
  QXL/spice display) the unity8 screen resolution stays the same.
  However in e.g. Gnome3, the shell is informed of a suggestion to
  change size, and complies.

  There appears to be an emerging de-facto standard in virtual display
  resizing, as described below by Thomas Hellstrom
   from VMware, which is supported by both qemu
  and VMware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670713/+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 1670713] [NEW] Automatic screen resizing for virtual machines

[Pete Woods]

Public bug reported:

Currently in when you resize the virtual display in qemu (with QXL/spice
display) the unity8 screen resolution stays the same. However in e.g.
Gnome3, the shell is informed of a suggestion to change size, and
complies.

There appears to be an emerging de-facto standard in virtual display
resizing, as described below by Thomas Hellstrom 
from VMware, which is supported by both qemu and VMware.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: mir
 Importance: Undecided
 Status: New

** Affects: mir (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qtmir (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: unity8-desktop

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

Title:
  Automatic screen resizing for virtual machines

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Currently in when you resize the virtual display in qemu (with
  QXL/spice display) the unity8 screen resolution stays the same.
  However in e.g. Gnome3, the shell is informed of a suggestion to
  change size, and complies.

  There appears to be an emerging de-facto standard in virtual display
  resizing, as described below by Thomas Hellstrom
   from VMware, which is supported by both qemu
  and VMware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670713/+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 1670713] Re: Automatic screen resizing for virtual machines

[Pete Woods]

Description of interfaces for automatic resolution change and desktop layout
(multimon) in a virtualized environment:

Note that these properties were first implemented by the qxl driver and have 
just
recently been implemented also by VMware but in any case they could probably be
viewed as some type of evolving standard for virtualized environments.
Gnome-shell works with the below interfaces both in the Xorg- and in the
wayland / DRM configurations.

The DRM KMS interface:
Each connector exposes the following properties:

*) hotplug_mode_update - if 1 indicates that the mode list and preferred mode 
may
change following an uevent.
*) suggested X, suggested Y - (note the spaces instead of underscore). In a 
multimon
environment, suggests the X and Y desktop coordinate for a connector.

Following a uevent, the client should, for all connectors
- Check if the connector is connected, in that case enable the connector, read 
the
preferred mode, set the mode and set the connector to scan out starting at the
suggested desktop origin.
- Disable the connector if not connected.

Future extensions: The above interface is racy as a new uevent may be triggered 
and
values updated while the client is reading the values. With atomic modesetting 
it
should be possible to assign each suggested configuration a sequence number and
have the modesetting operation back off if the sequence numbers don't match.
Similar to how XRandR works. This has not been discussed yet on the DRM list, 
though,
and in practice races are more theorectial than they seem to have an effect on 
the
user's experience.


The Xorg interface:

The Xorg XRandR interface (if Xorg is used as a backend for the compositor) is 
pretty
identical except that the sequence is triggered by (IIRC) an
XRRScreenChangeNotifyEvent.


VMware implementation:
For this to work with VMware a relatively new kernel version is needed, an
xf86-video-vmware driver 13.2.1 or later needs to be installed (but not
necessarily running) and a patched version of open-vm-tools present (the patch 
is
to appear on the open-vm-tools GitHub webpage quite soon, or can be obtained 
from me
on request.

Note that if running Xorg, the xf86-video-vmware driver 13.2.1 and later will, 
if
running, try to perform the automatic screen resizing and output placement if it
detects a uevent from DRM, so any Xorg client trying to do the same thing will
actually try to race with the Xorg driver. However XRandR will make sure that 
the
client will see the configuration set by the Xorg driver before it reacts on the
new property values.

/Thomas 


Below is a typical output of running xrandr --props on a VMware VM with the new
interface active:


xrandr --props
Screen 0: minimum 1 x 1, current 3200 x 1200, maximum 16384 x 16384
Virtual1 connected primary 1600x1200+1600+0 (normal left inverted right x axis 
y axis) 0mm x 0mm
_MUTTER_PRESENTATION_OUTPUT: 0 
implicit_placement: 0 
range: (0, 1)
suggested Y: 0 
range: (0, -1)
suggested X: 1600 
range: (0, -1)
hotplug_mode_update: 1 
range: (0, 1)
   1600x1200 60.00*+  60.00  
   2560x1600 59.99  
   1920x1440 60.00  
   1856x1392 60.00  
   1792x1344 60.00  
   1920x1200 59.88  
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 60.02  
   1440x900  59.89  
   1280x960  60.00  
   1360x768  60.02  
   1280x800  59.81  
   1152x864  75.00  
   1280x768  59.87  
   1024x768  60.00  
   800x600   60.32  
   640x480   59.94  
Virtual2 connected 1600x900+0+0 (normal left inverted right x axis y axis) 0mm 
x 0mm
implicit_placement: 0 
range: (0, 1)
suggested Y: 0 
range: (0, -1)
suggested X: 0 
range: (0, -1)
hotplug_mode_update: 1 
range: (0, 1)
   1600x900  60.00*+
   2560x1600 59.99  
   1920x1440 60.00  
   1856x1392 60.00  
   1792x1344 60.00  
   1920x1200 59.88  
   1600x1200 60.00  
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 60.02  
   1440x900  59.89  
   1280x960  60.00  
   1360x768  60.02  
   1280x800  59.81  
   1152x864  75.00  
   1280x768  59.87  
   1024x768  60.00  
   800x600   60.32  
   640x480   59.94  
Virtual3 disconnected (normal left inverted right x axis y axis)
implicit_placement: 0 
range: (0, 1)
suggested Y: 0 
range: (0, -1)
suggested X: 0 
range: (0, -1)
hotplug_mode_update: 1 
range: (0, 1)
Virtual4 disconnected (normal left inverted right x axis y axis)
implicit_placement: 0 
range: (0, 1)
suggested Y: 0 
range: (0, -1)
suggested X: 0 
range: (0, -1)
hotplug_mode_update: 1 

[Touch-packages] [Bug 1670679] Re: Lock screen only becomes visible after moving the pointer

[Pete Woods]

Definitely the lock screen, not greeter. For me, it's leaving the virt-
manager window up, and doing nothing until the lock timeout happens.
Then once you're sure it's happened move the pointer over the virt-
manager window. Only at this point does the screen redraw and show the
lock screen.

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

Title:
  Lock screen only becomes visible after moving the pointer

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  This means you can see the screen contents until you move the pointer.

  Presumably nothing is triggering a screen redraw when the lock screen
  becomes active (at least in a qemu VM).

  This has the potential to leave personal information if an attacker
  knows not to touch the pointer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670679/+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 1670678] Re: Super-a gesture somewhat unreliable

[Pete Woods]

** Description changed:

  A good portion of the time, it seems very easy to accidentally hold the
  keys on too long, causing the app drawer to be hidden again. In a qemu
  VM, you seem to have to hold the shortcut on a while before it is
  triggered.
  
  The scopes window can also be brought to the fore accidentally when
  attempting this shortcut.
  
  I suspect the root cause here, is the binding of the super key showing
  to the scopes window, and presumably having to have tricks in place to
- avoid it launching the scopes if you hit another key without a timeout.
+ avoid it launching the scopes if you hit another key within a timeout.

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

Title:
  Super-a gesture somewhat unreliable

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  A good portion of the time, it seems very easy to accidentally hold
  the keys on too long, causing the app drawer to be hidden again. In a
  qemu VM, you seem to have to hold the shortcut on a while before it is
  triggered.

  The scopes window can also be brought to the fore accidentally when
  attempting this shortcut.

  I suspect the root cause here, is the binding of the super key showing
  to the scopes window, and presumably having to have tricks in place to
  avoid it launching the scopes if you hit another key within a timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670678/+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 1670678] [NEW] Super-a gesture somewhat unreliable

[Pete Woods]

Public bug reported:

A good portion of the time, it seems very easy to accidentally hold the
keys on too long, causing the app drawer to be hidden again. In a qemu
VM, you seem to have to hold the shortcut on a while before it is
triggered.

The scopes window can also be brought to the fore accidentally when
attempting this shortcut.

I suspect the root cause here, is the binding of the super key showing
to the scopes window, and presumably having to have tricks in place to
avoid it launching the scopes if you hit another key without a timeout.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Super-a gesture somewhat unreliable

Status in unity8 package in Ubuntu:
  New

Bug description:
  A good portion of the time, it seems very easy to accidentally hold
  the keys on too long, causing the app drawer to be hidden again. In a
  qemu VM, you seem to have to hold the shortcut on a while before it is
  triggered.

  The scopes window can also be brought to the fore accidentally when
  attempting this shortcut.

  I suspect the root cause here, is the binding of the super key showing
  to the scopes window, and presumably having to have tricks in place to
  avoid it launching the scopes if you hit another key without a
  timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670678/+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 1670679] [NEW] Lock screen only becomes visible after moving the pointer

[Pete Woods]

Public bug reported:

This means you can see the screen contents until you move the pointer.

Presumably nothing is triggering a screen redraw when the lock screen
becomes active (at least in a qemu VM).

This has the potential to leave personal information if an attacker
knows not to touch the pointer.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Lock screen only becomes visible after moving the pointer

Status in unity8 package in Ubuntu:
  New

Bug description:
  This means you can see the screen contents until you move the pointer.

  Presumably nothing is triggering a screen redraw when the lock screen
  becomes active (at least in a qemu VM).

  This has the potential to leave personal information if an attacker
  knows not to touch the pointer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670679/+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 1670670] [NEW] Unity8 pointer does not stay in sync with Qemu VM tablet input

[Pete Woods]

Public bug reported:

Each time you login, or come back from the lock screen, you need to
"recalibrate" the pointer by carefully moving the pointer into each
corner.

Contrast this with unity7, where the absolute position of the virtual
tablet pointer is tracked, and sync is never lost.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unity8 pointer does not stay in sync with Qemu VM tablet input

Status in unity8 package in Ubuntu:
  New

Bug description:
  Each time you login, or come back from the lock screen, you need to
  "recalibrate" the pointer by carefully moving the pointer into each
  corner.

  Contrast this with unity7, where the absolute position of the virtual
  tablet pointer is tracked, and sync is never lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670670/+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 1670671] [NEW] At login, the scopes window sometimes appears outside the screen area

[Pete Woods]

Public bug reported:

Unsure as to the trigger, but this happened often after login on a fresh
Zesty install in Qemu.

You can't move or resize the window without knowing the super-alt-arrow
shortcuts.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "94973648.png"
   
https://bugs.launchpad.net/bugs/1670671/+attachment/4832851/+files/94973648.png

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

Title:
  At login, the scopes window sometimes appears outside the screen area

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unsure as to the trigger, but this happened often after login on a
  fresh Zesty install in Qemu.

  You can't move or resize the window without knowing the super-alt-
  arrow shortcuts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670671/+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 1670652] [NEW] Can't activate edge gestures in a VM

[Pete Woods]

Public bug reported:

In a Qemu VM, the side gestures (for the launcher and app switcher)
cannot be activated.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Can't activate edge gestures in a VM

Status in unity8 package in Ubuntu:
  New

Bug description:
  In a Qemu VM, the side gestures (for the launcher and app switcher)
  cannot be activated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670652/+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 1670654] [NEW] No way to dismiss edge gesture tutorial without activating the gesture

[Pete Woods]

Public bug reported:

Would be great to be able to press escape, or have a cross to click.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No way to dismiss edge gesture tutorial without activating the gesture

Status in unity8 package in Ubuntu:
  New

Bug description:
  Would be great to be able to press escape, or have a cross to click.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670654/+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 1670655] [NEW] Launcher hidden by default on desktop

[Pete Woods]

Public bug reported:

This makes it tough for a new user to know how to start an app (have to
know to use the left edge gesture, or use super-a).

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Launcher hidden by default on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  This makes it tough for a new user to know how to start an app (have
  to know to use the left edge gesture, or use super-a).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670655/+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 1613789] Re: indicator-network broken on laptop unity8 session

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: New => Fix Released

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1613789

Title:
  indicator-network broken on laptop unity8 session

Status in indicator-network package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Enviroment:

  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Steps to reproduce:

  1º Open unity8 session
  2º Check the indicator-network status

  Current result: indicator-network does not respond and it does not
  load the proper logo

  Expected result: indicator-network should link to System settings/Wi-
  Fi || mobile data(dongle 3G/4G)

  Add info: picture attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1613789/+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 1616475] Re: Enable tests on arm64

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: New => Fix Released

-- 
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/1616475

Title:
  Enable tests on arm64

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  From MIR bug 1612619, vivid/arm64 tests are broken, but xenial &
  yakkety are fine.  Right now we disable tests on arm64 for all
  distros, but we should be more nuanced and only disable them if the
  distro is vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1616475/+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 1655392] Re: [Wizard] Network list is cleared

[Pete Woods]

For indicator-network, I mean.

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

Title:
  [Wizard] Network list is cleared

Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Test case.
  - Flash device.
  - Select language.
  - Tap next.

  Expected result.
  - Wifi screen shows the list of available networks and allows to configure 
them.

  Actual result.
  - Wifi screen briefly shows the list of available networks and then clears 
the list.

  current build number: 119
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1655392/+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 1642989] Re: indicators should use 'com.canonical.indicators.link' type for Settings links

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: New => Triaged

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  indicators should use 'com.canonical.indicators.link' type for
  Settings links

Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  Triaged
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  Triaged
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/view/head:/qml/Panel/Indicators/MenuItemFactory.qml
  has this code:

  > if (modelData.action !== undefined && modelData.action.indexOf("settings") 
> -1) {
  >   // FIXME : At the moment, the indicators aren't using
  >   // com.canonical.indicators.link for settings menu. Need to fudge it.
  >   return linkMenu;
  > }

  We should set the type of settings menuitems to
  'com.canonical.indicators.link' so that this hack can be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1642989/+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 1445580] Re: Impossible to end a call after switching to airplane mode

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Triaged => Invalid

** Changed in: dialer-app (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Impossible to end a call after switching to airplane mode

Status in dialer-app package in Ubuntu:
  Invalid
Status in indicator-network package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  As I described here
  https://lists.launchpad.net/ubuntu-phone/msg12177.html
  I accidentally switched the phone to the airplane mode while having an active 
incoming call. As a result it is impossible to end a call - the red button does 
not end the call.

  The bug is easy to reproduce:
  1. Make a call to your Ubuntu phone and answer it.
  2. Switch on 'airplane mode'
  3. As a result you get unusable phone.

  Of course switching gsm off while having an active call is not a
  typical use of the phone, but still the phone should react to this
  situation differently.

  Another thing is that I somehow switched gsm off while holding my
  phone to my ear (which may suggest some issue with the top panel) -
  but I don't know how to reproduce this, hence currently I treat this
  as an very unfortunate accident.

  Workaround for ending the call: make another incoming call to your
  phone.

  BQ (r21)

  : "When you turn on
  Flight Mode: 1. If a phone or Voip call is in progress, an alert
  should appear, “Turning on Flight Mode will end your call.”, with
  buttons “Cancel” and “End Call”. The alert should close automatically
  if the call finishes by itself."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1445580/+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 1517847] Re: Global offline/inline swithc in the indicator

[Pete Woods]

*** This bug is a duplicate of bug 1373463 ***
https://bugs.launchpad.net/bugs/1373463

** This bug has been marked a duplicate of bug 1373463
   [indicators] Impossible to disable cellular data from indicator

-- 
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/1517847

Title:
  Global offline/inline swithc in the indicator

Status in Ubuntu UX:
  Triaged
Status in indicator-network package in Ubuntu:
  New

Bug description:
  On the Ubuntu Phone I wish to see and use a global switch  in the
  indicators to turn on or off my cellular data.

  Right now I need to do

  Settings -> Cellular -> Off

  and

  Settings -> Cellular -> Operator

  It takes long time as it needs to start the Settings app.

  I think a swipe down and tap to achieve the same would be more
  ergonomic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1517847/+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 1567389] Re: OpenVPN connections should allow username and password

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: ubuntu-ux
   Status: New => Fix Released

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

Title:
  OpenVPN connections should allow username and password

Status in Canonical System Image:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in indicator-network package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  Fix Released

Bug description:
  When configuring a VPN connection, there is no "username" field in
  which to enter one's username (an e-mail address, in my case).

  --

  Reproduce:
  - Access the VPN settings (Apps Scope-->System Settings-->VPN-->Add Manual 
Configuration...).
  - Attempt to enter username.

  Result:
  - There is no field in which to enter one's username.

  Expectation:
  - To be able to specify a username for one's VPN connection, as per their 
respective VPN subscription.

  --

  bq Aquaris E5 HD Ubuntu Edition:
  * OS build number: OTA-10
  * Ubuntu Image part: 20160401.1
  * Ubuntu build description: Ubuntu 15.04 - armhf (20160401-184657)
  * Device Image part: 20160329-a9bacdb
  * Device build description: VEGETA01A-S23A_BQ_L100EN_2011_160401
  * Customization Image part: 20160324--36-54-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567389/+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 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_m

[Pete Woods]

Or if not (I'm no graphics programmer), that's at least the comparable
snippet, I think?

-- 
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/1560498

Title:
  Unity8 using vmwgfx_dri.so crashed in
  mir::graphics::nested::detail::DisplayBuffer::make_current() ->
  eglMakeCurrent() -> ... -> dri2_image_get_buffers()
  [platform_mir.c:138]

Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

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+16.04.20160310.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1560498/+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 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_m

[Pete Woods]

I *think* it looks like there's something similar going on inside QtMir
(http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/screen.cpp#L60):

enum QImage::Format qImageFormatFromMirPixelFormat(MirPixelFormat 
mirPixelFormat) {
switch (mirPixelFormat) {
case mir_pixel_format_abgr_:
if (isLittleEndian()) {
// 0xRR,0xGG,0xBB,0xAA
return QImage::Format_RGBA;
} else {
// 0xAA,0xBB,0xGG,0xRR
qFatal("[mirserver QPA] "
   "Qt doesn't support mir_pixel_format_abgr_ in a big 
endian architecture");
}
break;
case mir_pixel_format_xbgr_:
if (isLittleEndian()) {
// 0xRR,0xGG,0xBB,0xXX
return QImage::Format_RGBX;
} else {
// 0xXX,0xBB,0xGG,0xRR
qFatal("[mirserver QPA] "
   "Qt doesn't support mir_pixel_format_xbgr_ in a big 
endian architecture");
}
break;
break;
case mir_pixel_format_argb_:
// 0xAARRGGBB
return QImage::Format_ARGB32;
break;
case mir_pixel_format_xrgb_:
// 0xffRRGGBB
return QImage::Format_RGB32;
break;
case mir_pixel_format_bgr_888:
qFatal("[mirserver QPA] Qt doesn't support mir_pixel_format_bgr_888");
break;
default:
qFatal("[mirserver QPA] Unknown mir pixel format");
break;
}
return QImage::Format_Invalid;
}

-- 
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/1560498

Title:
  Unity8 using vmwgfx_dri.so crashed in
  mir::graphics::nested::detail::DisplayBuffer::make_current() ->
  eglMakeCurrent() -> ... -> dri2_image_get_buffers()
  [platform_mir.c:138]

Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

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+16.04.20160310.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1560498/+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 1656042] Re: unity-scopes-api FTBFS with Qt 5.7.1

[Pete Woods]

There seems to be some weirdness with Qt5.7 messing with build flags.
For indicator-network, where we have C++14 enabled, Qt seemed to be
inserting -std-c++11 (or whatever the exact flag is) in addition.

Switching to the new set(CMAKE_CXX_STANDARD 14) and set(CMAKE_C_STANDARD
11) seemed to resolve it.

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

Title:
  unity-scopes-api FTBFS with Qt 5.7.1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  As part of test building Qt reverse dependencies, it was found unity-
  scopes-api fails to build (at least) when built against Qt 5.7.1 on
  zesty.

  As unity-scopes-api continues to work without a rebuild, it's not a
  blocker for Qt 5.7.1 transition but should be fixed for the next
  upload.

  Log: https://launchpadlibrarian.net/301312233/buildlog_ubuntu-zesty-
  amd64.unity-scopes-
  
api_1.0.7+17.04.20161115-0ubuntu2~~testrebuild1~~testrebuild1~57~57_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1656042/+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 1655392] Re: [Wizard] Network list is cleared

[Pete Woods]

Is there a crash file available?

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

Title:
  [Wizard] Network list is cleared

Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Test case.
  - Flash device.
  - Select language.
  - Tap next.

  Expected result.
  - Wifi screen shows the list of available networks and allows to configure 
them.

  Actual result.
  - Wifi screen briefly shows the list of available networks and then clears 
the list.

  current build number: 119
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1655392/+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 1656043] Re: indicator-network FTBFS with Qt 5.7.1

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => Critical

-- 
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/1656043

Title:
  indicator-network FTBFS with Qt 5.7.1

Status in indicator-network package in Ubuntu:
  New

Bug description:
  As part of test building Qt reverse dependencies, it was found
  indicator-network fails to build (at least) when built against Qt
  5.7.1 on zesty.

  As indicator-network continues to work without a rebuild, it's not a
  blocker for Qt 5.7.1 transition but should be fixed for the next
  upload.

  Log: https://launchpadlibrarian.net/301313128/buildlog_ubuntu-zesty-
  amd64.indicator-
  
network_0.9.0+17.04.20161223.3-0ubuntu3~~testrebuild1~~testrebuild1~57~57_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1656043/+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 1649613] Re: Networking indicator for unity8 shown in unity7

[Pete Woods]

*** This bug is a duplicate of bug 1648360 ***
https://bugs.launchpad.net/bugs/1648360

** This bug has been marked a duplicate of bug 1648360
   indicator-network, under systemd, starts on u7 when it shouldn't

-- 
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/1649613

Title:
  Networking indicator for unity8 shown in unity7

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Unity8's network indicator is shown along side the nm-applet in unity7
  desktops on zesty.

  See http://people.canonical.com/~davmor2/personal-screenshots/wrong-
  indicator.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1649613/+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 1646626] Re: indicator-network on Core 16 doesn't see ethernet connection

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

-- 
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/1646626

Title:
  indicator-network on Core 16 doesn't see ethernet connection

Status in Canonical System Image:
  Fix Released
Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  The dash does not load 7digital album art from the internet because it
  thinks it is not connected (though it clearly is -- the other album
  info comes from the internet).

  So I believe qml-module-ubuntu-connectivity is giving the wrong
  response.

  (I made sure that the network-manager snap was installed before
  testing.)

  It *might* be related, but indicator-network also shows no connection.
  Though maybe the indicator has its own issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646626/+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 1652288] [NEW] indicator-network uses urfkill on desktop if installed, breaking wifi drivers

[Pete Woods]

Public bug reported:

THe indicator needs to determine at startup if we are in a urfkill-
supported environment or not, and behave accordingly.

** Affects: indicator-network (Ubuntu)
 Importance: Critical
 Assignee: Pete Woods (pete-woods)
 Status: In Progress

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => Critical

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Changed in: indicator-network (Ubuntu)
   Status: New => In Progress

** Branch linked: lp:~pete-woods/indicator-network/no-urfkill-on-desktop

-- 
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/1652288

Title:
  indicator-network uses urfkill on desktop if installed, breaking wifi
  drivers

Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  THe indicator needs to determine at startup if we are in a urfkill-
  supported environment or not, and behave accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1652288/+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 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_m

[Pete Woods]

Guys, is it worth looping in Thomas Hellstrom 
and/or Jakob Bornecrantz  to this bug? IIRC they were
interested in getting the VMware driving working with Mir a while ago.

-- 
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/1560498

Title:
  Unity8 using vmwgfx_dri.so crashed in
  mir::graphics::nested::detail::DisplayBuffer::make_current() ->
  eglMakeCurrent() -> ... -> dri2_image_get_buffers()
  [platform_mir.c:138]

Status in Mir:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

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+16.04.20160310.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1560498/+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 1647830] Re: no wifi choices supplied in wizard on unity8-snap on classic

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => Critical

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  no wifi choices supplied in wizard on unity8-snap on classic

Status in indicator-network package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  in a recent unity8-snap on classic install, i was made to run through
  the wizard. i found that when arriving at the wifi page, there were no
  wifi networks provided just a blank white screen. Altho, when
  proceeding, the wifi indicator did show i was connected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1647830/+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 1622041] Re: Mobile network denied

[Pete Woods]

** Also affects: ofono (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/1622041

Title:
  Mobile network denied

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  New

Bug description:
  Device: Running Ubuntu 15.04 (OTA-13-rc) on the Meizu Pro 5.

  Description of problem: When I power on the phone, it connects to my
  mobile network for a brief period of time. I can send/receive SMS
  texts and make phone calls. After a few minutes though the mobile
  connection drops and the mobile status in the pull-down panel shows
  "Denied". It is then no longer possible to place calls or send/receive
  SMS texts.

  This issue started happening immediately following the upgrade from
  Ubuntu 15.04 (r-14) to the new OTA-13-rc upgrade which became
  available at the start of September.

  I have another phone running Android on the same network which is
  running smoothly, no connection issues.

  I suspect this is more than an indication issue, from what I've read
  the dropped mobile connection may be a software/firmware problem, but
  I haven't been able to find a location/project more suitable where
  this bug can be filed. My apologies.

  My phone's syslog file is downloadable from the link below. The
  problem occurs on September 9th between 19:00 and 20:00.
  http://resonatingmedia.com/logs/syslog.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1622041/+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 1632275] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Triaged => In Progress

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

-- 
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/1632275

Title:
  indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Live session on i386 has an issue immediately which reports that
  network-manager indicator crashed

  On the installed version it is impossible to connect to the net via
  wifi

  Will check on amd64 but as far as I can tell it is fine there.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  CasperVersion: 1.379
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Oct 11 10:17:39 2016
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ExecutableTimestamp: 1475255305
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha i386 (20161008)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ProcCwd: /home/ubuntu
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb779ceba <do_lookup_x+42>:   mov0x4(%eax),%ebx
   PC (0xb779ceba) ok
   source "0x4(%eax)" (0x03eb) not located in a known VMA region (needed 
readable region)!
   destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-network
  Stacktrace:
   #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 <do_lookup_x+1689>, 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   n = 
   list = 
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfacd72b, ref=0x0, 
result=0x644, scope=0x3e7, i=3807944636, version=0xb779d529 <do_lookup_x+1689>, 
flags=5, skip=0x1, type_class=-1226258504, undef_map=0xd62) at dl-lookup.c:361
   ?? ()
  Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.indicator-network.log: indicator-network stop/pre-start, process 5765

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1632275/+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 1632382] Re: indicator-network-secret-agent running automatically on unity7

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1632382

Title:
  indicator-network-secret-agent running automatically on unity7

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  see the summary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1632382/+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 1612619] Re: [MIR] indicator-network

[Pete Woods]

Any tips on where to look for for this? I could see any clearly labelled
debian build variables that would tell me which distro we were on.

-- 
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/1612619

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Fix Committed

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libqofono (needs bug)
   * network-manager-openvpn (bug #1574576)
   * urfkill (needs bug)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1612619/+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 1612619] Re: [MIR] indicator-network

[Pete Woods]

Whoops. Should have updated that message. The current state is that all
the tests work on xenial and yakkety. But arm64 is broken on vivid,
we've removed the build for s390x (due to dependencies being removed
from distro), and the powerpc build servers just kept being unbelievably
slow when trying to build the silo (timing out after several hours).

-- 
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/1612619

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libqofono (needs bug)
   * network-manager-openvpn (bug #1574576)
   * urfkill (needs bug)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1612619/+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 1612619] Re: [MIR] indicator-network

[Pete Woods]

Okay, the package from that MR is now in -proposed.

-- 
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/1612619

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libqofono (needs bug)
   * network-manager-openvpn (bug #1574576)
   * urfkill (needs bug)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1612619/+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 1612270] Re: [MIR] qdjango

[Pete Woods]

For some reason Qt itself doesn't include a good ORM, just a ODBC style
database connector, so you would be forced to do all that unpleasant
building of SQL strings manually.

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

Title:
  [MIR] qdjango

Status in qdjango package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 infographics

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   All dependencies are already in main

  [Standards compliance]
   * This package uses qmake and does not require translations.

  [Maintenance]
   * This package is maintained by Jeremy Laine, upstream in Debian and 
actively in use on the phone images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qdjango/+bug/1612270/+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 1612270] Re: [MIR] qdjango

[Pete Woods]

Well it's two libraries in the same source package, and HTTP server
(which we don't use) and a database ORM (which we do use). I looked
through several options when implementing the infographics, and this ORM
(which models itself after django) was clearly better than the other
options. The upstream developer is extremely responsive, and I've worked
with him on bug fixes and to resolve packaging problems in the past.

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

Title:
  [MIR] qdjango

Status in qdjango package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 infographics

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   All dependencies are already in main

  [Standards compliance]
   * This package uses qmake and does not require translations.

  [Maintenance]
   * This package is maintained by Jeremy Laine, upstream in Debian and 
actively in use on the phone images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qdjango/+bug/1612270/+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 1612619] Re: [MIR] indicator-network

[Pete Woods]

I don't think unity-api-bugs is the correct team for the subscription
(https://launchpad.net/~unity-api-bugs/+members#active). It looks like
only Steve Langasek and Brian Murray and members. We already have unity-
api-team subscribed, and we're the people who actually look after the
package.

-- 
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/1612619

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libqofono (needs bug)
   * network-manager-openvpn (bug #1574576)
   * urfkill (needs bug)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1612619/+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 1603453] Re: Network indicator does not run on Unity 8 desktop sessions, which also means the Ubuntu Store does not show any app pictures (just greyed out Ubuntu logos)

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: In Progress => Fix Released

-- 
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/1603453

Title:
  Network indicator does not run on Unity 8 desktop sessions, which also
  means the Ubuntu Store does not show any app pictures (just greyed out
  Ubuntu logos)

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  The network indicator stopped running after a recent upgrade to the
  Unity 8 desktop session.

  The cause is that the session name changed and the upstart job is
  using the incorrect session name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603453/+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 1612619] Re: [MIR] indicator-network

[Pete Woods]

Good spot with the || true for the tests. I've put a MR together now
that should fix it.

-- 
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/1612619

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libqofono (needs bug)
   * network-manager-openvpn (bug #1574576)
   * urfkill (needs bug)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1612619/+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 1403764] Re: Usermetrics temporarily bad during initialization on vivid r58

[Pete Woods]

** Changed in: libusermetrics (Ubuntu)
   Status: New => Incomplete

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

Title:
  Usermetrics temporarily bad during initialization on vivid r58

Status in libusermetrics package in Ubuntu:
  Incomplete

Bug description:
  On the most recent vivid image the welcome screen launches with an odd
  message (see attached). This seems to be a "user metrics" issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1403764/+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 1608809] Re: libusermetrics fails to build on xenial/yakkety

[Pete Woods]

** Changed in: libusermetrics (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  libusermetrics fails to build on xenial/yakkety

Status in Canonical System Image:
  Fix Released
Status in libusermetrics package in Ubuntu:
  Fix Released

Bug description:
  Build log:

  https://launchpadlibrarian.net/276298616/buildlog_ubuntu-xenial-
  
amd64.libusermetrics_1.1.1+15.10.20150915-0ubuntu2~~testrebuild1~~testrebuild1~1_BUILDING.txt.gz

  'error: ‘isnan’ was not declared in this scope'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1608809/+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 1310012] Re: package usermetricsservice 1.1.1+14.04.20140305-0ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/dbus-1/system-services/com.canonical.UserM

[Pete Woods]

** Changed in: libusermetrics (Ubuntu)
   Status: New => Incomplete

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

Title:
  package usermetricsservice 1.1.1+14.04.20140305-0ubuntu2 failed to
  install/upgrade: trying to overwrite shared '/usr/share/dbus-1/system-
  services/com.canonical.UserMetrics.service', which is different from
  other instances of package usermetricsservice:i386

Status in libusermetrics package in Ubuntu:
  Incomplete

Bug description:
  during installation it crashed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: usermetricsservice 1.1.1+14.04.20140305-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Sat Apr 19 17:21:39 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: 
package:usermetricsservice:1.1.1+14.04.20140305-0ubuntu2:trying to overwrite 
shared '/usr/share/dbus-1/system-services/com.canonical.UserMetrics.service', 
which is different from other instances of package usermetricsservice:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/dbus-1/system-services/com.canonical.UserMetrics.service', which is 
different from other instances of package usermetricsservice:i386
  InstallationDate: Installed on 2014-04-19 (0 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  SourcePackage: libusermetrics
  Title: package usermetricsservice 1.1.1+14.04.20140305-0ubuntu2 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/dbus-1/system-services/com.canonical.UserMetrics.service', which is 
different from other instances of package usermetricsservice:i386
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
  modified.conffile..etc.dbus.1.system.d.com.canonical.UserMetrics.conf: 
[deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1310012/+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