[Touch-packages] [Bug 1638510] Re: deja-dup asks to install software not from a trusted source

[Michael Terry]

It is expected that deja-dup would ask to install duplicity. Duplicity
is not preinstalled, to avoid having python2 on disk. The fact that the
packagekit dialog warns about untrusted sources makes me think you have
PPAs installed and packagekit should display that in a kinder way (as
that fedora bug suggests).

I don't think there's anything deja-dup can do here. I'll reassign to
packagekit.

** Package changed: deja-dup (Ubuntu) => packagekit (Ubuntu)

** Summary changed:

- deja-dup asks to install software not from a trusted source
+ "install software not from a trusted source" dialog could be more user 
friendly

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

Title:
  "install software not from a trusted source" dialog could be more user
  friendly

Status in packagekit package in Ubuntu:
  Confirmed

Bug description:
  deja-dup opens a dialog "The software is not from a trusted source. Do
  not install this package unless you are sure it is safe to do so"

  But I'm obviously not sure it is safe to do so!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  2 09:51:06 2016
  InstallationDate: Installed on 2016-10-31 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1638510/+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 1708933] Re: Can't add a Microsoft account to GNOME Online Accounts

[Michael Terry]

Right, good suggestion.  That reveals the error:

GoaBackend-WARNING **: Did not find emails.account in JSON data

I signed up for a Live account using my own email, not a MS one.  So
maybe that's causing an issue somewhere?

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

Title:
  Can't add a Microsoft account to GNOME Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  In artful:

  1) Open Settings->Online Accounts
  2) Click on "Microsoft" under "Add an account"
  3) See an authorization window pop up, enter my user/password for Microsoft 
Live
  4) Click next, see it ask whether it's OK to give GNOME various permissions
  5) Click yes, see the window disappear

  But at this point, no Microsoft account appears in the active-accounts
  section.  It just seems to have closed the window and done nothing.

  Is there a way to get better logging for this and try again?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-online-accounts 3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  6 10:03:55 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-09 (1669 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+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 1708933] [NEW] Can't add a Microsoft account to GNOME Online Accounts

[Michael Terry]

Public bug reported:

In artful:

1) Open Settings->Online Accounts
2) Click on "Microsoft" under "Add an account"
3) See an authorization window pop up, enter my user/password for Microsoft Live
4) Click next, see it ask whether it's OK to give GNOME various permissions
5) Click yes, see the window disappear

But at this point, no Microsoft account appears in the active-accounts
section.  It just seems to have closed the window and done nothing.

Is there a way to get better logging for this and try again?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-online-accounts 3.24.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Aug  6 10:03:55 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-01-09 (1669 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  Can't add a Microsoft account to GNOME Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  In artful:

  1) Open Settings->Online Accounts
  2) Click on "Microsoft" under "Add an account"
  3) See an authorization window pop up, enter my user/password for Microsoft 
Live
  4) Click next, see it ask whether it's OK to give GNOME various permissions
  5) Click yes, see the window disappear

  But at this point, no Microsoft account appears in the active-accounts
  section.  It just seems to have closed the window and done nothing.

  Is there a way to get better logging for this and try again?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-online-accounts 3.24.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  6 10:03:55 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-09 (1669 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+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 1524928] Re: Should expose 'alternatenames' field of cities15000.txt

[Michael Terry]

** Changed in: libtimezonemap (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Should expose 'alternatenames' field of cities15000.txt

Status in libtimezonemap package in Ubuntu:
  In Progress

Bug description:
  Exposing 'alternatenames' would allow users to search over names for
  cities in their own language (something useful for ubiquity, system
  settings, and unity8's oobe wizard).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libtimezonemap/+bug/1524928/+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 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

** Changed in: dialer-app (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

** Changed in: trust-store (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  UbuntuColors considered harmful

Status in webapps-sprint:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1581047/+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 1355093] Re: [Boot splash screen] Inconsistent spinning-logo screens for startup and system image update

[Michael Terry]

** Changed in: unity-system-compositor (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  [Boot splash screen] Inconsistent spinning-logo screens for startup
  and system image update

Status in Ubuntu UX:
  Fix Committed
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 r183

  1. Wait for an Ubuntu update to become available.
  2. Install the update, confirming the prompt to restart the phone.

  What happens:
  * The screen goes mostly black with a tiny, flat, dark orange, quickly 
spinning Ubuntu logo.
  * The phone restarts.
  * The screen goes black with a second, large, flat, pale orange, quickly 
spinning Ubuntu logo.
  * The phone restarts.
  * The screen goes black with a third, small, glowing, dark orange, slowly 
spinning Ubuntu logo.

  What should happen:
  * The Ubuntu logos should have exactly the same size, position, lighting, 
color, and speed on all screens where they appear.

  <https://wiki.ubuntu.com/SoftwareUpdates#installing-mobile-system>:
  "If you choose 'Restart & Install', a variation of the shutdown screen
  should appear..."

   mpt, to fix that properly you would have to run Mir in recovery :)
   ogra_: or change the graphics to be similar enough?
   larsu, tricky  one is a true color hi-res image, the other is 
more like a 64 color animated gif ...
   even getting the colors to roughly match will be hard
   it would be good to make them the same size per device and get rid of 
the awful progress bar in recovery at least ... but having them look the same 
will be a hard task

  It may save time to fix bug 1335789 at the same time as this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1355093/+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 1482317] Re: Unify code that turns screen on when a notification happens

[Michael Terry]

** Changed in: telephony-service (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

** Changed in: powerd (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Unify code that turns screen on when a notification happens

Status in powerd package in Ubuntu:
  In Progress
Status in telephony-service package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Right now, there are several places we ask USC to turn the screen on
  when a notification happens:

  - powerd for SMS, USSD, and incoming calls
  - telephony-service for MMS and telephony messages

  And we don't seem to be turning them on for ubuntu-push notifications,
  but we should, right?  Following the pattern above, we'd have ubuntu-
  push itself turn the screen on, for a third location.

  We don't turn the screen on at all for notifications that don't come
  via those sources.  For example, the following command line doesn't
  turn the screen on, but I think it should:

  gdbus call --session --dest org.freedesktop.Notifications --object-
  path /org/freedesktop/Notifications --method
  org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
  0

  It feels weird to have telephony-service turning the screen on.
  Logically, it is just emitting a notification.  The presentation of
  that notification is up to a higher layer (maybe we're on a raspberry
  pi2 and we present notifications as LED morse code or whatever).  It
  just makes sense that unity8, which is drawing the notification, is
  the one that knows that the screen needs to be on.  It also knows what
  form factor we are in (I assume we only want to turn screen on for
  phones/tablets, not desktops).

  So I'm proposing that we unify all those places into one code path in
  unity8 that can turn the screen on when a notification is received.

  (This is a breakout bug from bug 1426115.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1482317/+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 1581047] Re: UbuntuColors considered harmful

[Michael Terry]

** Changed in: reminders-app (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  UbuntuColors considered harmful

Status in webapps-sprint:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in trust-store package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  After the latest theme changes (that introduced blue and green to our
  palette), there are incorrect colors in ubuntu-system-settings (and
  elsewhere).

  Partly because of hardcoded colors via UbuntuColors.  Ideally,
  semantic color names from the palette would be used instead.
  "theme.palette.normal.positive" instead of "UbuntuColors.green" for
  example.

  A simple grep should give lots of locations that could be corrected.

  In addition, it seems that UbuntuColors.orange is used in several
  places that aren't focus related.  Like for buttons.  Those might want
  to switch to green via theme.palette.normal.positive.

  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.Themes.PaletteValues/

  And if you're curious what the semantic colors actually resolve to,
  you can see the current mapping between UbuntuColors and the theme by
  looking at /usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/AmbianceNormal.qml
  (or wherever it lives on your system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1581047/+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 1597290] Re: Wallpapers in Windowed Mode are not scaled correctly

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1597290

Title:
  Wallpapers in Windowed Mode are not scaled correctly

Status in unity8 package in Ubuntu:
  New

Bug description:
  When you set a new wallpaper from the Settings App, if it's a
  landscape wallpaper it will be well scaled if the phone screen is
  horizontal, but when it's vertical it will look blurry. When the
  wallpaper is a portrait picture, it happens the opposite: it is well
  scaled if the screen is vertical but when you rotate it, the wallpaper
  is blurry. Thanks ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1597290/+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 1623430] Re: User list jumps around when clicked

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1623430

Title:
  User list jumps around when clicked

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  This started with lp:~mterry/unity8/greeter-no-lockscreen - when you
  click somewhere around the user list, the list jumps around, often
  gets stuck out of bounds until you click again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8-greeter 8.14+16.04.20160914-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-078]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 12:22:09 2016
  InstallationDate: Installed on 2016-05-06 (130 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1623430/+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 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1332306

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

  <https://wiki.ubuntu.com/Networking#Inserting_a_new_SIM>: ‘If you
  insert a new SIM, a “Changing SIM” dialog should appear with the text
  “To use this new SIM, we need to restart.” and buttons “Later” and
  “Restart Now”.’

  Summary of required work:
   - enabling ofono hotswap support through environment variable
   - adding the modal dialog to unity8 side
   - modify i-network to detect the hotswapping and trickering
     the dialog from unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1332306/+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 1392699] Re: Can't change locale settings (e.g. language, 12/24-hour time, date format) independently

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1392699

Title:
  Can't change locale settings (e.g. language, 12/24-hour time, date
  format) independently

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  A. Try to use US English, but with all apps using 24-hour instead of 12-hour 
time. Or:
  B. Try to use UK English, but with all apps using -MM-DD date format.

  What happens: You can't.
  What should happen: You can.

  Since Ubuntu has existed, it has used the GNU locale system. This
  system assumes that every single person using a particular locale
  wants exactly the same settings for time display, date display,
  currency display, alphabetizing, and number formatting.
  <http://www.gnu.org/software/libc/manual/html_node/Effects-of-
  Locale.html>

  Windows, Mac OS, and (to a lesser extent) iOS have always been more
  flexible: setting a locale sets appropriate defaults for these
  settings, but you can also change them individually. Ubuntu should do
  the same.

  This might involve changing the locale system itself, or it might
  involve changing all relevant toolkits so that they ignore the locale
  system when appropriate.

  It would also involve adding settings in System Settings to customize
  the individual locale details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1392699/+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 1659302] Re: Wallpaper crossfade between users stutters

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1659302

Title:
  Wallpaper crossfade between users stutters

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  When you toggle between users with different wallpapers in the
  greeter, the crossfade animation gets stuck for a couple seconds,
  seemingly while the infographic gets updated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170124-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2272]
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 25 14:28:42 2017
  InstallationDate: Installed on 2016-05-06 (263 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1659302/+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 1589242] Re: Turning the mouse on or off unlocks the greeter

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1589242

