date:20161003

I don't think that's acceptable for security. Assigned to design so see
what they say.

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

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

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

Title:
  Can't log onto Unity8 because can't figure out keyboard layout, as
  there is no textbox to test it in.

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

Bug description:
  I use colemak, and a funky character in my password that requires
  altgr shift level 3.

  On 16.10, logging out of Unity7 brings me to the Unity8 login prompt.
  There is a label with my account name, and a text box for my password.

  I have no idea what I am typing, and what regularly works for me on
  lightdm, is not working for me on Unity8's login prompt. I simply can
  not login.

  I need a way to figure out what I am typing. There is no means to
  figure out what is being typed.

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

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

[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial

2016-10-03 Thread Vicamo Yang

** Description changed:

  Snappy heavily rely on systemd system session and xenial has systemd by
  default.
  
  [steps to construct systemd-based avila]
  
  1. flash images built from xenial branch [1]. This should gives a
  working xenial+upstart avila.
  
  2. Install systemd-sysv rather than upstart-sysv (Bug 1625023)
  2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] 
applied.
  2.2. download latest systemd-sysv package [4].
  2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb
  
  3. Install android-tools-adbd for systemd (Bug 1627613)
  3.1. Install prebuilt package [5] or recompile it from source [6] with patch 
[7] applied.
  3.2. Install the package from Terminal app because it will break adb 
connection and interrupt the installation process leaving a very bad state of 
the package.
  
  4. Modify lxc-android-config package systemd service file by hand as the
  merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug
  1626012, bug 1627613).
  
  5. Recompile upstart with merge proposal [12] include and install at
  least the built binary /sbin/upstart-local-bridge.
  
  6. Reboot.
  
  [1]: 
https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial
  [2]: 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/
  [3]: 
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch
  [4]: 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/
  [5]: 
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb
  [6]: 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/
  [7]: 
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch
  [8]: 
https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435
  [9]: 
https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144
  [10]: 
https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184
  [11]: 
https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587
  [12]: 
https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140
  
  [All Pending MPs]
  
  1. ubuntu-touch-meta:
  * 
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch
  2. lxc-android-config:
  * 
https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435
  * 
https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144
  * 
https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184
  * 
https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587
  3. upstart:
  * 
https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140
+ 
+ [Prebuilt rootfs tarball]
+ 
+ 
https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2
+ build_number: 49
+ version_detail: ubuntu=20161001,device=20160919.0,custom=20161001,version=49

** Description changed:

  Snappy heavily rely on systemd system session and xenial has systemd by
  default.
  
  [steps to construct systemd-based avila]
  
  1. flash images built from xenial branch [1]. This should gives a
  working xenial+upstart avila.
  
  2. Install systemd-sysv rather than upstart-sysv (Bug 1625023)
  2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] 
applied.
  2.2. download latest systemd-sysv package [4].
  2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb
  
  3. Install android-tools-adbd for systemd (Bug 1627613)
  3.1. Install prebuilt package [5] or recompile it from source [6] with patch 
[7] applied.
  3.2. Install the package from Terminal app because it will break adb 
connection and interrupt the installation process leaving a very bad state of 
the package.
  
  4. Modify lxc-android-config package systemd service file by hand as the
  merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug
  1626012, bug 1627613).
  
  5. Recompile upstart with merge proposal [12] include and install at
  least the built binary /sbin/upstart-local-bridge.
  
  6. Reboot.
  
  [1]: 
https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial
  [2]: 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/
  [3]:

[Touch-packages] [Bug 1630087] Re: Can't log onto Unity8 because can't figure out keyboard layout, as there is no textbox to test it in.

2016-10-03 Thread dinamic

maybe a "show password" check box would help

** Also affects: ubuntu-ux
   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/1630087

Title:
  Can't log onto Unity8 because can't figure out keyboard layout, as
  there is no textbox to test it in.

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

Bug description:
  I use colemak, and a funky character in my password that requires
  altgr shift level 3.

  On 16.10, logging out of Unity7 brings me to the Unity8 login prompt.
  There is a label with my account name, and a text box for my password.

  I have no idea what I am typing, and what regularly works for me on
  lightdm, is not working for me on Unity8's login prompt. I simply can
  not login.

  I need a way to figure out what I am typing. There is no means to
  figure out what is being typed.

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

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

[Touch-packages] [Bug 1552100] Re: Move to .snap

2016-10-03 Thread Emanuele Antonio Faraone

** Description changed:

- Move all packages to .snap (snappy)
+ Move all packages and the system to .snap (snappy)

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

Title:
  Move to .snap

Status in Canonical System Image:
  Opinion
Status in Ubuntu Music App:
  Triaged
Status in Ubuntu Notes app:
  Triaged
Status in Telegram app:
  Triaged
Status in Ubuntu Calendar App:
  In Progress
Status in Ubuntu Clock App:
  Triaged
Status in Ubuntu Document Viewer App:
  Triaged
Status in Ubuntu File Manager App:
  Triaged
Status in Ubuntu Terminal App:
  Triaged
Status in Ubuntu Weather App:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Move all packages and the system to .snap (snappy)

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

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

[Touch-packages] [Bug 1553328] Re: Mir crashes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors

** Summary changed:

- Mir crashes on nouveau (nv50) in pushbuf_kref()
+ Mir crashes on nouveau (nv50) in pushbuf_kref() especially with multiple 
monitors

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

Title:
  Mir crashes on nouveau (nv50) in pushbuf_kref() especially with
  multiple monitors

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in libdrm package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1497593] Re: webbrowser-app crashed with SIGABRT in __assert_fail_base()

This might be related to bug 1553328. It seems plausible that
webbrowser-app might be trying to do multi-threaded rendering, which we
know will crash on nouveau.

** Information type changed from Private to Public

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

Title:
  webbrowser-app crashed with SIGABRT in __assert_fail_base()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  webbrowser-app crashed with SIGABRT in __assert_fail_base()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: webbrowser-app 0.23+15.10.20150913-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 19 20:05:51 2015
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2015-09-18 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   __assert_fail_base (fmt=0x7f1aba6fd028 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7f1aa469f879 "kref", 
file=file@entry=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=line@entry=726, 
function=function@entry=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:92
   __GI___assert_fail (assertion=0x7f1aa469f879 "kref", file=0x7f1aa469f85a 
"../../nouveau/pushbuf.c", line=726, function=0x7f1aa469f8a0 
"nouveau_pushbuf_data") at assert.c:101
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
  Title: webbrowser-app crashed with SIGABRT in __assert_fail_base()
  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/webbrowser-app/+bug/1497593/+subscriptions

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

[Touch-packages] [Bug 1304498] Re: webapp-container crashed with SIGSEGV in cli_kref_set()

** Information type changed from Private to Public

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

Title:
  webapp-container crashed with SIGSEGV in cli_kref_set()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  opening twitter and gmail webapps from unity messaging menu after
  latest updates and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: webapp-container 0.23+14.04.20140407.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Apr  8 11:37:20 2014
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2013-06-24 (287 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: webapp-container --app-id=Gmailmailgooglecom --webapp=R21haWw= 
--enable-back-forward
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f7d258f9ea4:movq   $0x0,(%rcx)
   PC (0x7f7d258f9ea4) ok
   source "$0x0" ok
   destination "(%rcx)" (0x0900) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_kick () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: webapp-container crashed with SIGSEGV in nouveau_pushbuf_kick()
  UpgradeStatus: Upgraded to trusty on 2014-03-06 (33 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions

2016-10-03 Thread Theodore Ts'o

One bit of context --- metadata_csum is not enabled by default in the
official upstream e2fsprogs.tar.gz file. So with my upstream maintainer
hat, I deliberately decided not to enable it by default, and mentioned
in the release notes that individual distributions should decide whether
they wanted to enable it. So with the upstream e2fsprogs tarball, the
user can still request metadata_csum by asking for it explicitly: mke2fs
-t ext4 -O metadata_csum.

With my *Debian* maintainer hat on (well, with some egging on with my
upstream maintainer persona :-), I decided to enable metadata_csum by
default so that in the testing and unstable branches, metadadata_csum
checking would get some additional exposure, and hence testing. This
gambit has worked. There have been a number of bug between 1.43 and
1.43.3 that were fixed because they were reported by Debian users.
Whether I will continue leaving metadata_csum enabled right before
Debian Stretch goes into final lockdown for the Debian Stable release is
not something I have decided, but so far the bug report rate has been
positive.

Ubuntu has apparently adopted the Debian enablement of metadata_csum by
default, because it's based on the Debian 1.43.3-1 package. However,
there may be some differences between Ubuntu and Debian --- the average
technical sophistication of a Debian vs. a Ubuntu user, compatibility
constraints with Ubuntu LTS, etc. --- that may drive a different
decision with respect to mke2fs's *defaults*.

It would be good if a decision is made explicitly by Ubuntu / Canonical
to decide what best makes since for Ubuntu. If you decide that Ubuntu
16.10 is a community distro, and you want to help me test metadata_csum,
that's great.I have had some experiences with less-than-savvy Ubuntu
users who really struggled with filing a useful bug report and
participating in root causing a bug.

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

Title:
Ubuntu 16.10 installer sets metadata_csum option on ext4 partition
which is incompatible with other LTS Ubuntu versions

Status in e2fsprogs package in Ubuntu:
Invalid

Bug description:
Ubuntu 16.10 installer sets metadata_csum option on ext4 partition
which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04
LTS, 16.04 LTS).

Steps to reproduce:
1. Download Ubuntu 16.10 installation media.
2. Install Ubuntu.
3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro.

Expected results:
User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10.

Actual results:
User can not check and fix errors on ext4 filesystem because of lack of
'metadata_csum' option in previous LTS Ubuntu versions.
The only one working solution was to scan from 16.10 live install media.

Note:
it is known, that Dan Watkins disabled metadata_csum when creating ext4
filesystems ( see
http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305
). It is good solution.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: e2fsprogs 1.43.1-1
ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
Uname: Linux 4.4.0-30-generic i686
ApportVersion: 2.20.2-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Mon Jul 11 23:42:49 2016
SourcePackage: e2fsprogs
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1623508] Re: unity8 crashed with SIGSEGV

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

Thanks for your bug report.

Unfortunately we already know that the nouveau driver is unstable
particularly with multi-threaded (multi-headed) rendering. The best
suggestion right now is to either only use a single monitor or to use
intel or radeon graphics.

Duplicate of bug 1553328.

** This bug has been marked a duplicate of bug 1553328
   Mir crashes on nouveau (nv50) in pushbuf_kref()

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

Title:
  unity8 crashed with SIGSEGV

Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  16.10 first unity 8 run16.10 first unity 8 run

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Sep 14 10:32:07 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-09-14 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913)
  ProcCmdline: unity8 --mode=full-shell
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 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/mir/+bug/1623508/+subscriptions

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

