[Touch-packages] [Bug 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error

2016-10-14 Thread AnonymouseP
Just had this on reboot after today's updates. Error report brought me to 
bug#1452849, useful feature that!
Xenial 16.04 fresh install.

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

Title:
  /sbin/upstart:indicator-session-unknown-user-error

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Vivid:
  Confirmed
Status in upstart source package in Wily:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding upstart.  This problem was most recently seen with version
  1.13.2-0ubuntu13, the problem page at
  https://errors.ubuntu.com/problem/09ab1b2ed4cff7556ed135307deb9f99c107193a
  contains more details.

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

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


[Touch-packages] [Bug 1590244] Re: Upgrading upower package caused forced reboot

2016-10-14 Thread Jerry Quinn
Any progress on this bug?

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

Title:
  Upgrading upower package caused forced reboot

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When upower was updated, the system claimed that my UPS was empty.
  The system then proceeded to shut down.  On reboot, the UPS was fully
  charged as expected.

  This is a major data loss concern.  The system shut down while
  upgrading packages.  Perhaps the bug is in the handling of my specific
  UPS but it's still important.

  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  jlquinn@cerberus:~$ apt-cache policy upower
  upower:
Installed: 0.99.4-2ubuntu0.2
Candidate: 0.99.4-2ubuntu0.2
Version table:
   *** 0.99.4-2ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.99.4-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  output of lsusb -v for my UPS

  Bus 003 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x0764 Cyber Power System, Inc.
idProduct  0x0501 CP1500 AVR UPS
bcdDevice0.01
iManufacturer   3 CPS
iProduct1 CP625HGa
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   34
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass  0 No Subclass
bInterfaceProtocol  0 None
iInterface  0 
  HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID   1.10
bCountryCode   33 US
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 410
   Report Descriptors: 
 ** UNAVAILABLE **
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0008  1x 8 bytes
  bInterval  10
  Device Status: 0x
(Bus Powered)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-2ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 00:27:23 2016
  InstallationDate: Installed on 2016-05-30 (8 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: upower
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (7 days ago)

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

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


[Touch-packages] [Bug 1403764] Re: Usermetrics temporarily bad during initialization on vivid r58

2016-10-14 Thread Launchpad Bug Tracker
[Expired for libusermetrics (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  Usermetrics temporarily bad during initialization on vivid r58

Status in libusermetrics package in Ubuntu:
  Expired

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

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

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


[Touch-packages] [Bug 1275548] Re: package usermetricsservice (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2016-10-14 Thread Launchpad Bug Tracker
[Expired for libusermetrics (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  package usermetricsservice (not installed) failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in libusermetrics package in Ubuntu:
  Expired

Bug description:
  uninstalling Bluetooth software because it was no working properly y
  found this problem

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: usermetricsservice (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Sun Feb  2 14:21:01 2014
  DuplicateSignature: package:usermetricsservice:(not installed):subprocess new 
pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2014-01-13 (20 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: libusermetrics
  Title: package usermetricsservice (not installed) failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1605835] Re: Apport won't open web browser and submit to launchpad

2016-10-14 Thread Launchpad Bug Tracker
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apport (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Apport won't open web browser and submit to launchpad

Status in apport package in Ubuntu:
  Expired

Bug description:
  Apport won't open web browser after pressed continue button in crash report 
window.
  Have to do it manually every time doing it manually using (ubuntu-bug -c 
/var/crash/_bug.crash)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-32.51-generic 4.4.15
  Uname: Linux 4.4.0-32-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 23 11:28:32 2016
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1310012] Re: package usermetricsservice 1.1.1+14.04.20140305-0ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/dbus-1/system-services/com.canonical.UserM

2016-10-14 Thread Launchpad Bug Tracker
[Expired for libusermetrics (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  package usermetricsservice 1.1.1+14.04.20140305-0ubuntu2 failed to
  install/upgrade: trying to overwrite shared '/usr/share/dbus-1/system-
  services/com.canonical.UserMetrics.service', which is different from
  other instances of package usermetricsservice:i386

Status in libusermetrics package in Ubuntu:
  Expired

Bug description:
  during installation it crashed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: usermetricsservice 1.1.1+14.04.20140305-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Sat Apr 19 17:21:39 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: 
package:usermetricsservice:1.1.1+14.04.20140305-0ubuntu2:trying to overwrite 
shared '/usr/share/dbus-1/system-services/com.canonical.UserMetrics.service', 
which is different from other instances of package usermetricsservice:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/dbus-1/system-services/com.canonical.UserMetrics.service', which is 
different from other instances of package usermetricsservice:i386
  InstallationDate: Installed on 2014-04-19 (0 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  SourcePackage: libusermetrics
  Title: package usermetricsservice 1.1.1+14.04.20140305-0ubuntu2 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/dbus-1/system-services/com.canonical.UserMetrics.service', which is 
different from other instances of package usermetricsservice:i386
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
  modified.conffile..etc.dbus.1.system.d.com.canonical.UserMetrics.conf: 
[deleted]

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

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


[Touch-packages] [Bug 1632415] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-10-14 Thread clickwir
Was going through the regular GUI upgrade process from 16.04, message
kept coming up dozens of times. After clicking CLOSE on about the 20th
one, I just held ENTER until they went away. Upgrade continued, gave a
message at the end that something didn't install right and my system
might be unstable.

After the upgrade process was done, I manually ran apt update and dist-
upgrade, it found several more things to do. Those all completed without
issue, rebooted and everything is fine so far.

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  error after updating from 16.04.1 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Oct 11 22:08:46 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-25 (78 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago)

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

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


[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default

2016-10-14 Thread Luis Alvarado
Just if anybody is wondering, apport came enabled by default on Ubuntu
16.10 and in I would say 15 minutes of installing it from scratch I had
already 5 error reports, again, of things that were fixed automatically
when the app reloaded itself. It just pushes the entry point of Ubuntu
for new users away from being easy.

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

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

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


[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads

2016-10-14 Thread Thomas
It seemed like it happened every time at first, but it's really only
been about 50% in the past two weeks.  So every second login attempt
would end up getting stuck on average.

I upgraded to 16.10 yesterday and have not yet encountered this issue.

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions

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


[Touch-packages] [Bug 1630156] Re: No password needed to Log in after cancel the password and then reset again

2016-10-14 Thread Robert Ancell
Also attaching the contents of /var/log/lightdm/lightdm.log after
logging in will give more information.

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  OS: 14.04 trusty

  Tested with 16.10
  lightdm version is 1.19.5
  issue still exist

  
  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password.
  3. Reboot and log to desktop without password.
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Reboot but still no password needed at Log in interface.

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

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


[Touch-packages] [Bug 1630156] Re: No password needed to Log in after cancel the password and then reset again

2016-10-14 Thread Robert Ancell
Can you check at step 5 if the user is still in the "nopasswdlogin"
group? i.e. by running 'groups' as that user or checking the contents of
/etc/group

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  OS: 14.04 trusty

  Tested with 16.10
  lightdm version is 1.19.5
  issue still exist

  
  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password.
  3. Reboot and log to desktop without password.
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Reboot but still no password needed at Log in interface.

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

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


[Touch-packages] [Bug 1633618] Re: software updater: dialog unreadable with details

2016-10-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  software updater: dialog unreadable with details

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  In the dialog that you get when some ppa is not available the
  "details" are unreadable (see screenshot)

   i.e. the textbox is much too small

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 22:51:06 2016
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2014-07-08 (829 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1633618/+subscriptions

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


[Touch-packages] [Bug 1173915] Re: initctl continuously takes 100% of CPU

2016-10-14 Thread Felix Moreno
It's happening me to me in ubuntu 16.10 after a day of uptime maybe...

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

Title:
  initctl continuously takes 100% of CPU

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Many programs are fairly slow to start on my computer, despite it
  being relatively new (core i5). Suspecting a heavy CPU usage, I
  started gnome-system-monitor: all processes were displayed at 0% CPU,
  but the overall load was 1.33; 1.33; 1.34.

  Using the "top" command, however, revealed the real CPU use, with the
  "initctl" process taking 100%CPU, even 1 hour after startup.

  I upgraded to roaring ringtail before checking this but the symptoms
  were the same with quantal quetzal, so there is a fair chance the
  causes were identical.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Sun Apr 28 13:04:05 2013
  ExecutablePath: /sbin/initctl
  InstallationDate: Installed on 2012-12-15 (133 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UpstartBugCategory: System

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

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


[Touch-packages] [Bug 1633653] Re: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured bec

2016-10-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: package libhcrypto4-heimdal:amd64
  1.7~git20160703+dfsg-1 cannot be configured because
  libhcrypto4-heimdal:i386 is at a different version (1.7~git20150920
  +dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  This happened when upgrading to 16.10 from 16.04 on lubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 18:32:44 2016
  DuplicateSignature:
   package:libhcrypto4-heimdal:amd64:1.7~git20160703+dfsg-1
   Unpacking libgssapi3-heimdal:amd64 (1.7~git20160703+dfsg-1) over 
(1.7~git20150920+dfsg-4ubuntu1) ...
   dpkg: error processing package libwind0-heimdal:amd64 (--configure):
package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libwind0-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2015-12-05 (314 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633653] [NEW] package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured b

2016-10-14 Thread vanquishedangel
Public bug reported:

This happened when upgrading to 16.10 from 16.04 on lubuntu.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Oct 14 18:32:44 2016
DuplicateSignature:
 package:libhcrypto4-heimdal:amd64:1.7~git20160703+dfsg-1
 Unpacking libgssapi3-heimdal:amd64 (1.7~git20160703+dfsg-1) over 
(1.7~git20150920+dfsg-4ubuntu1) ...
 dpkg: error processing package libwind0-heimdal:amd64 (--configure):
  package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libwind0-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
ErrorMessage: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
InstallationDate: Installed on 2015-12-05 (314 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: heimdal
Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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


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

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

Title:
  package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: package libhcrypto4-heimdal:amd64
  1.7~git20160703+dfsg-1 cannot be configured because
  libhcrypto4-heimdal:i386 is at a different version (1.7~git20150920
  +dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  This happened when upgrading to 16.10 from 16.04 on lubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 18:32:44 2016
  DuplicateSignature:
   package:libhcrypto4-heimdal:amd64:1.7~git20160703+dfsg-1
   Unpacking libgssapi3-heimdal:amd64 (1.7~git20160703+dfsg-1) over 
(1.7~git20150920+dfsg-4ubuntu1) ...
   dpkg: error processing package libwind0-heimdal:amd64 (--configure):
package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libwind0-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2015-12-05 (314 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633643] [NEW] unnecessary dependency upon isc-dhcp-client

2016-10-14 Thread ben thielsen
Public bug reported:

with xenial-updates, there is suddenly a dependency [isc-dhcp-client]
not previously there.  please mark this as recommends/suggests/enhances
instead of as a depends, as it is not critical to the core functionality
of the software.  since ubuntu now defaults to installing recommends
unless configured otherwise, this compromise accommodates both the
unskilled users as well as those who know what they are doing and have
disabled automatic installation of suggested packages.

1] >lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

2] >apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.122ubuntu8.3
  Candidate: 0.122ubuntu8.3
  Version table:
 *** 0.122ubuntu8.3 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.122ubuntu8 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages

3] i expected to not be forced to install unnecessary packages
4] i was forced to

thanks

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  unnecessary dependency upon isc-dhcp-client

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  with xenial-updates, there is suddenly a dependency [isc-dhcp-client]
  not previously there.  please mark this as
  recommends/suggests/enhances instead of as a depends, as it is not
  critical to the core functionality of the software.  since ubuntu now
  defaults to installing recommends unless configured otherwise, this
  compromise accommodates both the unskilled users as well as those who
  know what they are doing and have disabled automatic installation of
  suggested packages.

  1] >lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2] >apt-cache policy initramfs-tools
  initramfs-tools:
Installed: 0.122ubuntu8.3
Candidate: 0.122ubuntu8.3
Version table:
   *** 0.122ubuntu8.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.122ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  3] i expected to not be forced to install unnecessary packages
  4] i was forced to

  thanks

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

-- 
Mailing list: https://launchpad.net/~touch-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: [mako] Alarm doesn't ring when screen locked

2016-10-14 Thread Michal Predotka
Comment #13 describes a problem with a different alarm sound played then
expected. I believe that could be the same situation as in bug #1596924
(sound change need to be confirmed)

-- 
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:
  [mako] 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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-10-14 Thread Jeremy
Luke, I haven't had a pulseaudio crash and I have been able to connect
to 2 different headsets since installing 16.04 however getting A2DP to
work by switching it in sound settings is usually impossible.  Both
headsets have volume controls and microphones.  A little bluetooth
speaker without microphone or volume controls uses A2DP without issues

The behavior I see is similar to your comment #18

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-14 Thread David
@April_J No my hardware is Samsung

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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: [mako] Alarm doesn't ring when screen locked

2016-10-14 Thread RAMupgrade
The suggestion of no longer supporting the Nexus 4 (comment #24) is worrying, 
as there are no current OEM devices for sale and few enough supported models. 
This deprecation isn't mentioned anywhere else (that I could find) and flies in 
the face of these current pages:
https://developer.ubuntu.com/en/phone/devices/
https://developer.ubuntu.com/en/phone/devices/devices/

This doesn't *appear* to be the official line from Canonical and
probably shouldn't be stated as fact or used as the basis for any
decisions until confirmed in a more official capacity.

I've just updated the clock app on my Nexus 4 to version 3.8.487. The
update's fix list doesn't mention a fix for the alarm issue discussed
above, so I'll continue testing because I care about this (as do
others). I don't plan to change device any time soon either! ;)

Additionally, comment #13 above describes the bug affecting the BQ
Aquarius M10, not the Nexus 4.

-- 
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:
  [mako] 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 1633415] Re: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because l

2016-10-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1
  cannot be configured because libwind0-heimdal:i386 is at a different
  version (1.7~git20150920+dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  apport showed up

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 12:11:33 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu1
   libcomerr2 1.43.3-1
   libgcc1 1:6.2.0-5ubuntu12
   libroken18-heimdal 1.7~git20160703+dfsg-1
  DuplicateSignature:
   package:libwind0-heimdal:amd64:1.7~git20160703+dfsg-1
   Unpacking libkrb5-26-heimdal:amd64 (1.7~git20160703+dfsg-1) over 
(1.7~git20150920+dfsg-4ubuntu1) ...
   dpkg: error processing package libwind0-heimdal:amd64 (--configure):
package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libwind0-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be 
configured because libwind0-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-02-19 (237 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: heimdal
  Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libwind0-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)

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

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


[Touch-packages] [Bug 1633416] Re: 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

2016-10-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  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)

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  apport showed up

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 12:07:20 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu1
   libcomerr2 1.43.3-1
   libgcc1 1:6.2.0-5ubuntu12
   libroken18-heimdal 1.7~git20160703+dfsg-1
  DpkgTerminalLog:
   Preparing to unpack .../libasn1-8-heimdal_1.7~git20160703+dfsg-1_amd64.deb 
...
   De-configuring libasn1-8-heimdal:i386 (1.7~git20150920+dfsg-4ubuntu1) ...
   Unpacking libasn1-8-heimdal:amd64 (1.7~git20160703+dfsg-1) over 
(1.7~git20150920+dfsg-4ubuntu1) ...
   dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
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)
  DuplicateSignature:
   package:libasn1-8-heimdal:amd64:1.7~git20160703+dfsg-1
   Unpacking libasn1-8-heimdal:amd64 (1.7~git20160703+dfsg-1) over 
(1.7~git20150920+dfsg-4ubuntu1) ...
   dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
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)
  ErrorMessage: 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)
  InstallationDate: Installed on 2016-02-19 (237 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: heimdal
  Title: 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)
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)

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

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


[Touch-packages] [Bug 1633616] Re: [webapp-container] Staging Regression: In staging the progress bar does not function within webapps

2016-10-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~osomon/webbrowser-app/staging-fix-webapp-
container-progress-bar

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

Title:
  [webapp-container] Staging Regression: In staging the progress bar
  does not function within webapps

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  What Happened:
  1) Open a webapp, eg facebook or twitter
  2) Watch the progress bar (the blue bar under the address at the top)
  3) Notice that it does not move or disappear

  What I expected to happen:
  At step 3 for the progress bar to function correctly.

  Note that this only happens on lp:webbrowser-app/staging (#1563) not
  trunk and only seems to happen within webapps not the browser.

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

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


[Touch-packages] [Bug 1633616] Re: [webapp-container] Staging Regression: In staging the progress bar does not function within webapps

2016-10-14 Thread Olivier Tilloy
** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => 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/1633616

Title:
  [webapp-container] Staging Regression: In staging the progress bar
  does not function within webapps

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  What Happened:
  1) Open a webapp, eg facebook or twitter
  2) Watch the progress bar (the blue bar under the address at the top)
  3) Notice that it does not move or disappear

  What I expected to happen:
  At step 3 for the progress bar to function correctly.

  Note that this only happens on lp:webbrowser-app/staging (#1563) not
  trunk and only seems to happen within webapps not the browser.

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

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


[Touch-packages] [Bug 1633619] [NEW] dhclient -1 exits 0 when no lease found

2016-10-14 Thread Scott Moser
Public bug reported:

I've tried this in containers of xenial, trusty and yakkety.

i've created a lxc network that does not have dhcp4.

See https://github.com/lxc/lxd/issues/2481 for some info on how to do
that.

Then, I launch an instance:

$ lxc launch ubuntu-daily:xenial --profile=sm-test-profile2 x1
% killall dhclient
% dhclient -r eth0
% dhclient -1 -v eth0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:16:3e:b8:e6:70
Sending on   LPF/eth0/00:16:3e:b8:e6:70
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xc08cb53c)

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0xc08cb53c)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0xc08cb53c)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0xc08cb53c)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xc08cb53c)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0xc08cb53c)
..
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