Title:
  Turning the mouse on or off unlocks the greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Ensure you have "no security/swiping" enabled for unlocking.
  - Switch the screen off and on, you get the greeter.
  - If your bluetooth mouse in off, turn it on. If it's on, turn it off.

  Expected result:
  Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.

  What actually happens:
  The greeter unlocks.

  Note that this doesn't happen if there is a security in place (Pin or
  password) so it's not really a security issue. It also does not happen
  every time, apparently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589242/+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 1407712] Re: Add option to disable /var/lib/lightdm-data/ directories

[Michael Terry]

** Changed in: lightdm
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Add option to disable /var/lib/lightdm-data/ directories

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  There is no way to disable the creation of directories under /var/lib
  /lightdm-data/ for users.

  In environments where[, there is a single user and] all the user's
  data should be controlled under solely /home directories, this is
  undesirable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1407712/+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 1573229] Re: Greeter does not rotate

[Michael Terry]

** Branch linked: lp:~mterry/unity8/greeter-arrangement

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1573229

Title:
  Greeter does not rotate

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

Bug description:
  The Ubuntu Touch start/welcome screen (with the big wheel) does not
  rotate following the tablet orientation.

  Device: Aquaris M10
  Ubuntu version: Ubuntu touch OTA 10.1

  This bug can be very tedious for convergence, when you are in desktop
  mode, with the tablet on the table upside-down and using a bluetooth
  mouse tryng to start the desktop (with no security configuration)
  because the cursor movements follow an opposite direction to mouse
  movements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573229/+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 1599163] Re: Move unity8's greeter off the "/" DBus path

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (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/1599163

Title:
  Move unity8's greeter off the "/" DBus path

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  We expose the Greeter DBus API (whether we're active, which user is
  selected, etc) on the root / DBus path.  This can easily conflict with
  other potential APIs (which are similarly rude as us to claim such a
  path).

  We should switch away from it.  Potential clients right now:

  - indicators
  - test tools
  - adb
  - telephony stack
  - mtp stack
  - push stack
  - maliit
  - messaging app (?)
  - SDK (unlocks device when deploying apps)

  While switching, it may be wise to move to some more standard APIs as
  well, like using logind's LockedHint instead of IsActive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1599163/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

** Changed in: systemd (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  In Progress
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1645798] Re: No snaps appear in scope on Core 16

[Michael Terry]

** Changed in: unity8-session-snap
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Won't Fix
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Won't Fix

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+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 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

[Michael Terry]

I agree with Brian that this might not be worth fixing, but at the same
time, there's 4 more years of 16.04 to go.

I've uploaded both the xenial and yakkety patches (I see that you had to
fix yakkety too so that the versions upgraded nicely) to proposed.
Let's see what the SRU team thinks.

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  In Progress
Status in iproute2 source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * The man pages for tc make reference to a non-existent tc-index man
  page. Purely a typo that should have been tc-tcindex.

   *  Purely a documentation fix, but nice to fix for an LTS release
  that has many years left to it.

  
  [Test Case]

   * To see this issue, fire up a 16,04 image (I did so via lxd) and
  type:

 root@xi386# man tc | grep tc-index
   Filter packets based on traffic control index. See 
tc-index(8).

  , HOWEVER:

 root@xi386:~# man tc-index
 No manual entry for tc-index

  
  * on a fixed system you should only see refereces to tc-tcindex, not tc-index:

 root@x1:~# man tc | grep tc-index
 root@x1:~# man tc | grep tc-tcindex
   Filter packets based on traffic control index. See 
tc-tcindex(8).
red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), 
tc-tcindex(8), tc-u32(8),


  
  [Regression Potential] 

   * This is only a change to man pages, so any regression would be non-
  functional, but this fix is trivial to fix and verify, and the fix is
  exactly from the upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+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 1668700] Re: Blank default scope in unity8-deb

[Michael Terry]

Yeah it might not play in "Try Ubuntu" mode, but it should in "Install
Ubuntu" mode if you have codecs.  But I haven't verified that.  Pat, are
you saying there are additional (non-codec) issues with playing sound in
u8?

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  Confirmed
Status in unity-scope-mediascanner package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 769314] Re: System bell completely silent because PulseAudio sample file undefined by default

[Michael Terry]

I've uploaded a version of Daniel Hahler's patch in comment #22 to
zesty.  Worked for me, I was able to hear the bell in gnome-terminal.

I believe that's the last piece of this puzzle?  I'll unsubscribe the
sponsors team.  Please re-subscribe if there's more to do that is ready
to be uploaded.

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

Title:
  System bell completely silent because PulseAudio sample file undefined
  by default

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in
  Ubuntu Classic/Metacity or another Metacity-based environment, please
  see bug #486154.

  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the
  Natty beta 2.  By default, no sound is produced, and several
  misconfigurations make it difficult to produce sound either from the
  PC speaker or Pulse Audio's module-x11-bell.  Not knowing what the
  desired behavior is, I can't say exactly what needs to be fixed.  But
  the combination of the following issues makes the system quite
  obviously broken.

  1) pcskpr is blacklisted.
  The pcspkr module is necessary for the PC speaker to produce sound.  It is 
blacklisted, so regular users cannot turn the bell on.  It would be nice for 
this to be fixed, but the attitudes displayed in #77010 suggest that it won't 
be.  Nonetheless, I note it here because it interacts with some of the 
following.

  2) The X bell volume is set to 0. (no more true in xenial)
  As reported by `xset q`, the bell volume is 0 when Unity is started.  Both 
the PC speaker and module-x11-bell respect this setting, so the volume must be 
turned up (with `xset b on` or `xset b 100`) for either to work.  Since both 
the PC speaker and module-x11-bell are disabled by default, this setting only 
serves to frustrate attempts to turn them on; it never prevents unwanted sound.

  3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
  This is a system file, not a user file, so users cannot decide whether they 
want this module loaded or not.  They could write a script to unload the module 
at login (and hope the module number doesn't vary between boots), but it would 
be much cleaner to have the modules loaded from a user file, possibly with 
defaults if the user file doesn't exist.

  4) Sample bell.ogg is not loaded.
  When module-x11-bell is loaded, it is told to use the sample bell.ogg.  But 