[Touch-packages] [Bug 1629553] Re: unity8 crashed with SIGSEGV in memcpy() from mir::frontend::SessionMediator::request_persistent_surface_id

** Summary changed:

- unity8 crashed with SIGSEGV in memcpy()
+ unity8 crashed with SIGSEGV in memcpy() from 
mir::frontend::SessionMediator::request_persistent_surface_id

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

** Changed in: mir
   Importance: Undecided => High

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

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

** Tags added: unity8-desktop

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

Title:
  unity8 crashed with SIGSEGV in memcpy() from
  mir::frontend::SessionMediator::request_persistent_surface_id

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

Bug description:
  unity8 crashed with SIGSEGV in memcpy()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Oct  1 16:15:40 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-06-05 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: unity8 --mode=full-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff9d530a877 :movups (%rsi),%xmm0
   PC (0x7ff9d530a877) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   memcpy () at 
../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S:141
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
  Title: unity8 crashed with SIGSEGV in memcpy()
  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/canonical-devices-system-image/+bug/1629553/+subscriptions

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

[Touch-packages] [Bug 1622126] Re: unity8 crashed with SIGSEGV in dri2_destroy_surface()

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

Yes Mesa 12.0.2 in yakkety was quite broken. And that's already fixed by
12.0.3.

** This bug has been marked a duplicate of bug 1620994
   [regression] Starting in Mesa 12.0.2, Mir EGL clients crash with SIGSEGV in 
dri2_destroy_context() (from eglDestroyContext or eglTerminate)

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

Title:
  unity8 crashed with SIGSEGV in dri2_destroy_surface()

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

Bug description:
  *

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Sep 10 10:38:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160909)
  ProcCmdline: unity8 --mode=full-shell
  SegvAnalysis:
   Segfault happened at: 0x7fe0b7c19624:mov(%rax),%rax
   PC (0x7fe0b7c19624) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglDestroySurface () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
  Title: unity8 crashed with SIGSEGV in eglDestroySurface()
  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/canonical-devices-system-image/+bug/1622126/+subscriptions

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

[Touch-packages] [Bug 1630087] Re: Can't log onto Unity8 because can't figure out keyboard layout, as there is no textbox to test it in.

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

** Tags added: a11y input unity8-desktop

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

Title:
  Can't log onto Unity8 because can't figure out keyboard layout, as
  there is no textbox to test it in.

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

Bug description:
  I use colemak, and a funky character in my password that requires
  altgr shift level 3.

  On 16.10, logging out of Unity7 brings me to the Unity8 login prompt.
  There is a label with my account name, and a text box for my password.

  I have no idea what I am typing, and what regularly works for me on
  lightdm, is not working for me on Unity8's login prompt. I simply can
  not login.

  I need a way to figure out what I am typing. There is no means to
  figure out what is being typed.

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

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

[Touch-packages] [Bug 1369111] Re: baloo_file_extractor crashed with SIGSEGV in memcpy()

2016-10-03 Thread Bug Watch Updater

** Changed in: taglib (Debian)
   Status: New => Fix Released

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

Title:
  baloo_file_extractor crashed with SIGSEGV in memcpy()

Status in taglib package in Ubuntu:
  Fix Released
Status in taglib package in Debian:
  Fix Released

Bug description:
  This happens during regular desktop use, after removing drives from
  Kubuntu's exlusion list, so that there were more drives to scan.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: baloo 4:4.13.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Sat Sep 13 17:36:59 2014
  ExecutablePath: /usr/bin/baloo_file_extractor
  ProcCmdline: /usr/bin/baloo_file_extractor 4752 4751 4750 4749 4748 4747 4746 
4745 4743 4741
  SegvAnalysis:
   Segfault happened at: 0x7f52bfda1a7e <__memcpy_sse2_unaligned+46>:   movdqu 
-0x10(%rsi,%rdx,1),%xmm8
   PC (0x7f52bfda1a7e) ok
   source "-0x10(%rsi,%rdx,1)" (0x101226e6b) not located in a known VMA region 
(needed readable region)!
   destination "%xmm8" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: baloo
  StacktraceTop:
   TagLib::ByteVector::replace(TagLib::ByteVector const&, TagLib::ByteVector 
const&) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::SynchData::decode(TagLib::ByteVector const&) () from 
/usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::FrameFactory::createFrame(TagLib::ByteVector const&, 
TagLib::ID3v2::Header*) const () from /usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::Tag::parse(TagLib::ByteVector const&) () from 
/usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::Tag::read() () from /usr/lib/x86_64-linux-gnu/libtag.so.1
  Title: baloo_file_extractor crashed with SIGSEGV in 
TagLib::ByteVector::replace()
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (14 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd 
lpadmin netdev plugdev pulse sambashare saned tape vboxusers video

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

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

[Touch-packages] [Bug 1630085] Re: Ubuntu 16.10 beta breaks Asus Laptop touchpad behavior

2016-10-03 Thread Rainer Rohde

** Description changed:

  In 16.04 LTS, the touchpad behaved perfectly, and as soon as I stepped
  up to 16.10 beta the touchpad became unusable.
  
  When holding a single finger on the touchpad, without moving my finger,
  the cursor jumps around like crazy, and even performs clicks. When
  placing a second finger on the touchpad, without moving either, it gets
  even worse.
  
- See desktop recording clip as reference.
+ See desktop recording clip as reference of the behavior (attached).
+ 
+ The laptop is an Asus ZenBook UX31E.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  BootLog: /dev/sda1: clean, 415810/7815168 files, 10983001/31258368 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Mon Oct  3 21:04:16 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1427]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1427]
  InstallationDate: Installed on 2016-03-17 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=77be5fdd-c844-4d59-af29-cc718cf6b41a ro intel_state=disable 
pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" 
"acpi_os_name=Windows 2009" quiet splash intel_state=disable pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" 
"acpi_os_name=Windows 2009"
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Mon Oct  3 16:12:15 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

** Description changed:

  In 16.04 LTS, the touchpad behaved perfectly, and as soon as I stepped
  up to 16.10 beta the touchpad became unusable.
  
  When holding a single finger on the touchpad, without moving my finger,
  the cursor jumps around like crazy, and even performs clicks. When
  placing a second finger on the touchpad, without moving either, it gets
  even worse.
  
- See desktop recording clip as reference of the behavior (attached).
+ See desktop recording clip as reference of the behavior (attached as
+ out.ogv).
  
  The laptop is an Asus ZenBook UX31E.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  BootLog: /dev/sda1: clean, 415810/7815168 files,

[Touch-packages] [Bug 1630087] [NEW] Can't log onto Unity8 because can't figure out keyboard layout, as there is no textbox to test it in.

2016-10-03 Thread Akiva

Public bug reported:

I use colemak, and a funky character in my password that requires altgr
shift level 3.

On 16.10, logging out of Unity7 brings me to the Unity8 login prompt.
There is a label with my account name, and a text box for my password.

I have no idea what I am typing, and what regularly works for me on
lightdm, is not working for me on Unity8's login prompt. I simply can
not login.

I need a way to figure out what I am typing. There is no means to figure
out what is being typed.

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


** Tags: keyboard layout

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

Title:
  Can't log onto Unity8 because can't figure out keyboard layout, as
  there is no textbox to test it in.

Status in unity8 package in Ubuntu:
  New

Bug description:
  I use colemak, and a funky character in my password that requires
  altgr shift level 3.

  On 16.10, logging out of Unity7 brings me to the Unity8 login prompt.
  There is a label with my account name, and a text box for my password.

  I have no idea what I am typing, and what regularly works for me on
  lightdm, is not working for me on Unity8's login prompt. I simply can
  not login.

  I need a way to figure out what I am typing. There is no means to
  figure out what is being typed.

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

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

[Touch-packages] [Bug 1630085] [NEW] Ubuntu 16.10 beta breaks Asus Laptop touchpad behavior

2016-10-03 Thread Rainer Rohde

Public bug reported:

In 16.04 LTS, the touchpad behaved perfectly, and as soon as I stepped
up to 16.10 beta the touchpad became unusable.

When holding a single finger on the touchpad, without moving my finger,
the cursor jumps around like crazy, and even performs clicks. When
placing a second finger on the touchpad, without moving either, it gets
even worse.

See desktop recording clip as reference.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
BootLog: /dev/sda1: clean, 415810/7815168 files, 10983001/31258368 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Mon Oct  3 21:04:16 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1427]
InstallationDate: Installed on 2016-03-17 (200 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160316)
MachineType: ASUSTeK Computer Inc. UX31E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=77be5fdd-c844-4d59-af29-cc718cf6b41a ro intel_state=disable 
pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" 
"acpi_os_name=Windows 2009" quiet splash intel_state=disable pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" 
"acpi_os_name=Windows 2009"
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Mon Oct  3 16:12:15 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety

** Attachment added: "out.ogv"
   https://bugs.launchpad.net/bugs/1630085/+attachment/4753808/+files/out.ogv

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

Title:
  Ubuntu 16.10 beta breaks Asus Laptop touchpad behavior

Status in xorg package in Ubuntu:
  New

Bug description:
  In 16.04 LTS, the touchpad behaved perfectly, and as soon as I stepped
  up to 16.10 beta the touchpad became unusable.

  When holding a single finger on the touchpad, without moving my
  finger, the cursor jumps around like crazy, and even performs clicks.
  When placing a second finger on the touchpad, without moving either,
  it gets even worse.

  See desktop recording clip as reference.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  BootLog: /dev/sda1: clean, 415810/7815168 files, 10983001/31258368 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz

[Touch-packages] [Bug 1629869] Re: Clients and server all crash

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

** Information type changed from Private to Public

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

Title:
  Clients and server all crash

Status in mir package in Ubuntu:
  New

Bug description:
  Trying to attach to lp:1629275

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: mir-demos 0.24.0+16.10.20160815.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Oct  3 12:48:34 2016
  ExecutablePath: /usr/bin/mir_demo_server_minimal
  InstallationDate: Installed on 2016-09-16 (16 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160906)
  ProcCmdline: mir_demo_server_minimal
  Signal: 11
  SourcePackage: mir
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_finalize (d=0x7ff7becb6360) at cxa_finalize.c:56
   __do_global_dtors_aux () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? ()
  Title: mir_demo_server_minimal crashed with SIGSEGV in __cxa_finalize()
  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/mir/+bug/1629869/+subscriptions

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

