[Touch-packages] [Bug 1634353] [NEW] file index is not responding

[ferguson apladey]

Public bug reported:

file index is not responding

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Oct 18 05:43:18 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.6, 4.4.0-43-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-25-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7640G] [103c:1984]
InstallationDate: Installed on 2016-07-01 (108 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-25-generic.efi.signed 
root=UUID=7eb94228-e677-4c99-944a-8d239a78479f ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1984
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 01.13
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097611405E0620180:rvnHewlett-Packard:rn1984:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 17 Notebook PC
dmi.product.version: 097611405E0620180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Tue Oct 18 05:17:29 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug third-party-packages ubuntu yakkety

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

Title:
  file index is not responding

Status in xorg package in Ubuntu:
  New

Bug description:
  file index is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Oct 18 05:43:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.4.0-43-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-25-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7640G] [103c:1984]
  InstallationDate: Installed on 2016-07-01 (108 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-25-generic.efi.signed 
root=UUID=7eb94228-e677-4c99-944a-8d239a78479f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1633274] Re: Systemd-networkd crashes with core dump

[Martin Pitt]

Thanks for forwarding this upstream! I cherry-picked the patch.

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

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

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

** Description changed:

  Systemd-networkd crashes with core dump, this happends in Yakkety and
  Xenial.
  
  The latest patch that was commited to Xenial-updates and Yakkety is the one 
that broke this.
  Everything works just fine with Xenial without latest update or Yakkety Beta 
2.
  
  The log entries i see is:
  Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at 
../src/network/networkd-netdev-tunnel.c:210, function 
netdev_vti_fill_message_key(). Aborting.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process 
exited, code=dumped, status=6/ABRT
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'core-dump'.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
  Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request 
repeated too quickly.
  Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service.
  Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network 
to be Configured.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: 
Job systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'start-limit-hit'.
  
+ 
+ SRU TEST CASE: See 
https://github.com/systemd/systemd/issues/4371#issuecomment-253697041
+ 
+ Regression potential: Very low, this just fixes an obvious type cast in
+ networkd and touches no code that applies to other network interfaces.
+ The service manager (pid 1) and other tools are entirely unaffected.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  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 02:39:05 2016
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
-  LANGUAGE=en_US:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
   Status: Fix Committed

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

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

** Changed in: systemd (Ubuntu Zesty)
   Status: New => Fix Committed

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

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

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

Title:
  Systemd-networkd crashes with core dump

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  Systemd-networkd crashes with core dump, this happends in Yakkety and
  Xenial.

  The latest patch that was commited to Xenial-updates and Yakkety is the one 
that broke this.
  Everything works just fine with Xenial without latest update or Yakkety Beta 
2.

  The log entries i see is:
  Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at 
../src/network/networkd-netdev-tunnel.c:210, function 
netdev_vti_fill_message_key(). 

[Touch-packages] [Bug 1632575] Re: systemd starts two copies of ntp at boot time

[Marius Gedminas]

Unfortunately there were more unattended upgrades that require a reboot
since I filed this bug, so systemd-analyze can't see what happened any
more.

As for systemd service files, I believe ntp has none. systemctl status
ntp says

   Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)

which AFAIU means it's still using legacy sysvinit scripts.

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

Title:
  systemd starts two copies of ntp at boot time

Status in ntp package in Ubuntu:
  Triaged

Bug description:
  My system monitoring check noticed a stale /var/run/ntpd.pid pidfile
  on a xenial machine that rebooted at 2 AM after unattended upgrades.
  ntpd itself was running, but with a different pid.

  Digging through journalctl I can see

  Oct 12 02:00:11 xenial64 ntp[681]:  * Starting NTP server ntpd
  Oct 12 02:00:11 xenial64 systemd[1]: Started Getty on tty1.
  Oct 12 02:00:11 xenial64 systemd[1]: Reached target Login Prompts.
  Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 run-parts[760]: run-parts: executing 
/etc/redis/redis-server.post-up.d/00_example
  Oct 12 02:00:11 xenial64 systemd[1]: Starting LSB: Start NTP daemon...
  Oct 12 02:00:11 xenial64 ntpd[719]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
  Oct 12 02:00:11 xenial64 ntpd[719]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
  Oct 12 02:00:11 xenial64 ntp[770]:  * Starting NTP server ntpd
  Oct 12 02:00:11 xenial64 ntpd[778]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
  Oct 12 02:00:11 xenial64 ntpd[778]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
  Oct 12 02:00:11 xenial64 ntp[770]:...done.
  Oct 12 02:00:11 xenial64 systemd[1]: Started LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 systemd[1]: Started Advanced key-value store.
  Oct 12 02:00:11 xenial64 ntpd[773]: proto: precision = 0.077 usec (-24)
  Oct 12 02:00:11 xenial64 ntpd[780]: proto: precision = 0.076 usec (-24)
  Oct 12 02:00:11 xenial64 ntpd[780]: unable to bind to wildcard address :: 
- another process may be running - EXITING
  Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 0 v6wildcard 
[::]:123
  Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 1 v4wildcard 
0.0.0.0:123

  As you can see, for some reason systemd starts ntpd twice, so there's
  a race to take over the socket, and a race to take over the pidfile.
  ntpd[773] gets the socket, ntpd[780] gets the pidfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.3
  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: Wed Oct 12 06:18:29 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Expired

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

"Reached target Shutdown"

  followed by

"systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

"connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1578501] Re: Can't add network printer

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Can't add network printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04
  CUPS: «server-error-internal-error» when I adding a network HP Printer.
  Screen in attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: system-config-printer-gnome 1.5.7+20160212-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  5 08:54:12 2016
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationDate: Installed on 2015-01-22 (468 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.5
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard p6-2412er
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bfe27f40-1b02-4e97-9ce9-5ba926a696b2 ro quiet splash vt.handoff=7
  SourcePackage: system-config-printer
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (0 days ago)
  dmi.bios.date: 06/25/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.19
  dmi.board.name: 2ADA
  dmi.board.vendor: Foxconn
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: RUA30800W0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.19:bd06/25/2014:svnHewlett-Packard:pnp6-2412er:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6-2412er
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1634061] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  package failed when update to ubuntu mate 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: avahi-dnsconfd 0.6.32-1ubuntu1
  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: Mon Oct 17 15:04:07 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-10-06 (11 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago)

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

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

[Touch-packages] [Bug 1634234] Re: apt-key leaves files in /dev open after exit

[Scott Moser]

curtin is also busted in cases where the user provides a 'keyid', or
even a 'key' (data inline).

It seems we can/should probably make add_apt_key_raw write data to
/etc/apt/trusted.gpg.d ourselves rather than using apt-key.


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

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

Title:
  apt-key leaves files in /dev open after exit

Status in apt package in Ubuntu:
  New
Status in curtin package in Ubuntu:
  New
Status in gnupg2 package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
  /dev/urandom open after exiting. Here's a procedure to replicate the
  problem:

  1. Install Ubuntu 16.10. (I used MAAS for this task.)
  2. Install the "lsof" package (which is not installed by default).
  3. Type "lsof | grep dev" to see open files.
  4. Type "sudo apt-key adv --recv-keys --keyserver 
hkp://keyserver.ubuntu.com:80 1FEADE10;"
  5. Type "lsof | grep dev" again.
  6. Compare the output of the two "lsof" commands.

  I'm attaching two files, before.txt and after.txt, that show the
  before and after results from "lsof | grep dev" in this scenario. Note
  that the /dev/null and /dev/urandom files are both open after apt-key
  is run, but not before. This problem does NOT occur with Ubuntu 16.04.

  This problem is preventing us (the server certification team) from
  importing keys in a custom MAAS preseed script; after installing
  successfully, umounting the installed image fails because of the open
  files on /dev.

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

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

[Touch-packages] [Bug 1634234] Re: apt-key leaves files in /dev open after exit

[Scott Moser]

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

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

Title:
  apt-key leaves files in /dev open after exit

Status in apt package in Ubuntu:
  New
Status in curtin package in Ubuntu:
  New
Status in gnupg2 package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
  /dev/urandom open after exiting. Here's a procedure to replicate the
  problem:

  1. Install Ubuntu 16.10. (I used MAAS for this task.)
  2. Install the "lsof" package (which is not installed by default).
  3. Type "lsof | grep dev" to see open files.
  4. Type "sudo apt-key adv --recv-keys --keyserver 
hkp://keyserver.ubuntu.com:80 1FEADE10;"
  5. Type "lsof | grep dev" again.
  6. Compare the output of the two "lsof" commands.

  I'm attaching two files, before.txt and after.txt, that show the
  before and after results from "lsof | grep dev" in this scenario. Note
  that the /dev/null and /dev/urandom files are both open after apt-key
  is run, but not before. This problem does NOT occur with Ubuntu 16.04.

  This problem is preventing us (the server certification team) from
  importing keys in a custom MAAS preseed script; after installing
  successfully, umounting the installed image fails because of the open
  files on /dev.

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

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

[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[Jared Fernandez]

** Tags added: yakkety

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

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   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
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  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/iptables/+bug/1556419/+subscriptions

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

[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[Launchpad Bug Tracker]

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

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

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

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   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
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  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/iptables/+bug/1556419/+subscriptions

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

[Touch-packages] [Bug 1342123] Re: evolution-calendar-factory always running with high memory usage

[Sergio]

maybe it's possible to remove it completely?

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

Title:
  evolution-calendar-factory always running with high memory usage

Status in Canonical System Image:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  At boot the process is using over 100MB on my mako (build 129)
  I sync'd a fairly large set of calendar events from google previously

  Does this process need to be running all the time?
  Can we streamline it to not read so much of the data set, which it appears to 
be doing?

  With no calendar entries (i.e. removing 
.local/share/evolution/xxx/calendar.ics) the process still uses over 30MB
  (looking at RSS with  ps aux --sort -rss )

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

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

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

[Bug Watch Updater]

** Changed in: ifupdown (Debian)
   Status: Unknown => New

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

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

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed
Status in ifupdown package in Debian:
  New

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

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

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

  [Impact]

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

  [Test Case]

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

  [Regression potential]

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

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

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

[Touch-packages] [Bug 1634234] Re: apt-key leaves files in /dev open after exit

[David Kalnischkies]

That isn't directly the fault of apt-key. It uses gpg which in its >=
2.0 versions has split its operations into a multitude of daemons for
security reasons. The daemons should be terminating themselves a few
seconds after the directory they operate in disappears. That is at least
the case for gpg-agent, but "a few seconds" is obviously too slow if you
are in a hurry, so apt-key tries to kill it via gpgconf --kill gpg-agent
(which isn't supported in all gpg version, but at least in the one in
ubuntu I hope). The manpage tells me that this isn't supported for
dirmngr through, which is the daemon left in your case, so solving that
from the apt-key side isn't exactly easy (short of implementing a sub-
subprocess supervisor in shell script…) so I would feel tempted to
declare that the problem of gpg and invalid for apt-key.

That said, your apt-key command is bad and should be replaced. Getting
keys from a keyserver is hopelessly insecure (it is better with recent
gpg versions) but still: Your use of a short-keyid screams security
problem due to easy collisions and hkp is a cleartext protocol so just
asking for MITM (and at least older gpg versions do no checks at all on
the received key(s)).

I guess the simplest & best solution is to ship the key in your preseed
script and drop it with an appropriate name (ending in .gpg) in
/etc/apt/trusted.gpg.d/  – as a bonus, your system will not need gnupg
installed (at least in terms of apt), gpgv will be enough.

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

Title:
  apt-key leaves files in /dev open after exit

Status in apt package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
  /dev/urandom open after exiting. Here's a procedure to replicate the
  problem:

  1. Install Ubuntu 16.10. (I used MAAS for this task.)
  2. Install the "lsof" package (which is not installed by default).
  3. Type "lsof | grep dev" to see open files.
  4. Type "sudo apt-key adv --recv-keys --keyserver 
hkp://keyserver.ubuntu.com:80 1FEADE10;"
  5. Type "lsof | grep dev" again.
  6. Compare the output of the two "lsof" commands.

  I'm attaching two files, before.txt and after.txt, that show the
  before and after results from "lsof | grep dev" in this scenario. Note
  that the /dev/null and /dev/urandom files are both open after apt-key
  is run, but not before. This problem does NOT occur with Ubuntu 16.04.

  This problem is preventing us (the server certification team) from
  importing keys in a custom MAAS preseed script; after installing
  successfully, umounting the installed image fails because of the open
  files on /dev.

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

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

[Touch-packages] [Bug 1595238] Re: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/gl

[Launchpad Bug Tracker]

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

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

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

Title:
  Unity 8 Desktop Preview System Settings do not work on nouveau
  [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file
  ../../../src/ubuntumirclient/glcontext.cpp, line 239]

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When I try to open System Settings, the Ubuntu logo keeps turning and nothing 
happens.
  I installed unity8-desktop-session-mir on my Xenial 16.04.1 Desktop where I 
use NVIDIA driver GF108[GeForce GT 530]. I also created a new user account with 
English (US) language settings, because Unity 8 does not work well when I use 
my own account with my language settings.

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

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

[Touch-packages] [Bug 1595238] Re: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/gl

[Launchpad Bug Tracker]

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

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

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

Title:
  Unity 8 Desktop Preview System Settings do not work on nouveau
  [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file
  ../../../src/ubuntumirclient/glcontext.cpp, line 239]

Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When I try to open System Settings, the Ubuntu logo keeps turning and nothing 
happens.
  I installed unity8-desktop-session-mir on my Xenial 16.04.1 Desktop where I 
use NVIDIA driver GF108[GeForce GT 530]. I also created a new user account with 
English (US) language settings, because Unity 8 does not work well when I use 
my own account with my language settings.

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

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

[Touch-packages] [Bug 1622157] Re: swiping to fast forward/backward

[krusty]

** Summary changed:

- swiping to move forward/backward
+ swiping to fast forward/backward

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

Title:
  swiping to fast forward/backward

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  currently you have to tap on the video/timeline bar to get to a
  later/earlier point in a video. it would be a nicer user experience to
  navigate with swipe gestures rather than by tapping. like swipe right
  over the video surface to fast forward. the further/faster i move the
  finger the faster it should fast forward.

  vlc on android does this very nicely. (it also controls volume and
  brightness with swipe gestures - ver convenient!)

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

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

[Touch-packages] [Bug 1634263] [NEW] Touchpad movements doesn't work after suspend

[svenmeier]

Public bug reported:

Once or twice a week *after* resume from suspend I can no longer use the
touchpad to movethe mouse pointer, mouse clicks are registered though.

Reloading module psmouse works as a workaround.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Oct 17 22:52:05 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-19-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
MachineType: LENOVO 20344
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=e61df794-2762-4b1b-bb74-3ad6415d4792 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 96CN31WW(V1.17)
dmi.board.asset.tag: 31900058Std
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900058Std
dmi.chassis.asset.tag: 31900058Std
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 13
dmi.modalias: 
dmi:bvnLENOVO:bvr96CN31WW(V1.17):bd07/21/2015:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoYoga213:
dmi.product.name: 20344
dmi.product.version: Lenovo Yoga 2 13
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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


** Tags: amd64 apport-bug ubuntu yakkety

** Description changed:

- Once or twice a week I can no longer use the touchpad to move the mouse
- pointer, mouse clicks are registered though.
+ Once or twice a week *after* resume from suspend I can no longer use the
+ touchpad to movethe mouse pointer, mouse clicks are registered though.
  
  Reloading module psmouse works as a workaround.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 17 22:52:05 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-19-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  MachineType: LENOVO 20344
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=e61df794-2762-4b1b-bb74-3ad6415d4792 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN31WW(V1.17)
  dmi.board.asset.tag: 31900058Std
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: 31900058Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN31WW(V1.17):bd07/21/2015:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: 

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

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

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

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  in termial some continuous error is coming

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raghava2075 F pulseaudio
  Date: Mon Oct 17 23:01:44 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=fbdfa4cf-6a89-4497-be1e-3fc933c6f704
  InstallationDate: Installed on 2016-05-23 (146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 0c45:6321 Microdia 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=3733ecc5-0176-40b8-becf-6781270cbc38 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-21-generic 4.4.0-21.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1695
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.1F
  dmi.chassis.asset.tag: 5CG2130PZ3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn1695:rvrKBCVersion15.1F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 06901320461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1634249] [NEW] Since upgrade to Gnome Ubuntu 16.10, my mouse is slow and cursor small on gnome shell menus

[Vianney Carel]

Public bug reported:

I upgraded 2 days ago to Gnome Ubuntu 16.10.
Since then, my mouse is 2x slower and my cursor is 2x smaller...:
- during Gnome startup (about 1 or 2 seconds on my system)
- on Gnome Shell menus

The cursor gets back to normal after I open a GTK application (such as 
Nautilus, but not Google Chrome). But the mouse is still slow anyway.
I have an Asus UX305 with an HiDPI screen (3200x1800).

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Oct 17 22:05:50 2016
DistUpgraded: 2016-10-15 22:12:07,962 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 520 [1043:1000]
InstallationDate: Installed on 2016-09-21 (26 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 04f2:b56b Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305UA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt quiet splash acpi_osi= 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
dmi.bios.date: 10/12/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305UA.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305UA.201:bd10/12/2015:svnASUSTeKCOMPUTERINC.:pnUX305UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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


** Tags: amd64 apport-bug ubuntu yakkety

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

Title:
  Since upgrade to Gnome Ubuntu 16.10, my mouse is slow and cursor small
  on gnome shell menus

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded 2 days ago to Gnome Ubuntu 16.10.
  Since then, my mouse is 2x slower and my cursor is 2x smaller...:
  - during Gnome startup (about 1 or 2 seconds on my system)
  - on Gnome Shell menus

  The cursor gets back to normal after I open a GTK application (such as 
Nautilus, but not Google Chrome). But the mouse is still slow anyway.
  I have an Asus UX305 with an HiDPI screen (3200x1800).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 17 22:05:50 2016
  DistUpgraded: 2016-10-15 22:12:07,962 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 520 [1043:1000]
  InstallationDate: Installed on 2016-09-21 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 

[Touch-packages] [Bug 1634220] Re: Wallpaper does not resize correctly when adding external display

[groucho]

I think I have the same bug with Ubuntu 16.10.
16.04 was fine.

Additionally, setting a new wallpaper is a bit slow. The new wallpaper
appears after a delay of 2 seconds without any special effect (no fading
in/out).

Graphics card : Intel HD graphics.

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

Title:
  Wallpaper does not resize correctly when adding external display

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I add a second (external) display to my laptop (Dell Latitude)
  the wallpaper/background is not resized correctly.

  1. just an internal display with a resolution of 1366x768
  2. adding an external display with a full HD resolution

  Adding the external display results in
  - the wallper is shown in the upper left corner of the external display 
(probably with the resolution of the internal display.
  - The rest of the screen is filled with random segments of windows that have 
been shown at these positions before
  - the internal display does not show any wallpaper (completely black)

  Additionally it looks like the left side panels (one for internal and
  one for external) are drawn over each other on the external display.
  See attachment Auswal_001.png

  Deactivating the internal display does not change anything

  Locking the screen shows a correctly resized wallpaper in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog: /dev/sda6: clean, 1281257/10911744 files, 22096310/43622400 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Oct 17 20:23:39 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-21-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04a9]
  InstallationDate: Installed on 2013-11-10 (1072 days ago)
  InstallationMedia: elementary OS 0.2 "Luna" - Stable amd64 (20130810)
  MachineType: Dell Inc. Latitude E6220
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=f1d78d25-23cf-4217-9db2-0750a8eb2b53 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0R97MN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/17/2012:svnDellInc.:pnLatitudeE6220:pvr01:rvnDellInc.:rn0R97MN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6220
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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

[Touch-packages] [Bug 1634220] Re: Wallpaper does not resize correctly when adding external display

[Launchpad Bug Tracker]

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

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

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

Title:
  Wallpaper does not resize correctly when adding external display

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I add a second (external) display to my laptop (Dell Latitude)
  the wallpaper/background is not resized correctly.

  1. just an internal display with a resolution of 1366x768
  2. adding an external display with a full HD resolution

  Adding the external display results in
  - the wallper is shown in the upper left corner of the external display 
(probably with the resolution of the internal display.
  - The rest of the screen is filled with random segments of windows that have 
been shown at these positions before
  - the internal display does not show any wallpaper (completely black)

  Additionally it looks like the left side panels (one for internal and
  one for external) are drawn over each other on the external display.
  See attachment Auswal_001.png

  Deactivating the internal display does not change anything

  Locking the screen shows a correctly resized wallpaper in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog: /dev/sda6: clean, 1281257/10911744 files, 22096310/43622400 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Oct 17 20:23:39 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-21-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04a9]
  InstallationDate: Installed on 2013-11-10 (1072 days ago)
  InstallationMedia: elementary OS 0.2 "Luna" - Stable amd64 (20130810)
  MachineType: Dell Inc. Latitude E6220
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=f1d78d25-23cf-4217-9db2-0750a8eb2b53 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0R97MN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/17/2012:svnDellInc.:pnLatitudeE6220:pvr01:rvnDellInc.:rn0R97MN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6220
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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

[Touch-packages] [Bug 1634234] Re: apt-key leaves files in /dev open after exit

[Rod Smith]

** Attachment added: ""lsof | grep dev" output from after running apt-key"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634234/+attachment/4762666/+files/after.txt

** Tags added: hwcert-server

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

Title:
  apt-key leaves files in /dev open after exit

Status in apt package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
  /dev/urandom open after exiting. Here's a procedure to replicate the
  problem:

  1. Install Ubuntu 16.10. (I used MAAS for this task.)
  2. Install the "lsof" package (which is not installed by default).
  3. Type "lsof | grep dev" to see open files.
  4. Type "sudo apt-key adv --recv-keys --keyserver 
hkp://keyserver.ubuntu.com:80 1FEADE10;"
  5. Type "lsof | grep dev" again.
  6. Compare the output of the two "lsof" commands.

  I'm attaching two files, before.txt and after.txt, that show the
  before and after results from "lsof | grep dev" in this scenario. Note
  that the /dev/null and /dev/urandom files are both open after apt-key
  is run, but not before. This problem does NOT occur with Ubuntu 16.04.

  This problem is preventing us (the server certification team) from
  importing keys in a custom MAAS preseed script; after installing
  successfully, umounting the installed image fails because of the open
  files on /dev.

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

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

[Touch-packages] [Bug 1634234] [NEW] apt-key leaves files in /dev open after exit

[Rod Smith]

Public bug reported:

In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
/dev/urandom open after exiting. Here's a procedure to replicate the
problem:

1. Install Ubuntu 16.10. (I used MAAS for this task.)
2. Install the "lsof" package (which is not installed by default).
3. Type "lsof | grep dev" to see open files.
4. Type "sudo apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 
1FEADE10;"
5. Type "lsof | grep dev" again.
6. Compare the output of the two "lsof" commands.

I'm attaching two files, before.txt and after.txt, that show the before
and after results from "lsof | grep dev" in this scenario. Note that the
/dev/null and /dev/urandom files are both open after apt-key is run, but
not before. This problem does NOT occur with Ubuntu 16.04.

This problem is preventing us (the server certification team) from
importing keys in a custom MAAS preseed script; after installing
successfully, umounting the installed image fails because of the open
files on /dev.

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


** Tags: hwcert-server

** Attachment added: ""lsof | grep dev" output from before running apt-key"
   https://bugs.launchpad.net/bugs/1634234/+attachment/4762665/+files/before.txt

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

Title:
  apt-key leaves files in /dev open after exit

Status in apt package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
  /dev/urandom open after exiting. Here's a procedure to replicate the
  problem:

  1. Install Ubuntu 16.10. (I used MAAS for this task.)
  2. Install the "lsof" package (which is not installed by default).
  3. Type "lsof | grep dev" to see open files.
  4. Type "sudo apt-key adv --recv-keys --keyserver 
hkp://keyserver.ubuntu.com:80 1FEADE10;"
  5. Type "lsof | grep dev" again.
  6. Compare the output of the two "lsof" commands.

  I'm attaching two files, before.txt and after.txt, that show the
  before and after results from "lsof | grep dev" in this scenario. Note
  that the /dev/null and /dev/urandom files are both open after apt-key
  is run, but not before. This problem does NOT occur with Ubuntu 16.04.

  This problem is preventing us (the server certification team) from
  importing keys in a custom MAAS preseed script; after installing
  successfully, umounting the installed image fails because of the open
  files on /dev.

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

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

[Touch-packages] [Bug 1373571] Re: Add the ability to include the device product name in the user agent string

[Ferry Toth]

In OTA 13 the current settings cause www.blendle.com to show a 'invalid
browser' page. This is a regression compared to a previous version
(can't remember when this worked).

This web site works with android's browser and even with sailfish.

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

Title:
  Add the ability to include the device product name in the user agent
  string

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  In order to be well supported in the wurfl database we would like to
  include a product name in the string. This is used as a key to
  ascertain capabilities.

  Our default UA already has a placeholder for a device ID, which by
  default is empty. What we’re missing is a mechanism to expose the
  actual device ID to QML.

  We would need to do additional testing to ensure the addition does not
  adversely affect results.

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

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

[Touch-packages] [Bug 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile

[Christian Boltz]

Thanks for the feedback!

I just submitted the patch for review upstream.

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

Title:
  In 16.10, LXD won't work with enforced dsnmasq profile

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

Bug description:
  After upgrading to 16.0, LXD networking stopped working due to
  enforced dnsmasq profile.

  audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
  operation="truncate" profile="/usr/sbin/dnsmasq"
  name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540
  comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

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

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

[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc

[Casey Marshall]

For any poor soul who wanders here, here is the best known workaround
for this issue I've seen to date:

22-09-2016 15:23:18 < stgraber!~stgraber@ubuntu/member/stgraber: cmars:
if you mask (systemctl mask) the systemd units related to binfmt
(systemctl -a | grep binfmt) and reboot, then the problem is gone for
good. This is related to systemd's use of automount and not to binfmt-
misc (which just ships a bunch of binfmt hooks)

FYI, I think this will disable binfmt.

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

Title:
   Too many levels of symbolic links /proc/sys/fs/binfmt_misc

Status in binfmt-support package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  At first I thought this was an LXD issue, but it turns out the issue
  is in systemd

  https://github.com/lxc/lxd/issues/1727#issuecomment-194416558

  ls -l  /proc/sys/fs/binfmt_misc  fails with error:

  Too many levels of symbolic links

  
  I restarted binfmt manually by running:

  sudo /usr/sbin/update-binfmts --disable
  sudo /usr/sbin/update-binfmts --enable

  I think using systemd to do this would have also worked:

  sudo service binfmt-support restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions

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

[Touch-packages] [Bug 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile

[Stéphane Graber]

/var/lib/lxd/networks/*/dnsmasq.leases rw,

should work fine

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

Title:
  In 16.10, LXD won't work with enforced dsnmasq profile

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

Bug description:
  After upgrading to 16.0, LXD networking stopped working due to
  enforced dnsmasq profile.

  audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
  operation="truncate" profile="/usr/sbin/dnsmasq"
  name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540
  comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

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

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

[Touch-packages] [Bug 1634220] [NEW] Wallpaper does not resize correctly when adding external display

[Andreas Büsching]

Public bug reported:

When I add a second (external) display to my laptop (Dell Latitude) the
wallpaper/background is not resized correctly.

1. just an internal display with a resolution of 1366x768
2. adding an external display with a full HD resolution

Adding the external display results in
- the wallper is shown in the upper left corner of the external display 
(probably with the resolution of the internal display.
- The rest of the screen is filled with random segments of windows that have 
been shown at these positions before
- the internal display does not show any wallpaper (completely black)

Additionally it looks like the left side panels (one for internal and
one for external) are drawn over each other on the external display. See
attachment Auswal_001.png

Deactivating the internal display does not change anything

Locking the screen shows a correctly resized wallpaper in the
background.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
BootLog: /dev/sda6: clean, 1281257/10911744 files, 22096310/43622400 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Oct 17 20:23:39 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.6, 4.8.0-21-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04a9]
InstallationDate: Installed on 2013-11-10 (1072 days ago)
InstallationMedia: elementary OS 0.2 "Luna" - Stable amd64 (20130810)
MachineType: Dell Inc. Latitude E6220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=f1d78d25-23cf-4217-9db2-0750a8eb2b53 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0R97MN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/17/2012:svnDellInc.:pnLatitudeE6220:pvr01:rvnDellInc.:rn0R97MN:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6220
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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


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

** Attachment added: "drawn over each other"
   
https://bugs.launchpad.net/bugs/1634220/+attachment/4762642/+files/Auswahl_001.png

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

Title:
  Wallpaper does not resize correctly when adding external display

Status in xorg package in Ubuntu:
  New

Bug description:
  When I add a second (external) display to my laptop (Dell Latitude)
  the wallpaper/background is not resized correctly.

  1. just an internal display with a resolution of 1366x768
  2. adding an external display with a full HD resolution

  Adding the external display results in
  - the wallper is shown in the upper left corner of the external display 
(probably with the resolution of the internal display.
  - The rest of the screen is filled with random segments of windows that have 
been shown at these positions before
  - the internal display does not show any wallpaper (completely black)

  Additionally it looks like the left side panels (one for internal and
  one for external) are drawn over each other on the external display.
  See attachment Auswal_001.png

  Deactivating the internal display does not change anything

  Locking the screen shows a correctly resized wallpaper in the
  background.

  

[Touch-packages] [Bug 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile

[Stéphane Graber]

The interface name is decided by the user in LXD 2.3 or higher, so it
can be any valid interface name.

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

Title:
  In 16.10, LXD won't work with enforced dsnmasq profile

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

Bug description:
  After upgrading to 16.0, LXD networking stopped working due to
  enforced dnsmasq profile.

  audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
  operation="truncate" profile="/usr/sbin/dnsmasq"
  name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540
  comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

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

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

[Touch-packages] [Bug 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile

[Christian Boltz]

Sounds like the path changed.

You'll need to add the following rule to /etc/apparmor.d/usr.sbin.dnsmasq (or 
to the local/ include):
  /var/lib/lxd/networks/lxdbr*/dnsmasq.leases rw,

BTW: Do you know if lxd supports different network interface types that
don't match the lxdbr* name pattern? If yes, we'll need to add a more
permissive rule.

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

** Tags added: aa-policy

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

Title:
  In 16.10, LXD won't work with enforced dsnmasq profile

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

Bug description:
  After upgrading to 16.0, LXD networking stopped working due to
  enforced dnsmasq profile.

  audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
  operation="truncate" profile="/usr/sbin/dnsmasq"
  name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540
  comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

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

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

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

[Steve Langasek]

** Also affects: initramfs-tools (Ubuntu Yakkety)
   Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: In Progress

** Also affects: klibc (Ubuntu Yakkety)
   Importance: Undecided
   Status: Won't Fix

** Also affects: open-iscsi (Ubuntu Yakkety)
   Importance: High
   Status: Fix Released

** Also affects: isc-dhcp (Ubuntu Yakkety)
   Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: Fix Released

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

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

Status in MAAS:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  Fix Released
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  New

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

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

  [Impact]

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

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

  [Test Case]

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

  [Regression Potential]

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

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

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

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

[Mathieu Trudel-Lapierre]

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Released => In Progress

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

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

Status in MAAS:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  Fix Released
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  New

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

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

  [Impact]

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

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

  [Test Case]

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

  [Regression Potential]

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

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

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

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

[Mathieu Trudel-Lapierre]

Reopening, as we reverted the SRU (but will also fix things in Zesty and
Yakkety with a better method than overriding ip=)

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

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

Status in MAAS:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  Fix Released
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  New

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

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

  [Impact]

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

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

  [Test Case]

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

  [Regression Potential]

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

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

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

[Touch-packages] [Bug 1634176] Re: Change of behavior in handling of 'ip=' on kernel command line now does ipv6 dhcp

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1621507
   initramfs-tools configure_networking() fails to dhcp ipv6 addresses

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

Title:
  Change of behavior in handling of 'ip=' on kernel command line now
  does ipv6 dhcp

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Yakkety:
  Confirmed
Status in initramfs-tools source package in Zesty:
  Confirmed

Bug description:
  Changes were initially made under bug 1621507 that changed the
  behavior of the initramfs when 'ip=' was seen on the kernel command
  line.  The changes were done to support doing an ipv6 dhcp request in
  addition to the expected ipv4 dhcp request.

  The result is that in all cases where 'ip=' is found on the kernel command 
line the initramfs will invoke 'dhclient -6'.  In all cases now, the changes 
that have occurred are:
   * initramfs now issues an ipv6 dhclient request
   * if no ipv6 dhcp server is available, the system waits unnecessarily for a 
response.
   * worst case scenario (admittedly unlikely), a system could now get a 
world-routable ipv6 address that previously was not exposed to the internet.
   * Two dhclient processes are left running from the initramfs (one -4 and one 
-6). I'm not sure, but I suspect they are not functional as root has been 
pivoted.

  The implementation has inconsistent behavior based on how quickly or if at 
all a dhcpv4/dhcpv6 server is found.  Things that can happen:
   a.) system uses only dhcpv4, timing out before dhcp6 was found or bug 
1633479 causes dhclient -6 to fail.
   b.) system uses only dhcpv6 address
   c.) system gets no dhclient response (v4 or v6) but uses link-local address 
to successfully reach its mount target.
   d.) the hostname provided in ip= command line not sent in the dhcp request 
as it would be with 'ipconfig' implementation.

  The way this should have been handled in a SRU was to require users
  who needed rthe new ipv6 functionality to explicitly request it.

  One way this could have been done would have been to extend the 'ip=' command
  line function.  klibc documents the previous ip= syntax at README.ipconfig 
[1].
    ::

  My suggestion is to extend the 'autoconf' parameter. Previously the
  supported documented values were 'rarp', 'bootp', 'both', 'dhcp',
  'all', 'off', 'static', 'none'.  I suggest we add 'dhcp6' to the the
  list.

  Additionally, I believe we should revert changes made since
  0.125ubuntu3 to finding further regressions.

  --
  [1] 
https://github.com/codehelp/klibc-aarch64/blob/master/usr/kinit/ipconfig/README.ipconfig

  Related bugs:
   * bug 1629972: networking stop incorrectly disconnects from (network) root 
filesystem
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp ipv6 
addresses
   * bug 1628306: network booting fails for iscsi root if no ip is set
   * bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp 
boot option
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)
   * bug 1633619: dhclient -1 exits 0 when no lease found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu5
  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: Mon Oct 17 11:14:00 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (452 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Steve Langasek]

initramfs-tools has been reverted in xenial due to regression (bug
#1631474).  Resetting the bug state, we need to get support for ipv6
back into xenial-updates but in a regression-free way, which - per
discussion on bug #1631474 and bug #1634176 - probably implies a
separate 'ip6=' boot option, with corresponding changes to the
components populating the boot commandline.

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Fix Released => Triaged

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

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

Status in MAAS:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  Fix Released
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  New

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

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

  [Impact]

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

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

  [Test Case]

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

  [Regression Potential]

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

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

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

[Touch-packages] [Bug 1631010] Re: please add a cmdline option to chose between ipv4, ipv6, or dual-stack network boot

[Mathieu Trudel-Lapierre]

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

** This bug has been marked a duplicate of bug 1621507
   initramfs-tools configure_networking() fails to dhcp ipv6 addresses

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

Title:
  please add a cmdline option to chose between ipv4, ipv6, or dual-stack
  network boot

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Right now, I can boot with "ip=hostname:BOOTIF" in the kernel
  commandline, and (after bug 1621507), I get whatever it came up with
  for ipv4 and ipv6.  If for nothing more than testing on a dual-stack
  environment, it would be nice to be able to force that to try both
  (current behavior, and an excellent default), only try IPv4, or only
  IPv6.

  NOT something that needs to be fixed before yakkety, but would be nice
  to eventually get back to xenial.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Update Released

[Steve Langasek]

The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  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

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.122ubuntu8.5

---
initramfs-tools (0.122ubuntu8.5) xenial; urgency=medium

  * scripts/functions: Revert configure_networking changes to the state at
0.122ubuntu8.1. (LP: #1631474)

 -- Mathieu Trudel-Lapierre   Thu, 13 Oct 2016
17:19:56 -0400

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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 Released
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[poet_imp]

The problem persists in 16.10. I was soo hoping that this would be
resolved by the upgrade. Ubuntu 16.10 is showing version 5.41 as the
latest available. Might someone be willing to package 5.42, if that
fixes this?

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Touch-packages] [Bug 1577926] Re: apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

[Viliam Dias]

Just for reference:

I had the same problem on my digital ocean droplet (after a distro
upgrade).

Problem solved after upgrade the kernel in the digital ocean
administration site. More details you can see here[1].

In my case the upgrade was from 3.x to 4.x serie.

[1] https://www.digitalocean.com/community/tutorials/how-to-update-a
-digitalocean-server-s-kernel

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

Title:
  apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Apt can fail to verify a Release file which verifies just fine when
  calling apt-key directly.

  Please advise how i can supply further debug information to help fix
  the underlying bug.

  Expected:
  apt-get should only report that a repository is not signed when no such 
signature was found.
  If a signature was in fact successfully acquired but not verified, apt-get 
should report failure to verify instead.
  apt-get should have a meaningful error message when calling apt-key fails.

  Bonus:
  Calling apt-key should not fail when the same thing works fine on command 
line.
  A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) 
documentation.

  Observed:

  # uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
i686 i686 i686 GNU/Linux
  # chroot reproducable
  $ uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
armv7l armv7l armv7l GNU/Linux

  $ lsb_release -a 2>/dev/null
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  $ apt-get -o "Debug::Acquire::gpgv=true" update
  Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB]
  0% [1 InRelease gpgv 92.2 kB]igners 
  Preparing to exec:  /usr/bin/apt-key --quiet --readonly verify --status-fd 3 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv exited with status 111
  Summary:
Good: 
Bad: 
Worthless: 
SoonWorthless: 
NoPubKey: 
  Ign:1 http://ports.ubuntu.com xenial-security InRelease
  Fetched 92.2 kB in 1s (79.5 kB/s)
  Reading package lists... Done
  W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not 
execute 'apt-key' to verify signature (is gnupg installed?)
  W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  $ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using DSA key ID 437D05B5
  [GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137
  [GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key 
"
  [GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 
1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using RSA key ID C0B21F32
  [GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137
  [GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) 
"
  [GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 
1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32

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

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

[Touch-packages] [Bug 1608965] Re: ssh GSSAPI rekey failure

[Nish Aravamudan]

I believe this was also reported to Debian as https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=819361. Thank you for filing this report! We
might need to follow-up with the upstream openssh community to help
debug this.

** Bug watch added: Debian Bug tracker #819361
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819361

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  ssh GSSAPI rekey failure

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  If I have ssh set up using GSSAPI with rekeying enabled, then the
  connection fails on rekey, and tries to do host-based verification
  'mid-session'.

  Steps to reproduce:

  $ ssh -vvv server.example.com
  
  debug1: Authenticating to ssh.example.com:22 as 'user'
  
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group1-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group14-sha1-A/vxljAEU54gt9a48EiANQ==,gss-gex-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group1-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group14-sha1-bontcUwnM6aGfWCP21alxQ==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group1-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
  
  Last login: Tue Aug 02 10:47:20 2016 from foo

  # Then do 'kinit' on the client to get a new ticket...

  debug1: need rekeying
  debug1: SSH2_MSG_KEXINIT sent
  debug1: rekeying in progress
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa,null
  [...]
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
  [...]
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: rekeying in progress
  debug1: rekeying in progress
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E
  The authenticity of host 'server.example.com (10.0.0.1)' can't be established.
  ECDSA key fingerprint is SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E.
  Are you sure you want to continue connecting (yes/no)? 
  Host key verification failed.

  It looks like the list of KEX algorithms differs between the initial
  connection, and the rekeying.

  This behaviour seems to occur with a client running 16.04 (openssh-
  client 1:7.2p2-4ubuntu1) but not on 15.10 (openssh-client
  1:6.9p1-2ubuntu0.2).

  ssh_config is as follows:

  HashKnownHosts no
  GSSAPIAuthentication yes
  GSSAPIDelegateCredentials yes
  GSSAPIRenewalForcesRekey yes
  GSSAPITrustDNS yes
  GSSAPIKeyExchange yes
  ForwardX11 yes
  ForwardX11Trusted yes

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

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

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

[Scott Moser]

** Bug watch added: Debian Bug tracker #841106
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841106

** Also affects: ifupdown (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841106
   Importance: Unknown
   Status: Unknown

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

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

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  Confirmed
Status in ifupdown package in Debian:
  Unknown

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

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

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

  [Impact]

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

  [Test Case]

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

  [Regression potential]

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

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

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

[Touch-packages] [Bug 1634176] Re: Change of behavior in handling of 'ip=' on kernel command line now does ipv6 dhcp

[Scott Moser]

** Description changed:

  Changes were initially made under bug 1621507 that changed the behavior
- of the linitramfs when 'ip=' was seen on the kernel command line.  The
+ of the initramfs when 'ip=' was seen on the kernel command line.  The
  changes were done to support doing an ipv6 dhcp request in addition to
  the expected ipv4 dhcp request.
  
  The result is that in all cases where 'ip=' is found on the kernel command 
line the initramfs will invoke 'dhclient -6'.  In all cases now, the changes 
that have occurred are:
   * initramfs now issues an ipv6 dhclient request
   * if no ipv6 dhcp server is available, the system waits unnecessarily for a 
response.
   * worst case scenario (admittedly unlikely), a system could now get a 
world-routable ipv6 address that previously was not exposed to the internet.
-  * 2 dhclient processes are left running from the initramfs (one -4 and one 
-6). I'm not sure, but I suspect they are not functional as root has been 
pivoted.
+  * Two dhclient processes are left running from the initramfs (one -4 and one 
-6). I'm not sure, but I suspect they are not functional as root has been 
pivoted.
  
  The implementation has inconsistent behavior based on how quickly or if at 
all a dhcpv4/dhcpv6 server is found.  Things that can happen:
   a.) system uses only dhcpv4, timing out before dhcp6 was found or bug 
1633479 causes dhclient -6 to fail.
   b.) system uses only dhcpv6 address
   c.) system gets no dhclient response (v4 or v6) but uses link-local address 
to successfully reach its mount target.
   d.) the hostname provided in ip= command line not sent in the dhcp request 
as it would be with 'ipconfig' implementation.
  
  The way this should have been handled in a SRU was to require users who
  needed rthe new ipv6 functionality to explicitly request it.
  
  One way this could have been done would have been to extend the 'ip=' command
  line function.  klibc documents the previous ip= syntax at README.ipconfig 
[1].
    ::
  
  My suggestion is to extend the 'autoconf' parameter. Previously the
  supported documented values were 'rarp', 'bootp', 'both', 'dhcp', 'all',
  'off', 'static', 'none'.  I suggest we add 'dhcp6' to the the list.
  
- Additionally, I believe we should revert changes made 0.125ubuntu3 to
- finding further regressions.
+ Additionally, I believe we should revert changes made since 0.125ubuntu3
+ to finding further regressions.
  
  --
  [1] 
https://github.com/codehelp/klibc-aarch64/blob/master/usr/kinit/ipconfig/README.ipconfig
  
  Related bugs:
-  * bug 1629972: networking stop incorrectly disconnects from (network) root 
filesystem 
+  * bug 1629972: networking stop incorrectly disconnects from (network) root 
filesystem
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp ipv6 
addresses
   * bug 1628306: network booting fails for iscsi root if no ip is set
   * bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp 
boot option
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)
   * bug 1633619: dhclient -1 exits 0 when no lease found
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu5
  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: Mon Oct 17 11:14:00 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (452 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1634176

Title:
  Change of behavior in handling of 'ip=' on kernel command line now
  does ipv6 dhcp

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Yakkety:
  Confirmed
Status in initramfs-tools source package in Zesty:
  Confirmed

Bug description:
  Changes were initially made under bug 1621507 that changed the
  behavior of the initramfs when 'ip=' was seen on the kernel command
  line.  The changes were done to support doing an ipv6 dhcp request in
  addition to the expected ipv4 dhcp request.

  The result is that in all cases where 'ip=' is found on the kernel command 
line the initramfs will invoke 'dhclient -6'.  In all cases now, the changes 
that have occurred are:
   * initramfs now issues an ipv6 dhclient request
   * if no ipv6 dhcp server is available, the system waits unnecessarily for a 
response.
   * worst case scenario (admittedly unlikely), a system could now get a 
world-routable ipv6 

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

[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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1634210

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  in termial some continuous error is coming

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raghava2075 F pulseaudio
  Date: Mon Oct 17 23:01:44 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=fbdfa4cf-6a89-4497-be1e-3fc933c6f704
  InstallationDate: Installed on 2016-05-23 (146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 0c45:6321 Microdia 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=3733ecc5-0176-40b8-becf-6781270cbc38 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-21-generic 4.4.0-21.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1695
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.1F
  dmi.chassis.asset.tag: 5CG2130PZ3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn1695:rvrKBCVersion15.1F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 06901320461620100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Raghava]

Public bug reported:

in termial some continuous error is coming

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  raghava2075 F pulseaudio
Date: Mon Oct 17 23:01:44 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=fbdfa4cf-6a89-4497-be1e-3fc933c6f704
InstallationDate: Installed on 2016-05-23 (146 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 003: ID 0c45:6321 Microdia 
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=3733ecc5-0176-40b8-becf-6781270cbc38 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-21-generic 4.4.0-21.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.37
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1695
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.1F
dmi.chassis.asset.tag: 5CG2130PZ3
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn1695:rvrKBCVersion15.1F:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 06901320461620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package xenial

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  in termial some continuous error is coming

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raghava2075 F pulseaudio
  Date: Mon Oct 17 23:01:44 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=fbdfa4cf-6a89-4497-be1e-3fc933c6f704
  InstallationDate: Installed on 2016-05-23 (146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 0c45:6321 Microdia 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=3733ecc5-0176-40b8-becf-6781270cbc38 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-21-generic 4.4.0-21.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2013
  dmi.bios.vendor: Hewlett-Packard

[Touch-packages] [Bug 1634208] [NEW] VPN cannot resolve DNS entries on second connect

[Bryn Cooke]

Public bug reported:

The first time I connect to a VPN (vpnc) everything works fine, but if I
disconnect and then reconnect I can no longer resolve DNS entries
although I can connect directly via IP address. The only solution seems
to be a reboot.

This was working fine in 16.04.

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

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

Title:
  VPN cannot resolve DNS entries on second connect

Status in network-manager package in Ubuntu:
  New

Bug description:
  The first time I connect to a VPN (vpnc) everything works fine, but if
  I disconnect and then reconnect I can no longer resolve DNS entries
  although I can connect directly via IP address. The only solution
  seems to be a reboot.

  This was working fine in 16.04.

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

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

[Touch-packages] [Bug 1487680] Re: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Chuck Short]

Looks like a bad package.

** Changed in: python-psutil (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-psutil package in Ubuntu:
  Won't Fix

Bug description:
  idk

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-psutil 1.2.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Sat Aug 22 13:37:03 2015
  DuplicateSignature: package:python-psutil:1.2.1-1ubuntu2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-22 (0 days ago)
  InstallationMedia: It
  SourcePackage: python-psutil
  Title: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: 
subprocess installed post-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/python-psutil/+bug/1487680/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

[Michal Predotka]

FWIW updating the Clock app will not affect this bug. The Clock app just
saves an alarm using Alarm API and the rest is done by the system.

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

[Joshua Powers]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

It looks as if you are using packages from proposed and have run into a
situation where packages are not in sync. Packages in yakkety-proposed
that are not in yakkety are *known to be broken* - otherwise they would
migrate to the release pocket within a few hours. We appreciate you
helping out in testing, but I suggest that you test by using yakkety
only - using the proposed pocket provides no real benefit to developers.

I am marking this a duplicate of another heimdal bug where the user was
using proposed as well. If you disagree please feel free to comment
adding details as to why you believe this is not the case.

Thanks again

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

** This bug is no longer a duplicate of bug 1617963
   package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
** This bug has been marked a duplicate of bug 1634201
   Release process leaves stable -proposed with broken packages, breaking users 
who volunteer to test stable -proposed for SRU verification purposes

-- 
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 1633355] Re: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured b

[Joshua Powers]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

It looks as if you are using packages from proposed and have run into a
situation where packages are not in sync. Packages in yakkety-proposed
that are not in yakkety are *known to be broken* - otherwise they would
migrate to the release pocket within a few hours. We appreciate you
helping out in testing, but I suggest that you test by using yakkety
only - using the proposed pocket provides no real benefit to developers.

I am marking this a duplicate of another heimdal bug where the user was
using proposed as well. If you disagree please feel free to comment
adding details as to why you believe this is not the case.

Thanks again

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

** This bug is no longer a duplicate of bug 1617963
   package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
** This bug has been marked a duplicate of bug 1634201
   Release process leaves stable -proposed with broken packages, breaking users 
who volunteer to test stable -proposed for SRU verification purposes

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

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

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  On startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1
  Uname: Linux 4.8.1-040801-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   libheimbase1-heimdal:amd64: Install
   NULL: ConfigurePending
   NULL: RemovePending
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct 14 02:53:05 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu1
   libgcc1 1:6.2.0-5ubuntu12
  DuplicateSignature:
   package:libheimbase1-heimdal:amd64:1.7~git20160703+dfsg-1
   Processing triggers for libc-bin (2.24-3ubuntu1) ...
   dpkg: error processing package libheimbase1-heimdal:amd64 (--configure):
package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be 
configured because libheimbase1-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libheimbase1-heimdal:i386 is at a different 
version (1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-02-27 (230 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: heimdal
  Title: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libheimbase1-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/1633355/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

[Joshua Powers]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

It looks as if you are using packages from proposed and have run into a
situation where packages are not in sync. Packages in yakkety-proposed
that are not in yakkety are *known to be broken* - otherwise they would
migrate to the release pocket within a few hours. We appreciate you
helping out in testing, but I suggest that you test by using yakkety
only - using the proposed pocket provides no real benefit to developers.

I am marking this a duplicate of another heimdal bug where the user was
using proposed as well. If you disagree please feel free to comment
adding details as to why you believe this is not the case.

Thanks again

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

** This bug is no longer a duplicate of bug 1617963
   package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
** This bug has been marked a duplicate of bug 1634201
   Release process leaves stable -proposed with broken packages, breaking users 
who volunteer to test stable -proposed for SRU verification purposes

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

[Joshua Powers]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

It looks as if you are using packages from proposed and have run into a
situation where packages are not in sync. Packages in yakkety-proposed
that are not in yakkety are *known to be broken* - otherwise they would
migrate to the release pocket within a few hours. We appreciate you
helping out in testing, but I suggest that you test by using yakkety
only - using the proposed pocket provides no real benefit to developers.

I am marking this a duplicate of another heimdal bug where the user was
using proposed as well. If you disagree please feel free to comment
adding details as to why you believe this is not the case.

Thanks again

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

** This bug is no longer a duplicate of bug 1617963
   package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
** This bug has been marked a duplicate of bug 1634201
   Release process leaves stable -proposed with broken packages, breaking users 
who volunteer to test stable -proposed for SRU verification purposes

-- 
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:
  Confirmed

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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

** Information type changed from Private to Public

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  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: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

** Information type changed from Private to Public

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  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: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

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

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

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

[Joshua Powers]

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

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

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

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

Status in heimdal package in Ubuntu:
  New

Bug description:
  apport showed up

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libheimbase1-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
  AptOrdering:
   libheimbase1-heimdal:amd64: Install
   NULL: ConfigurePending
   NULL: RemovePending
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct 14 12:10:25 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu1
   libgcc1 1:6.2.0-5ubuntu12
  DuplicateSignature:
   package:libheimbase1-heimdal:amd64:1.7~git20160703+dfsg-1
   Processing triggers for libc-bin (2.24-3ubuntu1) ...
   dpkg: error processing package libheimbase1-heimdal:amd64 (--configure):
package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be 
configured because libheimbase1-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libheimbase1-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 libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libheimbase1-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/1633417/+subscriptions

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

[Touch-packages] [Bug 1634201] [NEW] Release process leaves stable -proposed with broken packages, breaking users who volunteer to test stable -proposed for SRU verification purposes

[Robie Basak]

Public bug reported:

During development, we have packages in -proposed that fail to migrate,
as expected, for good reason.

At release time, these packages are still present. For example, Yakkety
released with libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 in
proposed, which is not in the release pocket because it is broken (see
bug 1617963).

I think we should be encouraging users to volunteer to risk testing
proposed in stable releases. This helps with SRU verification.

However, our current release process breaks these users when they
upgrade to a new release (which, given that they are testing the cutting
edge, they are likely to do early, before the proposed pocket has been
cleaned out).

This means that users, instead of being encouraged, are being
discouraged from testing the SRU proposed pocket since we are breaking
them with known bugs but delaying removal of those breakages.

How can we adjust our release process to stop this happening?

** Affects: ubuntu
 Importance: Undecided
 Status: Confirmed


** Tags: bot-stop-nagging

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

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

Title:
  Release process leaves stable -proposed with broken packages, breaking
  users who volunteer to test stable -proposed for SRU verification
  purposes

Status in Ubuntu:
  Confirmed

Bug description:
  During development, we have packages in -proposed that fail to
  migrate, as expected, for good reason.

  At release time, these packages are still present. For example,
  Yakkety released with libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  in proposed, which is not in the release pocket because it is broken
  (see bug 1617963).

  I think we should be encouraging users to volunteer to risk testing
  proposed in stable releases. This helps with SRU verification.

  However, our current release process breaks these users when they
  upgrade to a new release (which, given that they are testing the
  cutting edge, they are likely to do early, before the proposed pocket
  has been cleaned out).

  This means that users, instead of being encouraged, are being
  discouraged from testing the SRU proposed pocket since we are breaking
  them with known bugs but delaying removal of those breakages.

  How can we adjust our release process to stop this happening?

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

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

[Touch-packages] [Bug 1634199] [NEW] In 16.10, LXD won't work with enforced dsnmasq profile

[Franck]

Public bug reported:

After upgrading to 16.0, LXD networking stopped working due to enforced
dnsmasq profile.

audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
operation="truncate" profile="/usr/sbin/dnsmasq"
name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540
comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

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

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

Title:
  In 16.10, LXD won't work with enforced dsnmasq profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  After upgrading to 16.0, LXD networking stopped working due to
  enforced dnsmasq profile.

  audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
  operation="truncate" profile="/usr/sbin/dnsmasq"
  name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540
  comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

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

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

[Touch-packages] [Bug 1617341] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nish Aravamudan]

** Changed in: ntp (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  Triaged

Bug description:
  The update did not install. Maybe because the net got disconnected in
  between ???

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   ntp: Install
   ntpdate: Install
   ntp: Configure
   ntpdate: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Aug 26 19:39:18 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-26  19:36:04
   Commandline: aptdaemon role='role-commit-packages' sender=':1.65'
   Upgrade: ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1), 
ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-28 (151 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=790d64f7-9847-4d8c-bbaa-3c87b8aaac16 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (18 days ago)

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

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

[Touch-packages] [Bug 1632575] Re: systemd starts two copies of ntp at boot time

[Nish Aravamudan]

Thank you for filing this bug, it does look like a race.

We probably will need to see the systemd service files for ntp, at
least. I wonder if any of the `systemd-analyze` subcommands might be
helpful here to determine why ntpd is started twice.

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

** Changed in: ntp (Ubuntu)
   Importance: Undecided => Low

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

Title:
  systemd starts two copies of ntp at boot time

Status in ntp package in Ubuntu:
  Triaged

Bug description:
  My system monitoring check noticed a stale /var/run/ntpd.pid pidfile
  on a xenial machine that rebooted at 2 AM after unattended upgrades.
  ntpd itself was running, but with a different pid.

  Digging through journalctl I can see

  Oct 12 02:00:11 xenial64 ntp[681]:  * Starting NTP server ntpd
  Oct 12 02:00:11 xenial64 systemd[1]: Started Getty on tty1.
  Oct 12 02:00:11 xenial64 systemd[1]: Reached target Login Prompts.
  Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 run-parts[760]: run-parts: executing 
/etc/redis/redis-server.post-up.d/00_example
  Oct 12 02:00:11 xenial64 systemd[1]: Starting LSB: Start NTP daemon...
  Oct 12 02:00:11 xenial64 ntpd[719]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
  Oct 12 02:00:11 xenial64 ntpd[719]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
  Oct 12 02:00:11 xenial64 ntp[770]:  * Starting NTP server ntpd
  Oct 12 02:00:11 xenial64 ntpd[778]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
  Oct 12 02:00:11 xenial64 ntpd[778]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
  Oct 12 02:00:11 xenial64 ntp[770]:...done.
  Oct 12 02:00:11 xenial64 systemd[1]: Started LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 systemd[1]: Started Advanced key-value store.
  Oct 12 02:00:11 xenial64 ntpd[773]: proto: precision = 0.077 usec (-24)
  Oct 12 02:00:11 xenial64 ntpd[780]: proto: precision = 0.076 usec (-24)
  Oct 12 02:00:11 xenial64 ntpd[780]: unable to bind to wildcard address :: 
- another process may be running - EXITING
  Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 0 v6wildcard 
[::]:123
  Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 1 v4wildcard 
0.0.0.0:123

  As you can see, for some reason systemd starts ntpd twice, so there's
  a race to take over the socket, and a race to take over the pidfile.
  ntpd[773] gets the socket, ntpd[780] gets the pidfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.3
  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: Wed Oct 12 06:18:29 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576989] Re: stale lock files freeze apps

[Timo Jyrinki]

On staging armhf (the click test app is armhf) it's still pretty much as
described in comment #15. It is possible to get the "edit comnfig" to
hang, and after the fake stale lock file one will need a second start
attempt so that app really starts.

So this is with Qt 5.6.1 which includes all the patches tried before and
some more. It probably fixes Antti's issue and some others, but not
Michael's test app at least.

Maybe the test case could be submitted upstream stating it'd be nice to
get a fix to 5.6 series? (giving partial assigning to Michael to note
this) There are also no newer commits that seem meaningful to
qlockfile.cpp or qlockfile_unix.cpp, so it should be reproducable on
even dev.

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  stale lock files freeze apps

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  Confirmed

Bug description:
  Debugging why the Notes app would freeze for some people, I found
  there were some stale .lock files around. Those .lock files are
  autocreated by QSettings (with QLockFile) when this file is edited.
  Problem is, that it sometimes seems to happen that the app is
  suspended by our lifecycle and then killed (either by closing from
  spread or OOM killed) and those .lock files stick around. I have
  implemented a workaround in the notes app[1] to clear up those stale
  locks when the app starts app, however, today I ran twice in a row
  into the issue that the very same happened to music app. It would just
  freeze on startup and never come back. Digging around a bit I found
  such a stale lock file on its config file which is created with the
  QML Settings element. This implies that every app using QSettings or
  QML Settings {} are potentially affected. I suspect many more app
  freezes can be traced down to this.

  Now, there is some code in Qt to detect stale lock files [2], however,
  not sure why it doesn't detect those lock files as stale ones and
  decides to wait on them forever though. Probably a bug in the code or
  some of the wrong #ifdefs are triggered for our package builds.

  [1] 
https://code.launchpad.net/~mzanetti/reminders-app/remove-stale-lock-files/+merge/293355
  [2] 
http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qlockfile_unix.cpp

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

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

[Touch-packages] [Bug 1630324] Re: Broadcom wifi dies in 60s cycles with 4.8 kernel

[Alberto Salvia Novella]

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

Title:
  Broadcom wifi dies in 60s cycles with 4.8 kernel

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects
  fine, but dies for around 5-10s (the signal dies completely, tools
  like wavemon show "no interface data") in regular cycles of about 60s.
  dmesg logs the same brcmfmac errors every minute or so: "brcmfmac:
  brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)".

  network-manager's icon doesn't change however (remains as if the
  adapter was connected).

  This issue started to affect me when using kernel 4.8 on Ubuntu 16.04.
  I previously used kernel 4.7 and did not experience this bug.

  I booted the 16.10 daily build and experienced exactly the same
  errors.

  $ lspci | grep BCM4350
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)

  $ dmesg | grep brcm
  [5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
  [5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [   74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [  142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  ...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  Uname: Linux 4.8.0-040800-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct  4 14:15:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-26 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.29  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Guava Guest 1  68ae8dc2-ab23-42ef-9e41-ac8e9d91385a  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1606112] Re: package account-plugin-identica (not installed) failed to install/upgrade: попытка перезаписать «/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеется

[Alberto Salvia Novella]

** Changed in: account-plugins (Ubuntu)
   Importance: Undecided => High

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

Title:
  package account-plugin-identica (not installed) failed to
  install/upgrade: попытка перезаписать «/etc/signon-ui/webkit-
  options.d/identi.ca.conf», который уже имеется в пакете kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-identica (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Jul 25 07:59:19 2016
  ErrorMessage: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеется в пакете 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-03-29 (118 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-identica (not installed) failed to 
install/upgrade: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеется в пакете 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: Upgraded to xenial on 2016-05-12 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1606112/+subscriptions

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

[Touch-packages] [Bug 1622206] Re: package account-plugin-google not installed failed to install/upgrade: trying to overwrite /usr/share/accounts/services/google-im.service , which is also in package

[Alberto Salvia Novella]

** Changed in: account-plugins (Ubuntu)
   Importance: Undecided => High

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

Title:
  package account-plugin-google  not installed  failed to
  install/upgrade: trying to overwrite  /usr/share/accounts/services
  /google-im.service , which is also in package kde-config-telepathy-
  accounts 4:15.12.3-0ubuntu1!

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 10 00:41:19 2016
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1622206/+subscriptions

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

[Touch-packages] [Bug 1633791] Re: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

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

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

Title:
  package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016g-0ubuntu0.16.04
  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: Sat Oct 15 21:22:58 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-30 (107 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tzdata
  Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-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/tzdata/+bug/1633791/+subscriptions

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

[Touch-packages] [Bug 1634176] Re: Change of behavior in handling of 'ip=' on kernel command line now does ipv6 dhcp

[Scott Moser]

** Description changed:

  Changes were initially made under bug 1621507 that changed the behavior
  of the linitramfs when 'ip=' was seen on the kernel command line.  The
  changes were done to support doing an ipv6 dhcp request in addition to
  the expected ipv4 dhcp request.
  
  The result is that in all cases where 'ip=' is found on the kernel command 
line the initramfs will invoke 'dhclient -6'.  In all cases now, the changes 
that have occurred are:
   * initramfs now issues an ipv6 dhclient request
   * if no ipv6 dhcp server is available, the system waits unnecessarily for a 
response.
   * worst case scenario (admittedly unlikely), a system could now get a 
world-routable ipv6 address that previously was not exposed to the internet.
-  * 2 dhclient processes are left running from the initramfs (one -4 and one 
-6). I'm not sure, but I suspect they are not functional as root has been 
pivoted.
+  * 2 dhclient processes are left running from the initramfs (one -4 and one 
-6). I'm not sure, but I suspect they are not functional as root has been 
pivoted.
  
  The implementation has inconsistent behavior based on how quickly or if at 
all a dhcpv4/dhcpv6 server is found.  Things that can happen:
   a.) system uses only dhcpv4, timing out before dhcp6 was found or bug 
1633479 causes dhclient -6 to fail.
   b.) system uses only dhcpv6 address
   c.) system gets no dhclient response (v4 or v6) but uses link-local address 
to successfully reach its mount target.
   d.) the hostname provided in ip= command line not sent in the dhcp request 
as it would be with 'ipconfig' implementation.
  
  The way this should have been handled in a SRU was to require users who
  needed rthe new ipv6 functionality to explicitly request it.
  
  One way this could have been done would have been to extend the 'ip=' command
  line function.  klibc documents the previous ip= syntax at README.ipconfig 
[1].
    ::
  
  My suggestion is to extend the 'autoconf' parameter. Previously the
  supported documented values were 'rarp', 'bootp', 'both', 'dhcp', 'all',
  'off', 'static', 'none'.  I suggest we add 'dhcp6' to the the list.
  
  Additionally, I believe we should revert changes made 0.125ubuntu3 to
  finding further regressions.
  
  --
  [1] 
https://github.com/codehelp/klibc-aarch64/blob/master/usr/kinit/ipconfig/README.ipconfig
  
  Related bugs:
+  * bug 1629972: networking stop incorrectly disconnects from (network) root 
filesystem 
+  * bug 1621507: initramfs-tools configure_networking() fails to dhcp ipv6 
addresses
+  * bug 1628306: network booting fails for iscsi root if no ip is set
+  * bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp 
boot option
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)
-  * bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp 
boot option
-  * bug 1628306: network booting fails for iscsi root if no ip is set
-  * bug 1621507: initramfs-tools configure_networking() fails to dhcp ipv6 
addresses
   * bug 1633619: dhclient -1 exits 0 when no lease found
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu5
  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: Mon Oct 17 11:14:00 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (452 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1634176

Title:
  Change of behavior in handling of 'ip=' on kernel command line now
  does ipv6 dhcp

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

Bug description:
  Changes were initially made under bug 1621507 that changed the
  behavior of the linitramfs when 'ip=' was seen on the kernel command
  line.  The changes were done to support doing an ipv6 dhcp request in
  addition to the expected ipv4 dhcp request.

  The result is that in all cases where 'ip=' is found on the kernel command 
line the initramfs will invoke 'dhclient -6'.  In all cases now, the changes 
that have occurred are:
   * initramfs now issues an ipv6 dhclient request
   * if no ipv6 dhcp server is available, the system waits unnecessarily for a 
response.
   * worst case scenario (admittedly unlikely), a system could now get a 
world-routable ipv6 address that 

[Touch-packages] [Bug 1350782] Re: Upstart does not reopen /var/log/upstart/* logfiles upon log rotation

[Antonio Messina]

We have the same issue. Using "delaycompress" suppresses the "gzip:
stdin: file size changed while zipping" error but upstart will continue
to write on .1 file until this is actually gzipped, which is quite
annoying.

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

Title:
  Upstart does not reopen /var/log/upstart/* logfiles upon log rotation

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Note: this issue is reported from a 12.04 system, but I've confirmed
  the same behavior on a 14.04 system.

  Logrotate configuration for Upstart logs has no postrotate action:

  /var/log/upstart/*.log {
  daily
  missingok
  rotate 7
  compress
  notifempty
nocreate
  }

  As a result, when logs are rotated, upstart keeps open handles on
  deleted log files instead of reopening the new log files:

  # lsof -p1 | fgrep /var/log/upstart
  . . .
  init  1 root8w   REG  253,1   62  789436 
/var/log/upstart/dbus.log.1 (deleted)
  . . .

  From this point on, all subsequent log messages are lost, delivered
  into a deleted file.

  I could not find a way to get the upstart init process to reopen its
  log files, short of restarting _all_ services that log to
  /var/log/upstart/*.log files, which does not seem like a good solution
  at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upstart 1.5-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Thu Jul 31 10:43:25 2014
  InstallationMedia: Ubuntu-Server 10.04.4 LTS "Lucid Lynx" - Release amd64 
(20120214.2)
  MarkForUpload: True
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to precise on 2013-10-23 (280 days ago)

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

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

[Touch-packages] [Bug 1634176] [NEW] Change of behavior in handling of 'ip=' on kernel command line now does ipv6 dhcp

[Scott Moser]

Public bug reported:

Changes were initially made under bug 1621507 that changed the behavior
of the linitramfs when 'ip=' was seen on the kernel command line.  The
changes were done to support doing an ipv6 dhcp request in addition to
the expected ipv4 dhcp request.

The result is that in all cases where 'ip=' is found on the kernel command line 
the initramfs will invoke 'dhclient -6'.  In all cases now, the changes that 
have occurred are:
 * initramfs now issues an ipv6 dhclient request
 * if no ipv6 dhcp server is available, the system waits unnecessarily for a 
response.
 * worst case scenario (admittedly unlikely), a system could now get a 
world-routable ipv6 address that previously was not exposed to the internet.
 * 2 dhclient processes are left running from the initramfs (one -4 and one 
-6). I'm not sure, but I suspect they are not functional as root has been 
pivoted.

The implementation has inconsistent behavior based on how quickly or if at all 
a dhcpv4/dhcpv6 server is found.  Things that can happen:
 a.) system uses only dhcpv4, timing out before dhcp6 was found or bug 1633479 
causes dhclient -6 to fail.
 b.) system uses only dhcpv6 address
 c.) system gets no dhclient response (v4 or v6) but uses link-local address to 
successfully reach its mount target.
 d.) the hostname provided in ip= command line not sent in the dhcp request as 
it would be with 'ipconfig' implementation.

The way this should have been handled in a SRU was to require users who
needed rthe new ipv6 functionality to explicitly request it.

One way this could have been done would have been to extend the 'ip=' command
line function.  klibc documents the previous ip= syntax at README.ipconfig [1].
  ::

My suggestion is to extend the 'autoconf' parameter. Previously the
supported documented values were 'rarp', 'bootp', 'both', 'dhcp', 'all',
'off', 'static', 'none'.  I suggest we add 'dhcp6' to the the list.

Additionally, I believe we should revert changes made 0.125ubuntu3 to
finding further regressions.

--
[1] 
https://github.com/codehelp/klibc-aarch64/blob/master/usr/kinit/ipconfig/README.ipconfig

Related bugs:
 * bug 1629972: networking stop incorrectly disconnects from (network) root 
filesystem 
 * bug 1621507: initramfs-tools configure_networking() fails to dhcp ipv6 
addresses
 * bug 1628306: network booting fails for iscsi root if no ip is set
 * bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp 
boot option
 * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)
 * bug 1633619: dhclient -1 exits 0 when no lease found

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: initramfs-tools 0.125ubuntu5
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: Mon Oct 17 11:14:00 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (452 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** Affects: initramfs-tools (Ubuntu Z-series)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug regression-release regression-update xenial yakkety

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

** Tags added: regression-release xenial

** Also affects: initramfs-tools (Ubuntu Yakkety)
   Importance: Undecided
   Status: Confirmed

** Also affects: initramfs-tools (Ubuntu Z-series)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu Z-series)
   Status: New => Confirmed

** Description changed:

  Changes were initially made under bug 1621507 that changed the behavior
  of the linitramfs when 'ip=' was seen on the kernel command line.  The
  changes were done to support doing an ipv6 dhcp request in addition to
  the expected ipv4 dhcp request.
  
  The result is that in all cases where 'ip=' is found on the kernel command 
line the initramfs will invoke 'dhclient -6'.  In all cases now, the changes 
that have occurred are:
-  * initramfs now issues an ipv6 dhclient request
-  * if no ipv6 dhcp server is available, the system waits unnecessarily for a 
response.
-  * worst case scenario (admittedly unlikely), a system could now get a 
world-routable ipv6 address that previously was not exposed to the internet.
+  * initramfs now issues an ipv6 dhclient request
+  * if 

[Touch-packages] [Bug 1630324] Re: Broadcom wifi dies in 60s cycles with 4.8 kernel

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Broadcom wifi dies in 60s cycles with 4.8 kernel

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects
  fine, but dies for around 5-10s (the signal dies completely, tools
  like wavemon show "no interface data") in regular cycles of about 60s.
  dmesg logs the same brcmfmac errors every minute or so: "brcmfmac:
  brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)".

  network-manager's icon doesn't change however (remains as if the
  adapter was connected).

  This issue started to affect me when using kernel 4.8 on Ubuntu 16.04.
  I previously used kernel 4.7 and did not experience this bug.

  I booted the 16.10 daily build and experienced exactly the same
  errors.

  $ lspci | grep BCM4350
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)

  $ dmesg | grep brcm
  [5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
  [5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [   74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [  142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  ...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  Uname: Linux 4.8.0-040800-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct  4 14:15:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-26 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.29  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Guava Guest 1  68ae8dc2-ab23-42ef-9e41-ac8e9d91385a  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1066414] Re: cairo-5c ftbfs in quantal

[Bug Watch Updater]

** Changed in: cairo-5c (Debian)
   Status: New => Fix Released

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

Title:
  cairo-5c ftbfs in quantal

Status in cairo-5c package in Ubuntu:
  Confirmed
Status in freetype package in Ubuntu:
  Invalid
Status in cairo-5c package in Debian:
  Fix Released

Bug description:
  cairo ftbfs in quantal, failing some test cases. quantal and sid use
  the same cairo version, but the tests fail in quantal and succeed in
  sid.

  set-font  failed: pixel mismatch 0xe000 not similar to 0x0 at 
22 10
  set-font-size failed: pixel mismatch 0xf800 not similar to 0x0 at 
56 12
  set-font-matrix   failed: pixel mismatch 0xf800 not similar to 0x0 at 
6 22
  show-text failed: pixel mismatch 0xe000 not similar to 0x0 at 
27 10
  text-path failed: pixel mismatch 0x5b00 not similar to 
0x4400 at 53 16
  text-extents  failed: pixel mismatch 0xff1f1f1f not similar to 
0x at 27 30
  font-extents  failed: font_extents returned wrong value: {ascent = 
11, descent = 3, height = 14, max_x_advance = 16, max_y_advance = 0} != {ascent 
= 12, descent = 3, height = 14, max_x_advance = 16, max_y_advance = 0}

  all the test regressions are font related; sid has freetype 2.4.9,
  quantal 2.4.10, so either the test cases need adjustment, or this
  could be a regression in freetype.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[RAMupgrade]

Problem persists (alarm not waking phone) after updating to latest clock
app. Typically the problem occurs 1 or 2 days after a reset and always
comes back. My device has a bare minimum of apps installed and I don't
use any scopes, aside from the main home screen. Bluetooth and GPS
permanently off. Wi-fi rarely on. Device set to request passcode upon
waking.

I use both single-instance and repeating alarms. Often the alarm will
wake the phone 1 hour after the alarm is scheduled.

So far, I cannot find an obvious and repeatable trigger, from a user
perspective.


Nexus 4 running Ubuntu 15.04 (OTA-13), image 20160913.

-- 
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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Scott Moser]

Dan,
The use case I found was in initramfs-tools, which recently SRU'd a change that 
uses dhclient to support 'ip=' command lines and dhcpv6.

-- 
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 1631789] Re: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: EOF on stdin at conffile prompt

[Robie Basak]

It looks to me that this is either a bug in unattended-upgrades, or
intended behaviour that due to the conffile prompt unattended-upgrades
is supposed to fail and requires user intervention to answer the prompt.
I'm not sure which.

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

Title:
  package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: EOF on stdin at conffile prompt

Status in ntp package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Looks like unattended-upgrades failed?

  I just ran the update again and it installed an altered config file.

  #> apt-get install ntpdate
  Setting up ntpdate (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...

  Configuration file '/etc/network/if-up.d/ntpdate'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** ntpdate (Y/I/N/O/D/Z) [default=N] ? y
  Installing new version of config file /etc/network/if-up.d/ntpdate ...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-96-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  Date: Sun Oct  9 04:07:26 2016
  DpkgHistoryLog:
   Start-Date: 2016-10-09  04:07:05
   Upgrade: chromium-codecs-ffmpeg-extra:amd64 
(52.0.2743.116-0ubuntu0.14.04.1.1134, 53.0.2785.143-0ubuntu0.14.04.1.1142), 
chromium-browser-l10n:amd64 (52.0.2743.116-0ubuntu0.14.04.1.1134, 
53.0.2785.143-0ubuntu0.14.04.1.1142), chromium-browser:amd64 
(52.0.2743.116-0ubuntu0.14.04.1.1134, 53.0.2785.143-0ubuntu0.14.04.1.1142), 
ntpdate:amd64 (4.2.6.p5+dfsg-3ubuntu2.14.04.5, 4.2.6.p5+dfsg-3ubuntu2.14.04.10)
  DpkgTerminalLog: Log started: 2016-10-09  04:07:05
  ErrorMessage: EOF on stdin at conffile prompt
  InstallationDate: Installed on 2014-04-29 (894 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: ntp
  Title: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to 
install/upgrade: EOF on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: dhclient -1 exits 0 when no lease found

[Scott Moser]

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Medium

** Changed in: isc-dhcp (Ubuntu)
   Status: New => 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/1633619

Title:
  dhclient -1 exits 0 when no lease found

Status in isc-dhcp package in Ubuntu:
  Confirmed

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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Igor]

Sane for my Asus X555UB , the codec is Realtek ALC256

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade

[Paolo]

** Description changed:

- After the last automatic upgrade, the system suggested a restart to finalize 
the installation.
+ After the last automatic upgrade (kernel?), the system suggested a restart to 
finalize the installation.
  Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set a resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.
  
  My PC is an Acer Veriton X4610G
  CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
  RAM: 4GiB (128MiB VGA shared)
  
  I use an UBUNTU 16.04 LTS 64-bit
- 
  
  Thanks for any feedback!
  Paolo
  
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 17 15:39:54 2016
  DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
  InstallationDate: Installed on 2015-05-15 (521 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
-  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. 
-  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp.
+  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Veriton X4610G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat 
vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton X4610G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton X4610G
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 17 15:32:10 2016
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputAT Translated Set 2 keyboard KEYBOARD, id 8
-  inputImPS/2 Generic Wheel Mouse MOUSE, id 9
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputAT Translated Set 2 keyboard KEYBOARD, id 8
+  inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

** Description changed:

  After the last automatic 

[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade

[Paolo]

** Summary changed:

- Driver video doesn't work properly
+ Driver video doesn't work properly after Upgrade

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

Title:
  Driver video doesn't work properly after Upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last automatic upgrade, the system suggested a restart to finalize 
the installation.
  Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set a resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.

  My PC is an Acer Veriton X4610G
  CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
  RAM: 4GiB (128MiB VGA shared)

  I use an UBUNTU 16.04 LTS 64-bit

  
  Thanks for any feedback!
  Paolo

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 17 15:39:54 2016
  DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
  InstallationDate: Installed on 2015-05-15 (521 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Veriton X4610G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat 
vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton X4610G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton X4610G
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 17 15:32:10 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp

[Franck]

Ok, I just asked on firefox-dev mailing list...

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

Title:
  From v49.0, Firefox needs read access to @{PROC}/net/arp

Status in apparmor package in Ubuntu:
  New

Bug description:
  Since the latest upgrade of Firefox to 49.0, it will need read access
  to @{PROC}/net/arp

  I don't know what the security implications are, so I don't know if we
  want to give read access to explicitely deny it. Both seem to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor-profiles 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 29 16:55:21 2016
  InstallationDate: Installed on 2015-10-04 (361 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus 
mediation is enabled
   Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus 
mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
  modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
  modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
  mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
  mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
  mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser: 
2015-10-05T12:02:05.273141
  mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: 
2016-04-13T19:13:25.829679
  mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
  mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
  mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
  mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
  mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
  mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
  mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981

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

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

[Touch-packages] [Bug 1634152] [NEW] Driver video doesn't work properly

[Paolo]

Public bug reported:

After the last automatic upgrade, the system suggested a restart to finalize 
the installation.
Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set a resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.

My PC is an Acer Veriton X4610G
CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
RAM: 4GiB (128MiB VGA shared)

I use an UBUNTU 16.04 LTS 64-bit


Thanks for any feedback!
Paolo

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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct 17 15:39:54 2016
DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
InstallationDate: Installed on 2015-05-15 (521 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. 
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Veriton X4610G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat 
vesafb.invalid=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago)
dmi.bios.date: 05/30/2011
dmi.bios.vendor: Acer
dmi.bios.version: P01-B0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Veriton X4610G
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Veriton X4610G
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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 1:1.0.12-1build2
xserver.bootTime: Mon Oct 17 15:32:10 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 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/1634152

Title:
  Driver video doesn't work properly

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last automatic upgrade, the system suggested a restart to finalize 
the installation.
  Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set a resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.

  My PC is an Acer Veriton X4610G
  CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
  RAM: 4GiB (128MiB VGA shared)

  I use an UBUNTU 16.04 LTS 64-bit

  
  Thanks for any feedback!
  Paolo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 

[Touch-packages] [Bug 1634151] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld

[Robin]

Public bug reported:

Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system
the message occured

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Oct 17 13:29:10 2016
ErrorMessage: vereistenproblemen - triggers blijven onbehandeld
InstallationDate: Installed on 2016-05-04 (166 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: 
vereistenproblemen - triggers blijven onbehandeld
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago)

** Affects: gconf (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 gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1634151

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade:
  vereistenproblemen - triggers blijven onbehandeld

Status in gconf package in Ubuntu:
  New

Bug description:
  Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system
  the message occured

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 17 13:29:10 2016
  ErrorMessage: vereistenproblemen - triggers blijven onbehandeld
  InstallationDate: Installed on 2016-05-04 (166 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: 
vereistenproblemen - triggers blijven onbehandeld
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago)

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

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

[Touch-packages] [Bug 1631575] Re: Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service not loaded.

[Launchpad Bug Tracker]

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

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

** Changed in: android-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failed to stop android-tools-adbd.service: Unit android-tools-
  adbd.service not loaded.

Status in android-tools package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  dist=upgrade fails with:

  
  Preparing to unpack 
.../android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  invoke-rc.d: initscript android-tools-adbd, action "stop" failed.
  dpkg: warning: subprocess old pre-removal script returned error exit status 5
  dpkg: trying script from the new package instead ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  dpkg: error processing archive 
/var/cache/apt/archives/android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb
 (--unpack):

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.5
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Sat Oct  8 08:43:03 2016
  InstallationDate: Installed on 2015-04-10 (546 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-08-28 (40 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1631575] Re: Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service not loaded.

[Launchpad Bug Tracker]

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

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

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failed to stop android-tools-adbd.service: Unit android-tools-
  adbd.service not loaded.

Status in android-tools package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  dist=upgrade fails with:

  
  Preparing to unpack 
.../android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  invoke-rc.d: initscript android-tools-adbd, action "stop" failed.
  dpkg: warning: subprocess old pre-removal script returned error exit status 5
  dpkg: trying script from the new package instead ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  dpkg: error processing archive 
/var/cache/apt/archives/android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb
 (--unpack):

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.5
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Sat Oct  8 08:43:03 2016
  InstallationDate: Installed on 2015-04-10 (546 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-08-28 (40 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp

[Vincas Dargis]

Maybe we should ask Firefox devs what they mean by that? net/arp
contains rather sensitive info...

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

Title:
  From v49.0, Firefox needs read access to @{PROC}/net/arp

Status in apparmor package in Ubuntu:
  New

Bug description:
  Since the latest upgrade of Firefox to 49.0, it will need read access
  to @{PROC}/net/arp

  I don't know what the security implications are, so I don't know if we
  want to give read access to explicitely deny it. Both seem to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor-profiles 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 29 16:55:21 2016
  InstallationDate: Installed on 2015-10-04 (361 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus 
mediation is enabled
   Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus 
mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
  modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
  modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
  mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
  mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
  mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser: 
2015-10-05T12:02:05.273141
  mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: 
2016-04-13T19:13:25.829679
  mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
  mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
  mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
  mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
  mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
  mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
  mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981

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

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

[Touch-packages] [Bug 1600088] Re: fcitx does not get terminated on user logout

[Gunnar Hjalmarsson]

@krdondon: It has passed some time since you reported this issue. Is it
still present on a newly installed 16.10 or a fully updated 16.10. If
you are still on the Alpha installation, you can make sure the system is
fully updated via these commands:

sudo apt update
sudo apt full-upgrade

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

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

Title:
  fcitx does not get terminated on user logout

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  http://ubuntuforums.org/showthread.php?t=2330069
  https://youtu.be/etcudv3GxwU UCC..
  https://youtu.be/tz81PNqFBvo new.. UCC
  Linux tester 4.7.0-999-lowlatency #201607012202 SMP PREEMPT Sat Jul 2 
02:08:47 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu 16.10 desktop 64bit. July 0.2 days degree .. version. test


  Logout (even)
  It does not shut down.
  Continue to start further.
  The new Ubuntu 16.10
  Fixed bugs.(Normal until recently.)

  However, between the week.
  Old bugs are repeated like. 

  :)Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: fcitx 1:4.2.9.1-1ubuntu1
  Uname: Linux 4.7.0-999-lowlatency x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul  8 12:02:47 2016
  InstallationDate: Installed on 2016-07-02 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160701)
  PackageArchitecture: all
  SourcePackage: fcitx
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1403955] Re: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0

[Anastasia]

** Changed in: juju-core
   Status: Triaged => Won't Fix

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

Title:
  DHCP's "Option interface-mtu 9000" is being ignored on bridge
  interface br0

Status in juju-core:
  Won't Fix
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  In an env with jumbo frames enabled, and using MAAS as DHCP server,
  the client receives the following IPv4 lease:

  $ cat /var/lib/dhcp/dhclient.br0.leases
  lease {
    interface "br0";
    fixed-address 10.230.20.26;
    filename "pxelinux.0";
    option subnet-mask 255.255.248.0;
    option dhcp-lease-time 43200;
    option routers 10.230.16.1;
    option dhcp-message-type 5;
    option dhcp-server-identifier 10.230.20.1;
    option domain-name-servers 10.230.20.1;
    option interface-mtu 9000;
    option broadcast-address 10.230.23.255;
    option domain-name "ctsstack.qa.1ss";
    renew 3 2014/12/17 16:48:15;
    rebind 3 2014/12/17 21:52:09;
    expire 3 2014/12/17 23:22:09;
  }

  The interfaces show the following config after boot:

  $ ifconfig br0
  br0   Link encap:Ethernet  HWaddr a0:d3:c1:01:9d:58
    inet addr:10.230.20.26  Bcast:10.230.23.255  Mask:255.255.248.0
    inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:68713489 (68.7 MB)  TX bytes:213710979 (213.7 MB)

  $ ifconfig eth0
  eth0  Link encap:Ethernet  HWaddr a0:d3:c1:01:9d:58
    inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
    TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2320560616 (2.3 GB)  TX bytes:3562885157 (3.5 GB)
    Interrupt:32

  
  "option interface-mtu 9000;" from the lease file is being ignored by br0. 
Could it be related to eth0 MTU size? If that's the case, shouldn't both 
interfaces be updated?

  Other info:

  $ brctl show br0
  bridge name   bridge id   STP enabled interfaces
  br0   8000.a0d3c1019d58   no  eth0

  $ cat /etc/network/eth0.config
  iface eth0 inet manual

  auto br0
  iface br0 inet dhcp
    bridge_ports eth0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions

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

[Touch-packages] [Bug 1631627] Re: Unity 8 freezes on Nouveau

[Emanuele Sorce]

I have a Nvidia GT 730 and also happens to me. Unity 7 works fine

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

Title:
  Unity 8 freezes on Nouveau

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

Bug description:
  I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes
  after I do some clicking around the desktop (using Browser, System
  Settings and the like), I am running it on Nouveau driver for GTX970M,
  I refrained from installing proprietary drivers to test Unity 8, but
  it is unusable and after it freezes I can only power off my laptop as
  nothing works. Is this a known issue? Also Unity 7 does not load at
  all, but I will post a separate bug for that.

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

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

[Touch-packages] [Bug 1380480] Re: network disabled after suspend - resume

[Seth Arnold]

Hans, note that this bug was opened before systemd was used as a system
init.

A quick skim of this bug's history suggests that it's been polluted
beyond use.

If you're having trouble, please file a new bug. With luck, it'll be
focused on one thing and therefor fixable.

Thanks

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

Title:
  network disabled after suspend - resume

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Daniel Oehry]

The Problem persists in Ubuntu 16.10. The workaround (removing appmenu-
qt5) does not help anymore.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1600088] Re: ubuntu 16.10 fctix(Not terminated). bug..

[Aron Xu]

Looks more like a session tracking issue and the deskop session isn't
terminated cleanly, reassigning to lightdm to get some advices.

** Package changed: fcitx (Ubuntu) => lightdm (Ubuntu)

** Summary changed:

- ubuntu 16.10 fctix(Not terminated). bug..
+ fcitx does not get terminated on user logout

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

Title:
  fcitx does not get terminated on user logout

Status in lightdm package in Ubuntu:
  New

Bug description:
  http://ubuntuforums.org/showthread.php?t=2330069
  https://youtu.be/etcudv3GxwU UCC..
  https://youtu.be/tz81PNqFBvo new.. UCC
  Linux tester 4.7.0-999-lowlatency #201607012202 SMP PREEMPT Sat Jul 2 
02:08:47 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu 16.10 desktop 64bit. July 0.2 days degree .. version. test


  Logout (even)
  It does not shut down.
  Continue to start further.
  The new Ubuntu 16.10
  Fixed bugs.(Normal until recently.)

  However, between the week.
  Old bugs are repeated like. 

  :)Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: fcitx 1:4.2.9.1-1ubuntu1
  Uname: Linux 4.7.0-999-lowlatency x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul  8 12:02:47 2016
  InstallationDate: Installed on 2016-07-02 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160701)
  PackageArchitecture: all
  SourcePackage: fcitx
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1634017] Re: usb mouse and keyboard freeze after login

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => xorg (Ubuntu)

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

Title:
  usb mouse and keyboard freeze after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have a usb logitech wireless mouse and keyboard connected via an aten usb 
switchbox to my computers (desktop and laptop). With release 14.04 I did not 
have any issues. I have now upgraded my desktop to 16.04 and did a clean 
install on my laptop with 16.04. Now I have the following phenomena:
  Mouse and Keyboard are working fine when I have the login screen. However 
after login in my desktop (gnome) comes up and my mouse pointer is shortly (1s) 
disappearing and reappears.
  Then I have an approximately 2min freeze time for mouse and keyboard (meaning 
no response to the usb mouse and keyboard). After that everything is working 
fine. On my laptop there is no interruption using my internal touchpad and 
keyboard. This happens on both computers. Switching back and forth is seamless 
unless the period from switching from one computer to the other takes to long 
(can not specify the exact time here maybe 1 hour). Then I have the above 
phenomenon.
  I have already asked the question and checked the ubuntuforum with no success.
  Best regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Oct 17 09:22:43 2016
  InstallationDate: Installed on 2016-10-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1634017] [NEW] usb mouse and keyboard freeze after login

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,
I have a usb logitech wireless mouse and keyboard connected via an aten usb 
switchbox to my computers (desktop and laptop). With release 14.04 I did not 
have any issues. I have now upgraded my desktop to 16.04 and did a clean 
install on my laptop with 16.04. Now I have the following phenomena:
Mouse and Keyboard are working fine when I have the login screen. However after 
login in my desktop (gnome) comes up and my mouse pointer is shortly (1s) 
disappearing and reappears.
Then I have an approximately 2min freeze time for mouse and keyboard (meaning 
no response to the usb mouse and keyboard). After that everything is working 
fine. On my laptop there is no interruption using my internal touchpad and 
keyboard. This happens on both computers. Switching back and forth is seamless 
unless the period from switching from one computer to the other takes to long 
(can not specify the exact time here maybe 1 hour). Then I have the above 
phenomenon.
I have already asked the question and checked the ubuntuforum with no success.
Best regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.16
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Mon Oct 17 09:22:43 2016
InstallationDate: Installed on 2016-10-10 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade xenial
-- 
usb mouse and keyboard freeze after login
https://bugs.launchpad.net/bugs/1634017
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1633794] Re: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in tzdata package in Ubuntu:
  New

Bug description:
  r

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016g-0ubuntu0.16.04
  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
  AptOrdering:
   tzdata: Install
   tzdata: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Oct 15 21:40:59 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-08-04 (72 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tzdata
  Title: package tzdata 2016g-0ubuntu0.16.04 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)

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

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

[Touch-packages] [Bug 1600088] [NEW] ubuntu 16.10 fctix(Not terminated). bug..

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

http://ubuntuforums.org/showthread.php?t=2330069
https://youtu.be/etcudv3GxwU UCC..
https://youtu.be/tz81PNqFBvo new.. UCC
Linux tester 4.7.0-999-lowlatency #201607012202 SMP PREEMPT Sat Jul 2 02:08:47 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
ubuntu 16.10 desktop 64bit. July 0.2 days degree .. version. test


Logout (even)
It does not shut down.
Continue to start further.
The new Ubuntu 16.10
Fixed bugs.(Normal until recently.)

However, between the week.
Old bugs are repeated like. 

:)Thank you

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: fcitx 1:4.2.9.1-1ubuntu1
Uname: Linux 4.7.0-999-lowlatency x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul  8 12:02:47 2016
InstallationDate: Installed on 2016-07-02 (5 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160701)
PackageArchitecture: all
SourcePackage: fcitx
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety
-- 
ubuntu 16.10 fctix(Not terminated). bug..
https://bugs.launchpad.net/bugs/1600088
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lightdm 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 1591898] Re: NetworkManager should parse system config from /run/NetworkManager

[Bug Watch Updater]

** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Wishlist

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

Title:
  NetworkManager should parse system config from /run/NetworkManager

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  NetworkManager currently only reads configuration files from
  /etc/NetworkManager/NetworkManager.conf and
  /etc/NetworkManager/conf.d.

  It should be possible to also read and write config from
  /run/NetworkManager/conf.d; so that any changes to the system
  configuration done by NM would land in /run, rather than modifying
  /etc/ (which is meant only to be changed by the system owner). This
  would also allow other system tools to add configuration for
  NetworkManager to use, that might be dynamically written.

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

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

[Touch-packages] [Bug 1634063] Re: tst_QJSEngine::toFixed() will fail on i386

[Timo Jyrinki]

** Description changed:

+ Update: These tests actually weren't being executed in Ubuntu before.
+ 
  With the to-be-uploaded new patch version of Qt 5.6.1, the function will
  start to fail on i386 and i386 only:
  
  FAIL!  : tst_QJSEngine::toFixed() Compared values are not the same
     Actual   (result.toString()) : "12.0"
     Expected (QStringLiteral("12.1")): "12.1"
     Loc: [tst_qjsengine.cpp(3797)]
  
  Also failing are seven other similar tests:
  FAIL!  : tst_qqmlqt::rect() Compared values are not the same
-Actual   (qvariant_cast(object->property("test2"))): QRectF(-10,13 
100x109.6) (bottomright 90,122.6)
-Expected (QRectF(-10, 13, 100, 109.6)) : QRectF(-10,13 
100x109.6) (bottomright 90,122.6)
-Loc: [tst_qqmlqt.cpp(277)]
+    Actual   (qvariant_cast(object->property("test2"))): QRectF(-10,13 
100x109.6) (bottomright 90,122.6)
+    Expected (QRectF(-10, 13, 100, 109.6)) : QRectF(-10,13 
100x109.6) (bottomright 90,122.6)
+    Loc: [tst_qqmlqt.cpp(277)]
  FAIL!  : tst_qqmlqt::point() Compared values are not the same
-Actual   (qvariant_cast(object->property("test2"))): 
QPointF(-3,109.2)
-Expected (QPointF(-3, 109.2))   : 
QPointF(-3,109.2)
-Loc: [tst_qqmlqt.cpp(298)]
+    Actual   (qvariant_cast(object->property("test2"))): 
QPointF(-3,109.2)
+    Expected (QPointF(-3, 109.2))   : 
QPointF(-3,109.2)
+    Loc: [tst_qqmlqt.cpp(298)]
  FAIL!  : tst_qqmlqt::size() Compared values are not the same
-Actual   (qvariant_cast(object->property("test2"))): 
QSizeF(3x109.2)
-Expected (QSizeF(3, 109.2)): 
QSizeF(3x109.2)
-Loc: [tst_qqmlqt.cpp(318)]
+    Actual   (qvariant_cast(object->property("test2"))): 
QSizeF(3x109.2)
+    Expected (QSizeF(3, 109.2)): 
QSizeF(3x109.2)
+    Loc: [tst_qqmlqt.cpp(318)]
  FAIL!  : tst_qqmlqt::vector2d() Compared values are not the same
-Loc: [tst_qqmlqt.cpp(338)]
+    Loc: [tst_qqmlqt.cpp(338)]
  FAIL!  : tst_qqmlqt::vector3d() Compared values are not the same
-Loc: [tst_qqmlqt.cpp(358)]
+    Loc: [tst_qqmlqt.cpp(358)]
  FAIL!  : tst_qqmlqt::vector4d() Compared values are not the same
-Loc: [tst_qqmlqt.cpp(378)]
+    Loc: [tst_qqmlqt.cpp(378)]
  FAIL!  : tst_qqmlqt::quaternion() Compared values are not the same
-Loc: [tst_qqmlqt.cpp(398)]
+    Loc: [tst_qqmlqt.cpp(398)]

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

Title:
  tst_QJSEngine::toFixed() will fail on i386

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  Update: These tests actually weren't being executed in Ubuntu before.

  With the to-be-uploaded new patch version of Qt 5.6.1, the function
  will start to fail on i386 and i386 only:

  FAIL!  : tst_QJSEngine::toFixed() Compared values are not the same
     Actual   (result.toString()) : "12.0"
     Expected (QStringLiteral("12.1")): "12.1"
     Loc: [tst_qjsengine.cpp(3797)]

  Also failing are seven other similar tests:
  FAIL!  : tst_qqmlqt::rect() Compared values are not the same
     Actual   (qvariant_cast(object->property("test2"))): QRectF(-10,13 
100x109.6) (bottomright 90,122.6)
     Expected (QRectF(-10, 13, 100, 109.6)) : QRectF(-10,13 
100x109.6) (bottomright 90,122.6)
     Loc: [tst_qqmlqt.cpp(277)]
  FAIL!  : tst_qqmlqt::point() Compared values are not the same
     Actual   (qvariant_cast(object->property("test2"))): 
QPointF(-3,109.2)
     Expected (QPointF(-3, 109.2))   : 
QPointF(-3,109.2)
     Loc: [tst_qqmlqt.cpp(298)]
  FAIL!  : tst_qqmlqt::size() Compared values are not the same
     Actual   (qvariant_cast(object->property("test2"))): 
QSizeF(3x109.2)
     Expected (QSizeF(3, 109.2)): 
QSizeF(3x109.2)
     Loc: [tst_qqmlqt.cpp(318)]
  FAIL!  : tst_qqmlqt::vector2d() Compared values are not the same
     Loc: [tst_qqmlqt.cpp(338)]
  FAIL!  : tst_qqmlqt::vector3d() Compared values are not the same
     Loc: [tst_qqmlqt.cpp(358)]
  FAIL!  : tst_qqmlqt::vector4d() Compared values are not the same
     Loc: [tst_qqmlqt.cpp(378)]
  FAIL!  : tst_qqmlqt::quaternion() Compared values are not the same
     Loc: [tst_qqmlqt.cpp(398)]

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Leo Arias]

I tested this in a trusty lxc. Updated sudo to 1.8.9p5-1ubuntu1.3 and:

# mkdir -p /snap/bin
# cp $(which echo) /snap/bin/echo-test
# su ubuntu
$ sudo echo-test test
test

I'm marking it as verified. Thanks Brian.

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

Re: [Touch-packages] [Bug 1633851] Re: Middle-click clipboard no longer works

[Oxwivi]

Whether the equivalent tap exists or not is besides the point, because, for
one, libinput is supposed to handle what kind of tap it is, and second,
middle-clicks are still triggered by tapping top-right corner of the
touchpad.

On Mon, Oct 17, 2016 at 10:31 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> The equivalent touchpad tap actually doesn't exist in Xorg by default
> anymore. To get it back (click with three fingers) you need:
>synclient ClickFinger3=2
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633851
>
> Title:
>   Middle-click clipboard no longer works
>
> Status in Canonical System Image:
>   New
> Status in content-hub package in Ubuntu:
>   New
> Status in ubuntu-ui-toolkit package in Ubuntu:
>   New
> Status in unity8 package in Ubuntu:
>   New
>
> Bug description:
>   Under X, any selected text would be automatically be added to a
>   seperate clipboard whose contents could be pasted by pressing the
>   middle-click button or the equivalent touchpad tap.
>
>   I understand it's an X functionality, and I'm asking it to be
>   implemented in Mir.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1633851/+subscriptions
>

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

Title:
  Middle-click clipboard no longer works

Status in Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Under X, any selected text would be automatically be added to a
  seperate clipboard whose contents could be pasted by pressing the
  middle-click button or the equivalent touchpad tap.

  I understand it's an X functionality, and I'm asking it to be
  implemented in Mir.

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

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

[Touch-packages] [Bug 1633851] Re: Middle-click clipboard no longer works

[Launchpad Bug Tracker]

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

** Changed in: content-hub (Ubuntu)
   Status: New => Confirmed

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

Title:
  Middle-click clipboard no longer works

Status in Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Under X, any selected text would be automatically be added to a
  seperate clipboard whose contents could be pasted by pressing the
  middle-click button or the equivalent touchpad tap.

  I understand it's an X functionality, and I'm asking it to be
  implemented in Mir.

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

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

[Touch-packages] [Bug 1633851] Re: Middle-click clipboard no longer works

[Launchpad Bug Tracker]

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

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

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

Title:
  Middle-click clipboard no longer works

Status in Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Under X, any selected text would be automatically be added to a
  seperate clipboard whose contents could be pasted by pressing the
  middle-click button or the equivalent touchpad tap.

  I understand it's an X functionality, and I'm asking it to be
  implemented in Mir.

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

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

[Touch-packages] [Bug 1633851] Re: Middle-click clipboard no longer works

[Christian Dywan]

** No longer affects: ubuntu-ui-toolkit (Ubuntu)

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

Title:
  Middle-click clipboard no longer works

Status in Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Under X, any selected text would be automatically be added to a
  seperate clipboard whose contents could be pasted by pressing the
  middle-click button or the equivalent touchpad tap.

  I understand it's an X functionality, and I'm asking it to be
  implemented in Mir.

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

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

[Touch-packages] [Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

[Martin Pitt]

Discussed that upstream: The gist of it is:

- 8< --
if you want to be an early boot service, then you should use something like 
this:

Before=sysinit.target

And that's all.

Inserting yourself between the sockets and the regular services (which your 
suggested deps do) is highly problematic, if you actually intend to make use of 
the sockets, as then you will make the system hang, as to fulfill your requests 
you need the services you are delaying...
- 8< --

So replacing cloud-init.service's

  Before=basic.target
  Before=dbus.socket

with

  Before=sysinit.target

should DTRT. dbus.socket (and all other sockets) will start after
sysinit.target as part of basic.target.

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

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

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Committed
Status in D-Bus:
  Unknown
Status in cloud-init package in Ubuntu:
  Fix Released
Status in dbus package in Ubuntu:
  Won't Fix

Bug description:
  During boot, cloud-init does DNS resolution checks to if particular
  metadata services are available (in order to determine which cloud it
  is running on).  These checks happen before systemd-resolved is up[0]
  and if they resolve unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+subscriptions

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