no sample is loaded into Pulse Audio.  Thus, module-x11-bell traps system bell 
events (keeping them from going to the PC speaker) without producing any sound. 
 If module-x11-bell is loaded, the sample it calls on should be loaded as well. 
 (To fix this, run `pactl upload-sample 
/usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)

  5) gnome-volume-control doesn't.
  The "Sound Effects" tab of gnome-volume-control offers to set the volume and 
sound for system bell events, but these have no effect.  This is because 
gnome-volume-control is trying to control system bells through metacity.  
Ideally, it should be rewritten to control module-x11-bell instead, but a 
temporary fix could be to simply disable this tab.

  6) System bell settings don't transfer to the Ubuntu Classic environment.
  Because that is using metacity, which has it's own set of problems.  See bug 
#486154.

  This has been from testing in a VM (virtualbox), but all of these
  behaviors have also been seen in Compiz in various previous versions
  of Ubuntu running on various hardware.

  I have reported this bug against several components, as it is really an 
integration issue.  The eventual fix may not involve your component, but please 
do not mark this bug as invalid until we have at least a roadmap for fixing it. 
 Otherwise, I fear responsibility will be passed from component to component 
without anything being fixed.  Rationales:
  Unity - As the overarching environment, Unity should be responsible for 
getting everything integrated.  Additionally, some of the problems relate to 
session startup settings.
  Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
  Gnome Media - Own gnome-volume-control.

  Versions (but note the same behavior has been seen in many earlier versions):
  unity: 3.8.10-0ubuntu2
  pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
  gnome-media: 2.32.0-0ubuntu7

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook

[Michael Terry]

I've uploaded the patch in comment #3 to xenial.  I've also added some
SRU bits to the description -- if either Robie or Philip could maybe add
some test case steps, that would be swell.  Thanks!

** Description changed:

  In 1:4.2.8p3+dfsg-1, the default config was changed to
  "Use pool instead of server".  This needs a corresponding
  update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
  DHCP specified servers now get added to the default pool
  config instead of replacing them.
  
  This affects Xenial only as the Yakkety build includes the upstream fix
  (1:4.2.8p7+dfsg-1).
  
- Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 
+ Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344
  & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676
+ 
+ [Test Case]
+ 
+ mterry isn't sure on this.  Robie or Philip, do you have simple
+ instructions?
+ 
+ [Regression Potential]
+ 
+ As noted in comments #1 and #2, this SRU might surface an issue if the
+ user is receiving a broken set of NTP servers.
+ 
+ And as noted in comment #4, some people might be hackishly using the
+ distinction between spaces and tabs in the config file to trick our
+ current hook.  Debian has gotten rid of that distinction, so that hack
+ will stop working on distro-upgrade anyway.  The fix is *probably* going
+ to help more people who unintentionally mixed the two up rather than the
+ few that are relying on that bug.  But that bit can be easily dropped
+ from the SRU if ya like.

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

Title:
  ntp: changing the default config from server to pool broke the dhcp
  hook

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp package in Debian:
  Fix Released

Bug description:
  In 1:4.2.8p3+dfsg-1, the default config was changed to
  "Use pool instead of server".  This needs a corresponding
  update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
  DHCP specified servers now get added to the default pool
  config instead of replacing them.

  This affects Xenial only as the Yakkety build includes the upstream
  fix (1:4.2.8p7+dfsg-1).

  Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344
  & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676

  [Test Case]

  mterry isn't sure on this.  Robie or Philip, do you have simple
  instructions?

  [Regression Potential]

  As noted in comments #1 and #2, this SRU might surface an issue if the
  user is receiving a broken set of NTP servers.

  And as noted in comment #4, some people might be hackishly using the
  distinction between spaces and tabs in the config file to trick our
  current hook.  Debian has gotten rid of that distinction, so that hack
  will stop working on distro-upgrade anyway.  The fix is *probably*
  going to help more people who unintentionally mixed the two up rather
  than the few that are relying on that bug.  But that bit can be easily
  dropped from the SRU if ya like.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+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 1655782] Re: [FFe] Elfdalian layout + merge with Debian 2.19-1

[Michael Terry]

I've uploaded this to zesty, thanks Gunnar!

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

Title:
  [FFe] Elfdalian layout + merge with Debian 2.19-1

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  In Progress

Bug description:
  Please add the Elfdalian keyboard layout which has been added upstream
  (see the Freedesktop bug report).

  I also propose that we take this opportunity to merge with Debian
  xkeyboard-config 2.19-1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1655782/+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 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

[Michael Terry]

Thanks $4 for the patches!  But the patch for 16.04 does not apply
cleanly.  It tries to patch src/device-provider-upower.c which does not
exist.

I'll drop the sponsor team subscription for now; if a fixed patch is
uploaded, please re-add them.

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

Title:
  Power indicator favours 'not present' mouse over laptop battery level

Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  New

Bug description:
  [Impact]

   * It's very annoying to see the mouse battery instead of the system
  battery on indicator bar.

  [Test Case]

   * Using Logitech Wireless Mouse M325 or other wireless mouse can see
  this issue.

  [Regression Potential]

   * No regression as I know.

  [Other Info]
   
   * This is a SRU request for Ubuntu 16.04 (xenial).

  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status
  over the laptop battery level in the top bar.

  I haven't done a good job of explaining it, so check out the
  screenshot - it will explain all :)

  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546/+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 1668700] Re: Blank default scope in unity8-deb

[Michael Terry]

@bfiller, MIRs are already approved for unity-scope-mediascanner2 and
mediascanner2.

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  Confirmed
Status in unity-scope-mediascanner package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

> That said, if we're going to support an arbitrary number of users then
giving each one a different VT does not scale. USC should have a switch-
session key combo of its own (similar to the existing Ctrl-Alt-Fn).

Well, we could give each user session its own VT up to our system VT
limit.  Then we could just hide the rest behind our own switch-session
key?  Would cover most cases elegantly.

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  In Progress
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

I filed the linked upstream bug.  Lennart is on vacation for a couple
more weeks, so this won't see quick action.  pitti pointed me at old bug
1192842 which is basically an old dupe.

All signs are pointing at this being an involved fix that will require
upstream buy-in.  So I'm inclined to set this aside for now and just
accept the bug for zesty, rather than try to make big changes to logind
late in the cycle; changes that we may not end up using in that form
long term.

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  In Progress
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

** Bug watch added: github.com/systemd/systemd/issues #5631
   https://github.com/systemd/systemd/issues/5631

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/5631
   Importance: Unknown
   Status: Unknown

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  In Progress
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

lightdm (1.22.0-0ubuntu1) zesty; urgency=medium

  * Allow guest sessions to talk to Mir (allowing unity8)

 -- Robert Ancell <robert.anc...@canonical.com>  Wed, 22 Mar 2017
09:46:38 +1300

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

** Changed in: lightdm (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  unity8 fails to start as guest user

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

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::<lambda()>
  Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector
 >
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector
 >
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

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

[Michael Terry]

Alright, mediascanner2 now only runs in unity8.  I'll re-approve the
MIR.

** Changed in: mediascanner2 (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  [MIR] mediascanner2

Status in mediascanner2 package in Ubuntu:
  Fix Committed

Bug description:
  In order to add the mediascanner2 scope to the default image, we want
  to promote mediascanner2 and deps to main.  The scope itself is
  already approved (bug 1218409).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1669546/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

[Michael Terry]

@Alexandros, I uploaded this to zesty, thanks!  Since we're in freeze
for zesty (and releasing a beta on Thursday), it may not land in short
order, but I'll keep an eye on it.

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

Title:
  SDL apps either "Failed to connect to the mir server: ..." or segfault
  in protobuf via mir_connect_sync

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8, trying to run neverball game

  Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
  Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL 
(Failed to connect to the mir server: std::bad_alloc)
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main 
process exited, code=exited, status=1/FAI
  Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit 
entered failed state.
  Feb 23 17:46:44 pixel-desktop systemd[2629]: 
ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed 
with result 'exit-code'.

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

[Michael Terry]

https://code.launchpad.net/~mterry/mediascanner2/only-
in-u8/+merge/320505

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

Title:
  [MIR] mediascanner2

Status in mediascanner2 package in Ubuntu:
  Incomplete

Bug description:
  In order to add the mediascanner2 scope to the default image, we want
  to promote mediascanner2 and deps to main.  The scope itself is
  already approved (bug 1218409).

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

[Michael Terry]

OK, unapproving until mediascanner can be targetted at only unity8.  I'm
working on a patch.

** Changed in: mediascanner2 (Ubuntu)
   Status: Fix Committed => Incomplete

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

Title:
  [MIR] mediascanner2

Status in mediascanner2 package in Ubuntu:
  Incomplete

Bug description:
  In order to add the mediascanner2 scope to the default image, we want
  to promote mediascanner2 and deps to main.  The scope itself is
  already approved (bug 1218409).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1669546/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

** No longer affects: unity8 (Ubuntu)

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

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

Robert, can you comment on this?  Got a recommendation?

** Package changed: mir (Ubuntu) => systemd (Ubuntu)

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

OK, more research.  This looks to be a mismatch between what logind
expects lightdm to do and what we actually do.

Mir sessions started by lightdm all use the same VT number (they all
live on the VT owned by unity-system-compositor.

But logind does not allow two user sessions to be on the same VT.  (It
does allow greeter and user sessions to share one, which is why we
didn't notice this bug when using unity8-greeter logging into a unity8
session.)  The relevant logind check is listed below [1].

One fix would be to allow type=mir sessions to share a VT.  But I'd like
input from Robert Ancell before moving on that.  It's possible lightdm
should be doing something else or that we don't actually want to break
the assumption in systemd that each session has its own VT.

[1]
/*
 * Old gdm and lightdm start the user-session on the same VT as
 * the greeter session. But they destroy the greeter session
 * after the user-session and want the user-session to take
 * over the VT. We need to support this for
 * backwards-compatibility, so make sure we allow new sessions
 * on a VT that a greeter is running on. Furthermore, to allow
 * re-logins, we have to allow a greeter to take over a used VT for
 * the exact same reasons.
 */
if (c != SESSION_GREETER &&
vtnr > 0 &&
vtnr < m->seat0->position_count &&
m->seat0->positions[vtnr] &&
m->seat0->positions[vtnr]->class != SESSION_GREETER)
return sd_bus_error_setf(error, BUS_ERROR_SESSION_BUSY, 
"Already occupied by a session");

** No longer affects: mir

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

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

Some research -- this is because XDG_RUNTIME_DIR is empty for the second
user...  Not sure why yet.

You can see the message "QStandardPaths: XDG_RUNTIME_DIR not set,
defaulting to '/tmp/runtime-testuser'" in the log above.

The default for the mir socket that unity8 creates is
$XDG_RUNTIME_DIR/mir_socket, which resolves to "/mir_socket" which
unity8 can't create, bailing.

That env being empty is not tied to a specific user.  I have two users
and whichever one is second has this problem.

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

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673500] [NEW] Ctrl+Alt+T does not bring up a terminal

[Michael Terry]

Public bug reported:

I really miss that keyboard shortcut when using unity8.  In unity7, that
shortcut would bring up a gnome-terminal window (actual command
configurable in GNOME gsettings somewhere).

I guess in unity8, it would bring up a ubuntu-terminal-app window (deb
or snap).

** 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/1673500

Title:
  Ctrl+Alt+T does not bring up a terminal

Status in unity8 package in Ubuntu:
  New

Bug description:
  I really miss that keyboard shortcut when using unity8.  In unity7,
  that shortcut would bring up a gnome-terminal window (actual command
  configurable in GNOME gsettings somewhere).

  I guess in unity8, it would bring up a ubuntu-terminal-app window (deb
  or snap).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1673500/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

Ah...  If you use unity8-greeter, you don't see this bug.  I think this
is due to each session trying to create a USC for itself and they are
conflicting.  I believe we were trying to stop doing that, instead
always using a global USC, but that must not have been prioritized yet.

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

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

Aha!  My testing was accidentally done on my xenial+overlay laptop (hard
to tell environments apart sometimes).  I can confirm on zesty.

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

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1670796] Re: totem's menus don't open under deb-based unity8

[Michael Terry]

This seems fixed now.

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

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

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

Title:
  totem's menus don't open under deb-based unity8

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

Bug description:
  When launching totem ("Videos" in app drawer) under xmir, it's menus
  don't react to mouse clicks.

  Needs investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670796/+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 1670721] Re: gnome-terminal fails to launch under deb-based unity8 ["Failed to connect to Mir: Failed to connect: not accepted by server"]

[Michael Terry]

With the switch to XMir by default, this is fixed.

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

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  gnome-terminal fails to launch under deb-based unity8 ["Failed to
  connect to Mir: Failed to connect: not accepted by server"]

Status in Canonical System Image:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  "Failed to connect to Mir: Failed to connect: not accepted by server"

  And then a C++ exception about a broken pipe when sending a message to
  the Mir server.

  That first error message is from GDK's Mir backend when creating the
  terminal server user daemon.  I'm not sure what the root cause is yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670721/+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 1673229] Re: "Shutdown" app doesn't do anything in deb-based Unity8

[Michael Terry]

@Daniel, fair.  But this is just the newer API (as far as I can tell)
for an existing GNOME DBus API we already supported.  And it's not just
GNOME session tools; other legacy apps might call those APIs.

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

Title:
  "Shutdown" app doesn't do anything in deb-based Unity8

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

Bug description:
  Testing unity8 on classic desktop, I see that there is an icon in the
  app drawer that says "Shutdown" and runs "gnome-session-quit --power-
  off"

  It's not critical, but it would be nice if we supported the
  org.gnome.SessionManager dbus name and intercepted the call, like
  unity7 does.  We already support similar dbus names for backwards
  compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673229/+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 1673229] Re: "Shutdown" app doesn't do anything in deb-based Unity8

[Michael Terry]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  "Shutdown" app doesn't do anything in deb-based Unity8

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

Bug description:
  Testing unity8 on classic desktop, I see that there is an icon in the
  app drawer that says "Shutdown" and runs "gnome-session-quit --power-
  off"

  It's not critical, but it would be nice if we supported the
  org.gnome.SessionManager dbus name and intercepted the call, like
  unity7 does.  We already support similar dbus names for backwards
  compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673229/+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 1673229] [NEW] "Shutdown" app doesn't do anything in deb-based Unity8

[Michael Terry]

Public bug reported:

Testing unity8 on classic desktop, I see that there is an icon in the
app drawer that says "Shutdown" and runs "gnome-session-quit --power-
off"

It's not critical, but it would be nice if we supported the
org.gnome.SessionManager dbus name and intercepted the call, like unity7
does.  We already support similar dbus names for backwards
compatibility.

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

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


** Tags: unity8-desktop

** Tags added: unity8-desktop

** Also affects: canonical-devices-system-image
   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/1673229

Title:
  "Shutdown" app doesn't do anything in deb-based Unity8

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

Bug description:
  Testing unity8 on classic desktop, I see that there is an icon in the
  app drawer that says "Shutdown" and runs "gnome-session-quit --power-
  off"

  It's not critical, but it would be nice if we supported the
  org.gnome.SessionManager dbus name and intercepted the call, like
  unity7 does.  We already support similar dbus names for backwards
  compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673229/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

I was able to log into two different users with unity8 simultaneously.

So that's positive.  Maybe this isn't an everybody thing.  It might be a
graphics driver issue?  Like Mir can't handle it in some cases?  Adding
Mir task to see if that's a crazy thought.

/me is running Dell XPS 13 (intel graphics)

** Also affects: mir (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/1673215

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673215] Re: Second unity8 user session hangs with a black screen

[Michael Terry]

** 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/1673215

Title:
  Second unity8 user session hangs with a black screen

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

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+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 1673097] Re: Guest session warning dialog doesn't appear

[Michael Terry]

** Description changed:

  After the fix for bug 1644237 lands, you can start using unity8 as a
  guest session.
  
  Normally in the guest session, a dialog appears when you log in warning
  you that it is a temporary session and not to keep important data there.
  
  But this dialog does not appear under unity8.
  
  == Analysis ==
  
  The dialog is normally launched by lightdm.  It installs an autostart
  file for the guest user [1] that launches a script [2] which runs zenity
  to create a gtk3 dialog.
  
  Under unity8, we have two problems:
  A) We don't run xdg autostart apps. (this is done by gnome-session normally)
  B) We don't allow zenity to connect to Mir unless it's done through Ubuntu 
App Launch with an associated app desktop file (which can't specify NoDisplay 
or UAL won't launch it, but maybe we could hide it in launcher with something 
like OnlyShowIn=Nothing?)
  
  [1] 
/usr/share/lightdm/guest-session/skel/.config/autostart/guest-session-startup.desktop
  [2] /usr/lib/lightdm/guest-session-auto.sh
  
  == Options ==
  
  We could fix A & B from above.  Not sure if we want to though.  Or we
  could insert logic in unity8 to show the dialog itself.  That might be
  best integration?  But it's kind of a bummer that we have to edit the
  shell itself for anything like this we might want to do.
+ 
+ I suppose the long-term solution is that the lightdm system snap can
+ offer a user daemon that launches the dialog if in a guest session or
+ exit if not.  Or something like that.
+ 
+ So this is a problem that's going away.  I don't know if we want to
+ bother fixing this in the short term.

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

Title:
  Guest session warning dialog doesn't appear

Status in unity8 package in Ubuntu:
  New

Bug description:
  After the fix for bug 1644237 lands, you can start using unity8 as a
  guest session.

  Normally in the guest session, a dialog appears when you log in
  warning you that it is a temporary session and not to keep important
  data there.

  But this dialog does not appear under unity8.

  == Analysis ==

  The dialog is normally launched by lightdm.  It installs an autostart
  file for the guest user [1] that launches a script [2] which runs
  zenity to create a gtk3 dialog.

  Under unity8, we have two problems:
  A) We don't run xdg autostart apps. (this is done by gnome-session normally)
  B) We don't allow zenity to connect to Mir unless it's done through Ubuntu 
App Launch with an associated app desktop file (which can't specify NoDisplay 
or UAL won't launch it, but maybe we could hide it in launcher with something 
like OnlyShowIn=Nothing?)

  [1] 
/usr/share/lightdm/guest-session/skel/.config/autostart/guest-session-startup.desktop
  [2] /usr/lib/lightdm/guest-session-auto.sh

  == Options ==

  We could fix A & B from above.  Not sure if we want to though.  Or we
  could insert logic in unity8 to show the dialog itself.  That might be
  best integration?  But it's kind of a bummer that we have to edit the
  shell itself for anything like this we might want to do.

  I suppose the long-term solution is that the lightdm system snap can
  offer a user daemon that launches the dialog if in a guest session or
  exit if not.  Or something like that.

  So this is a problem that's going away.  I don't know if we want to
  bother fixing this in the short term.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1673097/+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 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

Filed bug 1673097 about the guest session dialog.

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

Title:
  unity8 fails to start as guest user

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

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1673097] [NEW] Guest session warning dialog doesn't appear

[Michael Terry]

Public bug reported:

After the fix for bug 1644237 lands, you can start using unity8 as a
guest session.

Normally in the guest session, a dialog appears when you log in warning
you that it is a temporary session and not to keep important data there.

But this dialog does not appear under unity8.

== Analysis ==

The dialog is normally launched by lightdm.  It installs an autostart
file for the guest user [1] that launches a script [2] which runs zenity
to create a gtk3 dialog.

Under unity8, we have two problems:
A) We don't run xdg autostart apps. (this is done by gnome-session normally)
B) We don't allow zenity to connect to Mir unless it's done through Ubuntu App 
Launch with an associated app desktop file (which can't specify NoDisplay or 
UAL won't launch it, but maybe we could hide it in launcher with something like 
OnlyShowIn=Nothing?)

[1] 
/usr/share/lightdm/guest-session/skel/.config/autostart/guest-session-startup.desktop
[2] /usr/lib/lightdm/guest-session-auto.sh

== Options ==

We could fix A & B from above.  Not sure if we want to though.  Or we
could insert logic in unity8 to show the dialog itself.  That might be
best integration?  But it's kind of a bummer that we have to edit the
shell itself for anything like this we might want to do.

** 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/1673097

Title:
  Guest session warning dialog doesn't appear

Status in unity8 package in Ubuntu:
  New

Bug description:
  After the fix for bug 1644237 lands, you can start using unity8 as a
  guest session.

  Normally in the guest session, a dialog appears when you log in
  warning you that it is a temporary session and not to keep important
  data there.

  But this dialog does not appear under unity8.

  == Analysis ==

  The dialog is normally launched by lightdm.  It installs an autostart
  file for the guest user [1] that launches a script [2] which runs
  zenity to create a gtk3 dialog.

  Under unity8, we have two problems:
  A) We don't run xdg autostart apps. (this is done by gnome-session normally)
  B) We don't allow zenity to connect to Mir unless it's done through Ubuntu 
App Launch with an associated app desktop file (which can't specify NoDisplay 
or UAL won't launch it, but maybe we could hide it in launcher with something 
like OnlyShowIn=Nothing?)

  [1] 
/usr/share/lightdm/guest-session/skel/.config/autostart/guest-session-startup.desktop
  [2] /usr/lib/lightdm/guest-session-auto.sh

  == Options ==

  We could fix A & B from above.  Not sure if we want to though.  Or we
  could insert logic in unity8 to show the dialog itself.  That might be
  best integration?  But it's kind of a bummer that we have to edit the
  shell itself for anything like this we might want to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1673097/+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 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

Hmm, unity8 also doesn't show the "this session and all its data will be
deleted when you log out" warning that unity7 does.  Because zenity
isn't allowed to connect to Mir.  Looking at how we might deal with
that.

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

Title:
  unity8 fails to start as guest user

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

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

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

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

Title:
  unity8 fails to start as guest user

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

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

** Branch linked: lp:~mterry/unity8/guest-lockscreen

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

Title:
  unity8 fails to start as guest user

Status in Canonical System Image:
  In Progress
Status in lightdm package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1644237] Re: unity8 fails to start as guest user

[Michael Terry]

** Branch linked: lp:~mterry/lightdm/guest-permissions

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

Title:
  unity8 fails to start as guest user

Status in Canonical System Image:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1668700] Re: Blank default scope in unity8-deb

[Michael Terry]

** No longer affects: unity-scope-mediascanner (Ubuntu)

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  New
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 1671214] [NEW] Several xmir instances crash unity8

[Michael Terry]

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

Public bug reported:

I'm testing the deb-based unity8.  And launching several xmir-using apps
will in short order take unity8 down.

The problem is about to get worse once the UAL that defaults to xmir
launches lands.

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

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


** Tags: unity8-desktop

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

** Tags added: unity8-desktop

** This bug has been marked a duplicate of bug 1670710
   unity8 crashed with SIGSEGV in qtmir::DBusFocusInfo::findQmlSurface()

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

Title:
  Several xmir instances crash unity8

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

Bug description:
  I'm testing the deb-based unity8.  And launching several xmir-using
  apps will in short order take unity8 down.

  The problem is about to get worse once the UAL that defaults to xmir
  launches lands.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671214/+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 1670796] Re: totem fails to launch under deb-based unity8

[Michael Terry]

With latest UAL (in zesty-proposed), totem opens (using xmir now).  Its
menus don't work though...  So I'll just convert this bug.

** Summary changed:

- totem fails to launch under deb-based unity8 
+ totem's menus don't open under deb-based unity8

** Description changed:

- This is very similar to bug 1670721, but looks to be a different root
- cause.
- 
- When launching totem, it complains about not being able to initialize a
- clutter backend.  Other clutter apps may have the same problem.
+ When launching totem under xmir, it's menus don't react to mouse clicks.
  
  Needs investigation.

** Description changed:

- When launching totem under xmir, it's menus don't react to mouse clicks.
+ When launching totem ("Videos" in app drawer) under xmir, it's menus
+ don't react to mouse clicks.
  
  Needs investigation.

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

Title:
  totem's menus don't open under deb-based unity8

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

Bug description:
  When launching totem ("Videos" in app drawer) under xmir, it's menus
  don't react to mouse clicks.

  Needs investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670796/+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 1670721] Re: gnome-terminal fails to launch under deb-based unity8

[Michael Terry]

Some research...  So normally, gnome-terminal seems to start a systemd
unit for a server process.  Which UAL doesn't associate with the
launching process, so doesn't allow a connection to Mir.

We can change how gnome-terminal is started by passing --disable-
factory, but that doesn't make much progress either.  It starts the
server process as a child, but a window still never appears for an
undiagnosed reason.

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

Title:
  gnome-terminal fails to launch under deb-based unity8

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

Bug description:
  "Failed to connect to Mir: Failed to connect: not accepted by server"

  And then a C++ exception about a broken pipe when sending a message to
  the Mir server.

  That first error message is from GDK's Mir backend when creating the
  terminal server user daemon.  I'm not sure what the root cause is yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670721/+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 1670796] [NEW] totem fails to launch under deb-based unity8

[Michael Terry]

Public bug reported:

This is very similar to bug 1670721, but looks to be a different root
cause.

When launching totem, it complains about not being able to initialize a
clutter backend.  Other clutter apps may have the same problem.

Needs investigation.

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

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


** Tags: unity8-desktop

** Tags added: unity8-desktop

** Also affects: canonical-devices-system-image
   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/1670796

Title:
  totem fails to launch under deb-based unity8

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

Bug description:
  This is very similar to bug 1670721, but looks to be a different root
  cause.

  When launching totem, it complains about not being able to initialize
  a clutter backend.  Other clutter apps may have the same problem.

  Needs investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670796/+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 1670721] Re: gnome-terminal fails to launch under deb-based unity8

[Michael Terry]

** Summary changed:

- Some GTK apps (terminal, totem) fail to launch under deb-based unity8
+ gnome-terminal fails to launch under deb-based unity8

** Description changed:

  "Failed to connect to Mir: Failed to connect: not accepted by server"
  
  And then a C++ exception about a broken pipe when sending a message to
  the Mir server.
  
  That first error message is from GDK's Mir backend.  I'm not sure what
  the root cause is yet.
+ 
+ Or sometimes I see an error about creating the terminal backend session
+ daemon...

** Description changed:

  "Failed to connect to Mir: Failed to connect: not accepted by server"
  
  And then a C++ exception about a broken pipe when sending a message to
  the Mir server.
  
  That first error message is from GDK's Mir backend.  I'm not sure what
  the root cause is yet.
  
  Or sometimes I see an error about creating the terminal backend session
- daemon...
+ daemon via dbus activation.

** Description changed:

  "Failed to connect to Mir: Failed to connect: not accepted by server"
  
  And then a C++ exception about a broken pipe when sending a message to
  the Mir server.
  
- That first error message is from GDK's Mir backend.  I'm not sure what
- the root cause is yet.
- 
- Or sometimes I see an error about creating the terminal backend session
- daemon via dbus activation.
+ That first error message is from GDK's Mir backend when creating the
+ terminal server user daemon.  I'm not sure what the root cause is 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/1670721

Title:
  gnome-terminal fails to launch under deb-based unity8

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

Bug description:
  "Failed to connect to Mir: Failed to connect: not accepted by server"

  And then a C++ exception about a broken pipe when sending a message to
  the Mir server.

  That first error message is from GDK's Mir backend when creating the
  terminal server user daemon.  I'm not sure what the root cause is yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670721/+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 1670721] Re: Some GTK apps (terminal, totem) fail to launch under deb-based unity8

[Michael Terry]

** Summary changed:

- gnome-terminal fails to launch under deb-based unity8
+ Some GTK apps (terminal, totem) fail to launch under deb-based unity8

** Description changed:

- It tries to launch a backend user daemon terminal server.  Which can't
- seem to connect to Mir.
+ "Failed to connect to Mir: Failed to connect: not accepted by server"
+ 
+ And then a C++ exception about a broken pipe when sending a message to
+ the Mir server.
+ 
+ That first error message is from GDK's Mir backend.  I'm not sure what
+ the root cause is 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/1670721

Title:
  Some GTK apps (terminal, totem) fail to launch under deb-based unity8

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

Bug description:
  "Failed to connect to Mir: Failed to connect: not accepted by server"

  And then a C++ exception about a broken pipe when sending a message to
  the Mir server.

  That first error message is from GDK's Mir backend.  I'm not sure what
  the root cause is yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670721/+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 1670721] [NEW] gnome-terminal fails to launch under deb-based unity8

[Michael Terry]

Public bug reported:

It tries to launch a backend user daemon terminal server.  Which can't
seem to connect to Mir.

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

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


** Tags: unity8-desktop

** Also affects: canonical-devices-system-image
   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/1670721

Title:
  gnome-terminal fails to launch under deb-based unity8

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

Bug description:
  It tries to launch a backend user daemon terminal server.  Which can't
  seem to connect to Mir.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670721/+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 1670387] Re: No icon by default in zesty live CD

[Michael Terry]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

** Summary changed:

- No icon by default in zesty live CD
+ No network icon by default in zesty live CD

** Description changed:

  To reproduce:
  
  1) Make a thumb drive with the latest zesty desktop image
  2) Load it up, log out of default unity7 desktop
  3) Switch desktop session to unity8, and log in as "ubuntu" (just press enter 
for password)
  
  You'll notice that the network icon is the default 'gear' icon instead
- of something networking-related.
+ of something networking-related.  Once you connect to a network, the
+ expected icon appears.
  
  I believe it is indicator-network itself that is not providing an icon
  name, because you can do the following from inside the Terminal app in
  unity8:
  
  gdbus call --session --dest com.canonical.indicator.network -o
  /com/canonical/indicator/network -m org.gtk.Actions.Describe desktop
  .network-status
  
  And you'll see there's no icon name specified.

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

Title:
  No network icon by default in zesty live CD

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

Bug description:
  To reproduce:

  1) Make a thumb drive with the latest zesty desktop image
  2) Load it up, log out of default unity7 desktop
  3) Switch desktop session to unity8, and log in as "ubuntu" (just press enter 
for password)

  You'll notice that the network icon is the default 'gear' icon instead
  of something networking-related.  Once you connect to a network, the
  expected icon appears.

  I believe it is indicator-network itself that is not providing an icon
  name, because you can do the following from inside the Terminal app in
  unity8:

  gdbus call --session --dest com.canonical.indicator.network -o
  /com/canonical/indicator/network -m org.gtk.Actions.Describe desktop
  .network-status

  And you'll see there's no icon name specified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670387/+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 1668700] Re: Blank default scope in unity8-deb

[Michael Terry]

** Tags added: unity8-desktop

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 1670383] Re: OSK doesn't work in unity8-greeter

[Michael Terry]

Quick update -- I've got some fixes to our greeter launch script that
let maliit-server run.  But OSK still isn't coming up.  Looking further.

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

Title:
  OSK doesn't work in unity8-greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  With silo https://bileto.ubuntu.com/#/ticket/2481 we get a better OSK
  experience on desktops.

  Unfortunately with unity8-greeter maliit isn't started in the
  lightdm/greeter session, nor can I see the keyboard switch or button
  in the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8-greeter 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar  6 15:53:31 2017
  InstallationDate: Installed on 2016-05-06 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1670383/+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 1670387] [NEW] No icon by default in zesty live CD

[Michael Terry]

Public bug reported:

To reproduce:

1) Make a thumb drive with the latest zesty desktop image
2) Load it up, log out of default unity7 desktop
3) Switch desktop session to unity8, and log in as "ubuntu" (just press enter 
for password)

You'll notice that the network icon is the default 'gear' icon instead
of something networking-related.

I believe it is indicator-network itself that is not providing an icon
name, because you can do the following from inside the Terminal app in
unity8:

gdbus call --session --dest com.canonical.indicator.network -o
/com/canonical/indicator/network -m org.gtk.Actions.Describe desktop
.network-status

And you'll see there's no icon name specified.

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

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

Title:
  No icon by default in zesty live CD

Status in indicator-network package in Ubuntu:
  New

Bug description:
  To reproduce:

  1) Make a thumb drive with the latest zesty desktop image
  2) Load it up, log out of default unity7 desktop
  3) Switch desktop session to unity8, and log in as "ubuntu" (just press enter 
for password)

  You'll notice that the network icon is the default 'gear' icon instead
  of something networking-related.

  I believe it is indicator-network itself that is not providing an icon
  name, because you can do the following from inside the Terminal app in
  unity8:

  gdbus call --session --dest com.canonical.indicator.network -o
  /com/canonical/indicator/network -m org.gtk.Actions.Describe desktop
  .network-status

  And you'll see there's no icon name specified.

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

[Michael Terry]

OK, talked to tedg, unity-api-team is subscribed.  This has worked well
enough in Touch for a while.  Should be good for main.

** Changed in: mediascanner2 (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  [MIR] mediascanner2

Status in mediascanner2 package in Ubuntu:
  Fix Committed

Bug description:
  In order to add the mediascanner2 scope to the default image, we want
  to promote mediascanner2 and deps to main.  The scope itself is
  already approved (bug 1218409).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1669546/+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 1668700] Re: Blank default scope in unity8-deb

[Michael Terry]

Oh looking into it, we already ship that config piece.  The default
gschema setting for favorite-scopes is in unity-schemas, part of the
unity7 source.

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 1668700] Re: Blank default scope in unity8-deb

[Michael Terry]

I believe we'd also need to ship a config piece to make the mediascanner
scope a default favorite scope, like it is in Touch.

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

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

[Michael Terry]

Reviewing the package, it seems fine.  It'd be nice if qtdeclarative5
-ubuntu-mediascanner0.1 could be dropped (just ubuntu-sdk-libs depends
on it).

It needs a team bug subscriber from http://bazaar.launchpad.net/~ubuntu-
archive/ubuntu-archive-tools/trunk/view/head:/package-subscribers#L107

Since it doesn't do any format parsing itself, I don't think it needs a
security review.

There are a lot of bugs.  Any comment from the maintainers about how
stable this is?

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

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

Title:
  [MIR] mediascanner2

Status in mediascanner2 package in Ubuntu:
  Incomplete

Bug description:
  In order to add the mediascanner2 scope to the default image, we want
  to promote mediascanner2 and deps to main.  The scope itself is
  already approved (bug 1218409).

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

[Michael Terry]

** Summary changed:

- [MIR] mediascanner2 and friends
+ [MIR] mediascanner2

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

Title:
  [MIR] mediascanner2

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  In order to add the mediascanner2 scope to the default image, we want
  to promote mediascanner2 and deps to main.  The scope itself is
  already approved (bug 1218409).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1669546/+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 1668700] Re: Blank default scope in unity8-deb

[Michael Terry]

I've filed FFe bug 1669543 to fix this for zesty, since we're post
feature freeze.

** Branch linked: lp:~mterry/unity8-desktop-session/add-mediascanner

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

Title:
  Blank default scope in unity8-deb

Status in Canonical System Image:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  unity8-deb on a fresh zesty installation in kvm

  Steps:

  1º Install zesty on kvm image
  2º Enter unity8-deb
  3º Check the default scope

  Expected result: some scopes should be marked by default as favorite,
  unity-scope-mediascanner2 wasn't installed along with zesty so some
  scopes are missing

  Current result: default scope is blank and only 3rd party scopes are
  available

  Add info: Bug #1668701

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 1669546] [NEW] [MIR] mediascanner2 and friends

[Michael Terry]

Public bug reported:

In order to add the mediascanner2 scope to the default image, we want to
promote mediascanner2 and deps to main.  The scope itself is already
approved (bug 1218409).

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

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

Title:
  [MIR] mediascanner2 and friends

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  In order to add the mediascanner2 scope to the default image, we want
  to promote mediascanner2 and deps to main.  The scope itself is
  already approved (bug 1218409).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1669546/+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 1669543] [NEW] [FFe] Add unity-scope-mediascanner to default unity8 experience

[Michael Terry]

Public bug reported:

We want to add the mediascanner scope into the default unity8
experience.  Especially since we're removing the click scope (in favor
of the app drawer in the launcher).  So by default, the scopes window is
just blank (bug 1668700).  :(

mediascanner2 and its dependencies will need a MIR.  I'll look into
doing that (done -- bug 1669546).  (The scope itself already has passed
MIR review: bug 1218409)

** Affects: unity8-desktop-session (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  We want to add the mediascanner scope into the default unity8
  experience.  Especially since we're removing the click scope (in favor
  of the app drawer in the launcher).  So by default, the scopes window is
- just blank.  :(
+ just blank (bug 1668700).  :(
  
  mediascanner2 and its dependencies will need a MIR.  I'll look into
  doing that.  (The scope itself already has passed MIR review: bug
  1218409)

** Package changed: unity-scope-mediascanner (Ubuntu) => unity8-desktop-
session (Ubuntu)

** Description changed:

  We want to add the mediascanner scope into the default unity8
  experience.  Especially since we're removing the click scope (in favor
  of the app drawer in the launcher).  So by default, the scopes window is
  just blank (bug 1668700).  :(
  
  mediascanner2 and its dependencies will need a MIR.  I'll look into
- doing that.  (The scope itself already has passed MIR review: bug
- 1218409)
+ doing that (done -- bug 1669546).  (The scope itself already has passed
+ MIR review: bug 1218409)

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

Title:
  [FFe] Add unity-scope-mediascanner to default unity8 experience

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

Bug description:
  We want to add the mediascanner scope into the default unity8
  experience.  Especially since we're removing the click scope (in favor
  of the app drawer in the launcher).  So by default, the scopes window
  is just blank (bug 1668700).  :(

  mediascanner2 and its dependencies will need a MIR.  I'll look into
  doing that (done -- bug 1669546).  (The scope itself already has
  passed MIR review: bug 1218409)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1669543/+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 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

[Michael Terry]

They should add mir, yeah.  No need to replace unity8, necessarily [1].

[1] For the moment, plugging unity8 will make you uninstallable.  This
is to prevent widespread use of that interface before we finish it.  The
default set of core apps have an exception to this, though.

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

Title:
  [regression] Some apps fail to start with [QPA]
  UbuntuClientIntegration: connection to Mir server failed.

Status in Canonical System Image:
  Confirmed
Status in platform-api:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in Unity8 Session Snap:
  Invalid
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

  Test Case
  1. Open the app drawer
  2. Launch an app (eg calculator)

  Expected result
  It starts successfully and the app works as expected

  Actual Result
  It launches, the loading screen then a black screen is shown for a sort 
moment, then the window closes.

  They all report:

  >>>
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [QPA] UbuntuClientIntegration: connection to Mir server failed.

  Mir returned: "Failed to connect to server socket: Permission denied"
  <<<

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1662145/+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 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

[Michael Terry]

Agreed.  I was just trying to highlight that an app that used to work as
Mir might now be run under XMir because we switched which interface we
look at.

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

Title:
  [regression] Some apps fail to start with [QPA]
  UbuntuClientIntegration: connection to Mir server failed.

Status in Canonical System Image:
  Confirmed
Status in platform-api:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in Unity8 Session Snap:
  Invalid
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

  Test Case
  1. Open the app drawer
  2. Launch an app (eg calculator)

  Expected result
  It starts successfully and the app works as expected

  Actual Result
  It launches, the loading screen then a black screen is shown for a sort 
moment, then the window closes.

  They all report:

  >>>
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [QPA] UbuntuClientIntegration: connection to Mir server failed.

  Mir returned: "Failed to connect to server socket: Permission denied"
  <<<

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1662145/+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 1663048] Re: libmirclient in snaps gets out of sync with archive

[Michael Terry]

** Changed in: unity8 (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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1663048

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: libmirclient in snaps gets out of sync with archive

[Michael Terry]

OK, I found a way to work around that with symlinks, so unity8-session
is now using mir-libs.

Though don't rush to upgrade; something (else?) broke, so edge isn't
rendering on screen.  I think it's a gsettings issue, digging into it.

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

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: libmirclient in snaps gets out of sync with archive

[Michael Terry]

Hmm, unity8-session runs into bug 1665123 when trying to use mir-libs.
I'll continue to bundle for now.

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

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: libmirclient in snaps gets out of sync with archive

[Michael Terry]

>From my end, I don't know of blockers for the UAP-without-Mir upload.

However, I would like to just take this moment to note that I haven't
heard any talk of actually bumping the UAP interface number.  Which
means that by removing libraries, we're breaking our snap interface
contract -- one we've released into the stable channel.

Now that's fine, teething pains and all that.  And maybe we don't expect
anyone to seriously be using the Mir libraries from UAP.  (Though
someone might be...)

Has the UAP team considered what the Right Thing would look like here?
At least as a thought experiment for next time.  But maybe even if it's
easy, we can do it here too.

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

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

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

[Michael Terry]

- This needs a team bug subscriber for whichever team is looking after
this.  ~unity-api-team?

- libzmqpp-dev should probably depend on libzmq3-dev (not libzmq5-dev).
The 3 version is a replacement for the deprecated 5 version, it seems.
Plus that would make the Build-Depends and the Depends consistent.  Not
a blocker, just saying.

- This isn't in Debian, which puts all the maintenance burden on the
above team.  Is there a reason they don't have it?

- There's a patch ("mkdir_before_install.diff") that's not being used.
Is that obsolete?

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

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

Title:
  [MIR] zmqpp

Status in zmqpp package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe.

  [Rationale]
   * This package is required by unity-scopes-api.

  [Security]
   * No known security issues at this time, it has been in active use on our 
touch devices since a very long time already.

  [Quality assurance]
   * This package comes with a set of unit tests that are all being run during 
build-time.

  [Dependencies]
   Most dependencies are already in main, with only a small nitpick:
   * libboost-test-dev is in universe, but its source boost-defaults is already 
in main.
   * zeromq3 has a MIR filled as well 
(https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1597439)

  [Maintenance]
   * This package is used by Canonical upstream projects so the packaging is 
maintained by Canonical. The upstream code is actively maintained and developed 
by the zeromq team.

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

[Michael Terry]

** Changed in: ubuntu-ui-extras (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [MIR] ubuntu-ui-extras

Status in ubuntu-ui-extras package in Ubuntu:
  Fix Committed

Bug description:
  Please consider ubuntu-ui-extras for inclusion in main.

  ubuntu-terminal-app and webbrowser-app now depend on ubuntu-ui-extras
  to provide certain UI components which are shared, they are in main so
  it is required for the ubuntu-ui-extras to also be in main.

  
  [Availability]
  http://launchpad.net/ubuntu-ui-extras - qtdeclarative5-ubuntu-ui-extras0.2 is 
already in universe 
(http://packages.ubuntu.com/search?keywords=qtdeclarative5-ubuntu-ui-extras0.2+=names=all=all)

  [Rationale]
  ubuntu-ui-extras is a new dependency of a package that we already support. 
  webbrowser-app and ubuntu-terminal-app want to use a common component which 
is in ubuntu-ui-extras.

  [Security]
  No CVE entries.
  No Secunia history.
  Written in QML and C++
  Does not open any port.

  [Quality assurance]
  Package provides components for other Qt apps to use.
  The components have been used extensively on ubuntu touch platforms.
  Does not deal with exotic hardware which we cannot support.

  [Dependencies]
  qml-module-qtquick2
  qml-module-ubuntu-components
  qml-module-qtquick-window2

  Which are all in main.

  [Standards compliance]
  Meets the FHS, Debian Policy
  Standard packaging

  [Maintenance]
  ubuntu-ui-extras is already in universe and is maintained by the Ubuntu 
Phablet Team

  [Background information] 
  Package has not been renamed recently

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-extras/+bug/1666556/+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 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

[Michael Terry]

Daniel, that may be because now we choose whether to use xmir or not
based on the presence of the 'mir' interface (used to be the 'unity8'
interface).  Not all apps may plug into that interface.

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

Title:
  [regression] Some apps fail to start with [QPA]
  UbuntuClientIntegration: connection to Mir server failed.

Status in Canonical System Image:
  Confirmed
Status in platform-api:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in Unity8 Session Snap:
  Invalid
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

  Test Case
  1. Open the app drawer
  2. Launch an app (eg calculator)

  Expected result
  It starts successfully and the app works as expected

  Actual Result
  It launches, the loading screen then a black screen is shown for a sort 
moment, then the window closes.

  They all report:

  >>>
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [QPA] UbuntuClientIntegration: connection to Mir server failed.

  Mir returned: "Failed to connect to server socket: Permission denied"
  <<<

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1662145/+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 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

[Michael Terry]

Is this still happening?

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

Title:
  [regression] Some apps fail to start with [QPA]
  UbuntuClientIntegration: connection to Mir server failed.

Status in Canonical System Image:
  Confirmed
Status in platform-api:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in Unity8 Session Snap:
  Invalid
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

  Test Case
  1. Open the app drawer
  2. Launch an app (eg calculator)

  Expected result
  It starts successfully and the app works as expected

  Actual Result
  It launches, the loading screen then a black screen is shown for a sort 
moment, then the window closes.

  They all report:

  >>>
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [QPA] UbuntuClientIntegration: connection to Mir server failed.

  Mir returned: "Failed to connect to server socket: Permission denied"
  <<<

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1662145/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Michael Terry]

Thank you Dan, for the analysis.  Per comment #23, I'll mark Won't Fix
for xenial.

** Changed in: ifupdown (Ubuntu Xenial)
   Status: In Progress => Won't Fix

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Won't Fix
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during
  boot.

  [Regression Potential]

  None

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+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 1663048] Re: libmirclient in snaps gets out of sync with archive

[Michael Terry]

mir-libs is only 0.26.0, but xenial overlay has 0.26.1.  I can't fix
unity8-session to use mir-libs until that's updated.

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

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: libmirclient in snaps gets out of sync with archive

[Michael Terry]

Didier and I settled on a version of desktop-launch that tries to use
mir-libs first, falling back to ubuntu-app-platform (while the libs are
in there), and if not, then falling back to an internal copy of the
libraries.

That should help the transition and doesn't encode a requirement on mir-
libs inside of desktop-launch.  But should enable the use of them if the
snap chooses.

This has landed and now also sets LD_LIBRARY_PATH to point inside mir-
libs for your snap, if mir-libs is connected.

So go ahead and update your snaps.  All you need to do is define the
plug and create the $SNAP/mir-libs folder.  Everything else should be
done for you.

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

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  Fix Released

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1666556] Re: [MIR] ubuntu-ui-extras

[Michael Terry]

- Please subscribe ~ubuntu-sdk-bugs to package bugs.

- qml-module-ubuntu-test, qtdeclarative5-dev-tools, and xvfb should be
added to the Build-Depends or else the test suite doesn't get run.

 - Not necessarily a blocker, but the binary package name should be qml-
module-ubuntu-components-extras.  This should be fixed before 18.04.
(Bug 1342031)

** Changed in: ubuntu-ui-extras (Ubuntu)
   Status: New => Incomplete

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

Title:
  [MIR] ubuntu-ui-extras

Status in ubuntu-ui-extras package in Ubuntu:
  Incomplete

Bug description:
  Please consider ubuntu-ui-extras for inclusion in main.

  ubuntu-terminal-app and webbrowser-app now depend on ubuntu-ui-extras
  to provide certain UI components which are shared, they are in main so
  it is required for the ubuntu-ui-extras to also be in main.

  
  [Availability]
  http://launchpad.net/ubuntu-ui-extras - qtdeclarative5-ubuntu-ui-extras0.2 is 
already in universe 
(http://packages.ubuntu.com/search?keywords=qtdeclarative5-ubuntu-ui-extras0.2+=names=all=all)

  [Rationale]
  ubuntu-ui-extras is a new dependency of a package that we already support. 
  webbrowser-app and ubuntu-terminal-app want to use a common component which 
is in ubuntu-ui-extras.

  [Security]
  No CVE entries.
  No Secunia history.
  Written in QML and C++
  Does not open any port.

  [Quality assurance]
  Package provides components for other Qt apps to use.
  The components have been used extensively on ubuntu touch platforms.
  Does not deal with exotic hardware which we cannot support.

  [Dependencies]
  qml-module-qtquick2
  qml-module-ubuntu-components
  qml-module-qtquick-window2

  Which are all in main.

  [Standards compliance]
  Meets the FHS, Debian Policy
  Standard packaging

  [Maintenance]
  ubuntu-ui-extras is already in universe and is maintained by the Ubuntu 
Phablet Team

  [Background information] 
  Package has not been renamed recently

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-extras/+bug/1666556/+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 1663048] Re: libmirclient in snaps gets out of sync with archive

[Michael Terry]

Didier, I mostly agree with you, but you are missing the context and
meetings that led to this approach.  I'm just the messenger here, and
anyone please correct me if I mess something up.

- The Mir team is actively working on a stable ABI 1.0 release.  That's
coming in short term (but will involve an ABI change when it lands).

- The Mir team is so-far uninterested in providing a stable socket
protocol, certainly in the short or medium term.  (Preferring instead to
say the library is the interface.)  This isn't a very snappy approach,
granted.  But it's been the approach they've used in the archive for a
while.

- *IF* the Mir team says "using a content snap is the only supported
way", we really don't want to make that content snap be u-a-p.  Partly
because there are Mir clients that don't care about the rest of u-a-p
(GTK has a Mir backend for example).  And partly because all the issues
around LD_LIBRARY_PATH and library content snaps (which is sort of a
nightmare that just hasn't happened to bite us yet) make it advantageous
to strongly limit the scope of an always-required content snap.

- I agree in theory Mir is not different than those other system
libraries.  Except that those system libraries tend to have a more
stable library and protocol interface policies.  Policies that mean the
interface can survive the lifetime of a Core series (which is all that
we care about, right?).  But Mir is not able to make such promises 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/1663048

Title:
  libmirclient in snaps gets out of sync with archive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: mirclient gets out of sync

[Michael Terry]

I've got a branch up for changing desktop-launch to point at mir-libs
[1].  I also adjust LD_LIBRARY_PATH, so apps won't have to manually add
that.  They just need to plug into mir-libs.

[1] https://github.com/ubuntu/snapcraft-desktop-helpers/pull/54

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

** Branch linked: lp:~mterry/unity8-desktop-session/mir-libs

** Changed in: unity8-desktop-session (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

** Changed in: unity8-desktop-session (Ubuntu)
   Importance: Undecided => High

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

Title:
  mirclient gets out of sync

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: mirclient gets out of sync

[Michael Terry]

Bug 1665775 is the request for mir-libs to be auto-connected.

** No longer affects: snapd

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

Title:
  mirclient gets out of sync

Status in Canonical System Image:
  Confirmed
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: mirclient gets out of sync

[Michael Terry]

Adding snapd task to get the mir-libs content interface auto-connected.

** Also affects: snapd
   Importance: Undecided
   Status: New

** Changed in: snapd
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  mirclient gets out of sync

Status in Canonical System Image:
  Confirmed
Status in snapd:
  New
Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1663048] Re: mirclient gets out of sync

[Michael Terry]

There was a meeting today with the Mir team and some stakeholders and I
believe the outcome was that mir-libs will continue to be the only
supported source for Mir libraries.

So we should probably do the following:

- Drop Mir libraries from the ubuntu-app-platform snap.

- Update snapcraft-desktop-helpers to stop including Mir libraries in
consuming snaps and to point at mir-libs's libraries if they are being
used.

- Update all Mir-consuming snaps to plug into mir-libs and to include
the path in their LD_LIBRARY_PATH.  And to remove any accidentally
included duplicate libraries in their own snap.

I'm working on #2 there (snapcraft-desktop-helpers).  I'll add a task
here.  I'll also work on converting the unity8 snap to use mir-libs.

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  mirclient gets out of sync

Status in Ubuntu App Platform:
  In Progress
Status in unity8 package in Ubuntu:
  New

Bug description:
  Because we directly include mir client libraries in the platform (due
  to a dependency of qtubuntu), when the mir interface is revised we get
  out of sync. The mir team publishes a mir-libs snap that tracks these
  changes and exposes a mir-libs content interface. We should
  investigate if that can be used transparently by apps connected to the
  platform.

  as of this report they are out of sync.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-app-platform/+bug/1663048/+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 1657845] Re: Unity8 snap can't load the testability libraries

[Michael Terry]

Agreed.  I see similar (using desktop u8 snap).  Looking into it...

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+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 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

[Michael Terry]

This is not the original issue, but yesterday I switched the unity8 snap
to use a different, more standard path (/run/user/xxx/mir_socket) for
the socket.

So if testing against the u8 snap, please re-create your app snaps to
pull down the latest version of the desktop-launch script which will
point your app at the new, correct socket location.  Again, this isn't
the same issue as OP, but I didn't want this new issue to confuse your
testing of this bug.

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

Title:
  [regression] Some apps fail to start with [QPA]
  UbuntuClientIntegration: connection to Mir server failed.

Status in Canonical System Image:
  Confirmed
Status in platform-api:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in Unity8 Session Snap:
  Invalid
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

  Test Case
  1. Open the app drawer
  2. Launch an app (eg calculator)

  Expected result
  It starts successfully and the app works as expected

  Actual Result
  It launches, the loading screen then a black screen is shown for a sort 
moment, then the window closes.

  They all report:

  >>>
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [QPA] UbuntuClientIntegration: connection to Mir server failed.

  Mir returned: "Failed to connect to server socket: Permission denied"
  <<<

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1662145/+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 1657845] Re: Unity8 snap can't load the testability libraries

[Michael Terry]

So in both the phone and the snap, the libraries get loaded twice.  The
first registration succeeds and the second fails.

But on the phone introspection works and with the snap, it doesn't.  But
we don't have clues as to why 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/1657845

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+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 1657845] Re: Unity8 snap can't load the testability libraries

[Michael Terry]

Should be better now.

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1657845/+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 1661216] Re: black screen with unity8 session snap

[Michael Terry]

Try the latest unity8-session snap, I think this is fixed.

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

Title:
  black screen with unity8 session snap

Status in Canonical System Image:
  New
Status in Unity8 Session Snap:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty up to date
  unity8-session  16.04   390

  I can login but the session does not start and apport running on top.
  The following lines are repeating in apport log:

  ERROR: apport (pid 20101) Thu Feb  2 12:16:49 2017: executable: 
/snap/unity8-session/390/usr/lib/x86_64-linux-gnu/policykit-unity8/policykit-agent
 (command line 
"/snap/unity8-session/390/usr/lib/x86_64-linux-gnu/policykit-unity8/policykit-agent")
  ERROR: apport (pid 20101) Thu Feb  2 12:16:49 2017: executable does not 
belong to a package, ignoring

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661216/+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