[Touch-packages] [Bug 1629275] Re: Clients and server all crash

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

Found it.

You logged this a couple of months ago :)

** This bug has been marked a duplicate of bug 1607812
   When stressed by a load of clients starting at once: Failed to get PRIME fd 
from gbm bo

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

** Tags added: unity8-desktop

** Changed in: canonical-devices-system-image
   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/1629863

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1629869] Re: Clients and server all crash

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

** This bug is no longer a duplicate of bug 1629275
   Clients and server all crash
** This bug has been marked a duplicate of bug 1607812
   When stressed by a load of clients starting at once: Failed to get PRIME fd 
from gbm bo

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

Title:
  Clients and server all crash

Status in mir package in Ubuntu:
  New

Bug description:
  Trying to attach to lp:1629275

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: mir-demos 0.24.0+16.10.20160815.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Oct  3 12:48:34 2016
  ExecutablePath: /usr/bin/mir_demo_server_minimal
  InstallationDate: Installed on 2016-09-16 (16 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160906)
  ProcCmdline: mir_demo_server_minimal
  Signal: 11
  SourcePackage: mir
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_finalize (d=0x7ff7becb6360) at cxa_finalize.c:56
   __do_global_dtors_aux () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? ()
  Title: mir_demo_server_minimal crashed with SIGSEGV in __cxa_finalize()
  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/mir/+bug/1629869/+subscriptions

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

[Touch-packages] [Bug 1579265] Re: Qt dev package does not include webenginewidgets

2016-10-03 Thread Simon Quigley

If I'm understanding this bug report correctly, you need QtWebEngine to
be in Debian. I'll assign this to myself as I have been working with the
Debian Qt people to get QtWebEngine and QtWebChannel (a dependency of
QtWebEngine) packaged.

At the moment, QtWebChannel is in Debian, and we're waiting on some
tweaks to QtWebEngine's debian/copyright file for it to be uploaded.

I can reasonably predict that QtWebEngine will be in Ubuntu 17.04 before
Feature Freeze. I'll keep this bug report updated.

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  Qt dev package does not include webenginewidgets

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

Bug description:
  Attached is a sample project that uses several QT components. To build
  this, one needs to install the following packages:

  apt-get install libqt5core5a qtconnectivity5-dev qtmultimedia5-dev
  qt5-default libqt5webkit5-dev qt3d5-dev g++

  Then, run qmake. The expected result should be output of a Makefile,
  Makefile.debug and Makefile.release. However, I get the following
  error:

  unknown modules: webenginewidgets

  I do not see any package that provides the web engine widgets
  component and must conclude that the QT package is missing this.

  Therefore am opening this bug and requesting that QT be packaged to
  include webengine. Or a separate package be provided with this.

  This is for 16.04 release which packages Qt 5.5.1. Thanks.

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

-- 
Mailing list: https://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 1629496] Re: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2016-10-03 Thread hcarrano

apt-get is rigth, but  the
linux-image-extra-4.4.0-38-generic 4.4.0-38.57no boot. I use the anterior
version.

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

