date:20170207

Hmm and apparently no snap named `ubuntu-calendar-app' exists. How do I
install it or any other app that exhibits this bug?

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

Title:
  Installing 0.26.1 breaks calendar app (and others)

Status in Mir:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Incomplete

Bug description:
  When installing the 0.26.1 silo I can no longer run calendar on
  Unity8. It gives this error in the logs:

  Feb 07 10:30:31 seven kernel: QSGRenderThread[6690]: segfault at 30 ip
  7f9fa93fcdc8 sp 7f9f655c6b28 error 4 in
  libEGL.so.1.0.0[7f9fa93e2000+3]

  Xenial+Overlay
  Deb based Unity8

  Snaps:
  ubuntu-app-platform  1   33   canonical  devmode
  ubuntu-calendar-app  0.1.1   23   canonical  devmode

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

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

[Touch-packages] [Bug 1540702] Re: While resizing Qt apps window contents jitter about erratically (including during animations)

Not a Unity8 bug. Qt apps are equally jittery in mir_proving_server.

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

Title:
  While resizing Qt apps window contents jitter about erratically
  (including during animations)

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

Bug description:
  Resizing a window (Scopes) the window contents jitter about
  erratically. Obviously they should appear to remain stationary unless
  being significantly repositioned.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  2 10:23:02 2016
  InstallationDate: Installed on 2015-12-03 (60 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log:
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.
   ubuntumirclient: Got invalid serialized mime data. Ignoring it.

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

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

[Touch-packages] [Bug 1662632] Re: Installing 0.26.1 breaks calendar app (and others)

Starting with pure zesty, the current lp:mir/0.26 (0.26.1 candidate
code) seems to happily run every touch app I have tried (except
webbrowser-app which is broken for its own reasons, and can't
immediately test calendar-app which apparently doesn't exist in zesty).

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

Title:
  Installing 0.26.1 breaks calendar app (and others)

Status in Mir:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Incomplete

Bug description:
  When installing the 0.26.1 silo I can no longer run calendar on
  Unity8. It gives this error in the logs:

  Feb 07 10:30:31 seven kernel: QSGRenderThread[6690]: segfault at 30 ip
  7f9fa93fcdc8 sp 7f9f655c6b28 error 4 in
  libEGL.so.1.0.0[7f9fa93e2000+3]

  Xenial+Overlay
  Deb based Unity8

  Snaps:
  ubuntu-app-platform  1   33   canonical  devmode
  ubuntu-calendar-app  0.1.1   23   canonical  devmode

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

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

[Touch-packages] [Bug 1567796] Re: It is sometimes unable to find DELL WWAN module.

** Project changed: modemmanager => modemmanager (Ubuntu)

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

Title:
  It is sometimes unable to find DELL WWAN module.

Status in OEM Priority Project:
  Incomplete
Status in modemmanager package in Ubuntu:
  New

Bug description:
  I have a DELL WWAN module (DW5580) on my platform. Normally it could
  be detect and used in Ubuntu 16.04 daily image. However it is
  sometimes unusable and can not be detected.

  After debugging, we found there is an upstream patch that can fix the
  issue:

  
https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2

  Please merge the fix to modem manager to fix the issue.

  Ubuntu Xenial (daily image)
  Release: 16.04
  modemmanager:
    Installed: 1.4.12-1ubuntu1
    Candidate: 1.4.12-1ubuntu1
    Version table:
   *** 1.4.12-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1567796/+subscriptions

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

[Touch-packages] [Bug 1567796] [NEW] It is sometimes unable to find DELL WWAN module.

You have been subscribed to a public bug:

I have a DELL WWAN module (DW5580) on my platform. Normally it could be
detect and used in Ubuntu 16.04 daily image. However it is sometimes
unusable and can not be detected.

After debugging, we found there is an upstream patch that can fix the
issue:

https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2

Please merge the fix to modem manager to fix the issue.

Ubuntu Xenial (daily image)
Release: 16.04
modemmanager:
  Installed: 1.4.12-1ubuntu1
  Candidate: 1.4.12-1ubuntu1
  Version table:
 *** 1.4.12-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

** Affects: oem-priority
 Importance: Undecided
 Status: Incomplete

-- 
It is sometimes unable to find DELL WWAN module.
https://bugs.launchpad.net/bugs/1567796
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to modemmanager in Ubuntu.

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

[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

2017-02-07 Thread Trent Lloyd

** Changed in: avahi (Ubuntu)
   Status: New => Confirmed

** Changed in: avahi (Ubuntu)
   Importance: Undecided => High

** Changed in: avahi (Ubuntu)
 Assignee: (unassigned) => Trent Lloyd (lathiat)

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

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  The bug, and workaround, are clearly described in this mailing list
  thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

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

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

[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

2017-02-07 Thread Mike Pontillo

Since [the released version of] MAAS declares avahi-utils as a
"Recommends", you can use `apt-get --no-install-recommends` as an
alternate workaround. But then you'll lose zeroconf hostname discoveries
in MAAS.

I understand that this has been changed to a hard dependency in MAAS
2.2, so I'm glad this is getting some attention upstream.

** Changed in: maas
   Status: New => Invalid

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

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  The bug, and workaround, are clearly described in this mailing list
  thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

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

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

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

** Tags added: somerville

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

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

[Touch-packages] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

2017-02-07 Thread stinger

well said,

[0207/004636:FATAL:oxide_browser_process_main.cc(474)] Check failed:
state_ == STATE_NOT_STARTED || state_ == STATE_SHUTDOWN.
BrowserProcessMain::Shutdown() should be called before process exit

caused by

Feb 07 00:46:14 luna compiz[1795]: libGL error: MESA-LOADER: failed to retrieve 
device information
Feb 07 00:46:14 luna compiz[1795]: libGL error: Version 4 or later of flush 
extension not found
Feb 07 00:46:14 luna compiz[1795]: libGL error: failed to load driver: i915
Feb 07 00:46:14 luna compiz[1795]: libGL error: MESA-LOADER: failed to retrieve 
device information
Feb 07 00:46:15 luna compiz[1795]: libGL error: MESA-LOADER: failed to retrieve 
device information
Feb 07 00:46:15 luna compiz[1795]: libGL error: Version 4 or later of flush 
extension not found
Feb 07 00:46:15 luna compiz[1795]: libGL error: failed to load driver: i915
Feb 07 00:46:15 luna compiz[1795]: libGL error: MESA-LOADER: failed to retrieve 
device information

a snap of my journal is attached. this is what zesty means if i start
under unity7

** Attachment added: "webapp_crash-journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1560994/+attachment/4815125/+files/webapp_crash-journalctl

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

Title:
  webbrowser-app crashed with SIGABRT in
  oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Crash upon maximizimg window.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160318-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 14:37:35 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-08 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
   __GI_exit (status=) at exit.c:104
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

** Description changed:

- 
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613
  
  Version: NetworkManager 1.4.2
  
  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:
  
- DEVICE   TYPE  STATECONNECTION 
+ DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
- lo   loopback  unmanaged-- 
+ lo   loopback  unmanaged--
  
  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.
  
  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
-  * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
-  * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
-  * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
-  * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
-  * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.
+  * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
+  * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
+  * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
+  * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
+  * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.
  
  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.
  
  I'm wondering if we are missing to update the type in the Object created
  after renaming and re-detecting the type.
+ 
+ fix need landing LP: #1645698

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

** Changed in: oem-priority
 Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

** Changed in: oem-priority
 Assignee: Yuan-Chen Cheng (ycheng-twn) => Alex Tu (alextu)

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-07 Thread Shih-Yuan Lee

** Changed in: oem-priority/xenial
   Status: Confirmed => Triaged

** Changed in: oem-priority
   Status: Confirmed => Triaged

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

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

[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

2017-02-07 Thread Alex Tu

** Tags added: needed-by-1655901

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION 
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged-- 

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

** Tags removed: somerville

** Changed in: oem-priority
 Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

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

[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

Gerry,

We have somewhat commandeered this bug. It's being experienced on Intel
graphics by most people, despite the description mentioning nvidia up
top. There is a separate bug (which I can't find right now) for nvidia
driver failures, but given Mir doesn't actually support the Nvidia
driver yet I find that part confusing too.

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

Title:
  webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
  EGL configs found

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When trying to start webbrowser-app a unresponsive window appears and
  after a few moments it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 22:56:35 2016
  InstallationDate: Installed on 2016-04-28 (41 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1662738] [NEW] Error on boot login

2017-02-07 Thread Andrew Clevenger

Public bug reported:

I get an error every time I login after a boot.  It started after an
update and I am not sure what is causing it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Feb  7 20:13:06 2017
DistUpgraded: 2016-04-19 22:45:47,223 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-62-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04a3]
 NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GF106GLM [Quadro 2000M] [1028:14a3]
InstallationDate: Installed on 2015-11-15 (450 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Dell Inc. Precision M4600
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-20 (293 days ago)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Feb  7 20:07:24 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   21576 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  Error on boot login

Status in xorg package in Ubuntu:
  New

Bug description:
  I get an error every time I login after a boot.  It started after an
  update and I am not sure what is causing it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Feb  7 20:13:06 2017
  DistUpgraded: 2016-04-19 22:45:47,223 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

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

[Touch-packages] [Bug 1662632] Re: Installing 0.26.1 breaks calendar app (and others)

Someone will need to produce a stack trace of this crash...

** Changed in: mir
   Status: New => Incomplete

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

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

Title:
  Installing 0.26.1 breaks calendar app (and others)

Status in Mir:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Incomplete

Bug description:
  When installing the 0.26.1 silo I can no longer run calendar on
  Unity8. It gives this error in the logs:

  Feb 07 10:30:31 seven kernel: QSGRenderThread[6690]: segfault at 30 ip
  7f9fa93fcdc8 sp 7f9f655c6b28 error 4 in
  libEGL.so.1.0.0[7f9fa93e2000+3]

  Xenial+Overlay
  Deb based Unity8

  Snaps:
  ubuntu-app-platform  1   33   canonical  devmode
  ubuntu-calendar-app  0.1.1   23   canonical  devmode

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

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

[Touch-packages] [Bug 1662733] [NEW] Window titlebar and shadow flickers when scrubbing through menus (or when a tooltip appears)

Public bug reported:

Application titlebar and shadow flickers when scrubbing through menus,
or when a tooltip appears.

Test case:
  1. $ sol -- --desktop_file_hint=unity8
  2. Click on a menu and move the mouse horizontally to the next menu.

Expected: No change in the app window's title bar or shadow.
Observed: Flickering in the app title bar and shadow on every menu change.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.15+17.04.20170206-0ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Feb  8 09:55:14 2017
InstallationDate: Installed on 2016-11-03 (97 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.unity8-dash.log: [2017-02-08:09:55:07.500] "clickscope" : setActive: 
true

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

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


** Tags: amd64 apport-bug unity8-desktop visual-quality zesty

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

** Tags added: unity8-desktop visual-quality

** Summary changed:

- Application titlebar and shadow flickers when scrubbing through menus
+ Application titlebar and shadow flickers when scrubbing through menus (or 
when a tooltip appears)

** Description changed:

- Application titlebar and shadow flickers when scrubbing through menus
+ Application titlebar and shadow flickers when scrubbing through menus,
+ or when a tooltip appears.
  
  Test case:
-   1. $ sol -- --desktop_file_hint=unity8
-   2. Click on a menu and move the mouse horizontally to the next menu.
+   1. $ sol -- --desktop_file_hint=unity8
+   2. Click on a menu and move the mouse horizontally to the next menu.
  
  Expected: No change in the app window's title bar or shadow.
  Observed: Flickering in the app title bar and shadow on every menu change.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170206-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  8 09:55:14 2017
  InstallationDate: Installed on 2016-11-03 (97 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log: [2017-02-08:09:55:07.500] "clickscope" : setActive: 
true

** Summary changed:

- Application titlebar and shadow flickers when scrubbing through menus (or 
when a tooltip appears)
+ Window titlebar and shadow flickers when scrubbing through menus (or when a 
tooltip appears)

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

Title:
  Window titlebar and shadow flickers when scrubbing through menus (or
  when a tooltip appears)

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

Bug description:
  Application titlebar and shadow flickers when scrubbing through menus,
  or when a tooltip appears.

  Test case:
    1. $ sol -- --desktop_file_hint=unity8
    2. Click on a menu and move the mouse horizontally to the next menu.

  Expected: No change in the app window's title bar or shadow.
  Observed: Flickering in the app title bar and shadow on every menu change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170206-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  8 09:55:14 2017
  InstallationDate: Installed on 2016-11-03 (97 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log: [2017-02-08:09:55:07.500] "clickscope" : setActive: 
true

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

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

[Touch-packages] [Bug 1662397] Re: a suspicious integer overflow in libselinux/src/compute_user.c : 54

Thanks shqking.

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

Title:
  a suspicious integer overflow in libselinux/src/compute_user.c : 54

Status in libselinux package in Ubuntu:
  Invalid

Bug description:
  Hello.

  A suspicious integer overflow is found in libselinux/src/compute_user.c : 54.
  The source code is here. 
(https://github.com/SELinuxProject/selinux/blob/master/libselinux/src/compute_user.c#L54)

  If variable "nel" can be crafted as 0x , the integer addition
  at line 54 would overflow to 0, leading to no memory space allocated.
  This would further lead to buffer overflow at line 62 in a loop. Note
  that vulnerable "nel" is read from a file "selinux_mnt/user",
  following the path, i.e. line 27, line 28, line 45 and line 49.

  Since I'm not an expert in the source code of libselinux, I'm not sure
  whether "nel" can be assigned with that very big integer (0x
  ). If so, this issue is a severe bug definitely. If not, it is a
  false positive and please ignore it.

  Thanks a lot.

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

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

[Touch-packages] [Bug 1662632] Re: Installing 0.26.1 breaks calendar app (and others)

** Changed in: mir
Milestone: None => 0.26.1

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

** Changed in: qtubuntu (Ubuntu)
   Importance: Undecided => High

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

Title:
  Installing 0.26.1 breaks calendar app (and others)

Status in Mir:
  New
Status in qtubuntu package in Ubuntu:
  New

Bug description:
  When installing the 0.26.1 silo I can no longer run calendar on
  Unity8. It gives this error in the logs:

  Feb 07 10:30:31 seven kernel: QSGRenderThread[6690]: segfault at 30 ip
  7f9fa93fcdc8 sp 7f9f655c6b28 error 4 in
  libEGL.so.1.0.0[7f9fa93e2000+3]

  Xenial+Overlay
  Deb based Unity8

  Snaps:
  ubuntu-app-platform  1   33   canonical  devmode
  ubuntu-calendar-app  0.1.1   23   canonical  devmode

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

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

[Touch-packages] [Bug 1662397] Re: a suspicious integer overflow in libselinux/src/compute_user.c : 54

2017-02-07 Thread shqking

Hi Arnold.

I got the reply from Stephen Smalley, saying that the overflow is not
possible (https://github.com/SELinuxProject/selinux/issues/47).

So i will close this issue.

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

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

Title:
  a suspicious integer overflow in libselinux/src/compute_user.c : 54

Status in libselinux package in Ubuntu:
  Invalid

Bug description:
  Hello.

  A suspicious integer overflow is found in libselinux/src/compute_user.c : 54.
  The source code is here. 
(https://github.com/SELinuxProject/selinux/blob/master/libselinux/src/compute_user.c#L54)

  If variable "nel" can be crafted as 0x , the integer addition
  at line 54 would overflow to 0, leading to no memory space allocated.
  This would further lead to buffer overflow at line 62 in a loop. Note
  that vulnerable "nel" is read from a file "selinux_mnt/user",
  following the path, i.e. line 27, line 28, line 45 and line 49.

  Since I'm not an expert in the source code of libselinux, I'm not sure
  whether "nel" can be assigned with that very big integer (0x
  ). If so, this issue is a severe bug definitely. If not, it is a
  false positive and please ignore it.

  Thanks a lot.

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

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

[Touch-packages] [Bug 1662602] Re: GTK+ windows don't render when larger than 478x478

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

Confirmed and duplicate of bug 1649662

** This bug has been marked a duplicate of bug 1649662
   [regression] resizing some apps in Unity8 makes them distorted and freeze 
(usually software clients)

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

Title:
  GTK+ windows don't render when larger than 478x478

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  PPA containing a more recent GTK+:
  https://launchpad.net/~attente/+archive/ubuntu/gtk-mir

  Under U8, GTK+ windows don't render when the width and height are both
  >= 479.

  If the app starts at a size larger than that, the window will
  initially appear entirely black.

  Once resized < 479 in either dimension, the window will render
  properly.

  After that, when resizing larger than 478x478, the window only
  upscales the most recent framebuffer contents.

  I haven't 100% confirmed that this is not GTK+. However:

  - This bug does not occur when tested with miral-shell
  - GTK+ is receiving configure events for surface resizes
  - GTK+ is re-creating cairo surfaces that match the larger size
  - GTK+ is still calling mir_buffer_stream_swap_buffers_sync at larger sizes
  - I don't think this specific 478/479 number is coming from GTK+, the 
initial/min/max sizes aren't that close to it

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

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

[Touch-packages] [Bug 1584685] Re: Xenial fails to install with Preseed d-i apt-setup/local0/repository set

2017-02-07 Thread Mathieu Trudel-Lapierre

I can't reproduce this issue here; trying to install ubuntu-server and
preseeding apt-
setup/local0/repository="http://ppa.launchpad.net/cyphermox/ppa/ubuntu
zesty main".

The preseeded repository is indeed showing in sources.list and is
written correctly.

If you can still reproduce this bug, please include both the exact
preseed used, along with the full contents of /etc/apt/sources.list at
the end of the install so we can see what happens.

** No longer affects: console-setup

** Changed in: console-setup (Ubuntu)
   Status: Confirmed => Invalid

** Package changed: debian-installer (Ubuntu) => apt-setup (Ubuntu)

** Changed in: apt-setup (Ubuntu)
   Importance: Critical => High

** Changed in: apt-setup (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: console-setup (Ubuntu)
   Importance: Critical => Undecided

** Changed in: hundredpapercuts
   Status: Confirmed => Incomplete

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

Title:
  Xenial fails to install with Preseed d-i apt-setup/local0/repository
  set

Status in One Hundred Papercuts:
  Incomplete
Status in apt-setup package in Ubuntu:
  Incomplete
Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  Preseed install of Ubuntu Xenial fails with d-i apt-
  setup/localX/repository option set. The problem is that debian
  installer does not concat the last string in sources.list correctly.
  The prefix "deb" is missing. So apt fails to update and the installer
  cannot continue because there are no valid package sources.

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

2017-02-07 Thread Mauricio Faria de Oliveira

Hi Christian,

Thanks for handling it to xenial-updates.

BTW, that point about the package to make the point release ISO is so
that people who use the ISO as package repository (which happens in some
scenarios like xCAT clusters), and not always get more updates from the
internet, can get it.

cheers

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2017-02-07 Thread Catch

This occured to me today, seemingly after no update for changes made to
my laptop.  I fixed in in the following way.   Hope this helps
someone...

What did not work: Running the latest update, installing kernel 4.8.x or
4.4.25, or any of the fixes you can find doing a google search for
kubuntu 16.04 suspend.  I had finally tried a commond line common pm-
suspend, which caused the laptop to freeze and then freeze on booting.

I have dell vostro 3500 laptop.

What worked:  I reinstalled the kubuntu 16.04.1 base.  I have a separate
/home partition so that was not effected by the reinstall (i didn't
format it.  just specified to mount /home in the install setup).

reinstall was fast.  After install finished, I also ran the update... to
kernel 4.4.0-62-generic.  I did not test the suspend here.  I installed
powernap and cpufreq, then rebooted.  Later I closed the lid and the
computer suspended.  All set and it works fine.

Not sure what was the exact problem was or the fix.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1662714] Re: apport-gtk crashed with SIGSEGV

2017-02-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1552577, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1662714/+attachment/4815074/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1662714/+attachment/4815077/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1662714/+attachment/4815079/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1662714/+attachment/4815080/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1662714/+attachment/4815081/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1662714/+attachment/4815082/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1662714/+attachment/4815083/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1552577

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  Appeared during multiple bug reports:
  https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1662703
  https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1662710

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Feb  7 14:54:22 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-01-31 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f86624fe889:mov(%rbx),%rdi
   PC (0x7f86624fe889) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.

2017-02-07 Thread AJ Fite

This is effecting me on Xubuntu 17.04

Intel Skylake i7 with HD530 Graphics (Lenovo Thninkpad T460s)

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

Title:
  Unable to unlock session after suspend using lightdm-gtk-greeter.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+subscriptions

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

[Touch-packages] [Bug 1662677] Re: apt-daily.service could rarely update the system

Hi Jérôme, thanks for the bug report. The apt-daily.timer starts the
apt-daily.service, which is still running at the end of your plot. That
doesn't necessarily mean it's doing the right thing but at least it has
an opportunity to handle many of the daily tasks.

We may need to tune the rules that fire the timer to make it more likely
for updates to be installed in a timely fashion.

At least with 16.04 LTS and newer, daily updates are enabled by default.
So this already is a welcome change from previous releases when users
had to opt in to daily updates manually.

Thanks

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

Title:
  apt-daily.service could rarely update the system

Status in apt package in Ubuntu:
  New

Bug description:
  On startup of computers with hard disks, apt-daily.service could
  complete before the Internet can be reached.

  A HDD computer would rarely get updates if it is just started daily
  after 6 am and it is running only 1 hour. Basically, the random time
  between 6 am and 18 pm will rarely be between 6 and 7 am. Finally this
  computer may catch a random update from time to time.

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

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

[Touch-packages] [Bug 1662677] Re: apt-daily.service could rarely update the system

** Information type changed from Private Security to Public Security

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

Title:
  apt-daily.service could rarely update the system

Status in apt package in Ubuntu:
  New

Bug description:
  On startup of computers with hard disks, apt-daily.service could
  complete before the Internet can be reached.

  A HDD computer would rarely get updates if it is just started daily
  after 6 am and it is running only 1 hour. Basically, the random time
  between 6 am and 18 pm will rarely be between 6 and 7 am. Finally this
  computer may catch a random update from time to time.

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

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

[Touch-packages] [Bug 1662244] Re: lightdm fails to start

2017-02-07 Thread Doug Goldstein

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

** Also affects: unity-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: lightdm

** No longer affects: lightdm (Ubuntu)

** Summary changed:

- lightdm fails to start
+ unity-greeter crashes causing lightdm to fail to start

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

Title:
  unity-greeter crashes causing lightdm to fail to start

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1662244/+subscriptions

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

[Touch-packages] [Bug 1662244] Re: lightdm fails to start

2017-02-07 Thread Doug Goldstein

Realized that it's likely unity-greeter because I'm seeing a lot of...

[25886.110278] traps: unity-greeter[820] trap int3 ip:7fb856a35241
sp:7fff145ad0f0 error:0 in libglib-2.0.so.0.5000.0[7fb8569e5000+11]

I've got libglib2.0 2.50.2-2ubuntu1  so I tried to roll back to 2.50.0-1
but that didn't help either. libglib-2.0 was something that was upgraded
in between my last reboot.

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

Title:
  unity-greeter crashes causing lightdm to fail to start

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1662244/+subscriptions

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

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

Actually, the False part is setting the default value for the key if it
doesn't exit.

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+subscriptions

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

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

apt_pkg.config.find_b() returns a boolean not a string.

"find_b(key[, default=False]) → bool Return the boolean value stored at
key, or the value given by the bool object default if the requested
option is not set."

>From apt.alioth.debian.org/python-apt-
doc/library/apt_pkg.html#apt_pkg.config.find_b

So it's not a bug in unattended-upgrade-shutdown as checking for False
is correct.

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+subscriptions

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

[Touch-packages] [Bug 1648224] Re: [krilin] Dialer-app surface freezes during outgoing calls

2017-02-07 Thread Pat McGowan

For those experiencing this please provide any additional information
you can as it is not reproducible.

How are you starting the dialer before the call? Does it matter if is
started from the app scope, the launcher, contacts, etc?

Does it happen every time?

Does it help to clear the dialer's QML cache (in
/home/phablet/.cache/QML)

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

Title:
  [krilin] Dialer-app surface freezes during outgoing calls

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  My phone is a BQ Aquaris E4.5 Ubuntu Edition, running with Ubuntu
  15.04 OTA 14 (stable channel).

  The dialer app version installed is 0.1+15.04.20160825.2-0ubuntu1.

  1. What I do
  When I do an outgoing call.

  2. What I expect
  The surface of the app continues to work, I can hang up, put on the 
microphone etc.

  3. What happens 
  The surface of the dialer-app freezes, the call goes on. But I cannot hang 
up, turn on the microphone etc. 

  The only workaround is:
  - close dialer app in Task Manager
  - Open other app.
  - Re-open dialer app via the green bar on the top.
  - Re-opened dialer app has working surface, so I can hang up, turn on the 
microphone etc.

  The bug did already appear in OTA13 and is still present now in OTA
  14.

  The bug does not occure when I accept an incoming call.

  The bus is reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1648224/+subscriptions

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

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

Could you provide the configuration line "Unattended-
Upgrade::InstallOnShutdown" from /etc/apt/apt.conf.d/20auto-upgrades and
50unattended-upgrades?  Thanks in advance!

** Changed in: unattended-upgrades (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+subscriptions

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

[Touch-packages] [Bug 1661523] Re: AppArmor profile for Firefox (51.0.1) after took in enforced mode falls back into unconfined

Sziráki, thanks for filing this bug. I've reviewed your logs and can't
figure out what exactly is wrong:

- Your kernel logs shows over 18000 DENIED accesses requested by
processes executing with a profile that matches
'profile="/usr/lib/firefox/'. Thus it certainly appears that much of
Firefox is executing while confined. Can you provide ps auxwZ output
that shows firefox processes that aren't executing in their profile?

- Your aa-status output shows that Chromium is executing in complain
mode.

- Note that the default AppArmor profile for Firefox is in fact very
permissive. See the /etc/apparmor.d/abstractions/ubuntu-browsers.d/user-
files file for the rules involved.

Can you please identify more concretely what is happening that you feel
is a bug?

Thanks

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

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

Title:
  AppArmor profile for Firefox (51.0.1) after took in enforced mode
  falls back into unconfined

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  The profile for Firefox after took in enforced mode falls back into
  unconfined mode, and download into any selected folders in my account,
  not only the allowed one.

  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  apt-cache policy apparmor
  apparmor:
Telepítve: 2.10.95-0ubuntu2.5
Jelölt:2.10.95-0ubuntu2.5
Verziótáblázat:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Feb  3 09:03:18 2017
  InstallationDate: Installed on 2015-09-19 (502 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=429aedd2-83c1-4b53-b23f-c8099109f278 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => High

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+subscriptions

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

[Touch-packages] [Bug 1662327] Re: apt-daily.service was slowing down one system startup

2017-02-07 Thread Jérôme

SSD aren't mandatory.

HDD computers would rarely get updates if they are just started after 6
am and are running only 1 hour in the morning. Basically, the random
time between 6 am and 18 pm will rarely be between 6 and 7 am.

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

Title:
  apt-daily.service was slowing down one system startup

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I don't understand why this service started before the light-dm invite
  was displayed to the end user.

  Up to the light-dm invite, the system needed roughly twice the time it
  usualy needs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.19
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb  6 21:28:54 2017
  InstallationDate: Installed on 2017-02-01 (4 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apt: 2017-02-03T22:39:52.394852

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

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

Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-07 Thread Rik Mills

On 30/01/17 13:27, Andre Heinecke wrote:
> I've discussed possibly high resource usage of the gpgme test suite
> (there were also other complaints) and we reduced it accordingly:
> https://git.gnupg.org/cgi-
> bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=7bd6ab4a91d43d7cbf5d347c0c12e0e4f9f7e3bf
> 
> This might fix the armhf error in t-thread-keylist-verify

I tried building today's git snapshot, and still get test failures on
armhf and arm64

https://launchpad.net/~rikmills/+archive/ubuntu/staging1/+sourcepub/7468978
/+listing-archive-extra

I can't test powerpc in a ppa.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1661199] Re: Apt-cacher-ng fails on https repo

** Tags added: xenial

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

Title:
  Apt-cacher-ng fails on https repo

Status in apt package in Ubuntu:
  Triaged
Status in apt-cacher-ng package in Ubuntu:
  Invalid

Bug description:
  Following the instructions to add the docker repo here:
  https://docs.docker.com/engine/installation/linux/ubuntu/

  /etc/apt/sources.list contains the repo: 
  deb https://apt.dockerproject.org/repo/ ubuntu-xenial main

  When running through apt-cacher-ng, apt-get update returns: 
  $ sudo apt-get update
  Ign:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease
  Ign:2 https://apt.dockerproject.org/repo ubuntu-xenial Release
  Ign:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 
Packages.diff/Index
  Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages
  Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages
  Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US
  Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en
  Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages
  Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages
  Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages
  Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US
  Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en
  Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages
  Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages
  Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages
  Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US
  Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en
  Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages
  Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages
  Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages
  Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US
  Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en
  Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages
  Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages
  Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages
  Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US
  Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en
  Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages
  Err:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages
Received HTTP code 403 from proxy after CONNECT
  Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages
  Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US
  Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en
  Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages
  Ign:9 http://dl.google.com/linux/chrome/deb stable InRelease
  Hit:10 http://archive.ubuntu.com/ubuntu xenial InRelease
  Hit:11 http://dl.google.com/linux/chrome/deb stable Release  
  Hit:13 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:14 http://archive.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done
  W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' 
does not have a Release file.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  E: Failed to fetch 
https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages
  Received HTTP code 403 from proxy after CONNECT
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  
  When apt is set to disable the proxy, using the following /etc/apt/apt.conf:
  Acquire::http::Proxy "http://127.0.0.1:/;;
  Acquire::https::Proxy "DIRECT";

  (note that the port has been changed from the default)

  The response is:
  $ sudo apt-get update
  Hit:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease
  Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease 
  Hit:3 http://archive.ubuntu.com/ubuntu xenial InRelease
  Hit:4 http://dl.google.com/linux/chrome/deb stable Release  
  Hit:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done

  
  $lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  $ apt-cache policy apt-cacher-ng

[Touch-packages] [Bug 1662670] [NEW] Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-MfyGcj8Fq2: Connection refused

2017-02-07 Thread Nico Orrù

Public bug reported:

Got this error after switching from Cinnamon to Xubuntu-Desktop

nico@nico-lenovo-ubuntu:~$ dropbox stop
Dropbox daemon stopped.
nico@nico-lenovo-ubuntu:~$ dropbox start
Starting Dropbox...
** (dropbox:3817): WARNING **: Couldn't connect to accessibility bus: Failed to 
connect to socket /tmp/dbus-MfyGcj8Fq2: Connection refused
Done!

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dbus 1.10.10-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.8.0-37.39-lowlatency 4.8.16
Uname: Linux 4.8.0-37-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Feb  7 21:02:58 2017
InstallationDate: Installed on 2016-10-20 (110 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed yakkety

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

Title:
  Couldn't connect to accessibility bus: Failed to connect to socket
  /tmp/dbus-MfyGcj8Fq2: Connection refused

Status in dbus package in Ubuntu:
  New

Bug description:
  Got this error after switching from Cinnamon to Xubuntu-Desktop

  nico@nico-lenovo-ubuntu:~$ dropbox stop
  Dropbox daemon stopped.
  nico@nico-lenovo-ubuntu:~$ dropbox start
  Starting Dropbox...
  ** (dropbox:3817): WARNING **: Couldn't connect to accessibility bus: Failed 
to connect to socket /tmp/dbus-MfyGcj8Fq2: Connection refused
  Done!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dbus 1.10.10-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-lowlatency 4.8.16
  Uname: Linux 4.8.0-37-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb  7 21:02:58 2017
  InstallationDate: Installed on 2016-10-20 (110 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1634855] Re: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.

** Tags added: yakkety

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

Title:
  Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at
  ../src/network/networkd-link.c:697, function link_enter_configured().
  Aborting.

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  the net of my PC is configured via systemd-networkd + systemd-
  resolved. And last two weeks I faced with the problem when my net is
  down. "journalctl -xe" helped to detect this issue:

  окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long
  окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down
  окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier
  окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == 
LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, 
function link_enter_configured(). Aborting.
  окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers 
for interface enp3s0, ignoring: Argument list too long

  
  When I type "systemctl restart systemd-networkd", nothing happens, net is 
still down. When I type "systemctl restart systemd-resolved", it's all starting 
to work fine, as usual.

  A little bit of googling gave me this bug in systemd bugtracker: 
https://github.com/systemd/systemd/issues/2228
  and this PR: https://github.com/systemd/systemd/pull/3224

  Looks like this issue was fixed in systemd-230. So can you backport
  this patch to systemd package?

  I can patch it and test it myself, actually, but it would be really
  nice if there will be no need to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu11
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 19 13:58:42 2016
  InstallationDate: Installed on 2016-09-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-02-07 Thread Dan Streetman

with udev version 204-5ubuntu20.22 the /dev/disk/by-id/ symlinks are
incorrect:

ubuntu@ip-172-31-27-212:/dev/disk/by-id$ apt list --installed udev
Listing... Done
udev/trusty-updates,now 204-5ubuntu20.22 amd64 [installed,upgradable to: 
204-5ubuntu20.24]

ubuntu@ip-172-31-27-212:/dev/disk/by-id$ ls -l
total 0
lrwxrwxrwx 1 root root 13 Feb  7 20:05 nvme-Amazon -> ../../nvme0n1


with udev version 204-5ubuntu20.24, symlinks are created correctly:

ubuntu@ip-172-31-27-212:/dev/disk/by-id$ apt list --installed udev
Listing... Done
udev/trusty-proposed,now 204-5ubuntu20.24 amd64 [installed]
ubuntu@ip-172-31-27-212:/dev/disk/by-id$ ls -l
total 0
lrwxrwxrwx 1 root root 13 Feb  7 20:10 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1A53C9B72B4551070 -> ../../nvme0n1
lrwxrwxrwx 1 root root 13 Feb  7 20:10 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS6A53C9B72B4551070 -> ../../nvme1n1


** Tags removed: verification-needed
** Tags added: verification-done verification-done-trusty

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in maas-images:
  Fix Released
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+subscriptions

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

[Touch-packages] [Bug 1652282] Re: Wayland default policy prohibits root applications

2017-02-07 Thread Nikita Yerenkov-Scott

@Phillip, This is an intended policy and it is there for security
reasons so rather than decreasing security standards, I think it would
be best for GParted to simply meet them.

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

Title:
  Wayland default policy prohibits root applications

Status in GParted:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22 that GParted does not run when I try to run it
  as root. That is when I click the icon and enter my password nothing
  happens. I have found that when running what is run when the icon is
  clicked that the output in Terminal is (gparted-pkexec):

  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/boot.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/boot.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/tmp.mount.

  So I am now unable to launch and use GParted as root which is really
  the only way I can run it in order to make changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 23 11:13:13 2016
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gparted
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

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

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

[Touch-packages] [Bug 1662513] Re: Update to 9.21 in Trusty

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is available, members of the security team will review it and
publish the package. See the following link for more information:
https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures

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

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

Title:
  Update to 9.21 in Trusty

Status in libav package in Ubuntu:
  Incomplete

Bug description:
  version 9.21:
  - mpeg12: move setting first_field to mpeg_field_start() (libav/999)
  - mpeg12: avoid signed overflow in bitrate calculation (libav/981)
  - mpegvideo_parser: avoid signed overflow in bitrate calculation (libav/981)
  - avformat/output-example: Declare link dependency on libswscale in the 
Makefile
  - build: output-example: Add avutil to ELIBS in link command

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (i.e. menus and tooltips)

2017-02-07 Thread Daniel d'Andrada

** Changed in: qtmir (Ubuntu)
   Status: Triaged => Fix Released

** No longer affects: qtmir

** Changed in: qtubuntu
   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/1543467

Title:
  Unity8 can't correctly display multi-surface apps (i.e. menus and
  tooltips)

Status in Canonical System Image:
  Triaged
Status in qtubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1241752] Re: Crash when opening image files larger than 5M (>5M)

2017-02-07 Thread Vincent Thiele

** Tags added: xenial

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

Title:
  Crash when opening image files larger than 5M (>5M)

Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  This is similar to the bug reported here: http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=710701

  However, the crash that is now getting generated is from an entirely
  different call and file.  Specifically, the error is:

  eog: /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c:619: 
_cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed.
  Aborted (core dumped)

  In the message above, I was using eog, but this affects other apps,
  like gThumb as well.

  In terms of the environment, I'm using Ubuntu 13.10 on an 64-bit
  machine, and am using libcairo2-1.12.16.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libcairo2 1.12.16-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Fri Oct 18 11:08:27 2013
  InstallationDate: Installed on 2013-04-25 (176 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cairo
  UpgradeStatus: Upgraded to saucy on 2013-10-15 (2 days ago)

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

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

[Touch-packages] [Bug 1652282] Re: Wayland default policy prohibits root applications

2017-02-07 Thread Phillip Susi

** Summary changed:

- GParted fails to run as root under Wayland
+ Wayland default policy prohibits root applications

** Package changed: gparted (Ubuntu) => wayland (Ubuntu)

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

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

Title:
  Wayland default policy prohibits root applications

Status in GParted:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22 that GParted does not run when I try to run it
  as root. That is when I click the icon and enter my password nothing
  happens. I have found that when running what is run when the icon is
  clicked that the output in Terminal is (gparted-pkexec):

  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/boot.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/boot.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/tmp.mount.

  So I am now unable to launch and use GParted as root which is really
  the only way I can run it in order to make changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 23 11:13:13 2016
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gparted
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

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

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

[Touch-packages] [Bug 1662397] Re: a suspicious integer overflow in libselinux/src/compute_user.c : 54

** Information type changed from Private Security to Public Security

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

Title:
  a suspicious integer overflow in libselinux/src/compute_user.c : 54

Status in libselinux package in Ubuntu:
  New

Bug description:
  Hello.

  A suspicious integer overflow is found in libselinux/src/compute_user.c : 54.
  The source code is here. 
(https://github.com/SELinuxProject/selinux/blob/master/libselinux/src/compute_user.c#L54)

  If variable "nel" can be crafted as 0x , the integer addition
  at line 54 would overflow to 0, leading to no memory space allocated.
  This would further lead to buffer overflow at line 62 in a loop. Note
  that vulnerable "nel" is read from a file "selinux_mnt/user",
  following the path, i.e. line 27, line 28, line 45 and line 49.

  Since I'm not an expert in the source code of libselinux, I'm not sure
  whether "nel" can be assigned with that very big integer (0x
  ). If so, this issue is a severe bug definitely. If not, it is a
  false positive and please ignore it.

  Thanks a lot.

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

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

[Touch-packages] [Bug 1652282] [NEW] Wayland default policy prohibits root applications

You have been subscribed to a public bug:

I have found that after switching from Xorg to Wayland on Ubuntu GNOME
16.10 with GNOME 3.22 that GParted does not run when I try to run it as
root. That is when I click the icon and enter my password nothing
happens. I have found that when running what is run when the icon is
clicked that the output in Terminal is (gparted-pkexec):

Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
Created symlink /run/systemd/system/boot.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
No protocol specified

(gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot-efi.mount.
Removed /run/systemd/system/boot.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/run-user-120.mount.
Removed /run/systemd/system/tmp.mount.

So I am now unable to launch and use GParted as root which is really the
only way I can run it in order to make changes.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gparted 0.25.0-1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 23 11:13:13 2016
InstallationDate: Installed on 2016-05-15 (221 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gparted
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

** Affects: gparted
 Importance: Medium
 Status: Confirmed

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug gnome3-ppa third-party-packages wayland-session 
yakkety
-- 
Wayland default policy prohibits root applications
https://bugs.launchpad.net/bugs/1652282
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-02-07 Thread elene bh

Same problem with my asus E200HA
I've tried Ubuntu both 16.10 and 16.04
Also i've tried Lubuntu ans Xubuntu
No sound

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Touch-packages] [Bug 1654313] Re: The greeter is not shown when switching users

2017-02-07 Thread Josh Arenson

** Attachment added: 
"indicator-session_12.10.5+17.04.20161201-0ubuntu1_amd64.deb"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654313/+attachment/4814924/+files/indicator-session_12.10.5+17.04.20161201-0ubuntu1_amd64.deb

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

Title:
  The greeter is not shown when switching users

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

Bug description:
  This is not consistent, when switching between two user sessions (one
  unity8 snap on classic and one unity7) I sometimes get presented with
  the unity8 lock screen that only provides the current session as an
  option.

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

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

[Touch-packages] [Bug 1621124] Re: Can't turn bluetooth off

2017-02-07 Thread GTriderXC

Today I paired my new Philips Bluetooth speaker with Krillin on OTA-15 (BQ 
Aquaris E4.5). I was able to pair but there was no sound: both speaker and 
phone stayed silent till I rebooted it. On reboot (9:24 on my video it played 
shortly a sound from an incoming message).
As You see on 7:10, 7:50 and 9:00 it turns on by itself. The icon in a 
notification area shows that device is connected though it is not.
What's more, it kills battery pretty quickly (I lost ~40% within a few Minutes).

https://youtu.be/hC4eNkWFYo4

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

Title:
  Can't turn bluetooth off

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  /!\ ARM64 BUILD ONLY

  Enviroment:

  current build number: 33
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-09-07 11:29:04
  version version: 33
  version ubuntu: 20160906
  version device: 20160906.0
  version custom: 20160906

  Steps to reproduce:

  Preconditions_ bluetooth on
  1º Go to System settings>Battery or indicator-bluetooth
  2º Switch bluetooth off and wait around 30 secs
  3º Check bluetooth toggle slides off->on again

  Current result: Can't turn bluetooth off

  Expected result: Bluetooth toggles should turn off bt

  Add:video attached

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

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

[Touch-packages] [Bug 1662619] [NEW] dependencies on lsb-release should be reevaluated

Public bug reported:

apport has a build-dep and python[3]-apport depends on lsb-release,
however apport/packaging.py only uses this as a fallback after looking
at /etc/os-release.

That being said backends/packaging-apt-dpkg.py contains a
get_distro_codename function which doesn't use /etc/os-release.

** Affects: apport (Ubuntu)
 Importance: Low
 Status: Triaged

** Affects: apport (Ubuntu Zesty)
 Importance: Low
 Status: Triaged


** Tags: zesty

** Tags added: zesty

** Also affects: apport (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: apport (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: apport (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: apport (Ubuntu Zesty)
   Importance: Medium => Low

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

Title:
  dependencies on lsb-release should be reevaluated

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Zesty:
  Triaged

Bug description:
  apport has a build-dep and python[3]-apport depends on lsb-release,
  however apport/packaging.py only uses this as a fallback after looking
  at /etc/os-release.

  That being said backends/packaging-apt-dpkg.py contains a
  get_distro_codename function which doesn't use /etc/os-release.

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

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

[Touch-packages] [Bug 1662620] [NEW] "ip addr add" permits illegal labels

2017-02-07 Thread Nahuel Greco

Public bug reported:

ip-address(8) manpage states:

  label NAME
Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.

But you can omit the colon, "ip addr add" is ONLY checking the label is
prefixed with the device:

# ip addr add 1.1.1.1 label test1 dev eth0
"dev" (eth0) must match "label" (test1).

# ip addr add 1.1.1.2 label eth0-test2 dev eth0

# ip addr add 1.1.1.3 label eth0:test3 dev eth0


Now ifconfig becomes confused about eth0-test2:

# ifconfig eth0-test2
eth0-test2: error fetching interface information: Device not found

# ifconfig eth0:test3
eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c  
  inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  Interrupt:171 

And daemons like ntpd also log errors about the interface with the
illegal label:

ntpd[7570]: eth0-test3: getting interface flags: No such device
  ## => many of this error per minute until:
ntpd[7570]: Too many errors.  Shutting up.


So, I think ip addr show disallow adding address with illegal (as stated by his 
own documentation) labels, it must also check for the colon following the dev 
name.

Version: 4.3.0-1ubuntu3

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

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

Title:
  "ip addr add" permits illegal labels

Status in iproute2 package in Ubuntu:
  New

Bug description:
  ip-address(8) manpage states:

label NAME
  Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.

  But you can omit the colon, "ip addr add" is ONLY checking the label
  is prefixed with the device:

  # ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).

  # ip addr add 1.1.1.2 label eth0-test2 dev eth0

  # ip addr add 1.1.1.3 label eth0:test3 dev eth0
  

  Now ifconfig becomes confused about eth0-test2:

  # ifconfig eth0-test2
  eth0-test2: error fetching interface information: Device not found

  # ifconfig eth0:test3
  eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c  
inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
Interrupt:171 

  And daemons like ntpd also log errors about the interface with the
  illegal label:

  ntpd[7570]: eth0-test3: getting interface flags: No such device
## => many of this error per minute until:
  ntpd[7570]: Too many errors.  Shutting up.

  
  So, I think ip addr show disallow adding address with illegal (as stated by 
his own documentation) labels, it must also check for the colon following the 
dev name.

  Version: 4.3.0-1ubuntu3

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

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

[Touch-packages] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  webbrowser-app crashed with SIGABRT in
  oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Crash upon maximizimg window.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160318-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 14:37:35 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-08 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
   __GI_exit (status=) at exit.c:104
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

2017-02-07 Thread Chris Coulson

The abort here is a red herring and is masking the primary issue, which
you can see a few frames further down:

#5  0x7f87c8e3d088 in __run_exit_handlers (status=status@entry=1, 
listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
atfct = 
onfct = 
cxafct = 
#6  0x7f87c8e3d0d5 in __GI_exit (status=status@entry=1) at exit.c:104
No locals.
#7  0x7f87bd0d2ea1 in gdk_x_io_error (display=) at 
/build/gtk+2.0-KsZKkB/gtk+2.0-2.24.30/gdk/x11/gdkmain-x11.c:544
No locals.
#8  0x7f87c8387cee in _XIOError (dpy=dpy@entry=0x5646ce4eb0f0) at 
../../src/XlibInt.c:1464
No locals.
#9  0x7f87c8385d4a in _XReply (dpy=dpy@entry=0x5646ce4eb0f0, 
rep=rep@entry=0x7ffebcbf6160, extra=extra@entry=0, discard=discard@entry=1) at 
../../src/xcb_io.c:708
error = 0x0
c = 
reply = 0x0
current = 0x5646cf5f8b60
__PRETTY_FUNCTION__ = "_XReply"
#10 0x7f87c838148d in XSync (dpy=0x5646ce4eb0f0, discard=0) at 
../../src/Sync.c:44
rep = {type = 167 '\247', revertTo = 98 'b', sequenceNumber = 48319, 
length = 28, focus = 3465286592, pad1 = 0, pad2 = 3166658864, pad3 = 32766, 
pad4 = 32, pad5 = 0}
#11 0x7f87c764deda in dri2SwapBuffers () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#12 0x7f87cb956342 in QGLXContext::swapBuffers(QPlatformSurface*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
No symbol table info available.
#13 0x7f87ca495326 in QOpenGLContext::swapBuffers(QSurface*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
No symbol table info available.
#14 0x7f87cae4978e in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
No symbol table info available.
#15 0x7f87cae4a521 in QSGGuiThreadRenderLoop::event(QEvent*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
No symbol table info available.
#16 0x7f87cb20e05c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#17 0x7f87cb213516 in QApplication::notify(QObject*, QEvent*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#18 0x7f87c9cf45bb in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#19 0x7f87c9d4986d in QTimerInfoList::activateTimers() () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#20 0x7f87c9d49d71 in timerSourceDispatch(_GSource*, int (*)(void*), void*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#21 0x7f87c86cc127 in g_main_context_dispatch () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#22 0x7f87c86cc380 in g_main_context_iterate.isra () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#23 0x7f87c86cc42c in g_main_context_iteration () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#24 0x7f87c9d4aa4f in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#25 0x7f87c9cf1d7a in 
QEventLoop::exec(QFlags) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#26 0x7f87c9cf9e1c in QCoreApplication::exec() () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#27 0x5646ccf87e26 in BrowserApplication::run (this=0x7ffebcbf6930) at 
/build/webbrowser-app-W5j7m8/webbrowser-app-0.23+16.04.20160318/src/app/browserapplication.cpp:261
No locals.
#28 0x5646ccf7ca85 in main (argc=1, argv=0x7ffebcbf6a88) at 
/build/webbrowser-app-W5j7m8/webbrowser-app-0.23+16.04.20160318/src/app/webbrowser/webbrowser-app.cpp:122
app = { = { = {}, 
static staticMetaObject = {d = {superdata = 0x7f87cb710140 
, stringdata = 0x5646ccfca9c0 
, data = 0x5646ccfca960 
, static_metacall = 0x5646ccf92bf0 
, relatedMetaObjects = 0x0, extradata = 0x0}}, m_arguments = 
{ = { = {}, {p = 
{static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin = 0, 
end = 0, array = {0x0}}, d = 0x5646ce80fbe0}, d = 0x5646ce80fbe0}}, }, m_engine = 0x5646ce818880, m_window = 0x5646ce8c13c0, m_component = 
0x5646ce8b8570, m_webbrowserWindowProxy =

[Touch-packages] [Bug 1621124] Re: Can't turn bluetooth off

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

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

Title:
  Can't turn bluetooth off

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  /!\ ARM64 BUILD ONLY

  Enviroment:

  current build number: 33
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-09-07 11:29:04
  version version: 33
  version ubuntu: 20160906
  version device: 20160906.0
  version custom: 20160906

  Steps to reproduce:

  Preconditions_ bluetooth on
  1º Go to System settings>Battery or indicator-bluetooth
  2º Switch bluetooth off and wait around 30 secs
  3º Check bluetooth toggle slides off->on again

  Current result: Can't turn bluetooth off

  Expected result: Bluetooth toggles should turn off bt

  Add:video attached

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

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

[Touch-packages] [Bug 1654313] Re: The greeter is not shown when switching users

** Branch linked: lp:~josharenson/indicator-session/clarify-options

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

Title:
  The greeter is not shown when switching users

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

Bug description:
  This is not consistent, when switching between two user sessions (one
  unity8 snap on classic and one unity7) I sometimes get presented with
  the unity8 lock screen that only provides the current session as an
  option.

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

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

[Touch-packages] [Bug 1662602] Re: GTK+ windows don't render when larger than 478x478

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  GTK+ windows don't render when larger than 478x478

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  PPA containing a more recent GTK+:
  https://launchpad.net/~attente/+archive/ubuntu/gtk-mir

  Under U8, GTK+ windows don't render when the width and height are both
  >= 479.

  If the app starts at a size larger than that, the window will
  initially appear entirely black.

  Once resized < 479 in either dimension, the window will render
  properly.

  After that, when resizing larger than 478x478, the window only
  upscales the most recent framebuffer contents.

  I haven't 100% confirmed that this is not GTK+. However:

  - This bug does not occur when tested with miral-shell
  - GTK+ is receiving configure events for surface resizes
  - GTK+ is re-creating cairo surfaces that match the larger size
  - GTK+ is still calling mir_buffer_stream_swap_buffers_sync at larger sizes
  - I don't think this specific 478/479 number is coming from GTK+, the 
initial/min/max sizes aren't that close to it

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

-- 
Mailing list: https://launchpad.net/~touch-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: Elfdalian layout + merge with Debian 2.19-1

2017-02-07 Thread Gunnar Hjalmarsson

So it seems... Embarrassing! :(

I must have had the 2.18 upstream source on disk when dput'ing, but I
still uploaded the correct upstream tarball. Shouldn't the package
system complain in such a case?

Anyway, it's fixed now (I hope). Sorry.

-- 
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:
  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 1657845] Re: Unity8 snap can't load the testability libraries

2017-02-07 Thread Santiago Baldassin

The testability libraries seemed to be loaded now and yet the
introspection is not working. See the script attached

** Attachment added: "introspection_bug.py"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1657845/+attachment/4814902/+files/introspection_bug.py

-- 
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 1662562] Re: Ubuntu 16.04.2 should have Mesa 13.0.4 out-of-the-box

2017-02-07 Thread Adam Conrad

** Changed in: ubuntu
   Status: Confirmed => Invalid

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

Title:
  Ubuntu 16.04.2 should have Mesa 13.0.4 out-of-the-box

Status in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Mesa 13.0.4 has been released recently, and it is a good idea to include Mesa 
13.0.4 to ubuntu 16.04.2 before its release. Please see this article:
  
http://news.softpedia.com/news/mesa-13-0-4-released-with-radeonsi-and-intel-anv-vulkan-driver-improvements-512493.shtml
  "Users are urged to update to Mesa 13.0.4 as soon as possible"
  It makes no sense to release 16.04.2 with outdated mesa, while there is a new 
stable mesa available

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

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

[Touch-packages] [Bug 1662562] Re: Ubuntu 16.04.2 should have Mesa 13.0.4 out-of-the-box

2017-02-07 Thread Timo Aaltonen

No it should not.

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Ubuntu 16.04.2 should have Mesa 13.0.4 out-of-the-box

Status in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Mesa 13.0.4 has been released recently, and it is a good idea to include Mesa 
13.0.4 to ubuntu 16.04.2 before its release. Please see this article:
  
http://news.softpedia.com/news/mesa-13-0-4-released-with-radeonsi-and-intel-anv-vulkan-driver-improvements-512493.shtml
  "Users are urged to update to Mesa 13.0.4 as soon as possible"
  It makes no sense to release 16.04.2 with outdated mesa, while there is a new 
stable mesa available

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

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

[Touch-packages] [Bug 1650056] Re: /bin/nano:* Error in `nano': munmap_chunk(): invalid pointer: ADDR *

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

** This bug has been marked a duplicate of bug 1641592
   nano 2.5.3-2 on Xenial crashes with long paths on lockfiles

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

Title:
  /bin/nano:*** Error in `nano': munmap_chunk(): invalid pointer: ADDR
  ***

Status in nano package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nano.  This problem was most recently seen with package version 2.5.3-2, the 
problem page at 
https://errors.ubuntu.com/problem/295eb585019cebe203e4b05aec3f4a4fb98932b1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1421718] Re: [Ubuntu Phone Store] No message when no applications found

2017-02-07 Thread Norbert

Same on M10 with OTA-15.

** Tags added: bq m10 touch

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

Title:
  [Ubuntu Phone Store] No message when no applications found

Status in Ubuntu UX:
  Won't Fix
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Hi!

  Steps:
  1. Open Store.
  2. Search RRS (Not RSS).
  3. Bug: Nothing found, but you can't see a message for this.
  4. Search RSS.
  5. OK: You see 5 applications found message.

  Thanks in advance!

  --
  Desired resolution:

  This is part of a bigger redesign project (Scopes toolkit) and it
  can't be fixed as a single bug. The description and specs will be
  updated as soon as they are available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1421718/+subscriptions

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

[Touch-packages] [Bug 1629541] Re: Ubuntu Touch should indicate that battery is charging with LED indicator on device

2017-02-07 Thread Norbert

Same on M10 with OTA-15.

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

Title:
  Ubuntu Touch should indicate that battery is charging with LED
  indicator on device

Status in indicator-power package in Ubuntu:
  New

Bug description:
  I have BQ M10 FHD Ubuntu Edition with OTA-13.
  This device has LED indicator.

  Steps to reproduce:
  1. Boot device.
  2. Connect microusb charger.
  3. Device will start to charge (tray indicator becomes green with zigzag, but 
device's LED is off).

  Expected result:
  Device LED indicates charge level as on Android devices:
  * red for critical level
  * orange for middle
  * yellow for low 
  * green for almost charged).

  Actual result:
  Device LED is off.

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

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

[Touch-packages] [Bug 1662608] [NEW] unity8 should not depend on unity8-tests

2017-02-07 Thread Jeremy Bicha

Public bug reported:

Today's unity8 update installs a bunch of -dev packages. This doesn't
seem intended.

It looks to me like the virtual package unity-application-impl-26
depends on unity8-tests but it shouldn't, right?


$ apt-cache showpkg unity-application-impl-23
Package: unity-application-impl-23
Versions: 

Reverse Depends: 
Dependencies: 
Provides: 
Reverse Provides: 
qtdeclarative5-qtmir-plugin 0.5.1+17.04.20170127-0ubuntu1 (= )
qtdeclarative5-qtmir-plugin 0.5.1+17.04.20170206-0ubuntu1 (= )

$ apt-cache showpkg unity-application-impl-26
Package: unity-application-impl-26
Versions: 

Reverse Depends: 
  unity8-common,unity-application-impl-26
Dependencies: 
Provides: 
Reverse Provides: 
unity8-tests 8.15+17.04.20170206-0ubuntu1 (= )

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

Title:
  unity8 should not depend on unity8-tests

Status in unity8 package in Ubuntu:
  New

Bug description:
  Today's unity8 update installs a bunch of -dev packages. This doesn't
  seem intended.

  It looks to me like the virtual package unity-application-impl-26
  depends on unity8-tests but it shouldn't, right?

  
  $ apt-cache showpkg unity-application-impl-23
  Package: unity-application-impl-23
  Versions: 

  Reverse Depends: 
  Dependencies: 
  Provides: 
  Reverse Provides: 
  qtdeclarative5-qtmir-plugin 0.5.1+17.04.20170127-0ubuntu1 (= )
  qtdeclarative5-qtmir-plugin 0.5.1+17.04.20170206-0ubuntu1 (= )

  $ apt-cache showpkg unity-application-impl-26
  Package: unity-application-impl-26
  Versions: 

  Reverse Depends: 
unity8-common,unity-application-impl-26
  Dependencies: 
  Provides: 
  Reverse Provides: 
  unity8-tests 8.15+17.04.20170206-0ubuntu1 (= )

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

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

[Touch-packages] [Bug 1662602] [NEW] GTK+ windows don't render when larger than 478x478

2017-02-07 Thread William Hua

Public bug reported:

PPA containing a more recent GTK+:
https://launchpad.net/~attente/+archive/ubuntu/gtk-mir

Under U8, GTK+ windows don't render when the width and height are both
>= 479.

If the app starts at a size larger than that, the window will initially
appear entirely black.

Once resized < 479 in either dimension, the window will render properly.

After that, when resizing larger than 478x478, the window only upscales
the most recent framebuffer contents.

I haven't 100% confirmed that this is not GTK+. However:

- This bug does not occur when tested with miral-shell
- GTK+ is receiving configure events for surface resizes
- GTK+ is re-creating cairo surfaces that match the larger size
- GTK+ is still calling mir_buffer_stream_swap_buffers_sync at larger sizes
- I don't think this specific 478/479 number is coming from GTK+, the 
initial/min/max sizes aren't that close to it

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

Title:
  GTK+ windows don't render when larger than 478x478

Status in unity8 package in Ubuntu:
  New

Bug description:
  PPA containing a more recent GTK+:
  https://launchpad.net/~attente/+archive/ubuntu/gtk-mir

  Under U8, GTK+ windows don't render when the width and height are both
  >= 479.

  If the app starts at a size larger than that, the window will
  initially appear entirely black.

  Once resized < 479 in either dimension, the window will render
  properly.

  After that, when resizing larger than 478x478, the window only
  upscales the most recent framebuffer contents.

  I haven't 100% confirmed that this is not GTK+. However:

  - This bug does not occur when tested with miral-shell
  - GTK+ is receiving configure events for surface resizes
  - GTK+ is re-creating cairo surfaces that match the larger size
  - GTK+ is still calling mir_buffer_stream_swap_buffers_sync at larger sizes
  - I don't think this specific 478/479 number is coming from GTK+, the 
initial/min/max sizes aren't that close to it

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

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

[Touch-packages] [Bug 1650737] Re: Written text disappears when trying to place a cursor in a new position

2017-02-07 Thread GTriderXC

I can't reproduce it in a web browser either. But the answer why may be
answered in an attached photo. If we comment, post or write a message in
a browser, a big new message editor opens. It doesn't look any more on
my device as it used to on a video.

HOWEVER, Yes I can reproduce it! I installed a Yahoo mail app. If You click a
Facebook link in a message, Facebook will be opened the way that You can see in
my video.
I have the very same problems when I write messages through this app. But the
video was taken from a web browser.

** Attachment added: "screenshot20170207_173156551.png"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1650737/+attachment/4814853/+files/screenshot20170207_173156551.png

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

Title:
Written text disappears when trying to place a cursor in a new
position

Status in ubuntu-keyboard package in Ubuntu:
New

Bug description:
As You can see in the video, I'm trying to work with previously
written text in a Facebook app on M10 HD with OTA-14:

https://www.youtube.com/watch?v=8M9AyGupkRc=youtu.be

Every time I try to place a cursor in a new position, I have to start
writing the last word all over again unless I do not hide and show the
keyboard again (You can see the "solution" at 2:24)

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

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

[Touch-packages] [Bug 1650737] Re: Written text disappears when trying to place a cursor in a new position

2017-02-07 Thread GTriderXC

Screenshot from a Yahoo mail app

** Attachment added: "screenshot20170207_180628850.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1650737/+attachment/4814860/+files/screenshot20170207_180628850.png

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

Title:
  Written text disappears when trying to place a cursor in a new
  position

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  As You can see in the video, I'm trying to work with previously
  written text in a Facebook app on M10 HD with OTA-14:

  https://www.youtube.com/watch?v=8M9AyGupkRc=youtu.be

  Every time I try to place a cursor in a new position, I have to start
  writing the last word all over again unless I do not hide and show the
  keyboard again (You can see the "solution" at 2:24)

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

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

[Touch-packages] [Bug 1662592] [NEW] [20F5S1A600, Intel Skylake HDMI, Digital Out, HDMI] Playback problem

2017-02-07 Thread Marius

Public bug reported:

Hi,

I encountered an audio bug on my new ThinkPad X260. Since I was not able to 
find a fix online I will try to explain my bug and hopefully get it fixed.
I'm using Ubuntu 16.04.1 LTS on my X260 with i5-6200. I want to use HDMI with 
my Samsung TV to watch videos eg. So I connect the HDMI cable, I get my desktop 
on my TV and in sound settings I can see HDMI Output. When I select HDMI Output 
I hear a cracking noise from my TV speakers. When I play a test tone, it looks 
like the TV needs a 1 or 2 seconds to get the tone so I can only hear the end 
of the tone. When I repeat this test everything works. But when I open a music 
player eg. or Chrome with YouTube I hear the cracking noise again and I get no 
sound on my TV. When I close all applications and start the test tone again, I 
get the same results.
To sum it up. Only test tone works with HDMI, i can select the output but dont 
get any sound.
I attach the alsa-info-alsa-info.sh to this report.
As this is my first report, feel free to ask for further outputs eg. 

Kind regards!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  marius 2072 F pulseaudio
CurrentDesktop: Unity
Date: Tue Feb  7 17:42:14 2017
InstallationDate: Installed on 2017-02-06 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Internes Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [20F5S1A600, Intel Skylake HDMI, Digital Out, HDMI] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R02ET50W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20F5S1A600
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET50W(1.23):bd09/20/2016:svnLENOVO:pn20F5S1A600:pvrThinkPadX260:rvnLENOVO:rn20F5S1A600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20F5S1A600
dmi.product.version: ThinkPad X260
dmi.sys.vendor: LENOVO
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-07T07:13:02.858136

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "alsa-info-alsa-info.sh"
   
https://bugs.launchpad.net/bugs/1662592/+attachment/4814844/+files/alsa-info-alsa-info.sh

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

Title:
  [20F5S1A600, Intel Skylake HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  I encountered an audio bug on my new ThinkPad X260. Since I was not able to 
find a fix online I will try to explain my bug and hopefully get it fixed.
  I'm using Ubuntu 16.04.1 LTS on my X260 with i5-6200. I want to use HDMI with 
my Samsung TV to watch videos eg. So I connect the HDMI cable, I get my desktop 
on my TV and in sound settings I can see HDMI Output. When I select HDMI Output 
I hear a cracking noise from my TV speakers. When I play a test tone, it looks 
like the TV needs a 1 or 2 seconds to get the tone so I can only hear the end 
of the tone. When I repeat this test everything works. But when I open a music 
player eg. or Chrome with YouTube I hear the cracking noise again and I get no 
sound on my TV. When I close all applications and start the test tone again, I 
get the same results.
  To sum it up. Only test tone works with HDMI, i can select the output but 
dont get any sound.
  I attach the alsa-info-alsa-info.sh to this report.
  As this is my first report, feel free to ask for further outputs eg. 

  Kind regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marius 2072 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb  7 17:42:14 2017
  InstallationDate: Installed on 2017-02-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio

[Touch-packages] [Bug 1654313] Re: The greeter is not shown when switching users

2017-02-07 Thread Josh Arenson

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Josh Arenson (josharenson)

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

Title:
  The greeter is not shown when switching users

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

Bug description:
  This is not consistent, when switching between two user sessions (one
  unity8 snap on classic and one unity7) I sometimes get presented with
  the unity8 lock screen that only provides the current session as an
  option.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

2017-02-07 Thread Tuomas Heino

Semi-worksforme @ OTA-15, as in symptoms disappeared for now.
But we shall see whether actual bug(s) were addressed as well after
after 10 weeks assuming no OTA-16 before that.

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

Title:
  webbrowser only partially loads some https sites

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

Re: [Touch-packages] [Bug 1660633] Re: /usr/bin/ucfr: line ... : [: : integer expression expected

2017-02-07 Thread Steve Langasek

On Tue, Feb 07, 2017 at 04:32:19PM -, Manfred Hampl wrote:
> /var/lib/ucf/registry is present on the system with the problem (see
> https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737 )

> As far as we already found out one of the causes of this error is that the 
> command
> egrep --count "[[:space:]]/etc/default/grub$" "/var/lib/ucf/registry"
> returns
> "Illegal variable name."
> when executed in a csh or tcsh shell.

It's not being executed in a csh or tcsh shell.  /usr/bin/ucfr is a
/bin/bash script.  If /bin/bash on your system is pointing to a csh
implementation, you get to keep both pieces.

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

Title:
  /usr/bin/ucfr: line ... : [: : integer expression expected

Status in ucf package in Ubuntu:
  Incomplete

Bug description:
  I've had a reoccurring issue: 
https://ubuntuforums.org/showthread.php?t=2350682
  Running: ucf_3.0036_all.deb

  
http://askubuntu.com/questions/875415/usr-bin-ucfr-errors-integer-expression-expected
  
http://serverfault.com/questions/827873/grub-pc-update-fail-dev-sda-ext2-doesnt-support-embedding

  I don't know why ucfr is erroring out but the accumulated errors are
  now enough to stall priority packages which I feel hamstrung about.
  I've reinstalled the ucf package and danced around the issue enough.

  Any maintainers have a shot in the dark for why this would be
  happening?

  Discussion:
  https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737

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

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

[Touch-packages] [Bug 1420554] Re: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: triggers looping, abandoned

2017-02-07 Thread Mina

affects me while upgrading from 14.04 to 16.04

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

Title:
  package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: triggers
  looping, abandoned

Status in fontconfig package in Ubuntu:
  Won't Fix

Bug description:
  Failed on update

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fontconfig 2.11.1-0ubuntu6
  Uname: Linux 3.18.3-031803-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Tue Feb 10 18:51:02 2015
  DuplicateSignature: package:fontconfig:2.11.1-0ubuntu6:triggers looping, 
abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-24 (17 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150124)
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1575354] Re: Connecting to VPN times out after 25 seconds if login credentials not entered

2017-02-07 Thread Ubuntu Foundations Team Bug Bot

The attachment "increase waiting time for secret input" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Connecting to VPN times out after 25 seconds if login credentials not
  entered

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connecting to OpenConnect VPN through the Gnome GUI fails because
  NetworkManager times out while requesting credentials through the GUI
  form in Ubuntu 16.04.

  It worked (is working on other computers I'm working on) fine from
  Ubuntu 12.04-15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openconnect 1.0.2-1build1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 22:06:41 2016
  SourcePackage: network-manager-openconnect
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1660633] Re: /usr/bin/ucfr: line ... : [: : integer expression expected

2017-02-07 Thread Manfred Hampl

/var/lib/ucf/registry is present on the system with the problem (see
https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737 )

As far as we already found out one of the causes of this error is that the 
command
egrep --count "[[:space:]]/etc/default/grub$" "/var/lib/ucf/registry"
returns
"Illegal variable name."
when executed in a csh or tcsh shell.
According to http://www.grymoire.com/unix/CshTop10.txt any use of the string $" 
in a csh or tcsh fails that way.

According to suggestions in the grymoire document, a potential workaround could 
be changing line 321 of ucfr from
count=$(egrep --count "[[:space:]]${real_conf_file_re}$" "$statedir/registry") 
|| true
into
count=$(egrep --count "[[:space:]]${real_conf_file_re}"'$' 
"$statedir/registry") || true
(instead of 'dollar doublequote' make it 'doublequote quote dollar quote')
(Note, I was not in a position that I could test myself whether this works.)

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

Title:
  /usr/bin/ucfr: line ... : [: : integer expression expected

Status in ucf package in Ubuntu:
  Incomplete

Bug description:
  I've had a reoccurring issue: 
https://ubuntuforums.org/showthread.php?t=2350682
  Running: ucf_3.0036_all.deb

  
http://askubuntu.com/questions/875415/usr-bin-ucfr-errors-integer-expression-expected
  
http://serverfault.com/questions/827873/grub-pc-update-fail-dev-sda-ext2-doesnt-support-embedding

  I don't know why ucfr is erroring out but the accumulated errors are
  now enough to stall priority packages which I feel hamstrung about.
  I've reinstalled the ucf package and danced around the issue enough.

  Any maintainers have a shot in the dark for why this would be
  happening?

  Discussion:
  https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737

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

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

[Touch-packages] [Bug 1048733] Re: add-apt-repository fails due to softwareproperties error

2017-02-07 Thread Junlan Liu

@Michael, that didn't work for me. The error showed up after I installed 
python3.5 from source.
$ wget http://python.org/ftp/python/3.5.2/Python-3.5.2.tar.xz
$ tar xpvf Python-3.5.2.tar.xz
$ cd Python-3.5.2
$ ./configure --prefix=/usr
$ make
$ make install

If I link python3 to python3.4, then it starts working again
$ sudo rm /usr/bin/python3
$ sudo ln -s /usr/bin/python3.4 /usr/bin/python3

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

Title:
  add-apt-repository fails due to softwareproperties error

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  $ sudo add-apt-repository ppa:lubuntu-dev/lubuntu-daily
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 10, in 
  from softwareproperties.SoftwareProperties import SoftwareProperties
  ImportError: No module named softwareproperties.SoftwareProperties

  I tried other PPAs and had the same error so it seems to be universal.

  Interestingly trying to add manually in Settings → Repository just
  results in a notice saying that repos have changed and you need to
  reload. It doesn't actually get to the point where you add repos. That
  may be a related issue so I will file a separate bug and link here and
  vice versa.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: python-software-properties 0.92.1
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic i686
  ApportVersion: 2.1.1-0ubuntu2
  Architecture: i386
  Date: Mon Sep 10 10:15:50 2012
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120215)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=screen
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1048733/+subscriptions

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

[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg

2017-02-07 Thread Samuel Matzek

This upstream patch needs to be backported to the 1.2 series for Xenial.
If left unfixed in Xenial it opens a timing window every hour with
Ubuntu Cloud Archive where users can fall into the "Some packages could
not be authenticated" state without Release.gpg that is described in the
description. This state will not self correct until an hour has passed
an another apt-get update is run. This really impacts automated
deployment technologies such as Juju and Ansible because if they hit
this hourly window with UCA their fallback retries on apt-get update
will not work and the automated deployments fail. The noted upstream
Debian bug is specifically about trying to do an apt-get update without
adding the keys first. The timing window that users can hit will occur
even if you add the keys first.

Now for background information to explain the assertions above. Ubuntu
Cloud Archive updates its files, and more importantly the timestamps on
its files including the Release and Release.gpg file every hour. The
timestamps are updated to be 45 minutes past the hour. The UCA servers
start to reflect these changes around 50 minutes after the hour with a
rolling update of the Packages and then the Release.* files. They are
not updated as an atomic unit as seen from an HTTP client.

So the order of events is:
1. User or automation adds keys by installing the 'ubuntu-cloud-keyring' apt
pacakge.
2. User adds the UCA repo using the Ansible apt_repository or other technique,
possilbly just adding the repo to a sources list file under
/etc/apt/sources/sources.list.d.
3. Either the tooling (apt_repository module) or the user triggers an apt-get
update or other apt cache update trigger. If this cache update hits the timing
window when UCA is being updated you can get into the state where you have the
Release file but not the Release.gpg file without triggering a cache or apt-get
update failure. A recreation Python main which uses straight python-apt can
show this. I will attach my recreation program and output showing the error
case.
4. At this point, as shown in the original description no further apt-get
updates will fix the situation and any package installs from UCA will fail with
"Some packages could not be authenticated".

While the timing window may seem small, probably a minute each hour,
with complex multi-node OpenStack deployments using Ansible we are
seeing this occur fairly frequently. Given the 'juju' in the host name
in the original description I suspect that multi-node orchestrated Juju
charm deployments using UCA are also hitting this often.

The bug is particularly harmful to automated deploy tooling because
while the deploy tooling normally has apt-get update retries or periodic
updates throughout the process, once this error state is entered the
apt-get updates do not work to correct it until after an hour has passed
and UCA has updated itself. The deployment tooling normally times and
fails much sooner than an hour of retries.

Here is the annotated log output of the recreation script:
#
# In this snippet we see apt update not pulling down the Release.gpg that was
deleted right before the update to test
# its ability to pull down a new copy.
#
Before update 2017-02-06 22:50:01.915
After update 2017-02-06 22:50:03.044
ctime changed for file
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release:
1486421402.8
Path does not exist
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg
Before update 2017-02-06 22:50:03.045
After update 2017-02-06 22:50:06.387
ctime changed for file
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release:
1486421404.05
mtime changed for file
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release:
1486421112.0
Path does not exist
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg

#
# In this iteration of the loop we see that the apt update has removed the
Release file as well as not pulling down the Release.gpg.
# UCA's hourly update is in progress.
#
Before update 2017-02-06 22:50:06.387
After update 2017-02-06 22:50:07.536
Path does not exist
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release
Path does not exist
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg

#
# In this iteration of the loop we see that the apt update has updates the
packages file and recreated the Release file.
# However, it did NOT pull down the Release.gpg file. If an automated tool
were to hit this window they enter the bug state
# where no amount of updates will fix this until after the next hourly UCA
update.
#
Before update 2017-02-06 22:50:07.536
After update 2017-02-06 22:50:09.966
ctime changed for file

[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg

2017-02-07 Thread Samuel Matzek

** Attachment added: "Recreation script"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657440/+attachment/4814822/+files/recreate.py

** Changed in: apt (Ubuntu)
   Status: Fix Committed => Confirmed

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

Title:
  apt won't redownload Release.gpg

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  
  I got myself into a situation where a repository has a Release and a 
Release.gpg file, but apt is just ignoring the gpg one and won't download it 
via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  
  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease   
 
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)   
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  
  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
python3-setuptools
  The following packages will be upgraded:
dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  WARNING: The following packages cannot be authenticated!
dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# 

  Somehow apt is thinking it has the Release.gpg file, but it doesn't?

  
  This server is behind a squid proxy.

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

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

[Touch-packages] [Bug 1504551] Re: Text input popover and selection cursors not oriented properly in shell

This bug was fixed in the package ubuntu-ui-toolkit -
1.3.2166+17.04.20170130

---
ubuntu-ui-toolkit (1.3.2166+17.04.20170130) zesty; urgency=medium

  [ Andrea Bernabei ]
  * ListItemLayout documentation: fix typo in color usage of a code example.
Fixes LP: #1561861

  [ Zsombor Egri ]
  * Get tst_listitem_focus_13 back alive. Fixes LP: #1624331.

  [ Arthur Mello ]
  * Add support for interacting with Content Hub Clipboard UI via DBus calls.
Fixes LP: #1563440.

  [ Daniel d'Andrada ]
  * If GRID_UNIT_PX set, always use it. It should override scaling information
from the QPA.

  [ Adnane Belmadiaf ]
  * Expose append method in TextArea. Fixes LP: #1658121.

  [ Tim Peeters ]
  * Toolbar visual refresh to scroll the icons instead of using an overflow
panel. Fixes LP: #1558018.
  * Add missing dependency for the UITK gallery. Fixes lLP: #1640135

  [ Sergio Cazzolato ]
  * This change is done to remove the dependencies with upstart in the tests.
To start apps with env vars is gonna be used the launch_test_application
method provided by autopilot in its test base class which is a wrapper for
the ubuntu-app-launch tools (API). This change removes all the dependencies
with upstart, so all the projects which are using the initctl api and
fixtures will be impacted. An update in the documentation or in the blog is
gonna be done also to communicate this change to the developers.

  [ Christian Dywan ]
  * Add visualRoot property to MainWindow. Fixes LP: #1504551, LP: #1656857.
  * Add python3-debian to control.gles and harden package-sorting.sh.
  * Add organizationName property to MainWindow
  * Add MainWindow to Ubuntu.Components.Labs.
Fixes LP: #1573118, LP: #1587431, LP: #1647415

  [ Albert Astals Cid ]
  * Labs is at 1.0.
  * You can't save the focus after the popup/dialog has been created, at that
stage the dialog has focus already, you need to do it before creating it.

 -- Zoltán Balogh   Mon, 30 Jan 2017
11:30:03 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Text input popover and selection cursors not oriented properly in
  shell

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  See attached screenshot, tapping twice on the password entry shows the
  text overlay, but it's in hardware orientation, not the real one.

  It's been fixed for dialogs, but we must've missed popovers somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.3.1627+15.10.20150908-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:17:56 2015
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1558018] Re: Scrolling of icons in Toolbar

This bug was fixed in the package ubuntu-ui-toolkit -
1.3.2166+17.04.20170130

---
ubuntu-ui-toolkit (1.3.2166+17.04.20170130) zesty; urgency=medium

[ Andrea Bernabei ]
* ListItemLayout documentation: fix typo in color usage of a code example.
Fixes LP: #1561861

[ Zsombor Egri ]
* Get tst_listitem_focus_13 back alive. Fixes LP: #1624331.

[ Arthur Mello ]
* Add support for interacting with Content Hub Clipboard UI via DBus calls.
Fixes LP: #1563440.

[ Daniel d'Andrada ]
* If GRID_UNIT_PX set, always use it. It should override scaling information
from the QPA.

[ Adnane Belmadiaf ]
* Expose append method in TextArea. Fixes LP: #1658121.

[ Tim Peeters ]
* Toolbar visual refresh to scroll the icons instead of using an overflow
panel. Fixes LP: #1558018.
* Add missing dependency for the UITK gallery. Fixes lLP: #1640135

[ Sergio Cazzolato ]
* This change is done to remove the dependencies with upstart in the tests.
To start apps with env vars is gonna be used the launch_test_application
method provided by autopilot in its test base class which is a wrapper for
the ubuntu-app-launch tools (API). This change removes all the dependencies
with upstart, so all the projects which are using the initctl api and
fixtures will be impacted. An update in the documentation or in the blog is
gonna be done also to communicate this change to the developers.

[ Christian Dywan ]
* Add visualRoot property to MainWindow. Fixes LP: #1504551, LP: #1656857.
* Add python3-debian to control.gles and harden package-sorting.sh.
* Add organizationName property to MainWindow
* Add MainWindow to Ubuntu.Components.Labs.
Fixes LP: #1573118, LP: #1587431, LP: #1647415

[ Albert Astals Cid ]
* Labs is at 1.0.
* You can't save the focus after the popup/dialog has been created, at that
stage the dialog has focus already, you need to do it before creating it.

-- Zoltán Balogh Mon, 30 Jan 2017
11:30:03 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Fix Committed => Fix Released

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

Title:
Scrolling of icons in Toolbar

Status in Ubuntu UX:
In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released

Bug description:
Currently, when the icons do not all fit in the toolbar, an overflow
button is shown that shows an overflow popover/panel when clicked.
This needs to be replaced by icon scrolling instead.

See https://docs.google.com/document/d/1F-zD6CF8YFfA-
nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit

UX solution:

https://docs.google.com/document/edit?hgd=1=1F-zD6CF8YFfA-nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.w16v0yn510iy
is this not what you need?

https://docs.google.com/document/edit?hgd=1=1F-zD6CF8YFfA-
nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.duaef4xy7sqv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1558018/+subscriptions

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

[Touch-packages] [Bug 1563440] Re: Add ContentHub text import option to text field context menu

This bug was fixed in the package ubuntu-ui-toolkit -
1.3.2166+17.04.20170130

---
ubuntu-ui-toolkit (1.3.2166+17.04.20170130) zesty; urgency=medium

  [ Andrea Bernabei ]
  * ListItemLayout documentation: fix typo in color usage of a code example.
Fixes LP: #1561861

  [ Zsombor Egri ]
  * Get tst_listitem_focus_13 back alive. Fixes LP: #1624331.

  [ Arthur Mello ]
  * Add support for interacting with Content Hub Clipboard UI via DBus calls.
Fixes LP: #1563440.

  [ Daniel d'Andrada ]
  * If GRID_UNIT_PX set, always use it. It should override scaling information
from the QPA.

  [ Adnane Belmadiaf ]
  * Expose append method in TextArea. Fixes LP: #1658121.

  [ Tim Peeters ]
  * Toolbar visual refresh to scroll the icons instead of using an overflow
panel. Fixes LP: #1558018.
  * Add missing dependency for the UITK gallery. Fixes lLP: #1640135

  [ Sergio Cazzolato ]
  * This change is done to remove the dependencies with upstart in the tests.
To start apps with env vars is gonna be used the launch_test_application
method provided by autopilot in its test base class which is a wrapper for
the ubuntu-app-launch tools (API). This change removes all the dependencies
with upstart, so all the projects which are using the initctl api and
fixtures will be impacted. An update in the documentation or in the blog is
gonna be done also to communicate this change to the developers.

  [ Christian Dywan ]
  * Add visualRoot property to MainWindow. Fixes LP: #1504551, LP: #1656857.
  * Add python3-debian to control.gles and harden package-sorting.sh.
  * Add organizationName property to MainWindow
  * Add MainWindow to Ubuntu.Components.Labs.
Fixes LP: #1573118, LP: #1587431, LP: #1647415

  [ Albert Astals Cid ]
  * Labs is at 1.0.
  * You can't save the focus after the popup/dialog has been created, at that
stage the dialog has focus already, you need to do it before creating it.

 -- Zoltán Balogh   Mon, 30 Jan 2017
11:30:03 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Add ContentHub text import option to text field context menu

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  It would be nice to have an "Import" option to a text field's context
  menu, next to cut/copy/paste, that will open a ContentPeerPicker for
  apps that can share Text.

  Currently you can open another app, and copy text from it if it
  supports copying, then paste it into the text field. But we have a
  nice ContentHub service that supports sharing chunks of text, and it
  would streamline the user experience if we could enable this by
  default for text inputs.

  Bonus points if we could send some context along with the import
  request, such as what app or website it's going to, but I don't think
  the ContentHub API supports that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1563440/+subscriptions

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

[Touch-packages] [Bug 1561861] Re: ListItemLayout documentation: UbuntuColors.Orange should be UbuntuColors.orange instead

This bug was fixed in the package ubuntu-ui-toolkit -
1.3.2166+17.04.20170130

---
ubuntu-ui-toolkit (1.3.2166+17.04.20170130) zesty; urgency=medium

  [ Andrea Bernabei ]
  * ListItemLayout documentation: fix typo in color usage of a code example.
Fixes LP: #1561861

  [ Zsombor Egri ]
  * Get tst_listitem_focus_13 back alive. Fixes LP: #1624331.

  [ Arthur Mello ]
  * Add support for interacting with Content Hub Clipboard UI via DBus calls.
Fixes LP: #1563440.

  [ Daniel d'Andrada ]
  * If GRID_UNIT_PX set, always use it. It should override scaling information
from the QPA.

  [ Adnane Belmadiaf ]
  * Expose append method in TextArea. Fixes LP: #1658121.

  [ Tim Peeters ]
  * Toolbar visual refresh to scroll the icons instead of using an overflow
panel. Fixes LP: #1558018.
  * Add missing dependency for the UITK gallery. Fixes lLP: #1640135

  [ Sergio Cazzolato ]
  * This change is done to remove the dependencies with upstart in the tests.
To start apps with env vars is gonna be used the launch_test_application
method provided by autopilot in its test base class which is a wrapper for
the ubuntu-app-launch tools (API). This change removes all the dependencies
with upstart, so all the projects which are using the initctl api and
fixtures will be impacted. An update in the documentation or in the blog is
gonna be done also to communicate this change to the developers.

  [ Christian Dywan ]
  * Add visualRoot property to MainWindow. Fixes LP: #1504551, LP: #1656857.
  * Add python3-debian to control.gles and harden package-sorting.sh.
  * Add organizationName property to MainWindow
  * Add MainWindow to Ubuntu.Components.Labs.
Fixes LP: #1573118, LP: #1587431, LP: #1647415

  [ Albert Astals Cid ]
  * Labs is at 1.0.
  * You can't save the focus after the popup/dialog has been created, at that
stage the dialog has focus already, you need to do it before creating it.

 -- Zoltán Balogh   Mon, 30 Jan 2017
11:30:03 +

** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1561861

Title:
  ListItemLayout documentation: UbuntuColors.Orange should be
  UbuntuColors.orange instead

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/

  The code:

  ListItemLayout {
  id: layout
  title.text: "Hello..."
  title.color: UbuntuColors.Orange
  subtitle.text: "...world!"
  Rectangle {
  SlotsLayout.position: SlotsLayout.Leading
  color: "pink"
  height: units.gu(6)
  width: height
  }

  
  UbuntuColors.Orange should be Ubuntu.orange

  Best regards,
  XiaoGuo

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

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

[Touch-packages] [Bug 1573118] Re: "units" context property is app-global

This bug was fixed in the package ubuntu-ui-toolkit -
1.3.2166+17.04.20170130

---
ubuntu-ui-toolkit (1.3.2166+17.04.20170130) zesty; urgency=medium

  [ Andrea Bernabei ]
  * ListItemLayout documentation: fix typo in color usage of a code example.
Fixes LP: #1561861

  [ Zsombor Egri ]
  * Get tst_listitem_focus_13 back alive. Fixes LP: #1624331.

  [ Arthur Mello ]
  * Add support for interacting with Content Hub Clipboard UI via DBus calls.
Fixes LP: #1563440.

  [ Daniel d'Andrada ]
  * If GRID_UNIT_PX set, always use it. It should override scaling information
from the QPA.

  [ Adnane Belmadiaf ]
  * Expose append method in TextArea. Fixes LP: #1658121.

  [ Tim Peeters ]
  * Toolbar visual refresh to scroll the icons instead of using an overflow
panel. Fixes LP: #1558018.
  * Add missing dependency for the UITK gallery. Fixes lLP: #1640135

  [ Sergio Cazzolato ]
  * This change is done to remove the dependencies with upstart in the tests.
To start apps with env vars is gonna be used the launch_test_application
method provided by autopilot in its test base class which is a wrapper for
the ubuntu-app-launch tools (API). This change removes all the dependencies
with upstart, so all the projects which are using the initctl api and
fixtures will be impacted. An update in the documentation or in the blog is
gonna be done also to communicate this change to the developers.

  [ Christian Dywan ]
  * Add visualRoot property to MainWindow. Fixes LP: #1504551, LP: #1656857.
  * Add python3-debian to control.gles and harden package-sorting.sh.
  * Add organizationName property to MainWindow
  * Add MainWindow to Ubuntu.Components.Labs.
Fixes LP: #1573118, LP: #1587431, LP: #1647415

  [ Albert Astals Cid ]
  * Labs is at 1.0.
  * You can't save the focus after the popup/dialog has been created, at that
stage the dialog has focus already, you need to do it before creating it.

 -- Zoltán Balogh   Mon, 30 Jan 2017
11:30:03 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  "units" context property is app-global

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The "units" context property has no idea about which screen it is on,
  making it impossible to have different grid unit values per window in
  a single app. This would be the case, for example, when one app has
  multiple windows on different screens.

  We're landing a workaround for this for use in unity8 (the only case
  supported today where a single app has multiple windows on different
  screens).

  Long-term we might need UITK 2.0 to fix this proper.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 1.3.1918+16.04.20160404-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 21 17:54:33 2016
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1587431] Re: Introduce MainWindow component