% echo $?
0
% ps axw | grep dhcl
  356 ?Ss 0:00 dhclient -1 -v eth0


the man page says of the '-1' option:
   -1 Try to get a lease once.  On  failure  exit  with  code  2.   In
  DHCPv6 this sets the maximum duration of the initial exchange to
  timeout (from dhclient.conf with a default of sixty seconds).

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: isc-dhcp-client 4.3.3-5ubuntu15
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 14 16:59:45 2016
DhclientLeases:

EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (449 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-bug yakkety

** Description changed:

- I've tried this in containers
+ I've tried this in containers of xenial, trusty and yakkety.
  
  i've created a lxc network that does not have dhcp4.
  
  See https://github.com/lxc/lxd/issues/2481 for some info on how to do
  that.
  
  Then, I launch an instance:
  
  $ lxc launch ubuntu-daily:xenial --profile=sm-test-profile2 x1
  % killall dhclient
  % dhclient -r eth0
  % dhclient -1 -v eth0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/eth0/00:16:3e:b8:e6:70
  Sending on   LPF/eth0/00:16:3e:b8:e6:70
  Sending on   Socket/fallback
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xc08cb53c)
  
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0xc08cb53c)
  ..
  No DHCPOFFERS received.
  No working leases in persistent database - sleeping.
  
  % echo $?
  0
+ % ps axw | grep dhcl
+   356 ?Ss 0:00 dhclient -1 -v eth0
  
  
  the man page says of the '-1' option:
--1 Try to get a lease once.  On  failure  exit  with  code  2.   In
-   DHCPv6 this sets the maximum duration of the initial exchange to
-   timeout (from dhclient.conf with a default of sixty seconds).
+    -1 Try to get a lease once.  On  failure  exit  with  code  2.   In
+   DHCPv6 this sets the maximum duration of the initial exchange to
+   timeout (from dhclient.conf with a default of sixty seconds).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 16:59:45 2016
  DhclientLeases:
-  
+ 
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  

[Touch-packages] [Bug 1633619] Re: dhclient -1 exits 0 when no lease found

2016-10-14 Thread Scott Moser
for reference, you can make it fail faster like this in
/etc/dhcp/dhclient.conf


timeout 3;
retry 3;
#reboot 10;
select-timeout 5;
initial-interval 1;

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

Title:
  dhclient -1 exits 0 when no lease found

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I've tried this in containers of xenial, trusty and yakkety.

  i've created a lxc network that does not have dhcp4.

  See https://github.com/lxc/lxd/issues/2481 for some info on how to do
  that.

  Then, I launch an instance:

  $ lxc launch ubuntu-daily:xenial --profile=sm-test-profile2 x1
  % killall dhclient
  % dhclient -r eth0
  % dhclient -1 -v eth0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eth0/00:16:3e:b8:e6:70
  Sending on   LPF/eth0/00:16:3e:b8:e6:70
  Sending on   Socket/fallback
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xc08cb53c)

  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0xc08cb53c)
  ..
  No DHCPOFFERS received.
  No working leases in persistent database - sleeping.

  % echo $?
  0
  % ps axw | grep dhcl
356 ?Ss 0:00 dhclient -1 -v eth0

  
  the man page says of the '-1' option:
     -1 Try to get a lease once.  On  failure  exit  with  code  2.   In
    DHCPv6 this sets the maximum duration of the initial exchange to
    timeout (from dhclient.conf with a default of sixty seconds).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 16:59:45 2016
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633619/+subscriptions

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


[Touch-packages] [Bug 1633621] Re: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

2016-10-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 14 17:12:56 2016
  DuplicateSignature:
   package:libqt4-sql:i386:4:4.8.7+dfsg-5ubuntu2
   Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ...
   dpkg: error processing package libqt4-sql:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-03-10 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (173 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1633621/+subscriptions

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


[Touch-packages] [Bug 1633616] Re: [webapp-container] Staging Regression: In staging the progress bar does not function within webapps

2016-10-14 Thread Olivier Tilloy
Interestingly, this is observable only when there is some chrome (i.e.
when the webapp container is invoked with --enable-addressbar or
--enable-back-forward). When there is no chrome, the progress bar
behaves as expected.

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

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Critical

** Changed in: webbrowser-app (Ubuntu)
   Importance: Critical => High

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  [webapp-container] Staging Regression: In staging the progress bar
  does not function within webapps

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  What Happened:
  1) Open a webapp, eg facebook or twitter
  2) Watch the progress bar (the blue bar under the address at the top)
  3) Notice that it does not move or disappear

  What I expected to happen:
  At step 3 for the progress bar to function correctly.

  Note that this only happens on lp:webbrowser-app/staging (#1563) not
  trunk and only seems to happen within webapps not the browser.

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

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


[Touch-packages] [Bug 1633621] [NEW] package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

2016-10-14 Thread Don Dryer
Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Oct 14 17:12:56 2016
DuplicateSignature:
 package:libqt4-sql:i386:4:4.8.7+dfsg-5ubuntu2
 Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ...
 dpkg: error processing package libqt4-sql:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-03-10 (218 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: qt4-x11
Title: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-04-24 (173 days ago)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 14 17:12:56 2016
  DuplicateSignature:
   package:libqt4-sql:i386:4:4.8.7+dfsg-5ubuntu2
   Processing triggers for libglib2.0-0:amd64 (2.48.1-1~ubuntu16.04.1) ...
   dpkg: error processing package libqt4-sql:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-03-10 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (173 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1633621/+subscriptions

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


[Touch-packages] [Bug 1225467] Re: Pashto keyboard bug

2016-10-14 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version.

When you test it and it is still an issue, kindly upload the updated
logs by running only once:

apport-collect 1225467

and any other logs that are relevant for this particular issue.

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

** Package changed: ubuntu => xkeyboard-config (Ubuntu)

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

Title:
  Pashto keyboard bug

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  On Pashto keyboard ALTGR+U KEY should yield  U+0659 ARABIC ZWARAKAY
  and ALTGR+Y KEY U+0653 ARABIC MADDAH ABOVE. Instead, they yield wacko
  Latin characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1225467/+subscriptions

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-14 Thread Jonathan Brier
Ran valgrind on the indicator-datetime-service with the following
command trying to track down the origin of the issue.

The following command and parameters were used:
G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --tool=memcheck 
--leak-check=full --num-callers=40 --log-file=valgrind.log 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service

** Attachment added: "valgrind.log"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+attachment/4761235/+files/valgrind.log

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633618] [NEW] software updater: dialog unreadable with details

2016-10-14 Thread Guntbert Reiter
Public bug reported:

In the dialog that you get when some ppa is not available the "details"
are unreadable (see screenshot)

 i.e. the textbox is much too small

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: software-properties-gtk 0.96.24.7
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 14 22:51:06 2016
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2014-07-08 (829 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

** Attachment added: "Untitled window_035.png"
   
https://bugs.launchpad.net/bugs/1633618/+attachment/4761229/+files/Untitled%20window_035.png

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

Title:
  software updater: dialog unreadable with details

Status in software-properties package in Ubuntu:
  New

Bug description:
  In the dialog that you get when some ppa is not available the
  "details" are unreadable (see screenshot)

   i.e. the textbox is much too small

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 22:51:06 2016
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2014-07-08 (829 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1633618/+subscriptions

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


[Touch-packages] [Bug 1633437] Re: unable to use intel graphic card

2016-10-14 Thread Timo Aaltonen
you are using unofficial ppa packages, those are not supported by ubuntu

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

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

Title:
  unable to use intel graphic card

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have t440p laptop with intel graphic card

  $ sudo lshw -c display
*-display UNCLAIMED 
 description: VGA compatible controller
 product: 4th Gen Core Processor Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:f000-f03f memory:e000-efff 
ioport:3000(size=64)

  But I am not able to use h/w rendering.

  Tried running following command (no success)
  sudo apt-get install xserver-xorg-video-intel

  Also, used intel's graphic tools to update the packages but no success their 
also.
  Anything I am missing.. 
  This problem appeared when I upgraded ubuntu 14.x to ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Start the GNUstep distributed 
object mapper.
  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
  Date: Fri Oct 14 17:05:27 2016
  DistUpgraded: 2016-08-09 13:35:04,151 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T440p [17aa:220e]
  InstallationDate: Installed on 2014-08-11 (794 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20AWS0L000
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic.efi.signed 
root=UUID=11b8d3e7-2288-4e79-90a2-2cd00d457e7c ro quiet splash pcie_aspm=force 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-09 (66 days ago)
  dmi.bios.date: 02/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET67WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AWS0L000
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWS0L000:pvrThinkPadT440p:rvnLENOVO:rn20AWS0L000:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AWS0L000
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.71+git20161010.a44c9c31-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 
12.1~git20161011.fc8b358b-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
12.1~git20161011.fc8b358b-0ubuntu0ricotz~xenial
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.7.99+git20161010.3fc839ff-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20161010.696f58f6-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20161010.e6479845-0ubuntu0ricotz~xenial
  xserver.bootTime: Fri Oct 14 16:32:19 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.1

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

-- 
Mailing list: 

[Touch-packages] [Bug 1225467] [NEW] Pashto keyboard bug

2016-10-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On Pashto keyboard ALTGR+U KEY should yield  U+0659 ARABIC ZWARAKAY and
ALTGR+Y KEY U+0653 ARABIC MADDAH ABOVE. Instead, they yield wacko Latin
characters.

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: bot-comment
-- 
Pashto keyboard bug
https://bugs.launchpad.net/bugs/1225467
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

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


[Touch-packages] [Bug 1633616] [NEW] [webapp-container] Staging Regression: In staging the progress bar does not function within webapps

2016-10-14 Thread Andrew Hayzen
Public bug reported:

What Happened:
1) Open a webapp, eg facebook or twitter
2) Watch the progress bar (the blue bar under the address at the top)
3) Notice that it does not move or disappear

What I expected to happen:
At step 3 for the progress bar to function correctly.

Note that this only happens on lp:webbrowser-app/staging (#1563) not
trunk and only seems to happen within webapps not the browser.

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

** Summary changed:

- [webapp-container] In staging the progress bar does not function
+ [webapp-container] Staging Regression: In staging the progress bar does not 
function within webapps

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

Title:
  [webapp-container] Staging Regression: In staging the progress bar
  does not function within webapps

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  What Happened:
  1) Open a webapp, eg facebook or twitter
  2) Watch the progress bar (the blue bar under the address at the top)
  3) Notice that it does not move or disappear

  What I expected to happen:
  At step 3 for the progress bar to function correctly.

  Note that this only happens on lp:webbrowser-app/staging (#1563) not
  trunk and only seems to happen within webapps not the browser.

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

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


[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-10-14 Thread D Tangman
Same problem - 16.04.1 LTS fully updated. Two copies of this message
logged about every 13 minutes.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-10-14 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

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

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

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+subscriptions

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


[Touch-packages] [Bug 1633615] [NEW] package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2016-10-14 Thread nil
Public bug reported:

after upgrade to ubuntu 16.10

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: bluez 5.41-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Oct 14 10:52:50 2016
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
InstallationDate: Installed on 2013-11-30 (1049 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Inspiron 1545
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=03c53b2c-c3ae-48ae-a246-49246e8c0344 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: bluez
Title: package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0W299R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd02/25/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0W299R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:24:2B:F9:D9:87  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:511 acl:0 sco:0 events:23 errors:0
TX bytes:339 acl:0 sco:0 commands:23 errors:0
rfkill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

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


** Tags: amd64 apport-package yakkety

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

Title:
  package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in bluez package in Ubuntu:
  New

Bug description:
  after upgrade to ubuntu 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 10:52:50 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2013-11-30 (1049 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 1545
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=03c53b2c-c3ae-48ae-a246-49246e8c0344 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: bluez
  Title: package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0W299R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd02/25/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0W299R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:24:2B:F9:D9:87  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:511 acl:0 sco:0 events:23 errors:0
TX bytes:339 acl:0 sco:0 commands:23 errors:0
  rfkill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

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

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


[Touch-packages] [Bug 592434] Re: ssh -X user@machine hangs when using exit to terminate

2016-10-14 Thread Bryan Quigley
This has been fixed in Ubuntu 16.10.  I'm guessing by systemd/dbus
changes but I'm not sure.  Tested with gedit and virt-manager.

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

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

Title:
  ssh -X user@machine hangs when using exit to terminate

Status in D-Bus:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in dbus package in Debian:
  New

Bug description:
  ssh -X user@server hangs when using exit to terminate

  Steps to reproduce:
  user@client:~$ ssh -X user@server
  user@server:~$ gedit

  At this point gedit from server will run locally. Closing the program
  and returning to the terminal you run:

  user@server:~$ exit
  logout

  At this point the terminal hangs on the echo logout, but does not return to 
the client prompt. The action has been consistent when connecting to a server 
running opensolaris or ubuntu 8.04.
  The client is using Ubuntu 10.04 and the server is using 8.04, and using 
default password authentication. As you will see in the video attached I can 
confirm the issue when using a clean Ubuntu 10.04 as a client and Ubuntu 8.04 
as the server, using default password authentication.

  Workaround
  --
  -When logging out with "exit" and it hangs, press Ctrl-C
  -If you would like to simply use gedit on another computer use the following 
command:
    $ dbus-launch gedit

  Date: Thu Jun 10 17:34:26 2010

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

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


[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-14 Thread Mathew Hodson
** Changed in: initramfs-tools (Ubuntu Z-series)
   Importance: Undecided => High

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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


[Touch-packages] [Bug 1571213] Re: package language-pack-en-base 1:16.04+20160415 failed to install/upgrade: package language-pack-en-base is already installed and configured

2016-10-14 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

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

** Changed in: language-pack-en-base (Ubuntu)
   Status: New => Confirmed

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

Title:
  package language-pack-en-base 1:16.04+20160415 failed to
  install/upgrade: package language-pack-en-base is already installed
  and configured

Status in language-pack-en-base package in Ubuntu:
  Confirmed

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: language-pack-en-base 1:16.04+20160415
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sat Apr 16 04:10:01 2016
  DuplicateSignature:
   Processing triggers for libc-bin (2.23-0ubuntu3) ...
   dpkg: error processing package language-pack-en-base (--configure):
package language-pack-en-base is already installed and configured
  ErrorMessage: package language-pack-en-base is already installed and 
configured
  InstallationDate: Installed on 2016-04-15 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: language-pack-en-base
  Title: package language-pack-en-base 1:16.04+20160415 failed to 
install/upgrade: package language-pack-en-base is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1571213/+subscriptions

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


[Touch-packages] [Bug 1633583] Re: Can not connect to Bluetooth headset

2016-10-14 Thread Paul White
** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can not connect to Bluetooth  headset

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I managed to pair with my wireless headset, but I was unable to
  connect to it.

  Every time I try to do it, I get this message in syslog:
  Oct 14 21:38:09 localhost bluetoothd[2246]: Unable to get Headset Voice 
gateway SDP record: Host is down

  Relating info is below

   Info from bluetoothctl: 
  bluetooth]# devices 
  Device 00:1B:66:03:C4:66 MOMENTUM M2 AEBT
  bluetooth]# info 00:1B:66:03:C4:66
  Device 00:1B:66:03:C4:66
  Name: MOMENTUM M2 AEBT
  Alias: MOMENTUM M2 AEBT
  Class: 0x240404
  Icon: audio-card
  Paired: yes
  Trusted: yes
  Blocked: no
  Connected: no
  LegacyPairing: yes
  UUID: Headset   (1108--1000-8000-00805f9b34fb)
  UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
  UUID: Handsfree (111e--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  UUID: Vendor specific   (1ddce62a-ecb1-4455-8153-0743c87aec9f)
  Modalias: bluetooth:v0082p004Bd010E

  
   Info from hciconfig 
  $ sudo hciconfig -a
  [sudo] password for dimanne: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 5C:F3:70:73:F2:B1  ACL MTU: 1021:8  SCO MTU: 64:1
  UP RUNNING PSCAN ISCAN 
  RX bytes:14866 acl:33 sco:0 events:2022 errors:0
  TX bytes:17848 acl:33 sco:0 commands:1639 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH SNIFF 
  Link mode: SLAVE ACCEPT 
  Name: 'impedance #1'
  Class: 0x1c0104
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Desktop workstation
  HCI Version: 4.0 (0x6)  Revision: 0x1000
  LMP Version: 4.0 (0x6)  Subversion: 0x220e
  Manufacturer: Broadcom Corporation (15)

  hci1:   Type: Primary  Bus: USB
  BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
  DOWN 
  RX bytes:2926 acl:0 sco:0 events:161 errors:0
  TX bytes:5699 acl:0 sco:0 commands:157 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH SNIFF 
  Link mode: SLAVE ACCEPT 

  
   rfkill: 
  $ rfkill list
  1: hci1: Bluetooth
  Soft blocked: no
  Hard blocked: no
  2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
   Info from dmesg: 
  $ dmesg | grep -i blue
  [5.170808] Bluetooth: Core ver 2.21
  [5.170819] Bluetooth: HCI device and connection manager initialized
  [5.170821] Bluetooth: HCI socket layer initialized
  [5.170822] Bluetooth: L2CAP socket layer initialized
  [5.170826] Bluetooth: SCO socket layer initialized
  [5.185923] Bluetooth: hci0: BCM: chip id 63
  [5.186665] Bluetooth: hci1: BCM: chip id 63
  [5.202506] Bluetooth: hci0: impedance #2
  [5.203150] Bluetooth: hci1: ChromeLinux_5818
  [5.203498] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [5.203670] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
  [5.203671] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not 
found
  [5.204662] Bluetooth: hci1: BCM20702A1 (001.002.014) build 
  [5.204671] bluetooth hci1: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
  [5.204671] Bluetooth: hci1: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
  [   11.359871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   11.359872] Bluetooth: BNEP filters: protocol multicast
  [   11.359874] Bluetooth: BNEP socket layer initialized
  [   34.046364] Bluetooth: RFCOMM TTY layer initialized
  [   34.046368] Bluetooth: RFCOMM socket layer initialized
  [   34.046371] Bluetooth: RFCOMM ver 1.11
  [ 1193.523500] Bluetooth: hci0: BCM: chip id 63
  [ 1193.539525] Bluetooth: hci0: BCM20702A
  [ 1193.540524] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [ 1193.540535] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cb.hcd 

[Touch-packages] [Bug 1633291] Re: package click-apparmor 0.3.17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-14 Thread Jeff-stafford
This is caused by having a conflicting Python package "click". To fix:

sudo pip3 uninstall click
sudo apt install -f

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  This occurred as part of an upgrade to 16.10.

  It was part of a number of failed upgrades:

  Errors were encountered while processing:
   click
   click-apparmor
   url-dispatcher:amd64
   ubuntu-app-launch
   ubuntu-system-settings
   url-dispatcher-tools
   ubuntu-app-launch-tools
   libunity-scopes1.0:amd64
   ubuntu-system-settings-online-accounts
   unity8
   account-plugin-ubuntuone
   unity-plugin-scopes:amd64
   unity-greeter-session-broadcast
   unity8-desktop-session
   ubuntu-push-client
   unity-scope-click
   account-plugin-facebook
   pay-service
   unity8-common
   unity8-private:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   ubuntu-release-upgrader-gtk:amd64: Install
   ubuntu-release-upgrader-core:amd64: Install
   python3-distupgrade:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Oct 13 20:54:48 2016
  DuplicateSignature:
   package:click-apparmor:0.3.17
   Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package click (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-10 (186 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-14 Thread LaMont Jones
After more discussion, marking this verification-done.

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

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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


[Touch-packages] [Bug 1633219] Re: Upgrade to yakkety fails due to non-us locale

2016-10-14 Thread QkiZ
For me do-release-upgrade crashed right after download packages needed
to system upgrade. But after that I was able to continue upgrade started
by sudo apt upgrade. Now Ubuntu 16.10 is booting and working, but people
that don't have knowledge may be frustrated.

LANG=pl_PL.UTF-8
LANGUAGE=pl:en
LC_CTYPE="pl_PL.UTF-8"
LC_NUMERIC=pl_PL.UTF-8
LC_TIME=pl_PL.UTF-8
LC_COLLATE="pl_PL.UTF-8"
LC_MONETARY=pl_PL.UTF-8
LC_MESSAGES="pl_PL.UTF-8"
LC_PAPER=pl_PL.UTF-8
LC_NAME=pl_PL.UTF-8
LC_ADDRESS=pl_PL.UTF-8
LC_TELEPHONE=pl_PL.UTF-8
LC_MEASUREMENT=pl_PL.UTF-8
LC_IDENTIFICATION=pl_PL.UTF-8
LC_ALL=

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

Title:
  Upgrade to yakkety fails due to non-us locale

Status in python-apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  Upgrade to yakkety failed during updates installation. The do-release-
  upgrade window froze and there was a stacktrace in the terminal:

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
  block = f.read(1048576)
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  

[Touch-packages] [Bug 1633377] Re: upgrade not possible

2016-10-14 Thread Timo Aaltonen
how is that a bug in xorg?

anyway, upgrading from vivid to xenial is not supported, you need to
upgrade to wily first

** Package changed: xorg (Ubuntu) => ubuntu

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

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

Title:
  upgrade not possible

Status in Ubuntu:
  Invalid

Bug description:
  hi ! I can't upgrade from vivid ubuntu 15.04 to xenial xerus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-71.79-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-71-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 14 10:36:35 2016
  DistUpgraded: 2016-10-14 10:32:47,175 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:041e]
  InstallationDate: Installed on 2014-12-18 (666 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-71-generic 
root=UUID=10e3fa53-feee-4a81-9b28-9c2094349818 ro plymouth:debug splash quiet 
drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to vivid on 2016-10-14 (0 days ago)
  dmi.bios.date: 07/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: H81M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/08/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Wed Oct 12 17:37:57 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3.1

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

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


[Touch-packages] [Bug 1633583] [NEW] Can not connect to Bluetooth headset

2016-10-14 Thread DimanNe
Public bug reported:

I managed to pair with my wireless headset, but I was unable to connect
to it.

Every time I try to do it, I get this message in syslog:
Oct 14 21:38:09 localhost bluetoothd[2246]: Unable to get Headset Voice gateway 
SDP record: Host is down

Relating info is below

 Info from bluetoothctl: 
bluetooth]# devices 
Device 00:1B:66:03:C4:66 MOMENTUM M2 AEBT
bluetooth]# info 00:1B:66:03:C4:66
Device 00:1B:66:03:C4:66
Name: MOMENTUM M2 AEBT
Alias: MOMENTUM M2 AEBT
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: yes
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (1ddce62a-ecb1-4455-8153-0743c87aec9f)
Modalias: bluetooth:v0082p004Bd010E


 Info from hciconfig 
$ sudo hciconfig -a
[sudo] password for dimanne: 
hci0:   Type: Primary  Bus: USB
BD Address: 5C:F3:70:73:F2:B1  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:14866 acl:33 sco:0 events:2022 errors:0
TX bytes:17848 acl:33 sco:0 commands:1639 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'impedance #1'
Class: 0x1c0104
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Desktop workstation
HCI Version: 4.0 (0x6)  Revision: 0x1000
LMP Version: 4.0 (0x6)  Subversion: 0x220e
Manufacturer: Broadcom Corporation (15)

hci1:   Type: Primary  Bus: USB
BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:2926 acl:0 sco:0 events:161 errors:0
TX bytes:5699 acl:0 sco:0 commands:157 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT 


 rfkill: 
$ rfkill list
1: hci1: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no


 Info from dmesg: 
$ dmesg | grep -i blue
[5.170808] Bluetooth: Core ver 2.21
[5.170819] Bluetooth: HCI device and connection manager initialized
[5.170821] Bluetooth: HCI socket layer initialized
[5.170822] Bluetooth: L2CAP socket layer initialized
[5.170826] Bluetooth: SCO socket layer initialized
[5.185923] Bluetooth: hci0: BCM: chip id 63
[5.186665] Bluetooth: hci1: BCM: chip id 63
[5.202506] Bluetooth: hci0: impedance #2
[5.203150] Bluetooth: hci1: ChromeLinux_5818
[5.203498] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
[5.203670] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
[5.203671] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not 
found
[5.204662] Bluetooth: hci1: BCM20702A1 (001.002.014) build 
[5.204671] bluetooth hci1: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
[5.204671] Bluetooth: hci1: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
[   11.359871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.359872] Bluetooth: BNEP filters: protocol multicast
[   11.359874] Bluetooth: BNEP socket layer initialized
[   34.046364] Bluetooth: RFCOMM TTY layer initialized
[   34.046368] Bluetooth: RFCOMM socket layer initialized
[   34.046371] Bluetooth: RFCOMM ver 1.11
[ 1193.523500] Bluetooth: hci0: BCM: chip id 63
[ 1193.539525] Bluetooth: hci0: BCM20702A
[ 1193.540524] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
[ 1193.540535] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
[ 1193.540536] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not 
found
[ 1575.051358] Bluetooth: Inquiry failed: status 0x12
[ 1593.226346] Bluetooth: Inquiry failed: status 0x12
[ 1684.104314] Bluetooth: Inquiry failed: status 0x12
[ 1694.087408] Bluetooth: Inquiry failed: status 0x12



pulseaudio-module-bluetooth is installed:
dpkg -l | grep pulseaudio-module-bluetooth
ii  pulseaudio-module-bluetooth 1:9.0-2ubuntu2 amd64 Bluetooth module for 

[Touch-packages] [Bug 1633437] Re: unable to use intel graphic card

2016-10-14 Thread Timo Aaltonen
do you have linux-image-generic installed?


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

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

Title:
  unable to use intel graphic card

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have t440p laptop with intel graphic card

  $ sudo lshw -c display
*-display UNCLAIMED 
 description: VGA compatible controller
 product: 4th Gen Core Processor Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:f000-f03f memory:e000-efff 
ioport:3000(size=64)

  But I am not able to use h/w rendering.

  Tried running following command (no success)
  sudo apt-get install xserver-xorg-video-intel

  Also, used intel's graphic tools to update the packages but no success their 
also.
  Anything I am missing.. 
  This problem appeared when I upgraded ubuntu 14.x to ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Start the GNUstep distributed 
object mapper.
  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
  Date: Fri Oct 14 17:05:27 2016
  DistUpgraded: 2016-08-09 13:35:04,151 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T440p [17aa:220e]
  InstallationDate: Installed on 2014-08-11 (794 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20AWS0L000
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic.efi.signed 
root=UUID=11b8d3e7-2288-4e79-90a2-2cd00d457e7c ro quiet splash pcie_aspm=force 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-09 (66 days ago)
  dmi.bios.date: 02/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET67WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AWS0L000
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWS0L000:pvrThinkPadT440p:rvnLENOVO:rn20AWS0L000:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AWS0L000
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.71+git20161010.a44c9c31-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 
12.1~git20161011.fc8b358b-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
12.1~git20161011.fc8b358b-0ubuntu0ricotz~xenial
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.7.99+git20161010.3fc839ff-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20161010.696f58f6-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20161010.e6479845-0ubuntu0ricotz~xenial
  xserver.bootTime: Fri Oct 14 16:32:19 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.1

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

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

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-14 Thread LaMont Jones
I have confirmed that this functions as expected for MAAS (behaves
exactly like 0.122ubuntu8.1 did.)  Not marking verification-done, but +1
from me/MAAS.

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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


[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-14 Thread Jason Gerard DeRose
Okay, tested 0.122ubuntu8.5 from xenial-proposed, and it fixes the issue
for my use-case.

But I'm not changing verification-needed to verification-done yet as I
don't know if it fixes the use case of the original reporter.

@scotte - can you please confirm whether this fixes things for you?

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in z-series:
  Fix Committed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
     - The ?*:?*:?*:?*: use case falls through to the default case, and likely 
breaks there.  As such static assignment via ip= appears broken
     -
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  This bug is a regression of changes made under bug 1628306.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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


[Touch-packages] [Bug 1630014] Re: GPS is unable to find any position

2016-10-14 Thread Anupam
Well, fortunately (or unfortunately?) my location is detected again
after one more /var/lib/ubuntu-location-service/config.ini deletion
followed by a cold boot. I shall try to gather the logs if I see this
issue again.

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

Title:
  GPS is unable to find any position

Status in Canonical System Image:
  New
Status in location-service package in Ubuntu:
  New

Bug description:
  Even if you enable tracking position on Aquaris E 4.5, either with
  here drive or just with the GPS on, no position is tracked.

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

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


[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

2016-10-14 Thread Dan Streetman
> The fix i intended was to dhclient, so that dhclient would wait in
PREINIT6 dhclient-script.

Looks good to me, fixing dhclient as well is a good idea.

> I think that is generally more functional as it would mean ifupdown or any 
> other user of dhclient
> would get the fix.

What other users are there of dhclient, besides ifupdown (and manually
running dhclient)?

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

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

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

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

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

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

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

  [Test Case]

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

  [Regression Potential]

  None

  [Other Info]

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

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

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

  exiting.
  -

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-10-14 Thread Stéphane Graber
So I'm not convinced that doing this in dhclient is necessarily right.
Unlike IPv4 where DHCP operates over a raw socket, in IPv6 mode,
dhclient is just a regular network client and as such requires a source
address to be set so it can contact the network (the link-local address
in this case).

As dhclient is supposed to only be triggered after a RA has been
received and parsed, it should be the job of whatever handles the RA to
wait until a viable link-local has been established before triggering
dhclient.

That being said, since we don't seem to have anything that handles that
first configuration step properly, this workaround certainly won't hurt
and will fix the current race condition.

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

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

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

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+subscriptions

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


[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2016-10-14 Thread Ognjen
This started on 16.10 btw.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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


[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2016-10-14 Thread Ognjen
Hello,

I'm having same issues with vpnc plugin and DNS servers I get from my
VPN. Seems like dnsmasq doesn't try to send DNS resolve packet at all
via tunnel. Once I connect to tunnel, DNS resolving is totally broken.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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


[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-10-14 Thread Scott Moser
** Patch added: "suggested fix"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+attachment/4761164/+files/suggested-fix.diff

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

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

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

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+subscriptions

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


[Touch-packages] [Bug 1633562] Re: 'dhclient -6 -S' does not bring interface up

2016-10-14 Thread Stéphane Graber
So I suspect the reason for this behavior is that there is no reason why
you'd want to run dhclient in IPv6 mode before you've brought up the
interface and parsed the router advertisement.

That's because unlike IPv4, IPv6 configuration is mostly done through
router advertisements which happen entirely outside of DHCPv6. The
content of that router advertisement then dictates whether DHCPv6 should
be done and if so, in which mode.

So the way things are expected to happen is:
 - Bring up the interface
 - Do router solicitation and get a router advertisement
 - Parse the router advertisement, looking for the other-config (O) and managed 
(M) flag.
 - If the managed bit is set, then trigger dhcpv6 in stateful mode
 - If the managed bit isn't set and other-config bit is set, then trigger 
dhcpv6 in stateless mode
 - If neither are, then use the RDNSS and DNSSL information from the 
advertisement to configure DNS

Triggering dhclient in stateless or even stateful mode before getting a
router advertisement may succeed but may also run into a race condition
as the gateway and prefix length may not have been received by the time
the DHCP dialog is over, leading to invalid configuration.

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Invalid

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

Title:
  'dhclient -6 -S' does not bring interface up

Status in isc-dhcp package in Ubuntu:
  Invalid

Bug description:
  When poking around with bug 1633479 i realized that 'dhclient -6 -S -1
  eth0' will not raise the interface eth0.  if it is not up already and
  have link local addresses, then it will fail.

  This may well be designed, so I'm fine if this bug is closed as 'INVALID' 
with such an explanation.
  One thing I did notice though, when seeing if this was easily fixed was
   a.) previously bringing the link up was not done (no scripts are called)
   b.) the PREINIT script in dhclient.linux does:
   # flush any stale global permanent IPs from interface
   ip -6 addr flush dev ${interface} scope global permanent

  That means that currently, a non-stateless dhclient
  invocation would flush global permanent addresses, but a stateless
  dhclient invocation would not.

  If we changed dhclient to call dhclient-script with PREINIT6, then this 
scenario:
ip link set down dev eth0
ip link set up dev eth0
ip address add fd42::2/64 dev eth0
dhclient -S -6 -v -1 eth0

  will cause the fd42::2 address to be removed from eth0, where
  as previously it was not.  I'm not sure if the previous behavior
  was designed or chance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 13:08:13 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633562/+subscriptions

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


[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-10-14 Thread Scott Moser
** Description changed:

  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:
  
   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/
  
   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.
  
   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1
  
  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
+  * bug 1633562: 'dhclient -6 -S' does not bring interface up 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

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

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

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+subscriptions

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


[Touch-packages] [Bug 1633562] [NEW] 'dhclient -6 -S' does not bring interface up

2016-10-14 Thread Scott Moser
Public bug reported:

When poking around with bug 1633479 i realized that 'dhclient -6 -S -1
eth0' will not raise the interface eth0.  if it is not up already and
have link local addresses, then it will fail.

This may well be designed, so I'm fine if this bug is closed as 'INVALID' with 
such an explanation.
One thing I did notice though, when seeing if this was easily fixed was
 a.) previously bringing the link up was not done (no scripts are called)
 b.) the PREINIT script in dhclient.linux does:
 # flush any stale global permanent IPs from interface
 ip -6 addr flush dev ${interface} scope global permanent

That means that currently, a non-stateless dhclient
invocation would flush global permanent addresses, but a stateless
dhclient invocation would not.

If we changed dhclient to call dhclient-script with PREINIT6, then this 
scenario:
  ip link set down dev eth0
  ip link set up dev eth0
  ip address add fd42::2/64 dev eth0
  dhclient -S -6 -v -1 eth0

will cause the fd42::2 address to be removed from eth0, where
as previously it was not.  I'm not sure if the previous behavior
was designed or chance.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: isc-dhcp-client 4.3.3-5ubuntu15
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 14 13:08:13 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (449 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  'dhclient -6 -S' does not bring interface up

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  When poking around with bug 1633479 i realized that 'dhclient -6 -S -1
  eth0' will not raise the interface eth0.  if it is not up already and
  have link local addresses, then it will fail.

  This may well be designed, so I'm fine if this bug is closed as 'INVALID' 
with such an explanation.
  One thing I did notice though, when seeing if this was easily fixed was
   a.) previously bringing the link up was not done (no scripts are called)
   b.) the PREINIT script in dhclient.linux does:
   # flush any stale global permanent IPs from interface
   ip -6 addr flush dev ${interface} scope global permanent

  That means that currently, a non-stateless dhclient
  invocation would flush global permanent addresses, but a stateless
  dhclient invocation would not.

  If we changed dhclient to call dhclient-script with PREINIT6, then this 
scenario:
ip link set down dev eth0
ip link set up dev eth0
ip address add fd42::2/64 dev eth0
dhclient -S -6 -v -1 eth0

  will cause the fd42::2 address to be removed from eth0, where
  as previously it was not.  I'm not sure if the previous behavior
  was designed or chance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 13:08:13 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633562/+subscriptions

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


[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

2016-10-14 Thread John Johansen
** Also affects: apparmor (Ubuntu Yakkety)
   Importance: Critical
 Assignee: Tyler Hicks (tyhicks)
   Status: Fix Released

** Also affects: linux (Ubuntu Yakkety)
   Importance: Critical
 Assignee: John Johansen (jjohansen)
   Status: Fix Released

** Also affects: lxd (Ubuntu Yakkety)
   Importance: Critical
 Assignee: Stéphane Graber (stgraber)
   Status: Fix Released

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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


[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-10-14 Thread Scott Moser
Note, bug 1447715 fixes ifupdown for this, but it seems to me that the
fix is better suited here.

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

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

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

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+subscriptions

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-14 Thread April J
@dklongley -- Can you let me know if you're also running on System76
hardware? I am attempting to reproduce this now. Thank you!

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

2016-10-14 Thread Scott Moser
I found this bug separately and filed bug 1633479.
The fix i intended was to dhclient, so that dhclient would wait in PREINIT6 
dhclient-script.

I think that is generally more functional as it would mean ifupdown or
any other user of dhclient would get the fix.

Thoughts?

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

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

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

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

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

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

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

  [Test Case]

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

  [Regression Potential]

  None

  [Other Info]

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

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

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

  exiting.
  -

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

2016-10-14 Thread Stéphane Graber
** Changed in: lxd (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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


[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-10-14 Thread Scott Moser
** Description changed:

  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:
  
-  $ dev=eth0
-  $ ip link set down dev $dev
-  $ dhclient -6 -1 -v eth0
-  Internet Systems Consortium DHCP Client 4.3.3
-  Copyright 2004-2015 Internet Systems Consortium.
-  All rights reserved.
-  For info, please visit https://www.isc.org/software/dhcp/
-  
-  Can't bind to dhcp address: Cannot assign requested address
-  Please make sure there is no other dhcp server
-  running and that there's no entry for dhcp or
-  bootp in /etc/inetd.conf.   Also make sure you
-  are not running HP JetAdmin software, which
-  includes a bootp server.
-  
-  If you think you have received this message due to a bug rather
-  than a configuration issue please read the section on submitting
-  bugs on either our web page at www.isc.org or in the README file
-  before submitting a bug.  These pages explain the proper
-  process and the information we find helpful for debugging..
-  $ echo $?
-  1
+  $ dev=eth0
+  $ ip link set down dev $dev
+  $ dhclient -6 -1 -v eth0
+  Internet Systems Consortium DHCP Client 4.3.3
+  Copyright 2004-2015 Internet Systems Consortium.
+  All rights reserved.
+  For info, please visit https://www.isc.org/software/dhcp/
  
+  Can't bind to dhcp address: Cannot assign requested address
+  Please make sure there is no other dhcp server
+  running and that there's no entry for dhcp or
+  bootp in /etc/inetd.conf.   Also make sure you
+  are not running HP JetAdmin software, which
+  includes a bootp server.
+ 
+  If you think you have received this message due to a bug rather
+  than a configuration issue please read the section on submitting
+  bugs on either our web page at www.isc.org or in the README file
+  before submitting a bug.  These pages explain the proper
+  process and the information we find helpful for debugging..
+  $ echo $?
+  1
+ 
+ 
+ Related bugs:
+  * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:
  
   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/
  
   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.
  
   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1
  
+ Related bugs:
+  * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
  
- Related bugs:
-  * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a 

[Touch-packages] [Bug 1633520] Re: Support dbus runtime relocation

2016-10-14 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  Support dbus runtime relocation

Status in D-Bus:
  Unknown
Status in dbus package in Ubuntu:
  New

Bug description:
  For example, when running in a snap.

  I ran into this while testing a unity8 desktop session snap.  Session
  services were being dbus-activated, but dbus was running the hardcoded
  paths in the session desktop files.  Which weren't pointed into the
  snap.

  DBus has support for relocating those paths, but it only does so on
  Windows.

  I've added a patch to support $DBUS_ROOT on Unix and relocate paths as
  needed.  I've linked the upstream bug here.  We may want to consider
  patching Ubuntu while we wait for it to land upstream.

  I've attached the patch here too.

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

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


[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial

2016-10-14 Thread Christian Dywan
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Released => In Progress

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

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

Title:
  UITK Date picker broken on xenial

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6
  (right).

  More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml
  [...]
  FAIL!  : components::DatePicker13API::test_1_changeMinimumBeforeDate() 
Uncaught exception: Cannot call method hasOwnProperty of null
   Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)]

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

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


[Touch-packages] [Bug 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list

2016-10-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~3v1n0/unity8/calendar-day-selection

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

Title:
  Clicking a date in the new calendar doesn't change the indicator's
  appointment list

Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Now that we've got a calendar in indicator-datetime in Unity 8, there
  are a few features from Unity 7 that we should decide if/how we're
  goint to handle in Unity 8.

  * Show Week Numbers
  * Highlight days of the month that include appointments
  * Unity tells indicator-datetime what calendar day has been clicked so that 
the "upcoming appointments" list can be adjusted accordingly

  These are currently implemented as fields in a GAction state
  dictionary and documented in http://bazaar.launchpad.net/~indicator-
  applet-developers/indicator-datetime/trunk.15.10/view/head:/README ...
  however that was all done for Unity 7, and IMO it would make sense to
  improve the unity<->indicator API here so that Unity8 doesn't have to
  deal with key-variant map GAction states.

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

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


[Touch-packages] [Bug 1622717] Re: "Quit" from quicklist doesn’t close all open windows, doesn’t actually quit the application

2016-10-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/qtmir/qtmir-ubuntu-yakkety-2077

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

Title:
  "Quit" from quicklist doesn’t close all open windows, doesn’t actually
  quit the application

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

Bug description:
  I’m attaching a sample click application that contains a simple qml
  scene that opens several windows. This can be installed on a device
  with:

pkcon install-local --allow-untrusted fubar.osomon_0.4_all.click

  Initially, only one window is open, and tapping on any window opens
  one more window.

  If I reveal the launcher and long press on the app’s icon to select
  the "Quit" option, not all windows are closed:

   - if there is only one window open, it’s closed and the application 
successfully exits
   - if there are two windows open, only the second window is closed, the first 
one remains open (and consequently the application is still running)
   - if there are three windows open, only the first and third one are closed, 
the second one remains…

  Expected behaviour: when "Quit" is tapped, all open windows are
  closed, and the application exits.

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

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


[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

2016-10-14 Thread Scott Moser
** Changed in: isc-dhcp (Ubuntu)
   Status: Fix Committed => Confirmed

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/
   
   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.
   
   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+subscriptions

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


[Touch-packages] [Bug 1630211] Re: Moving a tab quickly when there are many tabs open, sometimes causes tab to left in a incorrect position

2016-10-14 Thread Olivier Tilloy
I can reliably reproduce the issue with many tabs open.
This is mitigated by the fact that if you keep the mouse button pressed and 
start moving the tab again after its position got out of sync with your cursor, 
it will re-position itself to follow the cursor again.

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Moving a tab quickly when there are many tabs open, sometimes causes
  tab to left in a incorrect position

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  What happened:
  1) Open the webbrowser and many tabs
  2) Select the first tab
  3) Drag the tab quickly from the left side to the right
  4) Notice that as you are dragging the tab lags and is sometimes left at a 
previous position (not the end)

  What I expected to happen:
  At step 4 for the tab to be in the correct position.

  This occurs because the tab move() only moves +/- 1 at any time, and
  is performed onXChanged. Which occurs from the animation of the change
  X position from the mouse. However if you move fast enough the
  animation skips certain values, causing some moves to be missed.

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

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


[Touch-packages] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

2016-10-14 Thread Brian Murray
Hello Kyle, or anyone else affected,

Accepted sudo into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/sudo/1.8.9p5-1ubuntu1.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Trusty:
  Won't Fix
Status in sudo source package in Trusty:
  Fix Committed
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  Fix Released

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

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


[Touch-packages] [Bug 1624342] Re: tst_textarea.11.qml unit test fails

2016-10-14 Thread Christian Dywan
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   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-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1624342

Title:
  tst_textarea.11.qml unit test fails

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

Bug description:
  Fails with Qt 5.6.

  FAIL!  : components::TextAreaAPI::test_0_color() TextArea.color is same as 
TextEdit.canUndo
 Actual   (): #5d5d5d
 Expected (): #00
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)]

  See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/1201/consoleFull

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

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


[Touch-packages] [Bug 1633528] Re: QmlTests::UbuntuWebView02::test_no_contextual_actions() is flaky

2016-10-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~osomon/webbrowser-app/fix-1633528-flaky-unit-test

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

Title:
  QmlTests::UbuntuWebView02::test_no_contextual_actions() is flaky

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  I’m seeing intermittent failures in the following unit test when run
  by the system-apps jenkins instance when building packages:

  FAIL!  : QmlTests::UbuntuWebView02::test_no_contextual_actions() Compared 
values are not the same
  Actual   (): 
  Expected (): null
  Loc: [/[…]/tests/unittests/qml/tst_UbuntuWebView02.qml(98)]

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

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


[Touch-packages] [Bug 1633528] Re: QmlTests::UbuntuWebView02::test_no_contextual_actions() is flaky

2016-10-14 Thread Olivier Tilloy
** Changed in: webbrowser-app (Ubuntu)
   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/1633528

Title:
  QmlTests::UbuntuWebView02::test_no_contextual_actions() is flaky

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  I’m seeing intermittent failures in the following unit test when run
  by the system-apps jenkins instance when building packages:

  FAIL!  : QmlTests::UbuntuWebView02::test_no_contextual_actions() Compared 
values are not the same
  Actual   (): 
  Expected (): null
  Loc: [/[…]/tests/unittests/qml/tst_UbuntuWebView02.qml(98)]

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-10-14 Thread Alberto Salvia Novella
** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: nouveau via
   https://bugs.freedesktop.org/show_bug.cgi?id=92438
   Importance: Unknown
   Status: Unknown

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

** Changed in: qtmir (Ubuntu)
   Importance: Medium => Critical

** Changed in: libdrm (Ubuntu)
   Status: Confirmed => Triaged

-- 
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 Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
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 1310186] Re: mediascanner prevents unmounting usb device

2016-10-14 Thread Alberto Salvia Novella
** Changed in: mediascanner2 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  mediascanner prevents unmounting usb device

Status in mediascanner2 package in Ubuntu:
  Triaged

Bug description:
  Trying to unmount a block device I just mounted, I get the following
  error (sorry for not resetting the locale. It says "Device is busy"):

  :~$ sudo umount /media/tkluck/tjk-backup 
  umount2: Apparaat of hulpbron is bezig
  umount: /media/tkluck/tjk-backup: apparaat is bezig
  (Welke processen het apparaat gebruiken kan mogelijk
   gevonden worden met behulp van lsof(8) of fuser(1).)
  umount2: Apparaat of hulpbron is bezig

  I get the same error in a dialog window when trying to unmount from
  the file manager.

  Using lsof shows that the media-scanner daemon is the culprit:

  tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup 
  COMMANDPID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  mediascan 2898 tkluck   16r   DIR  252,3   2498562 
/media/tkluck/tjk-backup
  mediascan 2898 tkluck   17r   DIR  252,3 4096 50855937 
  mediascan 2898 tkluck   18r   DIR  252,3 4096 39080372 
  mediascan 2898 tkluck   19r   DIR  252,312288 39080513 
  mediascan 2898 tkluck   20r   DIR  252,320480 39080525 
  mediascan 2898 tkluck   21r   DIR  252,3 4096 46792990 
  mediascan 2898 tkluck   22r   DIR  252,3 4096 46792991 
  mediascan 2898 tkluck   23r   DIR  252,316384 46793749 
  mediascan 2898 tkluck   24r   DIR  252,3 4096 47317994 
  mediascan 2898 tkluck   25r   DIR  252,3 4096 47317997 
  mediascan 2898 tkluck   26r   DIR  252,3 4096 47317999 

  Sending it

  sudo kill -9 2898

  solved this for me.

  This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to
  solve this "once and for all" (which has no other impact since I do
  not use Unity).

  My guess is that the scan usually finishes quickly after mounting. But
  because this particular drive contains a big filetree, it doesn't,
  resulting in the issue.

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

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


[Touch-packages] [Bug 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list

2016-10-14 Thread Treviño
** Also affects: qmenumodel (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-settings-components (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: Fix Committed => In Progress

** Changed in: ubuntu-settings-components (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: qmenumodel (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Changed in: ubuntu-settings-components (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Clicking a date in the new calendar doesn't change the indicator's
  appointment list

Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Now that we've got a calendar in indicator-datetime in Unity 8, there
  are a few features from Unity 7 that we should decide if/how we're
  goint to handle in Unity 8.

  * Show Week Numbers
  * Highlight days of the month that include appointments
  * Unity tells indicator-datetime what calendar day has been clicked so that 
the "upcoming appointments" list can be adjusted accordingly

  These are currently implemented as fields in a GAction state
  dictionary and documented in http://bazaar.launchpad.net/~indicator-
  applet-developers/indicator-datetime/trunk.15.10/view/head:/README ...
  however that was all done for Unity 7, and IMO it would make sense to
  improve the unity<->indicator API here so that Unity8 doesn't have to
  deal with key-variant map GAction states.

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

-- 
Mailing list: https://launchpad.net/~touch-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-14 Thread Titantux
Hi, 2 days a go I've updated from 16.04.4 to 16.10 and problem still, as
@Dea1993 said got that version, but noticed than restarting just the nm-
applet, bring to me all wifi networks again.. as on
https://bugs.launchpad.net/oem-priority/+bug/1574347/comments/79

killall nm-applet && nm-applet &

-- 
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 1610241] Re: Failed upgrade from 14.04 to 16.04 : package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit

2016-10-14 Thread Alberto Salvia Novella
** Changed in: virtuoso-opensource (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: sysvinit (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: update-manager (Ubuntu)
   Status: In Progress => Invalid

** Changed in: virtuoso-opensource (Ubuntu)
   Status: In Progress => Triaged

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

** Changed in: hundredpapercuts
 Assignee: abner (a75) => (unassigned)

** Changed in: sysvinit (Ubuntu)
 Assignee: abner (a75) => (unassigned)

** Changed in: update-manager (Ubuntu)
 Assignee: abner (a75) => (unassigned)

** Changed in: virtuoso-opensource (Ubuntu)
 Assignee: abner (a75) => (unassigned)

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

Title:
  Failed upgrade from 14.04 to 16.04 : package sysv-rc
  2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed
  post-installation script returned error exit status 1

Status in One Hundred Papercuts:
  Triaged
Status in sysvinit package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in virtuoso-opensource package in Ubuntu:
  Triaged

Bug description:
  This happened on an computer that was installed many years ago, and upgraded 
on each LTS version.
  When upgrading from 14.04 to 16.04.1, it started telling me that something 
wrong happened with sysv-rc, then that there were some "initscripts dependency 
problems" making it "leaving unconfigured".
  Then many packages were reported as incorrectly setup : procps, udev, 
initramfs, keyboard-configuration, console-setup, plymouth, cups, upower, 
gnome-session, gnome-shell, udisk, gvfs, software-center, mountall, upstart, 
etc.

  After reading the log files, I found out that this was caused by insserv, 
reporting "insserv rejected the script header", coming from package 
virtuoso-nepomuk having an incorrect header in /etc/init.d : "missing end of 
LSB comment", "missing LSB tags and overrides".
  This package http://packages.ubuntu.com/precise/database/virtuoso-nepomuk was 
existing on 12.04, but was removed afterwards.
  The latest version 6.1.4+dfsg1-0ubuntu1 indeed contains an incorrect header 
in /etc/init.d/virtuoso-nepomuk.

  I managed to solve the issue by adding the "END INIT INFO" in this
  file, like below :

  #! /bin/sh
  #
  # virtuoso  OpenLink Virtuoso Open-Source Edition
  #
  #   Written by OpenLink Virtuoso Maintainer
  #   
  #
  # Version:  @(#)virtuoso  6.1.4  25-Mar-2011
vos.ad...@openlinksw.com
  #

  ### BEGIN INIT INFO
  # Provides: virtuoso
  # Required-Start:   $syslog
  # Required-Stop:$syslog
  # Default-Start:2 3 4 5
  # Default-Stop: 0 1 6
  # Short-Description:Start Virtuoso database server on startup
  # Description:  Start and stop the primary instance of Virtuoso 
running
  #   in /var/lib/virtuoso/db/. The first time this runs, it loads the
  #   Conductor administrative package.
  ### END INIT INFO

  Then a "sudo apt-get upgrade" allowed me to finish the installation
  successfully.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Aug  5 11:21:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2010-05-22 (2267 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (0 days ago)

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

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


[Touch-packages] [Bug 1632418] Re: Network Manager doesn't look for wifi after resume until restarted

2016-10-14 Thread Alberto Salvia Novella
It happens to me even by disabling wifi and re-enabling it again.

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

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

Title:
  Network Manager doesn't look for wifi after resume until restarted

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Once upon the time Network Manager doesn't scan to connect the
  networks until restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.1
  Uname: Linux 4.8.0-040800rc8-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 11 08:12:47 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-20 (509 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.32.254 dev wlp3s0  proto static  metric 600 
   192.168.32.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.32.245  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (170 days ago)
  modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [deleted]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-03T14:41:30.662323
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
~\_/~   a9c0eb9d-4df3-4769-95a6-b910d563d526  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   vpn0 tun   unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1633528] [NEW] QmlTests::UbuntuWebView02::test_no_contextual_actions() is flaky

2016-10-14 Thread Olivier Tilloy
Public bug reported:

I’m seeing intermittent failures in the following unit test when run by
the system-apps jenkins instance when building packages:

FAIL!  : QmlTests::UbuntuWebView02::test_no_contextual_actions() Compared 
values are not the same
Actual   (): 
Expected (): null
Loc: [/[…]/tests/unittests/qml/tst_UbuntuWebView02.qml(98)]

** Affects: webbrowser-app (Ubuntu)
 Importance: Medium
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged


** Tags: unittests

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Triaged

** Tags added: unittests

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

Title:
  QmlTests::UbuntuWebView02::test_no_contextual_actions() is flaky

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  I’m seeing intermittent failures in the following unit test when run
  by the system-apps jenkins instance when building packages:

  FAIL!  : QmlTests::UbuntuWebView02::test_no_contextual_actions() Compared 
values are not the same
  Actual   (): 
  Expected (): null
  Loc: [/[…]/tests/unittests/qml/tst_UbuntuWebView02.qml(98)]

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

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


[Touch-packages] [Bug 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list

2016-10-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~3v1n0/qmenumodel/variant-string-parser

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

Title:
  Clicking a date in the new calendar doesn't change the indicator's
  appointment list

Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Now that we've got a calendar in indicator-datetime in Unity 8, there
  are a few features from Unity 7 that we should decide if/how we're
  goint to handle in Unity 8.

  * Show Week Numbers
  * Highlight days of the month that include appointments
  * Unity tells indicator-datetime what calendar day has been clicked so that 
the "upcoming appointments" list can be adjusted accordingly

  These are currently implemented as fields in a GAction state
  dictionary and documented in http://bazaar.launchpad.net/~indicator-
  applet-developers/indicator-datetime/trunk.15.10/view/head:/README ...
  however that was all done for Unity 7, and IMO it would make sense to
  improve the unity<->indicator API here so that Unity8 doesn't have to
  deal with key-variant map GAction states.

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

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


[Touch-packages] [Bug 1633520] [NEW] Support dbus runtime relocation

2016-10-14 Thread Michael Terry
Public bug reported:

For example, when running in a snap.

I ran into this while testing a unity8 desktop session snap.  Session
services were being dbus-activated, but dbus was running the hardcoded
paths in the session desktop files.  Which weren't pointed into the
snap.

DBus has support for relocating those paths, but it only does so on
Windows.

I've added a patch to support $DBUS_ROOT on Unix and relocate paths as
needed.  I've linked the upstream bug here.  We may want to consider
patching Ubuntu while we wait for it to land upstream.

I've attached the patch here too.

** Affects: dbus
 Importance: Unknown
 Status: Unknown

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

** Patch added: 
"0001-Support-runtime-relocation-in-Unix-with-the-DBUS_ROO.patch"
   
https://bugs.launchpad.net/bugs/1633520/+attachment/4761121/+files/0001-Support-runtime-relocation-in-Unix-with-the-DBUS_ROO.patch

** Bug watch added: freedesktop.org Bugzilla #98260
   https://bugs.freedesktop.org/show_bug.cgi?id=98260

** Also affects: dbus via
   https://bugs.freedesktop.org/show_bug.cgi?id=98260
   Importance: Unknown
   Status: Unknown

** Description changed:

  For example, when running in a snap.
  
  I ran into this while testing a unity8 desktop session snap.  Session
  services were being dbus-activated, but dbus was running the hardcoded
  paths in the session desktop files.  Which weren't pointed into the
  snap.
  
  DBus has support for relocating those paths, but it only does so on
  Windows.
  
  I've added a patch to support $DBUS_ROOT on Unix and relocate paths as
  needed.  I've linked the upstream bug here.  We may want to consider
- patch Ubuntu while we wait for it to land upstream.
+ patching Ubuntu while we wait for it to land upstream.
  
  I've attached the patch here too.

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

Title:
  Support dbus runtime relocation

Status in D-Bus:
  Unknown
Status in dbus package in Ubuntu:
  New

Bug description:
  For example, when running in a snap.

  I ran into this while testing a unity8 desktop session snap.  Session
  services were being dbus-activated, but dbus was running the hardcoded
  paths in the session desktop files.  Which weren't pointed into the
  snap.

  DBus has support for relocating those paths, but it only does so on
  Windows.

  I've added a patch to support $DBUS_ROOT on Unix and relocate paths as
  needed.  I've linked the upstream bug here.  We may want to consider
  patching Ubuntu while we wait for it to land upstream.

  I've attached the patch here too.

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

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


[Touch-packages] [Bug 1574333] Re: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2)

2016-10-14 Thread Nick Buonanno
I'll back up Tjalling's work-around. I already had my boot partition on
a separate non-LVM partition at the front of my drive. My system started
booting normally on 4.4.0-38, and continues to do so on 4.4.0-42.

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

Title:
  LVM-based filesystem does not boot with kernel 4.4 (but works with
  4.2)

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I‘ve updated my home-made NAS from wily to xenial and it stopped
  booting.

  Selecting the 4.2 kernel on the grub menu makes it work again.

  The working kernel is 4.2.0-35-generic

  The failing kernel is 4.4.0-21-generic.

  When the booting sequence freezes, I can have a terminal with the
  following text :

   lvmetad is not active yet, using direct activation during sysinit
  Scannig for Btrfs flesystems
  _

  Actually my set-up is lvm based, and the correponding lines of the
  output of a mount command are

  /dev/mapper/clio-root on / type btrfs 
(rw,relatime,nospace_cache,subvolid=256,subvol=/@)
  /dev/mapper/clio-root on /mnt/clio-root type btrfs 
(rw,relatime,nospace_cache,subvolid=5,subvol=/)
  /dev/mapper/clio-root on /home type btrfs 
(rw,relatime,nospace_cache,subvolid=257,subvol=/@home)

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

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


[Touch-packages] [Bug 1633510] Re: QmlTests::HistoryView::test_delete_multiple_domains() is flaky

2016-10-14 Thread Olivier Tilloy
** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Triaged

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Tags added: unittests

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

Title:
  QmlTests::HistoryView::test_delete_multiple_domains() is flaky

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  I’m seeing intermittent failures in the following unit test when run
  by the system-apps jenkins instance when building packages:

  FAIL!  : QmlTests::HistoryView::test_delete_multiple_domains() property 
selectMode
  Actual   (): true
  Expected (): false
  Loc: [/[…]/tests/unittests/qml/tst_HistoryView.qml(153)]

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

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


[Touch-packages] [Bug 1633510] [NEW] QmlTests::HistoryView::test_delete_multiple_domains() is flaky

2016-10-14 Thread Olivier Tilloy
Public bug reported:

I’m seeing intermittent failures in the following unit test when run by
the system-apps jenkins instance when building packages:

FAIL!  : QmlTests::HistoryView::test_delete_multiple_domains() property 
selectMode
Actual   (): true
Expected (): false
Loc: [/[…]/tests/unittests/qml/tst_HistoryView.qml(153)]

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

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

Title:
  QmlTests::HistoryView::test_delete_multiple_domains() is flaky

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  I’m seeing intermittent failures in the following unit test when run
  by the system-apps jenkins instance when building packages:

  FAIL!  : QmlTests::HistoryView::test_delete_multiple_domains() property 
selectMode
  Actual   (): true
  Expected (): false
  Loc: [/[…]/tests/unittests/qml/tst_HistoryView.qml(153)]

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

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


[Touch-packages] [Bug 1633186] Re: Unity 8 crashes every 5 seconds

2016-10-14 Thread Ads20000
Removed fprint, Unity 8 works fine now (typing from it atm!), must be a
problem with using a fingerprint reader (or fprint, in particular) and
Unity 8.

** Summary changed:

- Unity 8 crashes every 5 seconds
+ When using fprint, Unity 8 crashes every 5 seconds and/or there is a cursor 
freeze

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

Title:
  When using fprint, Unity 8 crashes every 5 seconds and/or there is a
  cursor freeze

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

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

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


[Touch-packages] [Bug 1632620] Re: No audio from webbrowser-app in 16.10

2016-10-14 Thread Olivier Tilloy
Note for users affected by this bug: until the fix is SRU’d (work in
progress), you can try out the webbrowser-app snap (from the edge
channel of the store).

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

Title:
  No audio from webbrowser-app in 16.10

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  [Test case]
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube.
  Play a video.
  Notice there is no sound. Nor does the browser show in the sound menu/panel.

  TLDR: this is an apparmor confinement issue: on yakkety pulse audio
  needs write access to /{run,dev}/shm/pulse-shm*, which is being denied
  by the audio and microphone policy groups. The fix consists in
  punching an additional hole in the generated apparmor profile for
  webbrowser-app.

  [Regression potential]
  Low. As the fix consists in weakening the apparmor profile for 
webbrowser-app, the only concerns should be security-related. The change was 
ack’d by Jamie Strandboge (see comment #11 in this bug report).
  It is not anticipated that this change would make the browser’s functionality 
regress.

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

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


[Touch-packages] [Bug 1633186] Re: Unity 8 crashes every 5 seconds

2016-10-14 Thread Ads20000
** Attachment added: 
"_usr_lib_x86_64-linux-gnu_policykit-unity8_policykit-agent.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+attachment/4761107/+files/_usr_lib_x86_64-linux-gnu_policykit-unity8_policykit-agent.1000.crash

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

Title:
  When using fprint, Unity 8 crashes every 5 seconds and/or there is a
  cursor freeze

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

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

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


[Touch-packages] [Bug 1633186] Re: Unity 8 crashes every 5 seconds

2016-10-14 Thread Ads20000
** Attachment added: "_usr_bin_unity8-dash.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+attachment/4761106/+files/_usr_bin_unity8-dash.1000.crash

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

Title:
  When using fprint, Unity 8 crashes every 5 seconds and/or there is a
  cursor freeze

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

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

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


[Touch-packages] [Bug 1633186] Re: Unity 8 crashes every 5 seconds

2016-10-14 Thread Ads20000
Oh, is it safe to upload these crash files and do you even want them?

** Attachment removed: "_usr_bin_unity8.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+attachment/4761105/+files/_usr_bin_unity8.1000.crash

** Attachment removed: "_usr_bin_unity8-dash.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+attachment/4761106/+files/_usr_bin_unity8-dash.1000.crash

** Attachment removed: 
"_usr_lib_x86_64-linux-gnu_policykit-unity8_policykit-agent.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+attachment/4761107/+files/_usr_lib_x86_64-linux-gnu_policykit-unity8_policykit-agent.1000.crash

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

Title:
  When using fprint, Unity 8 crashes every 5 seconds and/or there is a
  cursor freeze

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

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

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


[Touch-packages] [Bug 1633186] Re: Unity 8 crashes every 5 seconds

2016-10-14 Thread Ads20000
OK, this time I wasn't able to get the cursor to unfreeze and, when I
switched to tty1 and switched back to tty7, I was left with the
'/dev/sda1: clean...' text which I briefly see before LightDM loads when
I boot Ubuntu, Unity 8 had gone.

Attaching crash files...

** Attachment added: "_usr_bin_unity8.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633186/+attachment/4761105/+files/_usr_bin_unity8.1000.crash

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

Title:
  When using fprint, Unity 8 crashes every 5 seconds and/or there is a
  cursor freeze

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

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

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


[Touch-packages] [Bug 1633499] [NEW] [SRU] Update to 9.20 in Trusty

2016-10-14 Thread Amr Ibrahim
Public bug reported:

https://git.libav.org/?p=libav.git;a=shortlog;h=refs/heads/release/9

version 9.20:
 - avcodec: bump micro version

version 9.19:
 - h264: deMpegEncContextize
 - h264: remove silly macros
 - mpegvideo: split ff_draw_horiz_band().
 - error_resilience: add required headers.
 - error_resilience: decouple ER from MpegEncContext
 - h264: remove a pointless if()
 - h264: simplify calls to ff_er_add_slice().
 - tls: Use the right return value for breaking out due to the interrupt 
callback
 - rtmpcrypt: Do the xtea decryption in little endian mode

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


** Tags: trusty

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

Title:
  [SRU] Update to 9.20 in Trusty

Status in libav package in Ubuntu:
  New

Bug description:
  https://git.libav.org/?p=libav.git;a=shortlog;h=refs/heads/release/9

  version 9.20:
   - avcodec: bump micro version

  version 9.19:
   - h264: deMpegEncContextize
   - h264: remove silly macros
   - mpegvideo: split ff_draw_horiz_band().
   - error_resilience: add required headers.
   - error_resilience: decouple ER from MpegEncContext
   - h264: remove a pointless if()
   - h264: simplify calls to ff_er_add_slice().
   - tls: Use the right return value for breaking out due to the interrupt 
callback
   - rtmpcrypt: Do the xtea decryption in little endian mode

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

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


[Touch-packages] [Bug 1633496] [NEW] boot screen give this

2016-10-14 Thread ibrahim
Public bug reported:

drm:cpt_set_fifo_underrun_reporting] ERROR uncleared pch fifo underrun
on pch transcoder A [drm:cpt_serr_int_handler] ERROR PCH transcoder A
FIFO underrun

during startup it gives this error and continue working . i can use
ubuntu but whats the reason behind this error ?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Oct 14 17:11:27 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3902]
 NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GF108M [GeForce GT 635M] [17aa:3902]
InstallationDate: Installed on 2016-10-07 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO IdeaPad Z580
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=fc2fc1f1-7700-4c16-b83d-ed23d95063a2 ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 5FCN91WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo
dmi.board.vendor: LENOVO
dmi.board.version: 3194WIN8 STD SGL
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z580
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr5FCN91WW:bd09/20/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoZ580:
dmi.product.name: IdeaPad Z580
dmi.product.version: Lenovo Z580
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Oct 14 17:02:15 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: amd64 apport-bug compiz-0.9 false-gpu-hang freeze ubuntu xenial

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

Title:
  boot screen give this

Status in xorg package in Ubuntu:
  New

Bug description:
  drm:cpt_set_fifo_underrun_reporting] ERROR uncleared pch fifo underrun
  on pch transcoder A [drm:cpt_serr_int_handler] ERROR PCH transcoder A
  FIFO underrun

  during startup it gives this error and continue working . i can use
  ubuntu but whats the reason behind this error ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No 

[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

2016-10-14 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  New

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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


[Touch-packages] [Bug 1622041] Re: Mobile network denied

2016-10-14 Thread Pete Woods
** Also affects: ofono (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Mobile network denied

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1632968] Re: Unity 8 does not start in Virtual Box

2016-10-14 Thread Michał Sawicz
Unfortunately VirtualBox is currently incompatible with Mir, the only VM
that can run Unity8 is KVM/QEMU and possibly VMWare Player at the
moment, AFAICT.

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

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

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

** Summary changed:

- Unity 8 does not start in Virtual Box 
+ Mir does not start in VirtualBox

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

Title:
  Mir does not start in VirtualBox

Status in Mir:
  New
Status in Virtualbox:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  If I want to start Unity 8 in my virtual box /VM Yakketi, Unity does
  not start at all, it goes straight back to the start screen

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

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


[Touch-packages] [Bug 1633186] Re: Unity 8 crashes every 5 seconds

2016-10-14 Thread Michał Sawicz
Do you not have .crash files in /var/crash? Can you please clear that
directory and try starting unity8 again.

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => 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/1633186

Title:
  Unity 8 crashes every 5 seconds

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I got some Bugsplat screens come up but they didn't bring up a
  Launchpad window so I'm gonna report it here too.

  I tried the Unity 8 session in Ubuntu 16.10 and when I log in I can't
  move the mouse (maybe this should be filed as a separate bug?), once I
  hit the keyboard (I used Alt+Tab) I am able to move the mouse but the
  screen goes black after five seconds and then comes back up after
  around 2.5 seconds with the scopes and indicator tray visibly
  reloading. After five seconds, the screen goes black again, comes up
  after 2.5 seconds, goes black after five seconds... seemingly forever.

  I noticed that my fingerprint scanner (this is a Lenovo ThinkPad X201)
  had its light on so it was wanting to receive a fingerprint. Trying to
  scan my fingerprint didn't make a difference to the situation. I use
  fprint from this PPA
  (https://launchpad.net/~fingerprint/+archive/ubuntu/fprint) to get the
  scanner to work, I don't think the official repository version of
  fprint supports my fingerprint reader. I will remove the package and
  see if this changes the situation and will edit/comment once I've done
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 19:36:47 2016
  InstallationDate: Installed on 2016-06-18 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (2 days ago)

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

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


[Touch-packages] [Bug 1384952] Re: USB Soundcard no microphone (input) device

2016-10-14 Thread Piotr Pałek
I have the same issue and it still isn't working :(

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

Title:
  USB Soundcard no microphone (input) device

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My Asus Xonar U7 Echelon External sound device working without input/capture 
device.
  No input device , Nothing recording with my usb soundcard. 

  ~$ arecord -l
   List of CAPTURE Hardware Devices 
  card 1: Ed [Xonar U7 Echelon Ed.], device 1: USB Audio [USB Audio #1]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ~$ lsusb
  Bus 002 Device 002: ID 1043:85c1 iCreate Technologies Corp.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.17.1-031701-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alper  2249 F pulseaudio
   /dev/snd/pcmC1D0p:   alper  2249 F...m pulseaudio
   /dev/snd/controlC1:  alper  2249 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 24 00:46:11 2014
  InstallationDate: Installed on 2014-10-07 (16 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G46 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.2:bd02/04/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7693
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-10-23T19:38:42.156766

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

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


  1   2   >