Title:
  package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  apt-get no work.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hudson 2921 F pulseaudio
  Date: Fri Sep 30 21:25:27 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=4e7a0dd9-aae5-4465-962f-73010a35ab89
  InstallationDate: Installed on 2016-08-10 (51 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA TOSHIBA NB255
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=5807cac2-6f74-4bbb-a607-fba249b82e31 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.30
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.30:bd05/26/2010:svnTOSHIBA:pnTOSHIBANB255:pvrPLL2PU-00901L:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: TOSHIBA NB255
  dmi.product.version: PLL2PU-00901L
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1629496/+subscriptions

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

[Touch-packages] [Bug 1564695] Re: The command "who -m" doesn't work

2016-10-03 Thread Brian Murray

I was unable to recreate this on an Ubuntu system running either 16.04
and 16.10.

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

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

Title:
  The command "who -m" doesn't work

Status in Ubuntu Kylin:
  New
Status in coreutils package in Ubuntu:
  Incomplete

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用，执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

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

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

[Touch-packages] [Bug 1628687] Re: Assertion failure when PID 1 receives a zero-length message over notify socket

2016-10-03 Thread Steve Beattie

Martin, if you can point me at the xenial branch, we can push this
through the security pocket. I wanted to wait and see if there were any
further issues addressed (and to not release an update on a Friday).
Thanks!

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

Title:
  Assertion failure when PID 1 receives a zero-length message over
  notify socket

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

Bug description:
  Environment:

  Xenial 16.04.1
  Amd64

  Description.

  Systemd fails an assertion in manager_invoke_notify_message when a
  zero-length message is received over /run/systemd/notify. This allows
  a local user to perform a denial-of-service attack against PID 1.

  How to trigger the bug:

  $ while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify "";
  done

  The following entries are written into /var/log/syslog, at this point
  systemd is crashed.

  Sep 28 20:57:20 ubuntu systemd[1]: Started User Manager for UID 1000.
  Sep 28 20:57:28 ubuntu systemd[1]: Assertion 'n > 0' failed at 
../src/core/manager.c:1501, function manager_invoke_notify_message(). Aborting.
  Sep 28 20:57:29 ubuntu systemd[1]: Caught , dumped core as pid 1307.
  Sep 28 20:57:29 ubuntu systemd[1]: Freezing execution.

  
  Public bug: https://github.com/systemd/systemd/issues/4234

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

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

[Touch-packages] [Bug 1275083] Re: [MIR] ubuntuone-credentials

Override component to main
ubuntuone-credentials 15.11+16.10.20160920 in yakkety: universe/libs -> main
account-plugin-ubuntuone 15.11+16.10.20160920 in yakkety amd64: 
universe/libs/extra/100% -> main
account-plugin-ubuntuone 15.11+16.10.20160920 in yakkety arm64: 
universe/libs/extra/100% -> main
account-plugin-ubuntuone 15.11+16.10.20160920 in yakkety armhf: 
universe/libs/extra/100% -> main
account-plugin-ubuntuone 15.11+16.10.20160920 in yakkety i386: 
universe/libs/extra/100% -> main
account-plugin-ubuntuone 15.11+16.10.20160920 in yakkety powerpc: 
universe/libs/extra/100% -> main
account-plugin-ubuntuone 15.11+16.10.20160920 in yakkety ppc64el: 
universe/libs/extra/100% -> main
libubuntuoneauth-2.0-0 15.11+16.10.20160920 in yakkety amd64: 
universe/libs/extra/100% -> main
libubuntuoneauth-2.0-0 15.11+16.10.20160920 in yakkety arm64: 
universe/libs/extra/100% -> main
libubuntuoneauth-2.0-0 15.11+16.10.20160920 in yakkety armhf: 
universe/libs/extra/100% -> main
libubuntuoneauth-2.0-0 15.11+16.10.20160920 in yakkety i386: 
universe/libs/extra/100% -> main
libubuntuoneauth-2.0-0 15.11+16.10.20160920 in yakkety powerpc: 
universe/libs/extra/100% -> main
libubuntuoneauth-2.0-0 15.11+16.10.20160920 in yakkety ppc64el: 
universe/libs/extra/100% -> main
libubuntuoneauth-2.0-dev 15.11+16.10.20160920 in yakkety amd64: 
universe/libdevel/extra/100% -> main
libubuntuoneauth-2.0-dev 15.11+16.10.20160920 in yakkety arm64: 
universe/libdevel/extra/100% -> main
libubuntuoneauth-2.0-dev 15.11+16.10.20160920 in yakkety armhf: 
universe/libdevel/extra/100% -> main
libubuntuoneauth-2.0-dev 15.11+16.10.20160920 in yakkety i386: 
universe/libdevel/extra/100% -> main
libubuntuoneauth-2.0-dev 15.11+16.10.20160920 in yakkety powerpc: 
universe/libdevel/extra/100% -> main
libubuntuoneauth-2.0-dev 15.11+16.10.20160920 in yakkety ppc64el: 
universe/libdevel/extra/100% -> main
qml-module-ubuntuone 15.11+16.10.20160920 in yakkety amd64: 
universe/libs/optional/100% -> main
qml-module-ubuntuone 15.11+16.10.20160920 in yakkety arm64: 
universe/libs/optional/100% -> main
qml-module-ubuntuone 15.11+16.10.20160920 in yakkety armhf: 
universe/libs/optional/100% -> main
qml-module-ubuntuone 15.11+16.10.20160920 in yakkety i386: 
universe/libs/optional/100% -> main
qml-module-ubuntuone 15.11+16.10.20160920 in yakkety powerpc: 
universe/libs/optional/100% -> main
qml-module-ubuntuone 15.11+16.10.20160920 in yakkety ppc64el: 
universe/libs/optional/100% -> main
signon-plugin-ubuntuone 15.11+16.10.20160920 in yakkety amd64: 
universe/libs/extra/100% -> main
signon-plugin-ubuntuone 15.11+16.10.20160920 in yakkety arm64: 
universe/libs/extra/100% -> main
signon-plugin-ubuntuone 15.11+16.10.20160920 in yakkety armhf: 
universe/libs/extra/100% -> main
signon-plugin-ubuntuone 15.11+16.10.20160920 in yakkety i386: 
universe/libs/extra/100% -> main
signon-plugin-ubuntuone 15.11+16.10.20160920 in yakkety powerpc: 
universe/libs/extra/100% -> main
signon-plugin-ubuntuone 15.11+16.10.20160920 in yakkety ppc64el: 
universe/libs/extra/100% -> main
ubuntuone-credentials-autopilot 15.11+16.10.20160920 in yakkety amd64: 
universe/libs/optional/100% -> main
ubuntuone-credentials-autopilot 15.11+16.10.20160920 in yakkety arm64: 
universe/libs/optional/100% -> main
ubuntuone-credentials-autopilot 15.11+16.10.20160920 in yakkety armhf: 
universe/libs/optional/100% -> main
ubuntuone-credentials-autopilot 15.11+16.10.20160920 in yakkety i386: 
universe/libs/optional/100% -> main
ubuntuone-credentials-autopilot 15.11+16.10.20160920 in yakkety powerpc: 
universe/libs/optional/100% -> main
ubuntuone-credentials-autopilot 15.11+16.10.20160920 in yakkety ppc64el: 
universe/libs/optional/100% -> main
ubuntuone-credentials-autopilot 15.11+16.10.20160920 in yakkety s390x: 
universe/libs/optional/100% -> main
ubuntuone-credentials-common 15.11+16.10.20160920 in yakkety amd64: 
universe/libs/extra/100% -> main
ubuntuone-credentials-common 15.11+16.10.20160920 in yakkety arm64: 
universe/libs/extra/100% -> main
ubuntuone-credentials-common 15.11+16.10.20160920 in yakkety armhf: 
universe/libs/extra/100% -> main
ubuntuone-credentials-common 15.11+16.10.20160920 in yakkety i386: 
universe/libs/extra/100% -> main
ubuntuone-credentials-common 15.11+16.10.20160920 in yakkety powerpc: 
universe/libs/extra/100% -> main
ubuntuone-credentials-common 15.11+16.10.20160920 in yakkety ppc64el: 
universe/libs/extra/100% -> main
ubuntuone-credentials-common 15.11+16.10.20160920 in yakkety s390x: 
universe/libs/extra/100% -> main
45 publications overridden.


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

Title:
  [MIR] ubuntuone-credentials

Status in ubuntuone-credentials package in Ubuntu:
  Fix Released

Bug description:
  Availability: Already

[Touch-packages] [Bug 1612299] Re: [MIR] ubuntu-system-settings-online-accounts

Override component to main
ubuntu-system-settings-online-accounts 0.7+16.10.20160929-0ubuntu1 in yakkety 
amd64: universe/gnome/optional/100% -> main
ubuntu-system-settings-online-accounts 0.7+16.10.20160929-0ubuntu1 in yakkety 
arm64: universe/gnome/optional/100% -> main
ubuntu-system-settings-online-accounts 0.7+16.10.20160929-0ubuntu1 in yakkety 
armhf: universe/gnome/optional/100% -> main
ubuntu-system-settings-online-accounts 0.7+16.10.20160929-0ubuntu1 in yakkety 
i386: universe/gnome/optional/100% -> main
ubuntu-system-settings-online-accounts 0.7+16.10.20160929-0ubuntu1 in yakkety 
powerpc: universe/gnome/optional/100% -> main
ubuntu-system-settings-online-accounts 0.7+16.10.20160929-0ubuntu1 in yakkety 
ppc64el: universe/gnome/optional/100% -> main
6 publications overridden.


** Changed in: ubuntu-system-settings-online-accounts (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-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1612299

Title:
  [MIR] ubuntu-system-settings-online-accounts

Status in webapps-sprint:
  Triaged
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

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

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libsystemsettings1, ubuntu-system-settings (bug #1612280)
   * qml-module-ubuntu-onlineaccounts (same source package as this one)
   * libonline-accounts-daemon1, qml-module-ubuntu-onlineaccounts (bug #1613575)
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1612299/+subscriptions

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

[Touch-packages] [Bug 1612619] Re: [MIR] indicator-network

Override component to main
indicator-network 0.8.0+16.10.20160930.5-0ubuntu1 in yakkety amd64: 
universe/gnome/optional/100% -> main
indicator-network 0.8.0+16.10.20160930.5-0ubuntu1 in yakkety arm64: 
universe/gnome/optional/100% -> main
indicator-network 0.8.0+16.10.20160930.5-0ubuntu1 in yakkety armhf: 
universe/gnome/optional/100% -> main
indicator-network 0.8.0+16.10.20160930.5-0ubuntu1 in yakkety i386: 
universe/gnome/optional/100% -> main
indicator-network 0.8.0+16.10.20160930.5-0ubuntu1 in yakkety powerpc: 
universe/gnome/optional/100% -> main
indicator-network 0.8.0+16.10.20160930.5-0ubuntu1 in yakkety ppc64el: 
universe/gnome/optional/100% -> main
Override [y|N]? y
6 publications overridden.


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

Title:
  [MIR] indicator-network

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

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

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

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

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

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

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

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

[Touch-packages] [Bug 1594634] Re: ZFS on iscsi target fails at boot/shutdown

2016-10-03 Thread Rob

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

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

Title:
  ZFS on iscsi target fails at boot/shutdown

Status in Native ZFS for Linux:
  New

Bug description:
  I've got a ZFS volume on an ISCSI target, once the system boots I can
  bring it online.

  My ISCSI target shows up as:

  root@test:/home/rob# lsblk
  NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
  sda  8:00  8.1T  0 disk

  root@test:/home/rob# zpool status
pool: data2
   state: ONLINE
scan: none requested
  config:

NAMESTATE READ WRITE CKSUM
data2   ONLINE   0 0 0
  sda   ONLINE   0 0 0

  errors: No known data errors

  root@test:/home/rob# df -h
  Filesystem  Size  Used Avail Use% Mounted on
  --- snip --
  data2   3.1T 0  3.1T   0% /data2
  data2/backup3.2T  165G  3.1T   6% /data2/backup
  data2/test 7.7T  4.7T  3.1T  61% /data2/test


  However in the case of a system shutdown/reboot the system tries to
  unmount the disk after the network has been brought down which
  obviously fails.

  When booting the system the zpool never gets imported as the 'zfs-
  import-cache.service' runs before the iscsi target is initiated.

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

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

[Touch-packages] [Bug 1594944] Re: Setup.exec() for existing account type results in blank full screen window

This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.7+16.10.20160929-0ubuntu1

---
ubuntu-system-settings-online-accounts (0.7+16.10.20160929-0ubuntu1) yakkety; 
urgency=medium

  * Properly handle early termination of account access requests (LP:
#1594944)

 -- Alberto Mardegan   Thu, 29 Sep 2016
09:08:00 +

** Changed in: ubuntu-system-settings-online-accounts (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-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1594944

Title:
  Setup.exec() for existing account type results in blank full screen
  window

Status in Canonical System Image:
  Fix Committed
Status in webapps-sprint:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  If an account already exists, calling Setup.exec() again results in a
  blank window being overlaid on top of the application which made the
  request. There is no way to close this window.

  This API is what the online accounts integration in the scopes API
  relies upon, to allow logging in to accounts, and so we have come to
  rely upon this API as well in multiple places, as a means to log into
  the Ubuntu One account, when it is necessary to do so. However, due to
  this issue, the only way to reliably present a login window at an
  appropriate time, is to delete the account when it appears to have
  been invalidated by the server, and to then present the login window
  to create a new account.

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

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

[Touch-packages] [Bug 1630018] [NEW] qtubuntu-desktop-dbgsym is not generated

2016-10-03 Thread Michael Terry

Public bug reported:

The android version is... But not the desktop version.  I'm not sure
why.  Maybe some special argument to dh_strip needs to be passed?

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

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

Title:
  qtubuntu-desktop-dbgsym is not generated

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  The android version is... But not the desktop version.  I'm not sure
  why.  Maybe some special argument to dh_strip needs to be passed?

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

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

[Touch-packages] [Bug 1576900] Re: fail to receive sms text messages on phone

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

** Changed in: messaging-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  fail to receive sms text messages on phone

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  OTA-10.1 (mako) Ubuntu Phone

  Another phone (iPhone) on same carrier service sends me text messages.

  Expectation: Receive message

  One of three results:

  1: Receive message as expected
  2: Never receive message (displays as delivered on iPhone, no notification or 
message in "Messaging")
  3: Receive bits of message sent, scrambled with bits of other messages (from 
this same conversation/phone)

  People are starting to blame my Ubuntu phone, think it might be bug.

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

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

[Touch-packages] [Bug 1628687] Re: Assertion failure when PID 1 receives a zero-length message over notify socket

2016-10-03 Thread Martin Pitt

I added the two patches to the xenial branch, and will test/upload the
SRU tomorrow.

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  Assertion failure when PID 1 receives a zero-length message over
  notify socket

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

Bug description:
  Environment:

  Xenial 16.04.1
  Amd64

  Description.

  Systemd fails an assertion in manager_invoke_notify_message when a
  zero-length message is received over /run/systemd/notify. This allows
  a local user to perform a denial-of-service attack against PID 1.

  How to trigger the bug:

  $ while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify "";
  done

  The following entries are written into /var/log/syslog, at this point
  systemd is crashed.

  Sep 28 20:57:20 ubuntu systemd[1]: Started User Manager for UID 1000.
  Sep 28 20:57:28 ubuntu systemd[1]: Assertion 'n > 0' failed at 
../src/core/manager.c:1501, function manager_invoke_notify_message(). Aborting.
  Sep 28 20:57:29 ubuntu systemd[1]: Caught , dumped core as pid 1307.
  Sep 28 20:57:29 ubuntu systemd[1]: Freezing execution.

  
  Public bug: https://github.com/systemd/systemd/issues/4234

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

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

[Touch-packages] [Bug 1469119] Re: Limited webgl support

2016-10-03 Thread Markcortbass

I confirm that webgl is working with the bq E4.5 and Nexus 4 (RC
proposed), but not with the bq M10 tablet.

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

Title:
  Limited webgl support

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The webbrowser of the BQ Aquaris E4.5 Ubuntu Edition has limited webgl
  support. It says webgl supported but I can't see the spinning cube
  from this link. It might be a driver issue?

  https://get.webgl.org/

  Google plus discussion about this bug:
  https://plus.google.com/+Markcortbass/posts/LDa92bTtKhW

  * It's not working for the BQ Aquaris E4.5 Ubuntu Edition
  * It's working for the Meizu MX4 Ubuntu Edition

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

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

[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-10-03 Thread Antonin Chambolle

Ubuntu 16.04 on  dell E6430, after upgrade:

- after suspend/resume sometimes the network manager cannot connect (but it 
tries: it keeps associating/de-associating) [before upgrade, the wifi was 
broken at this stage, cf below]
dmesg:
[101381.710749] wlan0: authenticate with 42:01:40:59:9f:3c
[101381.712600] wlan0: send auth to 42:01:40:59:9f:3c (try 1/3)
[101381.714512] wlan0: authenticated
[101381.716173] wlan0: associate with 42:01:40:59:9f:3c (try 1/3)
[101381.726242] wlan0: RX AssocResp from 42:01:40:59:9f:3c (capab=0x411 
status=0 aid=4)
[101381.728513] wlan0: associated
[101388.076989] wlan0: deauthenticated from 42:01:40:59:9f:3c (Reason: 
15=4WAY_HANDSHAKE_TIMEOUT)
[101388.104508] cfg80211: World regulatory domain updated:
[101388.104511] cfg80211:  DFS Master region: unset
[101388.104512] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)

- if I deactivate and then reactivate the wifi, then it reverts to the old bug 
(where there is only one network available and nothing happens). sudo service 
network-manager restart repairs everything...
The bug is still at this point:
[101418.822530] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[101418.869145] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[101423.443499] e1000e: eth0 NIC Link is Down
[101426.202627] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[101426.202873] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[101426.210391] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[101426.210491] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[101426.434605] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[101426.442165] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[101426.442267] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
a problem with the /dev/something, no?

strange...
hope this can be repaired soon. But also in the 14.04 distrib it was sometimes 
necessary to deactivate/restart the network manager to catch back the signal 
after resume...
good luck, thanks

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

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

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

[Touch-packages] [Bug 1629983] Re: Temperature in Weather Report applet impossible to read when using Ambiance

2016-10-03 Thread KyL416

Screenshot of the Weather Report applet with Radiance theme

** Attachment added: "Weather Report applet with Radiance theme"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1629983/+attachment/4753664/+files/gnome-weather-radiance.png

** Also affects: gnome-applets (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Temperature in Weather Report applet impossible to read when using
  Ambiance

Status in gnome-applets package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When using the Ambiance theme, the temperature on the Weather Report
  applet is impossible to read because the font is black, so it blends
  in with the background of the panel.

  
  Ubuntu Yakkety Yak (development branch) 16.10
  light-themes version 16.10+16.10.20160926-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1629983/+subscriptions

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

[Touch-packages] [Bug 1629983] Re: Temperature in Weather Report applet impossible to read when using Ambiance

2016-10-03 Thread KyL416

Screenshot of the Weather Report applet with Ambiance theme

** Attachment added: "Screenshot of the Weather Report applet with Ambiance 
theme"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1629983/+attachment/4753663/+files/Gnome-Weather-Ambiance.png

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

Title:
  Temperature in Weather Report applet impossible to read when using
  Ambiance

Status in gnome-applets package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When using the Ambiance theme, the temperature on the Weather Report
  applet is impossible to read because the font is black, so it blends
  in with the background of the panel.

  
  Ubuntu Yakkety Yak (development branch) 16.10
  light-themes version 16.10+16.10.20160926-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1629983/+subscriptions

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

[Touch-packages] [Bug 1629983] [NEW] Temperature in Weather Report applet impossible to read when using Ambiance

2016-10-03 Thread KyL416

Public bug reported:

When using the Ambiance theme, the temperature on the Weather Report
applet is impossible to read because the font is black, so it blends in
with the background of the panel.


Ubuntu Yakkety Yak (development branch) 16.10
light-themes version 16.10+16.10.20160926-0ubuntu1

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

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

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

Title:
  Temperature in Weather Report applet impossible to read when using
  Ambiance

Status in gnome-applets package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When using the Ambiance theme, the temperature on the Weather Report
  applet is impossible to read because the font is black, so it blends
  in with the background of the panel.

  
  Ubuntu Yakkety Yak (development branch) 16.10
  light-themes version 16.10+16.10.20160926-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1629983/+subscriptions

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

[Touch-packages] [Bug 1629203] Re: aa-logprof does not include #include in profiles

2016-10-03 Thread Seth Arnold

sles, thanks for the excellent reproducer.

Christian, I'd love the 'magic' version:
> b) when adding an include, check if all variables are defined.

Of course the user interface might be a bit awkward, especially if the
intended use of the abstraction is for the profile author to provide the
variable definition in the prologue.

THanks

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

Title:
  aa-logprof does not include #include  in profiles

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04, fresh profile, 
  systemctl reload  apparmor 
  says errors:
  сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC, 
but is never declared

  This is because there is no  #include 
  in profile.

  Question here is- why? Why aa-logprof did not add it while adding
  includes?

  Thank you!

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

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

[Touch-packages] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

** Description changed:

  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under us.
  
  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.
+ 
+ Related bugs:
+   * bug 1229458: grub2 needed changes
+   * bug 1621615: network not configured when ipv6 netbooted into cloud-init
+   * bug 1621507: ipv6 network boot does not work
+ 
+ [Impact]
+ 
+ With the changes from the above, the iscsi root (at least in the ipv6
+ case) gets disconneceted prior to clean shutdown (ifdown downs the
+ interface), resulting in a failure to enlist, commission, or deploy
+ cleanly under MAAS. (and a failure to cleanly unmount the root
+ filesystem when it is over iscsi.)
+ 
+ [Test Case]
+ 
+ Given a MAAS 2.0 installation, and the packages in the other bugs,
+ attempt to enlist, commission, or deploy a host with xenial.
+ 
+ [Regression potential]
+ 
+ This restores the pre-xenial behavior of not shutting down the interface
+ if there are network drives at the time that neworking is stopped
+ (making it a no-op.)  The additional change is to detect "/dev/disk/by-
+ path/*-iscsi-*" as a network disk, replacing the check for the existence
+ of /etc/iscsi/iscsi.initramfs, which was only created by debian-
+ installer (and maas until recently).

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  New
Status in ifupdown package in Ubuntu:
  New
Status in ifupdown source package in Xenial:
  New

Bug description:
  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: ipv6 network boot does not work

  [Impact]

  With the changes from the above, the iscsi root (at least in the ipv6
  case) gets disconneceted prior to clean shutdown (ifdown downs the
  interface), resulting in a failure to enlist, commission, or deploy
  cleanly under MAAS. (and a failure to cleanly unmount the root
  filesystem when it is over iscsi.)

  [Test Case]

  Given a MAAS 2.0 installation, and the packages in the other bugs,
  attempt to enlist, commission, or deploy a host with xenial.

  [Regression potential]

  This restores the pre-xenial behavior of not shutting down the
  interface if there are network drives at the time that neworking is
  stopped (making it a no-op.)  The additional change is to detect
  "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check
  for the existence of /etc/iscsi/iscsi.initramfs, which was only
  created by debian-installer (and maas until recently).

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

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

[Touch-packages] [Bug 1469119] Re: Limited webgl support

2016-10-03 Thread advocatux

Just for your information, the spinning cube is working perfectly fine
in my BQ Aquaris E4.5 Ubuntu Edition with OTA-13.

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

Title:
  Limited webgl support

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The webbrowser of the BQ Aquaris E4.5 Ubuntu Edition has limited webgl
  support. It says webgl supported but I can't see the spinning cube
  from this link. It might be a driver issue?

  https://get.webgl.org/

  Google plus discussion about this bug:
  https://plus.google.com/+Markcortbass/posts/LDa92bTtKhW

  * It's not working for the BQ Aquaris E4.5 Ubuntu Edition
  * It's working for the Meizu MX4 Ubuntu Edition

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

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

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

2016-10-03 Thread Lorn Potter

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

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

Title:
  wifi slows to a crawl when bluetooth is enabled

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

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

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

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

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

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

** No longer affects: ifupdown (Ubuntu)

** No longer affects: ifupdown (Ubuntu Xenial)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1629972] [NEW] networking stop incorrectly disconnects from (network) root filesystem

Public bug reported:

With the switch to systemd, all support for iscsi root (and other)
filesystems disappeared, since shutdown yanks the rug out from under us.

Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
creates..), the DEV check should be expanded to include iscsi devices,
and networking.service ExecStop should honor those checks.

** Affects: maas
 Importance: Undecided
 Status: New

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Assignee: LaMont Jones (lamont)
 Status: New

** Affects: ifupdown (Ubuntu Xenial)
 Importance: Undecided
 Status: New


** Tags: maas-ipv6

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

** Also affects: ifupdown (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  New
Status in ifupdown package in Ubuntu:
  New
Status in ifupdown source package in Xenial:
  New

Bug description:
  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

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

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

[Touch-packages] [Bug 1606693] Re: No results hint cut off

2016-10-03 Thread Larry Price

** Changed in: libertine-scope
   Status: Fix Released => Invalid

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

Title:
  No results hint cut off

Status in Canonical System Image:
  Fix Released
Status in Libertine Scope:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  If there are no apps or a search/exclusion results in no apps being
  shown, the no results hint is cut off. This happened pretty recently,
  caused by the allowances for libertine-scope in unity8.

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

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

[Touch-packages] [Bug 1552100] Re: Move to .snap

2016-10-03 Thread Renato Araujo Oliveira Filho

** Changed in: ubuntu-calendar-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: ubuntu-calendar-app
   Status: Triaged => In Progress

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

Title:
  Move to .snap

Status in Canonical System Image:
  Opinion
Status in Ubuntu Music App:
  Triaged
Status in Ubuntu Notes app:
  Triaged
Status in Telegram app:
  Triaged
Status in Ubuntu Calendar App:
  In Progress
Status in Ubuntu Clock App:
  Triaged
Status in Ubuntu Document Viewer App:
  Triaged
Status in Ubuntu File Manager App:
  Triaged
Status in Ubuntu Terminal App:
  Triaged
Status in Ubuntu Weather App:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Move all packages to .snap (snappy)

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-03 Thread monte

Centrino Advanced-N 6205 here too. I have different issues from time to
time, I'd rather say I have every one described on this page. But they
happen without some strict manner, the only thing for sure is that after
every suspend I have to restart nm-applet to bring it back to normal
work.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-03 Thread Dan Large

I have an X1 Carbon Gen1 with Intel Centrino Advanced-N 6205 [Taylor Peak] (rev 
96).
'sudo iw dev wlan0 scan' doesn't help. I usually have a blank wireless icon (no 
bars) with no networks listed, occasionally the up-down arrow wired connector 
icon. Need to go to System Settings > Network to see what I'm connected to.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

2016-10-03 Thread Renato Araujo Oliveira Filho

ubuntu-calendar-app is already on Rev. 6. And it has the desktop file as
"ubuntu-calendar-app.desktop" inside of setup/gui/ directory.

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1606693] Re: No results hint cut off

2016-10-03 Thread Larry Price

** Changed in: libertine-scope
   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/1606693

Title:
  No results hint cut off

Status in Canonical System Image:
  Fix Released
Status in Libertine Scope:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  If there are no apps or a search/exclusion results in no apps being
  shown, the no results hint is cut off. This happened pretty recently,
  caused by the allowances for libertine-scope in unity8.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

** Changed in: open-iscsi (Ubuntu)
 Assignee: LaMont Jones (lamont) => (unassigned)

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in ifupdown source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-03 Thread Peter S

I have Intel Wireless 3165 (rev 81)

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1629275] Re: Clients and server all crash

It is also worth noting that starting the mir clients outside the gnome-
terminal seems stable. So whatever weirdness is going on client-side is
associated with gnome-terminal.

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

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

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

[Touch-packages] [Bug 1629275] Re: Clients and server all crash

Using qterminal in place of gnome-terminal works, so I think the server
crash may be the only Mir problem here.

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

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

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

[Touch-packages] [Bug 1629490] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

The error in your dpkg log is:

> Настраивается пакет sysv-rc (2.88dsf-59.3ubuntu2) …
> info: Reordering boot system, log to /var/lib/insserv/run-20161001T0248.log
> error: Something failed while migrating.

Please attach the indicated insserv log.

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

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in sysvinit package in Ubuntu:
  Incomplete

Bug description:
  Failed on do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Sat Oct  1 02:48:15 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.14
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: Upgraded to xenial on 2016-09-30 (0 days ago)

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

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

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1622223] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-10-03 Thread Tom

Appears to be running satisfactorily

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Attempted system upgrade - many dialogue boxes appear with this error;
  attempted apt-get -f install but still get errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 10 12:16:04 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2013-04-27 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-09-10 (0 days ago)

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

-- 
Mailing list: https://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 1622223] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-10-03 Thread Tom

The system appears to be running satisfactorily but no idea why.

Tom

On 10/3/2016 11:42 AM, Alberto Salvia Novella wrote:
> Were you able to finish the installation and get a running system?
>
> When answered, please set status back to "confirmed". Thank you.
>
> ** Changed in: systemd (Ubuntu)
> Status: Confirmed => Incomplete
>

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

Title:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Attempted system upgrade - many dialogue boxes appear with this error;
  attempted apt-get -f install but still get errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 10 12:16:04 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2013-04-27 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-09-10 (0 days ago)

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

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

[Touch-packages] [Bug 1168742] Re: [udev] Disks are not unmounted when physical eject button is used

2016-10-03 Thread Peter Bennett

I tested this. Video CD gives this
:-( non-DVD media mounted, exiting...
peter@andromeda:~$ echo $?
252

Data CD gives the same result so I suppose it would also have the same
problem.

Audio CD gives the same so I suppose it would have the same problem of
being ejected upon insertion.

I will rather live with the problem that try changing the script. If you
want me to test a change out for the script or other fix I will be glad
to help.

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

Title:
[udev] Disks are not unmounted when physical eject button is used

Status in systemd:
Confirmed
Status in systemd package in Ubuntu:
Fix Released

Bug description:
In 13.04, disks (DVDs, CDS) are not unmounted when ejected via the
hardware button on the drive. After ejecting disks via the hardware
button, an entry for the disk still shows up in the file manager, and
shows when I run df. If I do a soft eject (ie from the right click
menu from the icon on the launcher), however, everything works
properly.

Just as a note, as per
https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions, I
attempted to report this using ubuntu-bug storage, however there is
not an option dealing with unmounting devices, and clicking other
tells you that you should run ubuntu-bug again with a specific package
name. In an attempt to get this to a semi-relevant audience, I ended
up just saying that a disk wasn't auto-mounted, clicking through the
next few popups, and ended up here. If this isn't the right place to
report this bug, I apologize.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-17-generic 3.8.0-17.27
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: chris 1590 F pulseaudio
/dev/snd/controlC0: chris 1590 F pulseaudio
Date: Sat Apr 13 12:54:33 2013
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=bd2c881c-7bf8-4996-8b05-7efbd9852333
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2013-03-26 (18 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325)
MachineType: ASUSTeK COMPUTER INC. G55VW
MarkForUpload: True
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic
root=UUID=f44b6481-8a06-4cf1-a494-0e4c233720c8 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-3.8.0-17-generic N/A
linux-backports-modules-3.8.0-17-generic N/A
linux-firmware1.105
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
Monitoring the udisks daemon. Press Ctrl+C to exit.
12:54:42.343: The udisks-daemon is running (name-owner :1.39).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/05/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G55VW.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G55VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G55VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1552100] Re: Move to .snap

2016-10-03 Thread Emanuele Antonio Faraone

Now you will pass to snaps on ubuntu touch?

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

Title:
  Move to .snap

Status in Canonical System Image:
  Opinion
Status in Ubuntu Music App:
  Triaged
Status in Ubuntu Notes app:
  Triaged
Status in Telegram app:
  Triaged
Status in Ubuntu Calendar App:
  Triaged
Status in Ubuntu Clock App:
  Triaged
Status in Ubuntu Document Viewer App:
  Triaged
Status in Ubuntu File Manager App:
  Triaged
Status in Ubuntu Terminal App:
  Triaged
Status in Ubuntu Weather App:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Move all packages to .snap (snappy)

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

2016-10-03 Thread Ted Gould

Revision 3 of the snap, version 0.1.

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1628926] Re: Postpone login attempts if X successive attempts have failed

This is a feature request that may be addressed by upstream, but
certainly won't be addressed by Ubuntu in a delta. Therefore I'm marking
the "openssh (Ubuntu)" task as Won't Fix for now, because we have no
plans to fix it in Ubuntu. If you'd still like this feature in the
openssh package, then you'll need to convince the upstream openssh
maintainers to add the feature, and then Ubuntu will in time inherit it.

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Postpone login attempts if X successive attempts have failed

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  ** This is a feature request that regards to security. **

  Please add to the login method a mechanism that postpones successive
  login attempts if X attempts have failed.

  Obviously this can be further enhanced - for example:
  If X successive login attempts failed, then disable that specific login 
method for that specific user for Y minutes.
  If Y minutes have passed and the additional successive attempts failed again 
- then disable that specific login method for that specific user for 2*Y 
minutes.
  And so on... 

  Values of X and Y should be configured by the 'root' user.

  Benefits: greatly reduces the risk of remotely brute-forcing the
  password.

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

2016-10-03 Thread Ted Gould

Ubuntu Calendar App doesn't have a desktop file that matches the app
name in the YAML file. The desktop file is:

com.ubuntu.calendar_calendar.desktop

And the YAML has a app name of:

ubuntu-calendar-app

This is an invalid snap.

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1594944] Re: Setup.exec() for existing account type results in blank full screen window

2016-10-03 Thread Jean-Baptiste Lallement

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

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

Title:
  Setup.exec() for existing account type results in blank full screen
  window

Status in Canonical System Image:
  Fix Committed
Status in webapps-sprint:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  If an account already exists, calling Setup.exec() again results in a
  blank window being overlaid on top of the application which made the
  request. There is no way to close this window.

  This API is what the online accounts integration in the scopes API
  relies upon, to allow logging in to accounts, and so we have come to
  rely upon this API as well in multiple places, as a means to log into
  the Ubuntu One account, when it is necessary to do so. However, due to
  this issue, the only way to reliably present a login window at an
  appropriate time, is to delete the account when it appears to have
  been invalidated by the server, and to then present the login window
  to create a new account.

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

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

[Touch-packages] [Bug 1627502] Re: GTK3 crash in various operations

2016-10-03 Thread Timo Jyrinki

apport-collected info from earlier time for the machine can be seen at
bug #1609745.

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

Title:
  GTK3 crash in various operations

Status in gtk+3.0 package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  GTK3 crash on this specific machine, preventing lightdm from starting
  (with GTK3 using greeter), apport-collect for finishing and using
  menus or multiple tabs in GNOME Terminal.

  --- original lightdm report ---

  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.

  After some while this disappears and the system goes to some sort of
  tty switching loop where sometimes text cursor is shown and sometimes
  just blank screen. If I want to recover text console control of
  machine I need to quickly after booting switch to tty1 and stop
  lightdm.

  This started happening last week after some upgrades and a reboot.

  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
  doesn't start at all. So I'm using sddm + Plasma now but would like to
  be also be able to run Unity 7 and Unity 8.

  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1627502/+subscriptions

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

2016-10-03 Thread kevin gunn

** Changed in: unity8 (Ubuntu)
 Assignee: kevin gunn (kgunn72) => Michael Terry (mterry)

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

2016-10-03 Thread Michael Terry

I'm guessing this is a UAL-side issue, perhaps fixed by
https://code.launchpad.net/~ted/ubuntu-app-launch/install-
root/+merge/305762 ?

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1629932] [NEW] /usr/bin/nmcli:11:nmc_find_connection:nmc_secrets_requested:ffi_call_VFP:ffi_call:g_cclosure_marshal_generic_va

2016-10-03 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding network-manager.  This problem was most recently seen with
version 1.2.2-0ubuntu1~vivid3, the problem page at
https://errors.ubuntu.com/problem/b3b7dae5bf05fa65c302fd75344f7924a83e66c1
contains more details.

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


** Tags: vivid

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

Title:
  
/usr/bin/nmcli:11:nmc_find_connection:nmc_secrets_requested:ffi_call_VFP:ffi_call:g_cclosure_marshal_generic_va

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.2-0ubuntu1~vivid3, the problem page at
  https://errors.ubuntu.com/problem/b3b7dae5bf05fa65c302fd75344f7924a83e66c1
  contains more details.

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

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

[Touch-packages] [Bug 1611859] Re: Keyboard layout isn't applied in dash after wizard

2016-10-03 Thread Lukáš Tinkl

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

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

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

Title:
  Keyboard layout isn't applied in dash after wizard

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  In https://requests.ci-train.ubuntu.com/#/ticket/1771

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout in the dash after completing the wizard

  Current:
  * layout is only applied on first app focus change

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160810.2-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-001]
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 10 19:04:24 2016
  InstallationDate: Installed on 2016-05-06 (95 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1626826] Re: KVM guest cannot use br0 created by brctl on Ubuntu16.04

** Changed in: bridge-utils (Ubuntu)
   Status: Incomplete => New

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

Title:
  KVM guest cannot use br0 created by brctl on Ubuntu16.04

Status in Ubuntu on IBM z Systems:
  New
Status in bridge-utils package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2016-09-22 06:01:59 ==
  ---Problem Description---
  Ubuntu16.04. Created a bridge br0 on enc100 via brctl.  enc100 is the only 
external accessible nic. Defined a ubuntu guest to use br0 and assigned an IP 
to the guest in the same subnet as br0. After started the guest, couldn't 
access external servers or internet from the guest. 
   

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 
s390x s 390x s390x GNU/Linux
   
  Machine Type = 2827 (z Systems EC12) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. define br0 on enc100 via brctl command (IP on br0 is 192.168.1.170 for 
example)
  2. update /etc/network/interfaces
  3. create a guest on KVM and use br0 for it's nic
  4. Start guest via virsh command and assign an IP, e.g. 192.168.1.171.  After 
installation, cannot access external systems via KVM host.

  == Comment: #2 - QI YE  - 2016-09-22 09:53:58 ==
  attached sosreport file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1626826/+subscriptions

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

[Touch-packages] [Bug 1628254] Re: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut pas être configuré p

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

** This bug is no longer a duplicate of bug 1628251
   package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
** This bug has been marked a duplicate of bug 1617963
   package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)

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

Title:
  package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: le paquet libwind0-heimdal:amd64
  1.7~git20160703+dfsg-1 ne peut pas être configuré parce que la version
  de libwind0-heimdal:i386 est différente (1.7~git20150920+dfsg-
  4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 27 20:18:32 2016
  Dependencies:
   gcc-6-base 6.2.0-3ubuntu15
   libc6 2.24-0ubuntu1
   libcomerr2 1.43.1-1
   libgcc1 1:6.2.0-3ubuntu15
   libroken18-heimdal 1.7~git20160703+dfsg-1
  ErrorMessage: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut 
pas être configuré parce que la version de libwind0-heimdal:i386 est différente 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-04-22 (158 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: heimdal
  Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libwind0-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1628251] Re: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut pas être confi

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

** This bug has been marked a duplicate of bug 1617963
   package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)

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

Title:
  package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: le paquet libhcrypto4-heimdal:amd64
  1.7~git20160703+dfsg-1 ne peut pas être configuré parce que la version
  de libhcrypto4-heimdal:i386 est différente (1.7~git20150920+dfsg-
  4ubuntu1)

Status in heimdal package in Ubuntu:
  Incomplete

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 27 20:18:33 2016
  ErrorMessage: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-04-22 (158 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1628255] Re: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut pas être configuré

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

** This bug is no longer a duplicate of bug 1628251
   package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
** This bug has been marked a duplicate of bug 1617963
   package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)

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

Title:
  package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: le paquet libasn1-8-heimdal:amd64
  1.7~git20160703+dfsg-1 ne peut pas être configuré parce que la version
  de libasn1-8-heimdal:i386 est différente (1.7~git20150920+dfsg-
  4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 27 20:18:33 2016
  Dependencies:
   gcc-6-base 6.2.0-3ubuntu15
   libc6 2.24-0ubuntu1
   libcomerr2 1.43.1-1
   libgcc1 1:6.2.0-3ubuntu15
   libroken18-heimdal 1.7~git20160703+dfsg-1
  ErrorMessage: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libasn1-8-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-04-22 (158 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: heimdal
  Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libasn1-8-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1629275] Re: Clients and server all crash

** Branch linked: lp:~alan-griffiths/mir/fix-server-crash

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

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

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

[Touch-packages] [Bug 1629370] Re: PKINIT fails with PKCS#11 middlware that implements PKCS#1 V2.1

2016-10-03 Thread Tom Yu

That is one possible workaround, but I don't have an easy way to test
this.

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

Title:
  PKINIT fails with PKCS#11 middlware that implements PKCS#1 V2.1

Status in krb5 package in Ubuntu:
  New

Bug description:
  Problem: can't do PK-INIT with a smartcard PKCS#11 middleware that
  implements PKCS#1 v2.10

  $ kinit -E name.surname@something@REALM

  -> fails

  Diagnostic using PKCS11-SPY from OpenSC:

  16: C_Sign
  2016-09-16 14:31:53.265
  [in] hSession = 0x6bc3a70e
  [in] pData[ulDataLen] 0931e898 / 33
    30 1F 30 07 06 05 2B 0E 03 02 1A 04 14 17 07 D3  
0.0...+.
  0010  5A 2B F8 78 C0 FD CD 87 EE 25 08 C2 DD AA 50 3D  
Z+.x.%P=
  0020  DC   .  
 
  Returned:  32 CKR_DATA_INVALID

  The signing algorithm is SHA1. However the Data Formatting is
  incorrect:

  30 1F 30 07 06 05 2B 0E 03 02 1A 04 14 17 07 D3 5A 2B F8 78 C0 FD CD
  87 EE 25 08 C2 DD AA 50 3D DC

  instead it should be:

  30 21 30 09 06 05 2B 0E 03 02 1A 05 00 04 14 17 07 D3 5A 2B F8 78 C0 FD CD 87 
EE 25 08 C2 DD AA 50 3D DC  

  See the PKCS#1 paper (page 43) https://tools.ietf.org/html/rfc3447

  Extract:
  " 
  1. For the six hash functions mentioned in Appendix B.1, the DER
encoding T of the DigestInfo value is equal to the following:

MD2: (0x)30 20 30 0c 06 08 2a 86 48 86 f7 0d 02 02 05 00 04
 10 || H.
MD5: (0x)30 20 30 0c 06 08 2a 86 48 86 f7 0d 02 05 05 00 04
 10 || H.
SHA-1:   (0x)30 21 30 09 06 05 2b 0e 03 02 1a 05 00 04 14 || H.
  "

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: krb5-pkinit 1.12+dfsg-2ubuntu5.2
  Uname: Linux 3.13.0-68-generic x86_64
  Architecture: amd64
  Date: Fri Sep 30 12:49:09 CEST 2016
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: krb5-pkinit

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

2016-10-03 Thread Bill Filler

when launching a snap from the dash it's also displaying a blank
"unity8" window in addition to the functional app window. Assuming that
is because of this workaround using --desktop_file_hint=unity8

you can test with ubuntu-calendar-app or address-book-app from store:
sudo snap install --edge --force-dangerous --devmode ubuntu-calendar-app

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => kevin gunn (kgunn72)

** Changed in: ubuntu-app-launch (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1622423] Re: My activity child link disappears after logged in fitbit account

2016-10-03 Thread Paweł Stołowski

Ok, I was able to reproduce the issue.

I've checked unity-scopes-shell plugin with a debug branch
(https://code.launchpad.net/~stolowski/unity-scopes-shell/debug-
category-link; packages available here https://code.launchpad.net
/~unity-api-team/+archive/ubuntu/dev-build-1/+packages) and it seems to
be innocent, according to my debug the category header link is correctly
exposed to the QML (the getter for header link gets called when the
issue happens, but for some reason is not rendered). Assigning to unity8
project.

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

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

Title:
  My activity child link disappears after logged in fitbit account

Status in Canonical System Image:
  New
Status in Today Scope:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  $ system-image-cli -i
  current build number: 15
  device name: turbo
  channel: ubuntu-touch/rc/meizu-pd.en
  last update: 2016-09-05 03:19:44
  version version: 15
  version ubuntu: 20160903
  version tag: OTA-13-rc
  version device: 20160824-d33b825
  version custom: 20160831-992-8-12

  The child arrow link of My Activity session disappears once logged in
  fitbit account in Today scope, so unable to open My Activity child
  scope from Today scope

  Steps to reproduce:
  1. Open Today scope and navigate to My Activity session, 
  2. Existing a child link, tap it will open My Activity scope
  2. Tap 'Add your fitbit account' and login with Google account
  3. Once logged in, back to Today scope and refresh, check if the child link 
still exist.

  Actual results:
  Once logged in fitbit account, some items of fitbit displayed in session, but 
the child scope link has gone, unable to open My Activity scope from Today scope
  If open My Activity scope from manage page by swiping up, blank scope page 
shown

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

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

[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

Mirroring the development release's Incomplete status in Xenial - see
comment 15.

** Changed in: lxc (Ubuntu Xenial)
   Status: Confirmed => Incomplete

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

Title:
  interuppting lxc-clone can destroy source container

Status in lxc package in Ubuntu:
  Incomplete
Status in lxc source package in Vivid:
  Won't Fix
Status in lxc source package in Wily:
  Won't Fix
Status in lxc source package in Xenial:
  Incomplete

Bug description:
  ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen
  containers on demand, but if i ctrl-c interuppt the operation, i've
  seen a few cases where it will destroy the source container (using
  snapshots and btrfs)

  $ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
  ctrl-c

  the source container's rootfs directory goes missing, and only a
  rootfs.hold file remains in place.

  btrfs subvolume list shows nothing for the missing container rootfs as
  well.

  lxc-version -> 1.0.0.alpha1

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

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

** Changed in: bridge-utils (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: bridge-utils (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Importance: High => Critical

** Changed in: bridge-utils (Ubuntu Yakkety)
   Importance: High => Critical

** Changed in: linux (Ubuntu)
   Importance: High => Critical

** Changed in: bridge-utils (Ubuntu Xenial)
   Importance: High => Critical

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70

[Touch-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-10-03 Thread Eric Desrochers

As per irc conversation with apw, I'm merging both LPs #1607920 &
#1628279 into one debdiff.

** Patch added: "lp1607920_lp1628279_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1607920/+attachment/4753590/+files/lp1607920_lp1628279_xenial.debdiff

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

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

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

[Touch-packages] [Bug 1629496] Re: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

Please:

1. Edit the description so it explains which are the perceptible symptoms of 
the bug.
2. Set status back to "confirmed".

Thank you.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  apt-get no work.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hudson 2921 F pulseaudio
  Date: Fri Sep 30 21:25:27 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=4e7a0dd9-aae5-4465-962f-73010a35ab89
  InstallationDate: Installed on 2016-08-10 (51 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA TOSHIBA NB255
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=5807cac2-6f74-4bbb-a607-fba249b82e31 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.30
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.30:bd05/26/2010:svnTOSHIBA:pnTOSHIBANB255:pvrPLL2PU-00901L:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: TOSHIBA NB255
  dmi.product.version: PLL2PU-00901L
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1629496/+subscriptions

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

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

** Changed in: ubuntu-app-launch (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/1629863

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch

2016-10-03 Thread kevin gunn

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

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

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

Title:
  snap apps require hardcode --desktop-file-hint to launch

Status in Canonical System Image:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Apps installed by snap does not launch from dash icon unless you
  hardcode the wrapper file adding "--desktop_file_hint=unity8" on the
  argument list.

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

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

[Touch-packages] [Bug 1622223] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

Were you able to finish the installation and get a running system?

When answered, please set status back to "confirmed". Thank you.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Attempted system upgrade - many dialogue boxes appear with this error;
  attempted apt-get -f install but still get errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 10 12:16:04 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2013-04-27 (1231 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-09-10 (0 days ago)

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

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

[Touch-packages] [Bug 1629275] Re: Clients and server all crash

And this is where the "signal comes from:

#1  0x777672fa in mir::terminate_with_current_exception ()
at 
/home/alan/display_server/mir/src/server/terminate_with_current_exception.cpp:52
#2  0x778af4c2 in mir::compositor::CompositingFunctor::operator() 
(this=0x559fcae0)
at 
/home/alan/display_server/mir/src/server/compositor/multi_threaded_compositor.cpp:180
#3  0x778b2a7c in std::_Function_handler 
>::_M_invoke(std::_Any_data const&) (__functor=...) at 
/usr/include/c++/6/functional:1770
#4  0x77769846 in std::function::operator()() const 
(this=0x7fffee012d00) at /usr/include/c++/6/functional:2136
#5  0x779ea451 in (anonymous namespace)::Task::execute 
(this=0x7fffee012d00)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:40
#6  0x779ea7ba in (anonymous namespace)::Worker::operator() 
(this=0x559fcbd0)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:91
#7  0x779ed66c in std::__invoke_impl (__f=...) at /usr/include/c++/6/functional:218
#8  0x779ed62e in std::__invoke<(anonymous namespace)::Worker&> 
(__fn=...) at /usr/include/c++/6/functional:260
#9  0x779ed5d8 in std::reference_wrapper<(anonymous 
namespace)::Worker>::operator()<>(void) const (this=0x559fcf08)
at /usr/include/c++/6/functional:474
#10 0x779ed5b6 in std::_Bind_simple()>::_M_invoke<>(std::_Index_tuple<>) (this=0x559fcf08) 
at /usr/include/c++/6/functional:1400
#11 0x779ed540 in std::_Bind_simple()>::operator()(void) (
this=0x559fcf08) at /usr/include/c++/6/functional:1389
#12 0x779ed510 in 
std::thread::_State_impl()> >::_M_run(void) (this=0x559fcf00) at 
/usr/include/c++/6/thread:196
#13 0x7743650f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#14 0x7490170a in start_thread (arg=0x7fffee013700) at 
pthread_create.c:333
#15 0x76ea50ff in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

And that appears to be from failing to handle an exception from
DMABufTextureBinder::ensure_egl_image() ("ERROR:
/home/alan/display_server/mir/src/platforms/mesa/server/buffer_allocator.cpp(151):"
in comment #7)

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

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

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

[Touch-packages] [Bug 1629662] Re: package systemd 229-4ubuntu10 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

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

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

Title:
  package systemd 229-4ubuntu10 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from 15.10 to 16.04 I am getting this "System program
  problem deteted" warning

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Oct  2 13:37:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu10_amd64.deb ...
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu10_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  DuplicateSignature:
   package:systemd:229-4ubuntu10
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu10_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2015-05-13 (507 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Apple Inc. MacBookAir6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=11c7ca66-bf6f-43b0-ac6d-16006e14d1d8 ro pcie_aspm=force 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 
acpi_backlight=vendor
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.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.
  Title: package systemd 229-4ubuntu10 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-10-02 (0 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B22.1602221559
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B22.1602221559:bd02/22/2016:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.name: MacBookAir6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1629275] Re: Clients and server all crash

The reason the server exits is:

Thread 1 "mir_demo_server" received signal SIGTERM, Terminated.
0x76ea6200 in __libc_sendmsg (fd=40, msg=0x7fffc3f0, flags=16384) 
at ../sysdeps/unix/sysv/linux/sendmsg.c:28
28  ../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
(gdb) info threads
  Id   Target Id Frame 
* 1Thread 0x77fa47c0 (LWP 23976) "mir_demo_server" 0x76ea6200 
in __libc_sendmsg (fd=40, msg=0x7fffc3f0, 
flags=16384) at ../sysdeps/unix/sysv/linux/sendmsg.c:28
  2Thread 0x7fffee814700 (LWP 23980) "Mir/Snapshot" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  3Thread 0x7fffee013700 (LWP 23981) "Mir/Comp" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  4Thread 0x7fffed812700 (LWP 23983) "Mir/Input Reade" 0x76e9910d 
in poll () at ../sysdeps/unix/syscall-template.S:84
  5Thread 0x7fffed011700 (LWP 23984) "Mir/IPC" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  6Thread 0x7fffec810700 (LWP 23985) "Mir/IPC" __lll_lock_wait () at 
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
(gdb) c
Continuing.
[Thread 0x7fffec810700 (LWP 23985) exited]
[Thread 0x7fffed011700 (LWP 23984) exited]
[Thread 0x7fffed812700 (LWP 23983) exited]
[Thread 0x7fffee013700 (LWP 23981) exited]
[Thread 0x7fffee814700 (LWP 23980) exited]
ERROR: 
/home/alan/display_server/mir/src/platforms/mesa/server/buffer_allocator.cpp(151):
 Throw in function virtual void 
{anonymous}::DMABufTextureBinder::ensure_egl_image()
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: Failed to get PRIME fd from gbm bo: No such file or 
directory


Thread 1 "mir_demo_server" received signal SIGSEGV, Segmentation fault.
0x7038b62c in ?? ()
(gdb) bt
#0  0x7038b62c in ?? ()
#1  0x7740a141 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x76dd765a in __cxa_finalize (d=0x77dd60a0) at cxa_finalize.c:56
#3  0x77761d23 in __do_global_dtors_aux () from 
/usr/local/lib/libmirserver.so.42
#4  0x7fffe320 in ?? ()
#5  0x77de8efa in _dl_fini () at dl-fini.c:235
Backtrace stopped: frame did not save the PC

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

Title:
  Clients and server all crash

Status in Mir:
  Incomplete
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  mir-24 on yakkety (or mir-0.21 on xenial, or  lp:mir on yakkety)

  Start a Mir-on-X11 session:

  $ mir_demo_server_minimal &
  $ mirrun gnome-terminal

  In the terminal:

  $ mir_demo_client_all&

  (A script that launches all the Mir demo clients - attached)

  Expect: all the clients open
  Actual (most times): gnome-terminal and all the clients crash
  Actual (frequently): gnome-terminal, all the clients, and the server crash
  Actual (occasionally): all the clients open

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

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

[Touch-packages] [Bug 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb

2016-10-03 Thread Paweł Stołowski

Looks like it's related to the changes to settings model made from a
separate thread (QtConcurrent is used to update child scopes).

** Changed in: unity-scopes-shell (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

Title:
  unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from
  QObjectPrivate::isSignalConnected from QMetaObject::activate from
  QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset

Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1622126] Re: unity8 crashed with SIGSEGV in dri2_destroy_surface()

2016-10-03 Thread kevin gunn

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  unity8 crashed with SIGSEGV in dri2_destroy_surface()

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

Bug description:
  *

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Sep 10 10:38:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160909)
  ProcCmdline: unity8 --mode=full-shell
  SegvAnalysis:
   Segfault happened at: 0x7fe0b7c19624:mov(%rax),%rax
   PC (0x7fe0b7c19624) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglDestroySurface () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
  Title: unity8 crashed with SIGSEGV in eglDestroySurface()
  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/canonical-devices-system-image/+bug/1622126/+subscriptions

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

[Touch-packages] [Bug 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb

2016-10-03 Thread Albert Astals Cid

** Also affects: unity-scopes-shell (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/1627795

Title:
  unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from
  QObjectPrivate::isSignalConnected from QMetaObject::activate from
  QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset

Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1629553] Re: unity8 crashed with SIGSEGV in memcpy()

2016-10-03 Thread Albert Astals Cid

** Information type changed from Private to Public

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

Title:
  unity8 crashed with SIGSEGV in memcpy()

Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  unity8 crashed with SIGSEGV in memcpy()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Oct  1 16:15:40 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-06-05 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: unity8 --mode=full-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff9d530a877 :movups (%rsi),%xmm0
   PC (0x7ff9d530a877) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   memcpy () at 
../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S:141
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
  Title: unity8 crashed with SIGSEGV in memcpy()
  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/mir/+bug/1629553/+subscriptions

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

[Touch-packages] [Bug 1588526] Re: Alarm doesn't ring when screen locked

2016-10-03 Thread slash

In my case, the reminders from the calendar fails to wake up the phone.

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

Title:
  Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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

[Touch-packages] [Bug 1575893] Re: Toolbar focus & keyboard navigation

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/actionbar-keyboard

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

Title:
  Toolbar focus & keyboard navigation

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Toolbar needs focus for keyboard navigation that works in the same way
  as the Sections.

  These two bugs need to be fixed first:

  - https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1611327
  - https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614541

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

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

[Touch-packages] [Bug 1629792] Re: udpsocket ready read not fired on arm64

2016-10-03 Thread Alexander Lampret

Unfortunately, upgrading and recompiling did not solve the problem.

netstat -l RECV-Q shows bytes received but readyRead is not fired.
Im listening to port 3512 (for example), but nothing happens inside udp
receiver test program.
I've added a possibility to send datagrams on 3512 in the same program. These
"writeDatagram()" datagrams fire a readyRead event, as long as there are no
other datagram from an external source are queued.

If I use a udp receiver written in python, for testing, it works like a
charm

P.S: Sorry, wrong bug attached, there was one bug related to linux and
this was a clone related to OSX.

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

Title:
udpsocket ready read not fired on arm64

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

Bug description:
Hello,

I faced a problem where readyRead is not fired for QUdpSocket.
I've tested this functionality with a basic udp receiver on different systems.
On armhf it works fine, the same code does not work on arm64 (Pine64).

This seems to be similar to bug https://bugreports.qt.io/browse/QTBUG-48556
mentioned on QT site to be fixed with 5.5.1
Maybe it was not merged to arm64? Or any other idea?
netstat -l shows that bytes are available

With polling implementation it's possible to receive the data.

Ubuntu 16.04.1, all updates
Pine64, arm64
Kernel: 3.10.102-2-pine64-longsleep

Best regards,
Alex

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-03 Thread Jeremy LaCroix

Running 'sudo iw dev wlan0 scan' does work around the issue for me. I
have this issue on two computers, they have the following wireless cards
from Intel:

Intel Wireless 7260 (rev bb)
Intel Wireless 7260 (rev 73)

Just to be clear, should I be creating a new bug for each of these two
cards? Would this be the 'linux' package, or 'iwlwifi'?

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-10-03 Thread Michael Terry

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

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

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

2016-10-03 Thread Thomas Niedermeier

This bug affects me too. I'm working on a Tyan Power8 machine (PPC64el) with 
Ubuntu 16.04.1 and 10GB network cards using the bnx2x driver. A configured 
network bridge on my machine results in a kernel oops if I trigger a shutdown 
or reboot, see attachment.
I installed the 4.8.0-040800-generic kernel and now the shutdown or reboot 
works fine, so I would recommend using the LTS Enablement Stack 
(linux-generic-lts-yakkety) when it's available.

** Attachment added: "shutdown-problem-power8"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616107/+attachment/4753518/+files/shutdown-problem-power8

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130

[Touch-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir