[Touch-packages] [Bug 1657656] [NEW] bug

[jeremyTran]

Public bug reported:

can you check it? 
And improve it better?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jan 19 14:01:50 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:2102]
InstallationDate: Installed on 2016-12-23 (26 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. K55A
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=b5bae7f7-be60-41a3-bd39-85c1eac84db6 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55A.403
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.403:bd08/03/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Jan 19 10:45:18 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9964 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  can you check it? 
  And improve it better?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 19 14:01:50 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2102]
  InstallationDate: Installed on 2016-12-23 (26 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=b5bae7f7-be60-41a3-bd39-85c1eac84db6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.403
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.403:bd08/03/2012:svnASUSTeK

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

[ChristianEhrhardt]

** Also affects: base-passwd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: base-passwd (Ubuntu Xenial)
   Status: New => Won't Fix

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

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

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

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

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

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

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

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

  12 microg5 running

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

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

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

  [Regression Potential]

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

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

  [Other Info]

   * None at this time.

  <...>

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

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones

[Konrad Zapałowicz]

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)

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

Title:
  Can not pair with bluetooth headphones

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 
wireless aebt).
  (If it matters, I *CAN* pair and use it on another laptop with Linux and with 
my android smartphone. So headset itself is working well.)

  Here is how I try to pair:
  $ bluetoothctl
  [NEW] Controller 54:27:1E:33:4B:85 impedance [default]
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes
  [bluetooth]# scan on

  I tried to put my headset in pairing mode just before and after
  issuing "scan on" command. It ends up with nothing - I waited for 3-5
  minutes. For example, my smartphone pairs with the headset within 5-15
  seconds, my laptop pairs with the headset within about 30 seconds.

  =

  Here is info

  $ hciconfig -a
  hci0:   Type: Primary  Bus: USB
  BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
  UP RUNNING PSCAN ISCAN
  RX bytes:4475 acl:0 sco:0 events:565 errors:0
  TX bytes:7214 acl:0 sco:0 commands:487 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'impedance'
  Class: 0x1c0104
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Desktop workstation
  HCI Version: 4.0 (0x6)  Revision: 0x1000
  LMP Version: 4.0 (0x6)  Subversion: 0x220e
  Manufacturer: Broadcom Corporation (15)

  =

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  =

  Bluez packages installed:
  $ dpkg -l | grep bluez
  ii  bluez
  ii  bluez-btsco
  ii  bluez-cups
  ii  bluez-hcidump
  ii  bluez-obexd
  ii  bluez-tools
  ii  libkf5bluezqt-data
  ii  libkf5bluezqt6:amd64
  ii  qml-module-org-kde-bluezqt:amd64

  =

  $ dmesg | grep -i blue
  [4.632406] Bluetooth: Core ver 2.21
  [4.632414] Bluetooth: HCI device and connection manager initialized
  [4.632416] Bluetooth: HCI socket layer initialized
  [4.632417] Bluetooth: L2CAP socket layer initialized
  [4.632420] Bluetooth: SCO socket layer initialized
  [4.644619] Bluetooth: hci0: BCM: chip id 63
  [4.660554] Bluetooth: hci0: impedance
  [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [4.661798] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
  [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
  [   15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.061604] Bluetooth: BNEP filters: protocol multicast
  [   15.061606] Bluetooth: BNEP socket layer initialized
  [   48.001553] Bluetooth: RFCOMM TTY layer initialized
  [   48.001558] Bluetooth: RFCOMM socket layer initialized
  [   48.001562] Bluetooth: RFCOMM ver 1.11
  [  615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp 
bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc 
nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor 
snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq 
btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd intel_cstate input_leds intel_rapl_perf 8021q garp mrp stp 
serio_raw llc b43 mac80211 snd_hda_codec_realtek snd_hda_codec_generic

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Jan  7 22:36:22 2017
  InstallationDate: Installed on 2014-07-05 (917 days ago)
  InstallationMedia: Kub

[Touch-packages] [Bug 1649086] Re: W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

[Bump]

Ok who is the developer of that repository?

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

Title:
  W: Invalid 'Date' entry in Release file
  
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

Status in apt package in Ubuntu:
  Invalid

Bug description:
  root@ubuntu:/var/lib/apt/lists# apt-get update
  Hit:1 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu yakkety InRelease
  Hit:3 http://ppa.launchpad.net/unit193/encryption/ubuntu yakkety InRelease
  
  Hit:4 http://es.archive.ubuntu.com/ubuntu yakkety InRelease   
  
  Hit:5 http://repository.spotify.com stable InRelease  
  
  Hit:6 http://ppa.launchpad.net/wine/wine-builds/ubuntu yakkety InRelease  
  
  Get:7 http://es.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]  
 
  Get:8 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]   
 
  Get:9 http://es.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 
kB]
  Hit:2 http://screenshots.getdeb.net yakkety-getdeb InRelease  

  Ign:10 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
InRelease   
  Hit:11 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
Release
  Fetched 306 kB in 1s (242 kB/s)
  Reading package lists... Done
  W: Invalid 'Date' entry in Release file 
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release
  root@ubuntu:/var/lib/apt/lists# 

  
  The file is as 
'developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release' 
follows:

  Origin: NVIDIA
  Label: NVIDIA CUDA
  Architecture: x86_64
  Date: Fri, 23 Sep 2016 18:52:52 -0700
  MD5Sum:
   3213a453e90b070bc10f329d2fe7f1a384080 Packages
   c1660fe24223ec9b07b04de1dfb3777122493 Packages.gz
  SHA1:
   60f8bd97333efb0bce147702712aab654ba3469b84080 Packages
   04e6ceaf9bcbcd3b36a9cc390b58110da138b7cd22493 Packages.gz
  SHA256:
   44a4473829b9403e7e2d36c43757b4d4ce8334b5804d90d920bd92edaf346241
84080 Packages
   f179e19b7c5b47d5c7247b5d6f37eb2ab2fba168ac70531dd02a0a1cda756038
22493 Packages.gz

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

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

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

[Aron Xu]

** Changed in: network-manager (Ubuntu Xenial)
   Status: Triaged => In Progress

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Regression Potential]

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

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

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

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

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

[Touch-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones

[Konrad Zapałowicz]

Hey,

Thanks for the report. I will mark it as "needs information" because I
need a follow up from your side. Once I get the log files I ask about
below I will change the status to further.

- what kind of Ubuntu version is installed on the Linux computer that
works just wine with your headset?

Also, could you capture a somewhat more verbose logs. I would love to
see at least a HCI trace. You can capture it with sudo btmon --write
~/hcitrace.snoop. Just start it and then try to pair with your headset.
Also please do not make the test case really long so that it is easier
to understand the output :) Finally please read also
https://wiki.ubuntu.com/DebuggingBluetooth to understand how different
logs for BT debugging can be captured.

Thanks.

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

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

Title:
  Can not pair with bluetooth headphones

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 
wireless aebt).
  (If it matters, I *CAN* pair and use it on another laptop with Linux and with 
my android smartphone. So headset itself is working well.)

  Here is how I try to pair:
  $ bluetoothctl
  [NEW] Controller 54:27:1E:33:4B:85 impedance [default]
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes
  [bluetooth]# scan on

  I tried to put my headset in pairing mode just before and after
  issuing "scan on" command. It ends up with nothing - I waited for 3-5
  minutes. For example, my smartphone pairs with the headset within 5-15
  seconds, my laptop pairs with the headset within about 30 seconds.

  =

  Here is info

  $ hciconfig -a
  hci0:   Type: Primary  Bus: USB
  BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
  UP RUNNING PSCAN ISCAN
  RX bytes:4475 acl:0 sco:0 events:565 errors:0
  TX bytes:7214 acl:0 sco:0 commands:487 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'impedance'
  Class: 0x1c0104
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Desktop workstation
  HCI Version: 4.0 (0x6)  Revision: 0x1000
  LMP Version: 4.0 (0x6)  Subversion: 0x220e
  Manufacturer: Broadcom Corporation (15)

  =

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  =

  Bluez packages installed:
  $ dpkg -l | grep bluez
  ii  bluez
  ii  bluez-btsco
  ii  bluez-cups
  ii  bluez-hcidump
  ii  bluez-obexd
  ii  bluez-tools
  ii  libkf5bluezqt-data
  ii  libkf5bluezqt6:amd64
  ii  qml-module-org-kde-bluezqt:amd64

  =

  $ dmesg | grep -i blue
  [4.632406] Bluetooth: Core ver 2.21
  [4.632414] Bluetooth: HCI device and connection manager initialized
  [4.632416] Bluetooth: HCI socket layer initialized
  [4.632417] Bluetooth: L2CAP socket layer initialized
  [4.632420] Bluetooth: SCO socket layer initialized
  [4.644619] Bluetooth: hci0: BCM: chip id 63
  [4.660554] Bluetooth: hci0: impedance
  [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [4.661798] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
  [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
  [   15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.061604] Bluetooth: BNEP filters: protocol multicast
  [   15.061606] Bluetooth: BNEP socket layer initialized
  [   48.001553] Bluetooth: RFCOMM TTY layer initialized
  [   48.001558] Bluetooth: RFCOMM socket layer initialized
  [   48.001562] Bluetooth: RFCOMM ver 1.11
  [  615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp 
bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc 
nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor 
snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq 
btusb btrtl btbcm bt

[Touch-packages] [Bug 1653314] Re: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Konrad Zapałowicz]

Hey,

Could you share some more information about the nature of the failure.
Right now I cannot tell what has happened.

Thanks

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

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

Title:
  package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  i can'conekt bluetooth

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez:i386 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Dec 30 19:39:34 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-11-29 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bnep bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=fb1fce69-ec71-4461-85dd-690d60245405 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: bluez
  Title: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CROSSHAIR V FORMULA-Z
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:

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

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Konrad Zapałowicz]

@Wesley

You mean with Sony or Bose?

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

Title:
  Fails to pair with Bose QC35 headphones

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

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

[Touch-packages] [Bug 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)

[Sojan James]

Hi Theodore,

The write_xattrs_to_buffer is already doing other modifications to the
xattrs, like sorting keys. (look for qsort).  The changes I made are a
logical extension to that.

Further refinement might need a larger bunch of changes. I don't have
the bandwidth for this now unfortunately.

Saving ACLs with mke2fs is completely broken now.  This patch fixes the
problem and I think it will be useful to merge this in so that others
can benefit this.

Regards,
Sojan

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

Title:
  e2fsprogs - could not preserve ACL permissions  : The getxattr()
  returns with (EINVAL)

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  The original installed e2fsprogs did not support mke2fs -d /directory
  " option . So ,  git cloned from e2fsprogs packages from repository
  and installed it and followed below steps to reproduce this :

  1. set the ACL rules as below to one of the binary :

  $ setfacl -m u:vipatil:r-- rootfs/usr/bin/helloworld
  $ getfacl rootfs/usr/bin/helloworld
  # file: rootfs/usr/bin/helloworld
  # owner: shkumar
  # group: hardev
  user::rwx
  user:vipatil:r--
  group::---
  mask::r--
  other::---

  2. $ dd if=/dev/zero of=test.ext4 bs=1M count=60

  3. $ mke2fs -t ext4 test.ext4 -d rootfs/
  mke2fs 1.43.3 (04-Sep-2016)
  Discarding device blocks: done
  Creating filesystem with 61440 1k blocks and 15360 inodes
  Filesystem UUID: 495713b3-5f1f-427a-8359-a736dfb2ece9
  Superblock backups stored on blocks:
  8193, 24577, 40961, 57345

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (4096 blocks): done
  Copying files into the device: done
  Writing superblocks and filesystem accounting information: done

  4. sudo mount -o loop,acl,user_xattr,rw,sync test.ext4 mountpoint

  5.@/mountpoint$ getfacl usr/bin/helloworld
  getfacl: usr/bin/helloworld: Invalid argument

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

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

[Touch-packages] [Bug 1657640] Re: package udev 229-4ubuntu15 failed to install/upgrade: package udev is already installed and configured

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1657640

Title:
  package udev 229-4ubuntu15 failed to install/upgrade: package udev is
  already installed and configured

Status in systemd package in Ubuntu:
  New

Bug description:
  error_is_appearing_many_times..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Jan 16 20:06:45 2017
  DuplicateSignature:
   package:udev:229-4ubuntu15
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libjson-c2:i386 (--configure):
package libjson-c2:i386 is already installed and configured
  ErrorMessage: package udev is already installed and configured
  InstallationDate: Installed on 2016-09-12 (128 days ago)
  InstallationMedia:
   
  MachineType: Sony Corporation VPCEH35EN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=e8eb36fb-fdb7-4c09-8dd3-78db81eadd62 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: systemd
  Title: package udev 229-4ubuntu15 failed to install/upgrade: package udev is 
already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH35EN:pvrC106ZPTE:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEH35EN
  dmi.product.version: C106ZPTE
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1657641] Re: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured

[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 json-c in Ubuntu.
https://bugs.launchpad.net/bugs/1657641

Title:
  package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade:
  package libjson-c2:i386 is already installed and configured

Status in json-c package in Ubuntu:
  New

Bug description:
  sameproblem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjson-c2:i386 0.11-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Jan 16 20:06:44 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu3
  DuplicateSignature:
   package:libjson-c2:i386:0.11-4ubuntu2
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libjson-c2:i386 (--configure):
package libjson-c2:i386 is already installed and configured
  ErrorMessage: package libjson-c2:i386 is already installed and configured
  InstallationDate: Installed on 2016-09-12 (128 days ago)
  InstallationMedia:
   
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: json-c
  Title: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: 
package libjson-c2:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657640] [NEW] package udev 229-4ubuntu15 failed to install/upgrade: package udev is already installed and configured

[navdeep_rana]

Public bug reported:

error_is_appearing_many_times..

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu15
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Mon Jan 16 20:06:45 2017
DuplicateSignature:
 package:udev:229-4ubuntu15
 Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
 dpkg: error processing package libjson-c2:i386 (--configure):
  package libjson-c2:i386 is already installed and configured
ErrorMessage: package udev is already installed and configured
InstallationDate: Installed on 2016-09-12 (128 days ago)
InstallationMedia:
 
MachineType: Sony Corporation VPCEH35EN
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=e8eb36fb-fdb7-4c09-8dd3-78db81eadd62 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: systemd
Title: package udev 229-4ubuntu15 failed to install/upgrade: package udev is 
already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R0190Z9
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH35EN:pvrC106ZPTE:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCEH35EN
dmi.product.version: C106ZPTE
dmi.sys.vendor: Sony Corporation

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package udev 229-4ubuntu15 failed to install/upgrade: package udev is
  already installed and configured

Status in systemd package in Ubuntu:
  New

Bug description:
  error_is_appearing_many_times..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Jan 16 20:06:45 2017
  DuplicateSignature:
   package:udev:229-4ubuntu15
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libjson-c2:i386 (--configure):
package libjson-c2:i386 is already installed and configured
  ErrorMessage: package udev is already installed and configured
  InstallationDate: Installed on 2016-09-12 (128 days ago)
  InstallationMedia:
   
  MachineType: Sony Corporation VPCEH35EN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=e8eb36fb-fdb7-4c09-8dd3-78db81eadd62 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: systemd
  Title: package udev 229-4ubuntu15 failed to install/upgrade: package udev is 
already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH35EN:pvrC106ZPTE:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEH35EN
  dmi.product.version: C106ZPTE
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1657641] [NEW] package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured

[navdeep_rana]

Public bug reported:

sameproblem

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjson-c2:i386 0.11-4ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Mon Jan 16 20:06:44 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu5
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu3
DuplicateSignature:
 package:libjson-c2:i386:0.11-4ubuntu2
 Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
 dpkg: error processing package libjson-c2:i386 (--configure):
  package libjson-c2:i386 is already installed and configured
ErrorMessage: package libjson-c2:i386 is already installed and configured
InstallationDate: Installed on 2016-09-12 (128 days ago)
InstallationMedia:
 
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: json-c
Title: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package 
libjson-c2:i386 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: json-c (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed apport-package i386 xenial

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

Title:
  package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade:
  package libjson-c2:i386 is already installed and configured

Status in json-c package in Ubuntu:
  New

Bug description:
  sameproblem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjson-c2:i386 0.11-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Jan 16 20:06:44 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu3
  DuplicateSignature:
   package:libjson-c2:i386:0.11-4ubuntu2
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libjson-c2:i386 (--configure):
package libjson-c2:i386 is already installed and configured
  ErrorMessage: package libjson-c2:i386 is already installed and configured
  InstallationDate: Installed on 2016-09-12 (128 days ago)
  InstallationMedia:
   
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: json-c
  Title: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: 
package libjson-c2:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657625] [NEW] /usr/bin/pulseaudio:6:pa_hook_slot_free:pa_dynarray_free:pa_module_load:pa_cli_command_load:pa_cli_command_execute_line_stateful

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: xenial yakkety

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

Title:
  
/usr/bin/pulseaudio:6:pa_hook_slot_free:pa_dynarray_free:pa_module_load:pa_cli_command_load:pa_cli_command_execute_line_stateful

Status in pulseaudio package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1656250] Re: Unity8 crashes on screensaver suspend [Nested Mir Display Error: Failed to update EGL surface: EGL_BAD_CONTEXT (0x3006)]

[Daniel van Vugt]

Sounds similar to bug 1521403 actually. That is also Unity8 crashing on
suspend (but suspend triggered by Xmir).

** Branch linked: lp:~gerboland/qtmir/fix-glcontext-loss-on-reconfigure

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

** Package changed: unity8 (Ubuntu) => qtmir (Ubuntu)

** Changed in: qtmir (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

Title:
  Unity8 crashes on screensaver suspend [Nested Mir Display Error:
  Failed to update EGL surface: EGL_BAD_CONTEXT (0x3006)]

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

Bug description:
  On Zesty desktop with unity8-session 16.04 349

  Test Case
  1. Start a unity8 session
  2. Launch an app (eg Calculator)
  3. Wait 

  Expected result
  After an hour the session and the calculator are still running

  Actual result
  At some point (less than an hour) the session restarts (the calculator is 
gone if you were not staring at the screen when it restarted)

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

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

[Touch-packages] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

[Daniel van Vugt]

** Summary changed:

- Unity8 crashes with SIGSEGV in Screen::makeCurrent 
(./src/platforms/mirserver/screen.cpp:406)
+ Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent 
(./src/platforms/mirserver/screen.cpp:406)

** Tags added: unity8-desktop

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

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

Title:
  Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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

[Touch-packages] [Bug 1649086] Re: W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

[David Kalnischkies]

The solution is to tell the owners of the respective repositories to fix
their Release file(s). The Date (and Valid-Until) field MUST be in UTC
(aka GMT, Z, +). Earlier apt versions accepted other timezones
silently, but parsed it as UTC anyhow which could cause all kinds of
fun. Now a /warning/ is generated – a user can work with the repository
as before. As the content of that field is only of use for applications
and apt isn't a fullblown calendar-application we decided to not
implement all the craziness which is time.

All hints for creating repositories which apt (and other clients and
servers) can work with: https://wiki.debian.org/RepositoryFormat

So, as this isn't a bug: Closing as invalid.

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

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

Title:
  W: Invalid 'Date' entry in Release file
  
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

Status in apt package in Ubuntu:
  Invalid

Bug description:
  root@ubuntu:/var/lib/apt/lists# apt-get update
  Hit:1 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu yakkety InRelease
  Hit:3 http://ppa.launchpad.net/unit193/encryption/ubuntu yakkety InRelease
  
  Hit:4 http://es.archive.ubuntu.com/ubuntu yakkety InRelease   
  
  Hit:5 http://repository.spotify.com stable InRelease  
  
  Hit:6 http://ppa.launchpad.net/wine/wine-builds/ubuntu yakkety InRelease  
  
  Get:7 http://es.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]  
 
  Get:8 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]   
 
  Get:9 http://es.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 
kB]
  Hit:2 http://screenshots.getdeb.net yakkety-getdeb InRelease  

  Ign:10 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
InRelease   
  Hit:11 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
Release
  Fetched 306 kB in 1s (242 kB/s)
  Reading package lists... Done
  W: Invalid 'Date' entry in Release file 
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release
  root@ubuntu:/var/lib/apt/lists# 

  
  The file is as 
'developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release' 
follows:

  Origin: NVIDIA
  Label: NVIDIA CUDA
  Architecture: x86_64
  Date: Fri, 23 Sep 2016 18:52:52 -0700
  MD5Sum:
   3213a453e90b070bc10f329d2fe7f1a384080 Packages
   c1660fe24223ec9b07b04de1dfb3777122493 Packages.gz
  SHA1:
   60f8bd97333efb0bce147702712aab654ba3469b84080 Packages
   04e6ceaf9bcbcd3b36a9cc390b58110da138b7cd22493 Packages.gz
  SHA256:
   44a4473829b9403e7e2d36c43757b4d4ce8334b5804d90d920bd92edaf346241
84080 Packages
   f179e19b7c5b47d5c7247b5d6f37eb2ab2fba168ac70531dd02a0a1cda756038
22493 Packages.gz

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

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

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

[Daniel van Vugt]

Yeah, sorry I was meaning to tell you but never caught you on IRC... I
noticed Xmir does modify the display config, but only to implement DPMS.
That's legacy code from the days when Xmir was full screen. Although
full screen mode is also the default mode. So I'm wondering if we need
to make the behaviour conditional rather than delete the feature. It
should be disabled in windowed and rootless modes...

It is actually valid for apps to be able to change the power mode of the
display. mirout in Mir 0.26.0 has such an option. But I agree it's bad
for apps to do it unexpectedly.

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

Title:
  Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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

[Touch-packages] [Bug 1649086] Re: W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

[Li Zhou]

I got the same problem. WHen I run apt-get update, I receive the
warning:

W: Invalid 'Date' entry in Release file 
/var/lib/apt/lists/partial/_var_cuda-repo-8-0-local_Release
W: Invalid 'Date' entry in Release file 
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

Any solution?

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

Title:
  W: Invalid 'Date' entry in Release file
  
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  root@ubuntu:/var/lib/apt/lists# apt-get update
  Hit:1 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu yakkety InRelease
  Hit:3 http://ppa.launchpad.net/unit193/encryption/ubuntu yakkety InRelease
  
  Hit:4 http://es.archive.ubuntu.com/ubuntu yakkety InRelease   
  
  Hit:5 http://repository.spotify.com stable InRelease  
  
  Hit:6 http://ppa.launchpad.net/wine/wine-builds/ubuntu yakkety InRelease  
  
  Get:7 http://es.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]  
 
  Get:8 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]   
 
  Get:9 http://es.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 
kB]
  Hit:2 http://screenshots.getdeb.net yakkety-getdeb InRelease  

  Ign:10 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
InRelease   
  Hit:11 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
Release
  Fetched 306 kB in 1s (242 kB/s)
  Reading package lists... Done
  W: Invalid 'Date' entry in Release file 
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release
  root@ubuntu:/var/lib/apt/lists# 

  
  The file is as 
'developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release' 
follows:

  Origin: NVIDIA
  Label: NVIDIA CUDA
  Architecture: x86_64
  Date: Fri, 23 Sep 2016 18:52:52 -0700
  MD5Sum:
   3213a453e90b070bc10f329d2fe7f1a384080 Packages
   c1660fe24223ec9b07b04de1dfb3777122493 Packages.gz
  SHA1:
   60f8bd97333efb0bce147702712aab654ba3469b84080 Packages
   04e6ceaf9bcbcd3b36a9cc390b58110da138b7cd22493 Packages.gz
  SHA256:
   44a4473829b9403e7e2d36c43757b4d4ce8334b5804d90d920bd92edaf346241
84080 Packages
   f179e19b7c5b47d5c7247b5d6f37eb2ab2fba168ac70531dd02a0a1cda756038
22493 Packages.gz

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

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

[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Stéphane Charette]

Just ran into this exact problem today in 16.10, so problem still
exists.  Thanks, Reuben, your workaround in comment #3 got me back up
and running again.

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  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
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Wesley C wamer]

I am also seeing the identical issues as described above

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

Title:
  Fails to pair with Bose QC35 headphones

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

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Luke Faraone]

** Changed in: initramfs-tools
 Assignee: gintassi (gintassi) => (unassigned)

** Changed in: initramfs-tools (Ubuntu)
 Assignee: gintassi (gintassi) => Luke Faraone (lfaraone)

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

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

[Vaclav Rehak]

I can confirm that after every resume my wifi is not working. I used to
"solve" it by network-manager restart but running "wpa_cli resume"
manually fixes the problem as well.

I tried the sleep workaround by Hans but it did not help. I can see this
in /var/log/syslog:

Jan 19 00:20:34 vaclav-ntb systemd[1]: Reached target Sleep.
Jan 19 00:20:34 vaclav-ntb systemd[1]: Starting Suspend...
Jan 19 00:20:34 vaclav-ntb systemd-sleep[6171]: Failed to connect to non-global 
ctrl_ifname: (nil)  error: No such file or directory
Jan 19 00:20:34 vaclav-ntb systemd-sleep[6173]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Jan 19 00:20:34 vaclav-ntb systemd-sleep[6171]: Suspending system...

[snip]

Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]:   [1484781657.4625] 
manager: waking up...
Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]:   [1484781657.4626] 
device (wlan0): state change: unmanaged -> unavailable (reason 'managed') [10 
20 2]
...
Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]:   [1484781657.8564] 
manager: NetworkManager state is now CONNECTED_LOCAL
Jan 19 00:20:57 vaclav-ntb wpa_supplicant[1606]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jan 19 00:20:57 vaclav-ntb wpa_supplicant[1606]: dbus: Failed to construct 
signal
Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]:   [1484781657.9052] 
device (wlan0): supplicant interface state: starting -> ready
Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]:   [1484781657.9053] 
device (wlan0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
Jan 19 00:20:57 vaclav-ntb kernel: [138425.339676] IPv6: ADDRCONF(NETDEV_UP): 
wlan0: link is not ready

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

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

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

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

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

  Expected result:
  The WiFi still functioned.

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

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

[Mathew Hodson]

** Changed in: indicator-power (Ubuntu Xenial)
   Importance: Undecided => Medium

** Project changed: indicator-power => ubuntu-translations

** Changed in: ubuntu-translations
 Assignee: Charles Kerr (charlesk) => (unassigned)

** No longer affects: ubuntu-translations

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

   * No regression as I know.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1570921] Re: suspend not working

[Cody Seal]

Same issue on an Acer E5-575G

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

Title:
  suspend not working

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  My computer cannot go to suspend state.  The monitor switch off but the 
cpu/cpu fan keeps running and the hard drive is active.
  It doesn't respond, I need to switch off manually to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 15 18:42:49 2016
  InstallationDate: Installed on 2016-04-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1570921/+subscriptions

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

[Touch-packages] [Bug 1607666] Missing SRU information

[Brian Murray]

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Confirmed
Status in sudo source package in Yakkety:
  New

Bug description:
  Sudo currently fails to validate netgroups against host netgroups
  returned from the sss plugin, see
  https://fedorahosted.org/freeipa/ticket/6139 for the glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

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

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

[Touch-packages] [Bug 1657592] Re: Cannot set hour and minute at same time

[Redsandro]

Update: It seems that minutes past the half hour are working.

12 23 * * 1-5 command # does not work
45 23 * * 1-5 command # works

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

Title:
  Cannot set hour and minute at same time

Status in cron package in Ubuntu:
  New

Bug description:
  I'm using Linux Mint 18 Sarah, which is based on Ubuntu 16.04 LTS,
  which uses the Ubuntu cron package version 3.0pl1-128ubuntu2.

  Expectation:
  ---

  11 23 * * 1-5 command

  To run command from monday to friday on 11 past 23.

  Observation:
  ---

  Doesn't run.

  * 23 * * 1-5 command # WORKS - every minute at 23 o' clock
  11 * * * 1-5 command # WORKS - 11 past every hour
  11 23 * * 1-5 command # Does NOT work

  Work around:
  ---

  Only schedule jobs in the second half hour (e.g. 44 minutes past) is
  possible using this hack:

  */44 23 * * 1-5 # WORKS

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

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

[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg

[David Kalnischkies]

That sounds like what this commit describes: 
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=84eec207be35b8c117c430296d4c212b079c00c1
Hence tagged as such as its available in the 1.4 series. Not sure if this 
should be backported to 1.2 or not.

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

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

Title:
  apt won't redownload Release.gpg

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  
  I got myself into a situation where a repository has a Release and a 
Release.gpg file, but apt is just ignoring the gpg one and won't download it 
via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  
  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease   
 
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)   
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  
  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
python3-setuptools
  The following packages will be upgraded:
dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  WARNING: The following packages cannot be authenticated!
dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# 

  Somehow apt is thinking it has the Release.gpg file, but it doesn't?

  
  This server is behind a squid proxy.

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

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

[Touch-packages] [Bug 1567168] Re: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de i

[Joshua Powers]

This looks like a local configuration problem, rather than a bug in
Ubuntu. It appears that your packages are in a bad state and need to be
reinstalled.

You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problems, I'm marking this bug as 'Incomplete'. This helps
us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  This error appeared just prior to login. After it, Ubuntu kept working
  fine

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  5 22:54:35 2016
  DuplicateSignature: package:libgssapi-krb5-2:amd64:1.13.2+dfsg-2ubuntu0.1:El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2011-10-15 (1635 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1550912] Re: python-lxc segfaults when calling get_ips()

[Joshua Powers]

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

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

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

Title:
  python-lxc segfaults when calling get_ips()

Status in ansible package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in python-lxc package in Ubuntu:
  Fix Released

Bug description:
  Ohai,

  it seems liblxc broke ABI and python-lxc will segfault with something as 
simple as:
  >>> import lxc
  >>> c = lxc.Container(name='foo')
  >>> c.get_ips()
  Segmentation fault (core dumped)

  It does not matter if the container "foo" actually exists, is running or not.
  A rebuild helps.

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

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

[Touch-packages] [Bug 1567168] Re: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de i

[Joshua Powers]

>From log:

Dpkg: failed to process package libgssapi-krb5-2: amd64 (--configure):
 The package is in a serious state of inconsistency - you must reinstall it
 Before attempting its configuration.
Dpkg: dependency problems prevent configuration of libdns100:
 Libdns100 depends on libgssapi-krb5-2 (> = 1.10 + dfsg ~); but nevertheless:
 The `libgssapi-krb5-2: amd64 'package is not configured yet.

Dpkg: error processing package libdns100 (--configure):
 Dependency problems - left unconfigured
Dpkg: dependency problems prevent the configuration of libisccfg90:
 Libisccfg90 depends on libdns100; but nevertheless:
 Package `libdns100 'is not configured yet.

Dpkg: error processing package libisccfg90 (--configure):
 Dependency problems - left unconfigured
Dpkg: dependency problems prevent the configuration of libbind9-90:

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

Title:
  package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  This error appeared just prior to login. After it, Ubuntu kept working
  fine

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  5 22:54:35 2016
  DuplicateSignature: package:libgssapi-krb5-2:amd64:1.13.2+dfsg-2ubuntu0.1:El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2011-10-15 (1635 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657592] [NEW] Cannot set hour and minute at same time

[Redsandro]

Public bug reported:

I'm using Linux Mint 18 Sarah, which is based on Ubuntu 16.04 LTS, which
uses the Ubuntu cron package version 3.0pl1-128ubuntu2.

Expectation:
---

11 23 * * 1-5 command

To run command from monday to friday on 11 past 23.

Observation:
---

Doesn't run.

* 23 * * 1-5 command # WORKS - every minute at 23 o' clock
11 * * * 1-5 command # WORKS - 11 past every hour
11 23 * * 1-5 command # Does NOT work

Work around:
---

Only schedule jobs in the second half hour (e.g. 44 minutes past) is
possible using this hack:

*/44 23 * * 1-5 # WORKS

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

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

Title:
  Cannot set hour and minute at same time

Status in cron package in Ubuntu:
  New

Bug description:
  I'm using Linux Mint 18 Sarah, which is based on Ubuntu 16.04 LTS,
  which uses the Ubuntu cron package version 3.0pl1-128ubuntu2.

  Expectation:
  ---

  11 23 * * 1-5 command

  To run command from monday to friday on 11 past 23.

  Observation:
  ---

  Doesn't run.

  * 23 * * 1-5 command # WORKS - every minute at 23 o' clock
  11 * * * 1-5 command # WORKS - 11 past every hour
  11 23 * * 1-5 command # Does NOT work

  Work around:
  ---

  Only schedule jobs in the second half hour (e.g. 44 minutes past) is
  possible using this hack:

  */44 23 * * 1-5 # WORKS

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

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

[Touch-packages] [Bug 1597415] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Michael Doube]

This bug definitely depends on kernel version. Both the fix mentioned
above in #8
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/comments/8
and mainline kernel after this commit (found with reverse bisect), are
required. Marking as linux bug. Would be very nice if fix could make it
into Ubuntu 16.04 LTS.

:~/linux/linux$ git bisect bad
e075b3c898e4055ec62a1f0ed7f3b8e62814bfb6 is the first bad commit
commit e075b3c898e4055ec62a1f0ed7f3b8e62814bfb6
Author: Pali Rohár 
Date:   Wed Jun 15 21:49:13 2016 +0200

dell-wmi: Generate one sparse keymap for all machines

This patch reworks code for generating sparse keymap and processing WMI
events. It unifies procedure for generating sparse keymap and also unifies
big switch code for processing WMI events of different types. After this
patch dell-wmi driver does not differ between "old" and "new" hotkey type.

It constructs sparse keymap table with all WMI codes. It is because on some
laptops (e.g. Dell Latitude E6440) ACPI/firmware send both event types (old
and new).

Each WMI code in sparse keymap table is prefixed by 16bit event type, so it
does not change functionality on laptops with "old" hotkey support (those
without scancodes in DMI).

This allow us to distinguish between same WMI codes with different types in
sparse keymap. Thanks to this WMI events of type 0x0011 were moved from big
switch into sparse keymap table too.

This patch also fixes possible bug in parsing WMI event buffer introduced
in commit 5ea2559726b7 ("dell-wmi: Add support for new Dell systems"). That
commit changed buffer type from int* to u16* without fixing code. More at:
http://lkml.iu.edu/hypermail/linux/kernel/1507.0/01950.html

Signed-off-by: Pali Rohár 
Tested-by: Michał Kępień 
Reviewed-by: Michał Kępień 
Tested-by: Gabriele Mazzotta 
Signed-off-by: Darren Hart 

:04 04 babec68576f8756c9b0ee28a7ca7496de1c3c41a
b2e0e8cffb710d6ef2bdb9d4634cbd8b65867a34 M  drivers


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

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Steve Langasek]

Hello Dan, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu16
in a few hours, and then in the -proposed repository.

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

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

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

** Tags removed: verification-done

** Tags added: verification-needed

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

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

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

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

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

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

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

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

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

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

  [Regression Potential]

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

  [Other Info]

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

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

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

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

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

[Ryan Harper]

systemd-networkd-resolvconf-update.service uses default dependencies
which will only run after sysinit.target, however cloud-init.service
needs to run before sysinit.target; systemd apparently dropped running
the service due to the inconsistent order.  Adding a
DefaultDependencies=no to systemd-networkd-resolvconf-
update.{service,path} allows cloud-init.service to run early with DNS
before sysinit.target.

I've marked verification failed for this bug since the current proposed
packages do not resolv the issue without changes to systemd package
(/lib/systemd/system/systemd-networkd-resolvconf-update.{service,path}.


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

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed
Status in resolvconf source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  Test Case:
    lxc launch ubuntu-daily:xenial x1
    lxc exec x1 /bin/bash

    # make sure you're on systemd-229-4ubuntu13
    apt update && apt install -y systemd

    # enable networkd and netplan
    apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
  EOF
    sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

    netplan generate

    # make sure cloud-init.service uses networkd
    sed -i.orig -e '/After=networking.service/a 
After=systemd-networkd-wait-online.service' 
/lib/systemd/system/cloud-init.service

    reboot

    # check that the order of execution with:
    journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

    # the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+

[Touch-packages] [Bug 1655059] Re: ifup@.service doesn't work with interface names containing a dash

[Launchpad Bug Tracker]

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

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

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

Title:
  ifup@.service doesn't work with interface names containing a dash

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  It seems dashes get replaced by forward slash in the unit file and hence the 
interface is not found.
  Endresult is that the interface does not come up.

  $ sudo systemctl start ifup@br-vxlan
  $ # I'm expecting this brings up the br-vxlan, but nothing happens, this 
command doesn't return an error message

  Further info:

  $ sudo systemctl status ifup@br-vxlan
  * ifup@br-vxlan.service - ifup for br/vxlan
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: active (exited) since Mon 2017-01-09 15:55:15 CET; 10min ago
Process: 4705 ExecStop=/sbin/ifdown %I (code=exited, status=1/FAILURE)
Process: 4713 ExecStart=/bin/sh -ec ifup --allow=hotplug %I; ifup 
--allow=auto %I;  if ifquery %I >/dev/
   Main PID: 4713 (code=exited, status=0/SUCCESS)
 CGroup: /system.slice/ifup@br-vxlan.service

  Jan 09 15:55:15 xxx systemd[1]: Started ifup for br/vxlan.
  Jan 09 15:55:15 xxx sh[4713]: Unknown interface br/vxlan

  
  $ cat /etc/network/interfaces.d/60_iface_br-vxlan

  allow-auto br-vxlan
  allow-boot br-vxlan
  allow-hotplug br-vxlan
  iface br-vxlan inet manual
  bridge_fd 0
  bridge_maxwait 0
  bridge_ports enp1s0f1
  bridge_stp off
  bridge_waitport 0

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

  
  $ apt-cache policy ifupdown
  ifupdown:
Installed: 0.8.10ubuntu1.2
Candidate: 0.8.10ubuntu1.2
Version table:
   *** 0.8.10ubuntu1.2 500
  500 http://xxx.cisco.com/ubuntu xenial-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.8.10ubuntu1 500
  500 http://xxx.cisco.com/ubuntu xenial/main amd64 Packages

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

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

[Touch-packages] [Bug 1647016] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1647016

Title:
  SRU of LXC 1.0.9 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Invalid
Status in lxc source package in Precise:
  In Progress
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  LXC upstream released LXC 1.0.9 as a bugfix release with following
  changelog:

   - Security fix for CVE-2016-8649
   - utils: make detect_ramfs_rootfs() return bool
   - tests: add test for detect_ramfs_rootfs()
   - add Documentation entries to lxc and lxc@ units
   - mark the python examples as having utf-8 encoding
   - log: sanity check the returned value from snprintf()
   - lxc-alpine: mount /dev/shm as tmpfs
   - archlinux: Do DHCP on eth0
   - archlinux: Fix resolving
   - Drop leftover references to lxc_strerror()
   - tests: fix image download for s390x
   - tools: fix coding style in lxc_attach
   - tools: make overlay valid backend
   - tools: better error reporting for lxc-start
   - alpine: Fix installing extra packages
   - lxc-alpine: do not drop setfcap
   - s390x: Fix seccomp handling of personalities
   - tools: correct the argument typo in lxc_copy
   - Use libtool for liblxc.so
   - c/r: use --external instead of --veth-pair
   - c/r: remember to increment netnr
   - c/r: add checkpoint/restore support for macvlan interfaces
   - ubuntu: Fix package upgrades requiring proc
   - c/r: drop duplicate hunk from macvlan case
   - c/r: use snprintf to compute device name
   - Tweak libtool handling to work with Android
   - tests: add lxc_error() and lxc_debug()
   - container start: clone newcgroup immediately
   - use python3_sitearch for including the python code
   - fix rpm build, include all built files, but only once
   - cgfs: fix invalid free()
   - find OpenSUSE's build also as obs-build
   - improve help text for --fancy and --fancy-format
   - improve wording of the help page for lxc-ls
   - cgfs: add print_cgfs_init_debuginfo()
   - cgfs: skip empty entries under /proc/self/cgroup
   - cgfs: explicitly check for NULL
   - tools: use correct exit code for lxc-stop
   - c/r: explicitly emit bind mounts as criu arguments
   - log: bump LXC_LOG_BUFFER_SIZE to 4096
   - conf: merge network namespace move & rename on shutdown
   - c/r: save criu's stdout during dump too
   - c/r: remove extra \ns from logs
   - c/r: fix off-by-one error
   - c/r: check state before doing a checkpoint/restore
   - start: CLONE_NEWCGROUP after we have setup cgroups
   - create symlink for /var/run
   - utils: add lxc_append_string()
   - cgroups: remove isolated cpus from cpuset.cpus
   - Update Ubuntu release name: add zesty and remove wily
   - templates: add squashfs support to lxc-ubuntu-cloud.in
   - cgroups: skip v2 hierarchy entry
   - also stop lxc-net in runlevels 0 and 6
   - add lxc.egg-info to gitignore
   - install bash completion where pkg-config tells us to
   - conf: do not use %m format specifier
   - debian: Don't depend on libui-dialog-perl
   - cgroups: use %zu format specifier to print size_t
   - lxc-checkpoint: automatically detect if --external or --veth-pair
   - cgroups: prevent segfault in cgfsng
   - utils: add lxc_preserve_ns()
   - start: add netnsfd to lxc_handler
   - conf: use lxc_preserve_ns()
   - attach: use lxc_preserve_ns()
   - lxc_user_nic: use lxc_preserve_ns()
   - conf, start: improve log output
   - conf: explicitly remove veth device from host
   - conf, start: be smarter when deleting networks
   - start, utils: improve preserve_ns()
   - start, error: improve log + non-functional changes
   - start, namespace: move ns_info to namespace.{c,h}
   - attach, utils: bugfixes
   - attach: use ns_info[LXC_NS_MAX] struct
   - namespace: always attach to user namespace first
   - cgroup: improve isolcpus handling
   - cgroups: handle non-existent isolcpus file
   - utils: add lxc_safe_uint()
   - tests: add unit tests for lxc_safe_uint()
   - utils: add lxc_safe_int()
   - tests: add unit tests for lxc_safe_int()
   - conf/ile: get ip prefix via lxc_safe_uint()
   - confile: use lxc_safe_u/int in config_init_{u,g}id
   - conf/ile: use lxc_safe_uint() in config_pts()
   - conf/ile: use lxc_safe_u/int() in config_start()
   - conf/ile: use lxc_safe_uint() in config_monitor()
   - conf/ile: use lxc_safe_uint() in config_tty()
   - conf/ile: use lxc_safe_uint() in config_kmsg()
   - conf/ile: avoid atoi in config_lsm_aa_i

[Touch-packages] [Bug 1647016] Re: SRU of LXC 1.0.9 (upstream bugfix release)

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.0.9-0ubuntu2

---
lxc (1.0.9-0ubuntu2) trusty; urgency=medium

  * Cherry-pick upstream bugfix (LP: #1647016):
- 0001-tests-skip-unpriv-tests-on-broken-overlay-module.patch

 -- Stéphane Graber   Wed, 04 Jan 2017 12:38:37
-0500

** Changed in: lxc (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  SRU of LXC 1.0.9 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Invalid
Status in lxc source package in Precise:
  In Progress
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  LXC upstream released LXC 1.0.9 as a bugfix release with following
  changelog:

   - Security fix for CVE-2016-8649
   - utils: make detect_ramfs_rootfs() return bool
   - tests: add test for detect_ramfs_rootfs()
   - add Documentation entries to lxc and lxc@ units
   - mark the python examples as having utf-8 encoding
   - log: sanity check the returned value from snprintf()
   - lxc-alpine: mount /dev/shm as tmpfs
   - archlinux: Do DHCP on eth0
   - archlinux: Fix resolving
   - Drop leftover references to lxc_strerror()
   - tests: fix image download for s390x
   - tools: fix coding style in lxc_attach
   - tools: make overlay valid backend
   - tools: better error reporting for lxc-start
   - alpine: Fix installing extra packages
   - lxc-alpine: do not drop setfcap
   - s390x: Fix seccomp handling of personalities
   - tools: correct the argument typo in lxc_copy
   - Use libtool for liblxc.so
   - c/r: use --external instead of --veth-pair
   - c/r: remember to increment netnr
   - c/r: add checkpoint/restore support for macvlan interfaces
   - ubuntu: Fix package upgrades requiring proc
   - c/r: drop duplicate hunk from macvlan case
   - c/r: use snprintf to compute device name
   - Tweak libtool handling to work with Android
   - tests: add lxc_error() and lxc_debug()
   - container start: clone newcgroup immediately
   - use python3_sitearch for including the python code
   - fix rpm build, include all built files, but only once
   - cgfs: fix invalid free()
   - find OpenSUSE's build also as obs-build
   - improve help text for --fancy and --fancy-format
   - improve wording of the help page for lxc-ls
   - cgfs: add print_cgfs_init_debuginfo()
   - cgfs: skip empty entries under /proc/self/cgroup
   - cgfs: explicitly check for NULL
   - tools: use correct exit code for lxc-stop
   - c/r: explicitly emit bind mounts as criu arguments
   - log: bump LXC_LOG_BUFFER_SIZE to 4096
   - conf: merge network namespace move & rename on shutdown
   - c/r: save criu's stdout during dump too
   - c/r: remove extra \ns from logs
   - c/r: fix off-by-one error
   - c/r: check state before doing a checkpoint/restore
   - start: CLONE_NEWCGROUP after we have setup cgroups
   - create symlink for /var/run
   - utils: add lxc_append_string()
   - cgroups: remove isolated cpus from cpuset.cpus
   - Update Ubuntu release name: add zesty and remove wily
   - templates: add squashfs support to lxc-ubuntu-cloud.in
   - cgroups: skip v2 hierarchy entry
   - also stop lxc-net in runlevels 0 and 6
   - add lxc.egg-info to gitignore
   - install bash completion where pkg-config tells us to
   - conf: do not use %m format specifier
   - debian: Don't depend on libui-dialog-perl
   - cgroups: use %zu format specifier to print size_t
   - lxc-checkpoint: automatically detect if --external or --veth-pair
   - cgroups: prevent segfault in cgfsng
   - utils: add lxc_preserve_ns()
   - start: add netnsfd to lxc_handler
   - conf: use lxc_preserve_ns()
   - attach: use lxc_preserve_ns()
   - lxc_user_nic: use lxc_preserve_ns()
   - conf, start: improve log output
   - conf: explicitly remove veth device from host
   - conf, start: be smarter when deleting networks
   - start, utils: improve preserve_ns()
   - start, error: improve log + non-functional changes
   - start, namespace: move ns_info to namespace.{c,h}
   - attach, utils: bugfixes
   - attach: use ns_info[LXC_NS_MAX] struct
   - namespace: always attach to user namespace first
   - cgroup: improve isolcpus handling
   - cgroups: handle non-existent isolcpus file
   - utils: add lxc_safe_uint()
   - tests: add unit tests for lxc_safe_uint()
   - utils: add lxc_safe_int()
   - tests: add unit tests for lxc_safe_int()
   - conf/ile: get ip prefix via lxc_safe_uint()
   - confile: use lxc_safe_u/int in config_init_{u,g}id
   - conf/ile: use lxc_safe_uint() in config_pts()
   - conf/ile: use lxc_safe_u/int() in config_start()
   - conf/ile: use lxc_safe_uint() in config_monitor()
   - conf/ile: use lxc_safe_uint() in config_tty()
   - conf/ile: use lxc_safe_uint() in config_kmsg()
   - conf/ile: avoid atoi in config_lsm_aa_incomplete()
   - conf/ile: use lxc_safe_uint() in config_autodev()
   - conf/ile: avoid atoi

[Touch-packages] [Bug 1647016] Re: SRU of LXC 1.0.9 (upstream bugfix release)

[Stéphane Graber]

Looks like this version passes all our tests just fine and we haven't
heard anything bad from users of -proposed or other distros that are
already including 1.0.9.

** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1647016

Title:
  SRU of LXC 1.0.9 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Invalid
Status in lxc source package in Precise:
  In Progress
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  LXC upstream released LXC 1.0.9 as a bugfix release with following
  changelog:

   - Security fix for CVE-2016-8649
   - utils: make detect_ramfs_rootfs() return bool
   - tests: add test for detect_ramfs_rootfs()
   - add Documentation entries to lxc and lxc@ units
   - mark the python examples as having utf-8 encoding
   - log: sanity check the returned value from snprintf()
   - lxc-alpine: mount /dev/shm as tmpfs
   - archlinux: Do DHCP on eth0
   - archlinux: Fix resolving
   - Drop leftover references to lxc_strerror()
   - tests: fix image download for s390x
   - tools: fix coding style in lxc_attach
   - tools: make overlay valid backend
   - tools: better error reporting for lxc-start
   - alpine: Fix installing extra packages
   - lxc-alpine: do not drop setfcap
   - s390x: Fix seccomp handling of personalities
   - tools: correct the argument typo in lxc_copy
   - Use libtool for liblxc.so
   - c/r: use --external instead of --veth-pair
   - c/r: remember to increment netnr
   - c/r: add checkpoint/restore support for macvlan interfaces
   - ubuntu: Fix package upgrades requiring proc
   - c/r: drop duplicate hunk from macvlan case
   - c/r: use snprintf to compute device name
   - Tweak libtool handling to work with Android
   - tests: add lxc_error() and lxc_debug()
   - container start: clone newcgroup immediately
   - use python3_sitearch for including the python code
   - fix rpm build, include all built files, but only once
   - cgfs: fix invalid free()
   - find OpenSUSE's build also as obs-build
   - improve help text for --fancy and --fancy-format
   - improve wording of the help page for lxc-ls
   - cgfs: add print_cgfs_init_debuginfo()
   - cgfs: skip empty entries under /proc/self/cgroup
   - cgfs: explicitly check for NULL
   - tools: use correct exit code for lxc-stop
   - c/r: explicitly emit bind mounts as criu arguments
   - log: bump LXC_LOG_BUFFER_SIZE to 4096
   - conf: merge network namespace move & rename on shutdown
   - c/r: save criu's stdout during dump too
   - c/r: remove extra \ns from logs
   - c/r: fix off-by-one error
   - c/r: check state before doing a checkpoint/restore
   - start: CLONE_NEWCGROUP after we have setup cgroups
   - create symlink for /var/run
   - utils: add lxc_append_string()
   - cgroups: remove isolated cpus from cpuset.cpus
   - Update Ubuntu release name: add zesty and remove wily
   - templates: add squashfs support to lxc-ubuntu-cloud.in
   - cgroups: skip v2 hierarchy entry
   - also stop lxc-net in runlevels 0 and 6
   - add lxc.egg-info to gitignore
   - install bash completion where pkg-config tells us to
   - conf: do not use %m format specifier
   - debian: Don't depend on libui-dialog-perl
   - cgroups: use %zu format specifier to print size_t
   - lxc-checkpoint: automatically detect if --external or --veth-pair
   - cgroups: prevent segfault in cgfsng
   - utils: add lxc_preserve_ns()
   - start: add netnsfd to lxc_handler
   - conf: use lxc_preserve_ns()
   - attach: use lxc_preserve_ns()
   - lxc_user_nic: use lxc_preserve_ns()
   - conf, start: improve log output
   - conf: explicitly remove veth device from host
   - conf, start: be smarter when deleting networks
   - start, utils: improve preserve_ns()
   - start, error: improve log + non-functional changes
   - start, namespace: move ns_info to namespace.{c,h}
   - attach, utils: bugfixes
   - attach: use ns_info[LXC_NS_MAX] struct
   - namespace: always attach to user namespace first
   - cgroup: improve isolcpus handling
   - cgroups: handle non-existent isolcpus file
   - utils: add lxc_safe_uint()
   - tests: add unit tests for lxc_safe_uint()
   - utils: add lxc_safe_int()
   - tests: add unit tests for lxc_safe_int()
   - conf/ile: get ip prefix via lxc_safe_uint()
   - confile: use lxc_safe_u/int in config_init_{u,g}id
   - conf/ile: use lxc_safe_uint() in config_pts()
   - conf/ile: use lxc_safe_u/int() in config_start()
   - conf/ile: use lxc_safe_uint() in config_monitor()
   - conf/ile: use lxc_safe_uint() in config_tty()
   - conf/ile: use lxc_safe_uint() in config_kmsg()
   - conf/ile: avoid atoi in config_lsm_aa_incomplete()
   - conf/ile: use lxc_safe_uint() in config_autodev()
   - conf/ile: avoid atoi() in config_ephemeral()
   - utils: use lxc_safe_int()
   - lxc_monitord: use lxc_safe_int() && use exit()
   - start: use lxc_safe

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

[Ryan Harper]

Something isn't working here.  I also typo'd the test-case, in
particular, the change to the cloud-init.service unit didn't specify
'systemd-networkd-wait-online.service', the sed command missed the 'd'
in networkd.

When I fix that, I find that systemd-networkd-resolvconf-update.service
does NOT run.  Manually adding that to
/lib/systemd/system/resolvconf.service.wants fixes the networkd boot
path, but of course breaks the ifupdown path.


** Description changed:

  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.
  
  This was discussed in https://launchpad.net/bugs/1636912 however it was
  not a regression since there aren't any users of networkd + DNS early in
  boot at this time, it was requested that we move this DNS issue to a
  separate bug.
  
- 
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.
  
  Regression potential: Low. networkd is not widely being used outside of
  netplan/snappy in xenial.
  
+ Test Case:
+   lxc launch ubuntu-daily:xenial x1
+   lxc exec x1 /bin/bash
  
- Test Case:
-   lxc launch ubuntu-daily:xenial x1
-   lxc exec x1 /bin/bash
+   # make sure you're on systemd-229-4ubuntu13
+   apt update && apt install -y systemd
  
-   # make sure you're on systemd-229-4ubuntu13
-   apt update && apt install -y systemd
- 
-   # enable networkd and netplan
-   apt install -y nplan
+   # enable networkd and netplan
+   apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
-   version: 2
-   ethernets:
- eth0:
-   dhcp4: true
+   version: 2
+   ethernets:
+ eth0:
+   dhcp4: true
  EOF
-   sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
-   
-   netplan generate
-   
-   # make sure cloud-init.service uses networkd
-   sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service
+   sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
  
-   reboot
+   netplan generate
  
-   # check that the order of execution with:
-   journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service
+   # make sure cloud-init.service uses networkd
+   sed -i.orig -e '/After=networking.service/a 
After=systemd-networkd-wait-online.service' 
/lib/systemd/system/cloud-init.service
  
-   # the order should be:
- 1. resolvconf:  systemd[1]: Started Nameserver information manager.
- 2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
- 3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
- 4. network-online.target: systemd[1]: Reached target Network is Online.
+   reboot
+ 
+   # check that the order of execution with:
+   journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service
+ 
+   # the order should be:
+ 1. resolvconf:  systemd[1]: Started Nameserver information manager.
+ 2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
+ 3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
+ 4. network-online.target: systemd[1]: Reached target Network is Online.
  
  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:
  
  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  
- 
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.
  
  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.6-0ubuntu1~ubuntu16.04.2

---
lxc (2.0.6-0ubuntu1~ubuntu16.04.2) xenial; urgency=medium

  * Cherry-pick upstream bugfix:
- 0003-tools-only-check-for-O_RDONLY.patch (LP: #1653725)

 -- Stéphane Graber   Wed, 04 Jan 2017 19:52:32
-0500

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

Title:
  lxc-android-config not starting on ubuntu-touch/staging/* xenial-based
  images after lxc upgrade

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Fix Released

Bug description:
  # SRU
  ## Rationale
  LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the 
corner case of partly-writable systems like the Ubuntu phone.
  This upload fixes this by changing the test to a simple readability one.

  ## Test case
  1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but 
/var/lib/lxc/ on a writable one.
  2) Confirm that the container now starts.

  ## Regression potential
  This upload only changes the check from read/write to read so the only 
consequence of this should be more cases now being allowed. In the case where a 
writable /var/lib/lxc is in fact absolutely required for the requested 
operation, the operation will still fail, just a bit later and with a slightly 
less clear error message (as was the case pre-2.0.6).

  
  # Original report
  As in topic. Since the 20161217 rootfs, after upgrade of lxc from 
2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the 
lxc-android-config service does not start - making the devices unbootable.

  The syslog only states this:

  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and 
Container Initialization...
  Jan  3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN 
= 0x1
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager...
  Jan  3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate 
persistent MAC address for ifb0: No such file or directory
  Jan  3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate 
persistent MAC address for ifb1: No such file or directory
  Jan  3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to 
/var/lib/lxc
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: 
Control process exited, code=exited status=1
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config 
and Container Initialization.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for 
force-mtp.service.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job 
force-mtp.service/start failed with result 'dependency'.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit 
entered failed state.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed 
with result 'exit-code'.

  This makes all of our frieza and cooler devices useless for testing
  purposes.

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

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

[Touch-packages] [Bug 1656431] Re: Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.7.1+dfsg-
2ubuntu2~1

---
qtbase-opensource-src (5.7.1+dfsg-2ubuntu2~1) zesty; urgency=medium

  * Disable gold linker also on arm64 and ppc64el (LP: #1656431)

 -- Timo Jyrinki   Mon, 16 Jan 2017 09:23:57
+

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

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

Title:
  Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  libkf5kipi https://userbase.kde.org/KIPI
  parley
  kidentitymanagement
  libkeduvocdocument

  FTBFS with errors similar to the one shown at the bottom of this

  As is the case with LP Bug #1654820, it seems likely that

  kmail
  kdepim-addons

  would also fail in the same fashion, but the build depends are not yet
  in place to confirm that absolutely.

  Again, this seems to be a case of qtbase using the gold linker, and I
  would surmise that as with amd64 etc, setting no gold linker for
  arm64 and ppc64el would resolve this.

  no gold linker is already set in qtbase for amd64, i386, powerpc &
  armhf.

  
  --- log extract --

  [ 56%] Linking CXX executable plaintexteditortest
  cd 
/<>/obj-aarch64-linux-gnu/src/texteditor/plaintexteditor/autotests 
&& /usr/bin/cmake -E cmake_link_script 
CMakeFiles/plaintexteditortest.dir/link.txt --verbose=1
  /usr/bin/c++   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions 
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -pedantic  -Wl,--enable-new-dtags -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest.cpp.o 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest_automoc.cpp.o  -o 
plaintexteditortest -Wl,-rpath,/<>/obj-aarch64-linux-gnu/src 
-rdynamic ../../../libKF5PimTextEdit.so.5.4.0.abi1 
/usr/lib/aarch64-linux-gnu/libQt5Test.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1 
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_edata'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `__bss_start'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_end'
  collect2: error: ld returned 1 exit status
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_edata'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `__bss_start'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_end'
  collect2: error: ld returned 1 exit status

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

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.6-0ubuntu1~ubuntu16.10.2

---
lxc (2.0.6-0ubuntu1~ubuntu16.10.2) yakkety; urgency=medium

  * Cherry-pick upstream bugfix:
- 0003-tools-only-check-for-O_RDONLY.patch (LP: #1653725)

 -- Stéphane Graber   Wed, 04 Jan 2017 19:51:22
-0500

** Changed in: lxc (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  lxc-android-config not starting on ubuntu-touch/staging/* xenial-based
  images after lxc upgrade

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Fix Released

Bug description:
  # SRU
  ## Rationale
  LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the 
corner case of partly-writable systems like the Ubuntu phone.
  This upload fixes this by changing the test to a simple readability one.

  ## Test case
  1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but 
/var/lib/lxc/ on a writable one.
  2) Confirm that the container now starts.

  ## Regression potential
  This upload only changes the check from read/write to read so the only 
consequence of this should be more cases now being allowed. In the case where a 
writable /var/lib/lxc is in fact absolutely required for the requested 
operation, the operation will still fail, just a bit later and with a slightly 
less clear error message (as was the case pre-2.0.6).

  
  # Original report
  As in topic. Since the 20161217 rootfs, after upgrade of lxc from 
2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the 
lxc-android-config service does not start - making the devices unbootable.

  The syslog only states this:

  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and 
Container Initialization...
  Jan  3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN 
= 0x1
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager...
  Jan  3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate 
persistent MAC address for ifb0: No such file or directory
  Jan  3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate 
persistent MAC address for ifb1: No such file or directory
  Jan  3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to 
/var/lib/lxc
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: 
Control process exited, code=exited status=1
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config 
and Container Initialization.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for 
force-mtp.service.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job 
force-mtp.service/start failed with result 'dependency'.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit 
entered failed state.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed 
with result 'exit-code'.

  This makes all of our frieza and cooler devices useless for testing
  purposes.

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

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

[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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.

** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1653725

Title:
  lxc-android-config not starting on ubuntu-touch/staging/* xenial-based
  images after lxc upgrade

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Fix Released

Bug description:
  # SRU
  ## Rationale
  LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the 
corner case of partly-writable systems like the Ubuntu phone.
  This upload fixes this by changing the test to a simple readability one.

  ## Test case
  1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but 
/var/lib/lxc/ on a writable one.
  2) Confirm that the container now starts.

  ## Regression potential
  This upload only changes the check from read/write to read so the only 
consequence of this should be more cases now being allowed. In the case where a 
writable /var/lib/lxc is in fact absolutely required for the requested 
operation, the operation will still fail, just a bit later and with a slightly 
less clear error message (as was the case pre-2.0.6).

  
  # Original report
  As in topic. Since the 20161217 rootfs, after upgrade of lxc from 
2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the 
lxc-android-config service does not start - making the devices unbootable.

  The syslog only states this:

  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and 
Container Initialization...
  Jan  3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN 
= 0x1
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager...
  Jan  3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate 
persistent MAC address for ifb0: No such file or directory
  Jan  3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate 
persistent MAC address for ifb1: No such file or directory
  Jan  3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to 
/var/lib/lxc
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: 
Control process exited, code=exited status=1
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config 
and Container Initialization.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for 
force-mtp.service.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job 
force-mtp.service/start failed with result 'dependency'.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit 
entered failed state.
  Jan  3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed 
with result 'exit-code'.

  This makes all of our frieza and cooler devices useless for testing
  purposes.

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

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

[Touch-packages] [Bug 1657578] [NEW] package libpng12-0:i386 1.2.49-1ubuntu2 failed to install/upgrade: o pacote libpng12-0:i386 1.2.49-1ubuntu2 não pode ser configurado porque libpng12-0:amd64 está n

[Fernando Anselmo]

Public bug reported:

No execute on VirtualBox

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libpng12-0:i386 1.2.49-1ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Wed Jan 18 17:11:34 2017
Dependencies:
 gcc-6-base 6.2.0-5ubuntu12
 libc6 2.24-3ubuntu2
 libgcc1 1:6.2.0-5ubuntu12
 multiarch-support 2.24-3ubuntu2
 zlib1g 1:1.2.8.dfsg-2ubuntu5
ErrorMessage: o pacote libpng12-0:i386 1.2.49-1ubuntu2 não pode ser configurado 
porque libpng12-0:amd64 está numa versão diferente (1.2.54-1ubuntu1)
InstallationDate: Installed on 2014-07-18 (915 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.3
SourcePackage: libpng
Title: package libpng12-0:i386 1.2.49-1ubuntu2 failed to install/upgrade: o 
pacote libpng12-0:i386 1.2.49-1ubuntu2 não pode ser configurado porque 
libpng12-0:amd64 está numa versão diferente (1.2.54-1ubuntu1)
UpgradeStatus: Upgraded to yakkety on 2016-11-12 (67 days ago)

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


** Tags: apport-package i386 yakkety

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

Title:
  package libpng12-0:i386 1.2.49-1ubuntu2 failed to install/upgrade: o
  pacote libpng12-0:i386 1.2.49-1ubuntu2 não pode ser configurado porque
  libpng12-0:amd64 está numa versão diferente (1.2.54-1ubuntu1)

Status in libpng package in Ubuntu:
  New

Bug description:
  No execute on VirtualBox

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libpng12-0:i386 1.2.49-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Wed Jan 18 17:11:34 2017
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu2
   libgcc1 1:6.2.0-5ubuntu12
   multiarch-support 2.24-3ubuntu2
   zlib1g 1:1.2.8.dfsg-2ubuntu5
  ErrorMessage: o pacote libpng12-0:i386 1.2.49-1ubuntu2 não pode ser 
configurado porque libpng12-0:amd64 está numa versão diferente (1.2.54-1ubuntu1)
  InstallationDate: Installed on 2014-07-18 (915 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: libpng
  Title: package libpng12-0:i386 1.2.49-1ubuntu2 failed to install/upgrade: o 
pacote libpng12-0:i386 1.2.49-1ubuntu2 não pode ser configurado porque 
libpng12-0:amd64 está numa versão diferente (1.2.54-1ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (67 days ago)

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

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

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

[Mauricio Maluff Masi]

I managed to find a workaround thanks to Dell tech support. This worked
for me, though be careful, as it does involve removing a package without
removing dependencies. Here's what we did:

sudo dpkg --remove --force-depends pulseaudio
sudo apt install pulseaudio

I haven't had the issue since even after a few reboots! It used to be
very easy to reproduce previously.

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Touch-packages] [Bug 1657437] Re: Unprivileged containers run by non-root fail to start if trying to bind-mount a directory that contains a mounted ecryptfs

[Florian Haas]

All right, that makes sense — thanks for clearing this up!

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

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

Title:
  Unprivileged containers run by non-root fail to start if trying to
  bind-mount a directory that contains a mounted ecryptfs

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Not sure if this is an lxc bug or an ecryptfs bug. Please reassign if
  necessary.

  I have an unprivileged container that is defined in the default
  location, ~/.share/local/lxc. It bind-mounts the host's /home
  directory to /home inside the container, like so:

  lxc.mount.entry = /home home none bind 0 0

  My /home directory contains an ecryptfs at ~/.Private, which is
  mounted to ~/Private with default options, at login, via pam_ecryptfs.

  lxc-start then results in the following error showing up in the log
  file:

lxc-start 20170118124950.117 ERRORlxc_utils - 
utils.c:safe_mount:1746 - Invalid argument - Failed to mount /home onto 
/usr/lib/x86_64-linux-gnu/lxc/home
lxc-start 20170118124950.117 ERRORlxc_conf - 
conf.c:mount_entry:1650 - Invalid argument - failed to mount '/home' on 
'/usr/lib/x86_64-linux-gnu/lxc/home'
lxc-start 20170118124950.117 ERRORlxc_conf - conf.c:lxc_setup:3790 
- failed to setup the mount entries for 'trusty-edx-devstack'
lxc-start 20170118124950.117 ERRORlxc_start - start.c:do_start:826 
- Failed to setup container "trusty-edx-devstack".
lxc-start 20170118124950.117 ERRORlxc_sync - sync.c:__sync_wait:57 
- An error occurred in another process (expected sequence number 3)
lxc-start 20170118124950.118 ERRORlxc_start - 
start.c:__lxc_start:1338 - Failed to spawn container "trusty-edx-devstack".
lxc-start 20170118124955.668 ERRORlxc_start_ui - 
tools/lxc_start.c:main:360 - The container failed to start.

  Unmounting the ecryptfs allows the container to start normally. After
  the container has been started, the ecryptfs can be remounted with
  ecryptfs-mount-private, which appears to have no ill effect on the
  container.

  I don't quite see why the mounted ecryptfs would prevent /home from
  being bind-mounted into the container. After all, bind-mounting /home
  to some other mount point in the host works just fine — with the
  Private directory simply being empty, save for the Access-Your-
  Private-Data.desktop and README.txt symlinks, in the bind mount
  location. This is also what happens in privileged containers whose
  configuration has the same lxc.mount.entry.

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

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

[Touch-packages] [Bug 1637601] xenial_libvirt_uid_v4.debdiff

[bugproxy]

Default Comment by Bridge

** Attachment added: "xenial_libvirt_uid_v4.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4805989/+files/xenial_libvirt_uidgid_v4.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

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

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

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

  12 microg5 running

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

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

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

  [Regression Potential]

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

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

  [Other Info]

   * None at this time.

  <...>

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

  Sorry about the inconvenience.

  <...>

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

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

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

[Mauricio Faria de Oliveira]

Okay, thanks again for all you (excellent) support on all this,
Christian.

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

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

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

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

  12 microg5 running

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

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

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

  [Regression Potential]

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

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

  [Other Info]

   * None at this time.

  <...>

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

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Triaged

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

The Content-Range issue with partial downloads on SF is tracked in bug
1657567 now. That's less urgent though, so we may just want to roll that
one out when I do the next "scheduled" bugfix update.

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

OK. We now have comments of success from yakkety and xenial, and I have
also checked both, so marking it verified-done.

I'll open up a new bug for the partial download issue.

** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1651923

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657567] [NEW] "Content-Range: */" on non-416 responses considered invalid

[Julian Andres Klode]

Public bug reported:

APT only allows Content-Range: */ to be specified on a 416
response. Sourceforge sometimes replies with that in a 302 redirect.

We should probably just accept and silently ignore that content-range
field for other values.

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

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

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

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

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Triaged

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Adrien Beau]

I have tested the new package on Xenial, following the instructions in
https://wiki.ubuntu.com/Testing/EnableProposed

APT packages installed before updating:

apt  1.2.18
apt-transport-https  1.2.18
apt-utils1.2.18
libapt-inst2.0   1.2.18
libapt-pkg5.01.2.18

Bug cases reproduced before updating:

1) dpkg-reconfigure update-notifier-common (calls apt-helper)
2) apt-helper download-file downloads.sourceforge.net
3) apt-helper download-file people.debian.org/~jak

Bug case *not* reproduced before updating:

4) apt-helper download-file kxstudio.linuxaudio.org

In this case, it appears that GitHub fixed its redirect response so it
does not include spaces anymore (I see a %20 in the reply now).


APT packages installed after updating:

apt  1.2.19
apt-transport-https  1.2.19
apt-utils1.2.19
libapt-inst2.0   1.2.19
libapt-pkg5.01.2.19

Bug cases fixed by updating:

1) dpkg-reconfigure update-notifier-common (calls apt-helper)
2) apt-helper download-file downloads.sourceforge.net
3) apt-helper download-file people.debian.org/~jak

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architectu

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Elvis Stansvik]

Julian: Ah, indeed. If I make sure to use https against the SF, and make
sure the file doesn't exist, it works reliably. Sorry for the confusion!

So, LGTM from xenial.

Thanks a lot for working this out!

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

[Gerry Boland]

Yeah I figured it out. Non rootless (rooted!) XMir wants to decide the
display power state (DPMS). Unity8/QtMir never had to deal with clients
doing that before.

Longer term Unity8 should filter such requests as it's quite rude for an
app to be able to turn off your display on you, but I've a branch up to
at least not crash.

I've more work to do on this though, as waking up the display isn't
working with that branch. To be continued

** Branch linked: lp:~gerboland/qtmir/fix-glcontext-loss-on-reconfigure

** Changed in: qtmir (Ubuntu)
   Status: Confirmed => In Progress

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Gerry Boland (gerboland)

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

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

Title:
  Unity8 crashes with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151130.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d
  contains more details.

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

The first log looks entirely correct. The server is broken, vorboss does
not support partial requests, but instead of responding correctly with
all the content, it just redirects to another location. That other
location is http, so unencrypted which we do not allow for security
reasons.

Re the invalid content-range - Delete the file and it will work again.
Their servers have another weird thing they do when replying to a
request for partial content:

HTTP/1.1 302 Moved Temporarily
[...]
Content-Range: bytes */198384

They are responding with a Content-Range field for a redirect which
really makes no sense. That's another issue I should be fixing, but it's
really unrelated to that one and a bit less urgent.

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[ChristianEhrhardt]

Ok, test succeeded - sponsoring the upload.

It is in the SRU queue now and I pinged the Release Team for you if
there is any chance to slip into 16.04.2

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

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

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

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

  12 microg5 running

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

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

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

  [Regression Potential]

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

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

  [Other Info]

   * None at this time.

  <...>

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

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

And note that the redirect from vorboss is to a site that indicates a
failure, not the file.

Or in short: Sourceforge sucks, don't use it.

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Nico Orrù]

Yep, fixed! Great work! Thanks for your time!

```
norru@GBWWSRUNUBWS02:~$ sudo apt install apt-transport-https
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  apt-transport-https
1 to upgrade, 0 to newly install, 0 to remove and 76 not to upgrade.
Need to get 34.3 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://gb.archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 
apt-transport-https amd64 1.3.4 [34.3 kB]
Fetched 34.3 kB in 0s (679 kB/s)   
(Reading database ... 348718 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_1.3.4_amd64.deb ...
Unpacking apt-transport-https (1.3.4) over (1.3.3) ...
Setting up apt-transport-https (1.3.4) ...
norru@GBWWSRUNUBWS02:~$ /usr/lib/apt/apt-helper download-file 
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb 
test.deb
Get:1 
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb 
[60.2 MB]
Fetched 60.2 MB in 6s (8,814 kB/s)
```

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Archit

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

[Joshua R. Poulson]

We tested Xenial as well. Trusty is missing some other required
packages.

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Fix Committed
Status in krb5 source package in Xenial:
  Fix Committed
Status in krb5 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

  [Test Case]

  create a file with some credentials:

  $ echo F23:guest:guest > ~/ntlmcreds.txt
  $ export NTLM_USER_FILE=~/ntlmcreds.txt
  $ python
  import gssapi

  spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
  c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
  tname = gssapi.raw.names.import_name("F23/server", 
name_type=gssapi.raw.types.NameType.hostbased_service)
  ac = gssapi.creds.Credentials(mechs=[spnego], usage='accept')

  seci = gssapi.SecurityContext(creds=c, name=tname, mech=spnego, 
usage='initiate')
  seca = gssapi.SecurityContext(creds=ac, usage='accept')
  it = seci.step(token=None)
  ot = seca.step(token=it)
  it = seci.step(token=ot)
  ot = seca.step(token=it)
  it = seci.step(token=ot)

  e = seci.wrap("Secrets", True)
  o = seca.unwrap(e.message)

  o.message
  'Secrets'

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

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

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

[Joshua R. Poulson]

Bruce is saying that he tested Trusty as well.

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Fix Committed
Status in krb5 source package in Xenial:
  Fix Committed
Status in krb5 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

  [Test Case]

  create a file with some credentials:

  $ echo F23:guest:guest > ~/ntlmcreds.txt
  $ export NTLM_USER_FILE=~/ntlmcreds.txt
  $ python
  import gssapi

  spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
  c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
  tname = gssapi.raw.names.import_name("F23/server", 
name_type=gssapi.raw.types.NameType.hostbased_service)
  ac = gssapi.creds.Credentials(mechs=[spnego], usage='accept')

  seci = gssapi.SecurityContext(creds=c, name=tname, mech=spnego, 
usage='initiate')
  seca = gssapi.SecurityContext(creds=ac, usage='accept')
  it = seci.step(token=None)
  ot = seca.step(token=it)
  it = seci.step(token=ot)
  ot = seca.step(token=it)
  it = seci.step(token=ot)

  e = seci.wrap("Secrets", True)
  o = seca.unwrap(e.message)

  o.message
  'Secrets'

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

Again: You need to install apt-transport-https, not apt. Nobody cares
about your version of the apt package, the fix is in apt-transport-
https.

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

Another test case is downloading

"https://people.debian.org/~jak/a b/c"

with apt-helper. That fails in 1.2.18 and succeeds in 1.2.19.

** Description changed:

  [Impact]
- Downloads via HTTPS fail if the URL contains a space. This breaks packages 
like ttf-mscorefonts-installer and various third party hosters.
+ Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.
  
  [Test case]
+ Install/Upgrade apt-transport-https, that's where the fix is.
+ 
  Check that
  
  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb
  
  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.
  
  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.
  
  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.
  
  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");
  
  Some servers might not like + or ~ being quoted. We use the same quoting
  call for the http method too, though, so it seems highly unlikely to
  cause an issue.
  
  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  
  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)
  
  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:
  
  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?
  
  Error allegedly not present in Ubuntu 14.04 and 16.04
  
  More details in these forum posts:
  
  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503
  
  https://www.linuxmusicians.com/viewtopic.php?t=16056
  
  https://www.drupal.org/node/2324991 (clues on root cause)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1651923

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully do

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

This problem does not occur with that file on xenial, as it first
redirects to an https URI without a space which then redirects to an
HTTPS uri with a space (http w/o space -> https w/o space -> https w/
space). In xenial, https->https redirects where handled internally by
curl.

Another test (applicable to xenial) is to install ttf-mscorefonts-
installer.


And please note: You need to upgrade apt-transport-https for testing, just apt 
does nothing.

** Description changed:

  [Impact]
  Downloads via HTTPS fail if the URL contains a space. This breaks packages 
like ttf-mscorefonts-installer and various third party hosters.
  
  [Test case]
- Check that 
+ Check that
  
  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb
  
  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.
+ 
+ This problem does not occur with that file on xenial, as it first
+ redirects to an https URI without a space which then redirects to an
+ HTTPS uri with a space (http w/o space -> https w/o space -> https w/
+ space). In xenial, https->https redirects where handled internally by
+ curl.
+ 
+ Another test (applicable to xenial) is to install ttf-mscorefonts-
+ installer.
  
  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");
  
  Some servers might not like + or ~ being quoted. We use the same quoting
  call for the http method too, though, so it seems highly unlikely to
  cause an issue.
  
  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  
  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)
  
  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:
  
  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?
  
  Error allegedly not present in Ubuntu 14.04 and 16.04
  
  More details in these forum posts:
  
  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503
  
  https://www.linuxmusicians.com/viewtopic.php?t=16056
  
  https://www.drupal.org/node/2324991 (clues on root cause)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1651923

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space. This breaks packages 
like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not sup

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Brian Murray]

Here is the debug output with 1.2.18.

** Attachment added: "debug-output.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+attachment/4805952/+files/debug-output.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/1651923

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space. This breaks packages 
like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576282] Re: Snaps built from deb can't be gettext translated

[Christian Dywan]

Responding to my own comment: indeed we only need to count the memory
used by individual files accessed by a snap on top of the compressed
size on disk. Which for a single locale is negligible. So it's worth re-
considering including the locales with each platform snap.

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

Title:
  Snaps built from deb can't be gettext translated

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

Bug description:
  Currently it seems not possible to have working gettext translations
  without included a patch glibc build in your snap

  - the core image doesn't have locales definition

  that can be worked around by including locales definitions in the
  snap, though that's tedious, ideally snapcraft would help there

  
  - traditional desktop applications are built with calls to 'bindtextdomain 
("domain", LOCALEDIR)', where LOCALDIR is defined at buildtime and so pointing 
to /usr 

  there seems to be no way to redirect to another directory at runtime

  
  - desktop applications needs system library translations sometime which means 
langpacks need to be included in snaps

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

@Robin: I just confirmed that apt 1.2.19 fixes the corefonts issue:

All fonts downloaded and installed.
Setting up ttf-mscorefonts-installer (3.4+nmu1ubuntu2) ...

Did you really upgrade apt-transport-https or only apt?


But bdmurray is right, the ardour thing works fine in 1.2.18. In xenial with 
1.3.3 it fails with 
"505  HTTP Version not supported" though.

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space. This breaks packages 
like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1575614] Re: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication

[SergeyMtv]

Fresh installed 16.04.1 with updates:
network-manager/xenial-proposed,now 1.2.4-0ubuntu0.16.04.01 amd64
network-manager-gnome/xenial-updates,now 1.2.0-0ubuntu0.16.04.4 amd64

I confirm the bug. I see an empty list when try to select private key file 
(privkey.pem) in 802.1x tab.
The above mentioned workaround with dran&drop from nautilus works with warning 
message about empty password (wrong).

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

Title:
  [SRU]Can't select p12 secret key for TLS auth for 802.1X
  authentication

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Users cannot select TLS certificate when connecting to a network that
  requires TLS type 802.1X authentication

  [Test case]
  STR:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  For wifi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  [Regression Potential]
  The fix is quite straight forward and the possibility of causing regression 
is limited.

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

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

[Touch-packages] [Bug 1576282] Re: Snaps built from deb can't be gettext translated

[Christian Dywan]

Perhaps I'm thinking about it wrong - but the uncompressed data has to
reside in memory at least? Even if it's not "on disk" per se. So having
an extra 100M in memory could still be quite bad.

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

Title:
  Snaps built from deb can't be gettext translated

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

Bug description:
  Currently it seems not possible to have working gettext translations
  without included a patch glibc build in your snap

  - the core image doesn't have locales definition

  that can be worked around by including locales definitions in the
  snap, though that's tedious, ideally snapcraft would help there

  
  - traditional desktop applications are built with calls to 'bindtextdomain 
("domain", LOCALEDIR)', where LOCALDIR is defined at buildtime and so pointing 
to /usr 

  there seems to be no way to redirect to another directory at runtime

  
  - desktop applications needs system library translations sometime which means 
langpacks need to be included in snaps

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

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

[Touch-packages] [Bug 1582394] Re: [16.04, lxc] Failed to reset devices.list on ...

[Alvaro Uría]

Linux 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:55:08 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux

I've created an Ubuntu Xenial LXC on top of an Ubuntu Xenial node and
have run:

snap install hello-world

root@juju-machine-0-lxc-1:~# journalctl -xe
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/mdadm.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/apparmor.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/atd.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/dev-lxc-tty3.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/system-getty.slice: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/cloud-init.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/proc-uptime.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/systemd-logind.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/dev-lxc-tty1.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/proc-swaps.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/dev-mqueue.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/ufw.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/proc-stat.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/resolvconf.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/proc-diskstats.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/ondemand.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/proc-sysrq\x2dtrigger.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/dev-lxc-tty2.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/cloud-config.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/cron.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/run-user-1000.mount: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/cloud-final.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/jujud-unit-prometheus-0.service: Operation not permitted
Jan 18 17:23:15 juju-machine-0-lxc-1 systemd[1]: Failed to reset devices.list 
on /system.slice/iscsid.service: Operation not permitted
Jan 18 17:23:16 juju-machine-0-lxc-1 systemd[1]: snap-core-714.mount: Mount 
process exited, code=exited status=32
Jan 18 17:23:16 juju-machine-0-lxc-1 systemd[1]: Failed to mount Mount unit for 
core. 


** Tags added: canonical-bootstack

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

Title:
  [16.04, lxc] Failed to reset devices.list on ...

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This seems to be identical to Bug #1413193 which affected 15.04 and
  was marked Fix Released.

  On a 16.04 host with a 16.04 container:

  $ lxc-create -t download -n vpn01 -- -d ubuntu -r xenial -a amd64
  $ lxc-start -n vpn02 -d

  the container syslog shows repeated instances of "Failed to reset
  devices.list on ..." and continues generating such messages:

  $ grep devices.list .local/share/lxc/vpn01/rootfs/var/log/syslog

  May 16 14:37:20 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-remount-fs.service: Operation not permitted
  May 16 14:37:20 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/systemd-random-seed.service: Operation not permitted
  May 16 14:37:23 vpn01 systemd[1]: Failed to reset devices.list on 
/system.slice/rc-local.service: Operation not permitted
  May 16 14

[Touch-packages] [Bug 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml

[Michal Predotka]

Can we have this in OTA15?

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

Title:
  Invalid property assignment in ActivityIndicatorStyle.qml

Status in Canonical System Image:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  I get

  file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

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

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

[Touch-packages] [Bug 1272028] Re: remount, not honored on bind mounts

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5~14.04.1

---
apparmor (2.10.95-0ubuntu2.5~14.04.1) trusty; urgency=medium

  * Bring apparmor 2.10.95-0ubuntu2.5, from Ubuntu 16.04, to Ubuntu 14.04.
- This allows for proper snap confinement on Ubuntu 14.04 when using the
  hardware enablement kernel (LP: #1641243)
  * Changes made on top of 2.10.95-0ubuntu2.5:
- debian/apparmor.upstart: Remove the upstart job and continue using the
  init script in 14.04
- debian/apparmor.postinst, debian/apparmor-profiles.postinst,
  debian/apparmor-profiles.postrm, debian/rules: Revert to using
  invoke-rc.d to load the profiles, rather than reloading them directly,
  since 14.04 will continue using the init script rather than the upstart
  job.
- debian/apparmor.init, debian/lib/apparmor/functions,
  debian/apparmor.postinst, debian/apparmor.postrm: Remove functionality
  dealing with AppArmor policy in system image based environments since
  this 14.04 package will not need to handle such environments. This
  removes the handle_system_policy_package_updates(),
  compare_previous_version(), compare_and_save_debsums() functions and
  their callers.
- debian/apparmor.init: Continue using running-in-container since
  systemd-detect-virt doesn't exist on 14.04
- debian/lib/apparmor/functions, debian/apparmor.init: Remove the
  is_container_with_internal_policy() function and adjust its call sites
  in apparmor.init so that AppArmor policy is not loaded inside of 14.04
  LXD containers (avoids bug #1641236)
- debian/lib/apparmor/profile-load, debian/apparmor.install: Remove
  profile-load as upstart's apparmor-profile-load is used in 14.04
- debian/patches/libapparmor-mention-dbus-method-in-getcon-man.patch:
  Continue applying this patch since the dbus version in 14.04 isn't new
  enough to support fetching the AppArmor context from
  org.freedesktop.DBus.GetConnectionCredentials().
- debian/patches/libapparmor-force-libtoolize-replacement.patch: Force
  libtoolize to replace existing files to fix a libapparmor FTBFS issue on
  14.04.
- debian/control: Retain the original 14.04 Breaks and ignore the new
  Breaks from 2.10.95-0ubuntu2.5 since they were put in place as part of
  the enablement of UNIX domain socket mediation. They're not needed in
  this upload since UNIX domain socket mediation is disabled by default so
  updates to the profiles included in those packages are not needed.
- Preserve the profiles and abstractions from 14.04's
  2.8.95~2430-0ubuntu5.3 apparmor package by recreating them in the
  top-level profiles-14.04/ directory of the source. They'll be installed
  to debian/tmp/etc/apparmor.d/ during the build process and then to
  /etc/apparmor.d/ on package install so that there are no changes to the
  shipped profiles or abstractions. The abstractions from
  2.10.95-0ubuntu2.5 will be installed into
  debian/tmp/snap/etc/apparmor.d/ during the build process and then into
  /etc/apparmor.d/snap/abstractions/ on package install for use with snap
  confinement. Snap confinement profiles, which includes AppArmor profiles
  loaded by snapd and profiles loaded by snaps that are allowed to manage
  AppArmor policy, will use the snap abstractions. All other AppArmor
  profiles will continue to use the 14.04 abstractions.
  - debian/rules: Adjust for new profiles-14.04/ directory
  - debian/apparmor-profiles.install: Adjust to install the profiles that
were installed in the 2.8.95~2430-0ubuntu5.3 package
  - debian/apparmor.install: Install the abstractions from the
2.10.95-0ubuntu2.5 package into /etc/apparmor.d/snap/abstractions/
  - debian/patches/14.04-profiles.patch: Preserve the 14.04 profiles and
abstractions from the 2.8.95~2430-0ubuntu5.3 apparmor package.
  - debian/patches/conditionalize-post-release-features.patch: Disable new
mediation features, implemented after the Ubuntu 14.04 release, unless
the profile is for snap confinement. If the profile is for snap
confinement, the abstractions from /etc/apparmor.d/snap/abstractions
will be used and all of the mediation features will be enabled.
- 14.04-add-chromium-browser.patch,
  14.04-add-debian-integration-to-lighttpd.patch,
  14.04-etc-writable.patch,
  14.04-update-base-abstraction-for-signals-and-ptrace.patch,
  14.04-dnsmasq-libvirtd-signal-ptrace.patch,
  14.04-update-chromium-browser.patch,
  14.04-php5-Zend_semaphore-lp1401084.patch,
  14.04-dnsmasq-lxc_networking-lp1403468.patch,
  14.04-profiles-texlive_font_generation-lp1010909.patch,
  14.04-profiles-dovecot-updates-lp1296667.patch,
  14.04-profiles-adjust_X_for_lightdm-lp1339727.patch: Import all of the
  patches, from 14.04's 2.8.95~2430-0ubuntu5.3 

[Touch-packages] [Bug 1305108] Re: please provide upstart job for apparmor

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5~14.04.1

---
apparmor (2.10.95-0ubuntu2.5~14.04.1) trusty; urgency=medium

  * Bring apparmor 2.10.95-0ubuntu2.5, from Ubuntu 16.04, to Ubuntu 14.04.
- This allows for proper snap confinement on Ubuntu 14.04 when using the
  hardware enablement kernel (LP: #1641243)
  * Changes made on top of 2.10.95-0ubuntu2.5:
- debian/apparmor.upstart: Remove the upstart job and continue using the
  init script in 14.04
- debian/apparmor.postinst, debian/apparmor-profiles.postinst,
  debian/apparmor-profiles.postrm, debian/rules: Revert to using
  invoke-rc.d to load the profiles, rather than reloading them directly,
  since 14.04 will continue using the init script rather than the upstart
  job.
- debian/apparmor.init, debian/lib/apparmor/functions,
  debian/apparmor.postinst, debian/apparmor.postrm: Remove functionality
  dealing with AppArmor policy in system image based environments since
  this 14.04 package will not need to handle such environments. This
  removes the handle_system_policy_package_updates(),
  compare_previous_version(), compare_and_save_debsums() functions and
  their callers.
- debian/apparmor.init: Continue using running-in-container since
  systemd-detect-virt doesn't exist on 14.04
- debian/lib/apparmor/functions, debian/apparmor.init: Remove the
  is_container_with_internal_policy() function and adjust its call sites
  in apparmor.init so that AppArmor policy is not loaded inside of 14.04
  LXD containers (avoids bug #1641236)
- debian/lib/apparmor/profile-load, debian/apparmor.install: Remove
  profile-load as upstart's apparmor-profile-load is used in 14.04
- debian/patches/libapparmor-mention-dbus-method-in-getcon-man.patch:
  Continue applying this patch since the dbus version in 14.04 isn't new
  enough to support fetching the AppArmor context from
  org.freedesktop.DBus.GetConnectionCredentials().
- debian/patches/libapparmor-force-libtoolize-replacement.patch: Force
  libtoolize to replace existing files to fix a libapparmor FTBFS issue on
  14.04.
- debian/control: Retain the original 14.04 Breaks and ignore the new
  Breaks from 2.10.95-0ubuntu2.5 since they were put in place as part of
  the enablement of UNIX domain socket mediation. They're not needed in
  this upload since UNIX domain socket mediation is disabled by default so
  updates to the profiles included in those packages are not needed.
- Preserve the profiles and abstractions from 14.04's
  2.8.95~2430-0ubuntu5.3 apparmor package by recreating them in the
  top-level profiles-14.04/ directory of the source. They'll be installed
  to debian/tmp/etc/apparmor.d/ during the build process and then to
  /etc/apparmor.d/ on package install so that there are no changes to the
  shipped profiles or abstractions. The abstractions from
  2.10.95-0ubuntu2.5 will be installed into
  debian/tmp/snap/etc/apparmor.d/ during the build process and then into
  /etc/apparmor.d/snap/abstractions/ on package install for use with snap
  confinement. Snap confinement profiles, which includes AppArmor profiles
  loaded by snapd and profiles loaded by snaps that are allowed to manage
  AppArmor policy, will use the snap abstractions. All other AppArmor
  profiles will continue to use the 14.04 abstractions.
  - debian/rules: Adjust for new profiles-14.04/ directory
  - debian/apparmor-profiles.install: Adjust to install the profiles that
were installed in the 2.8.95~2430-0ubuntu5.3 package
  - debian/apparmor.install: Install the abstractions from the
2.10.95-0ubuntu2.5 package into /etc/apparmor.d/snap/abstractions/
  - debian/patches/14.04-profiles.patch: Preserve the 14.04 profiles and
abstractions from the 2.8.95~2430-0ubuntu5.3 apparmor package.
  - debian/patches/conditionalize-post-release-features.patch: Disable new
mediation features, implemented after the Ubuntu 14.04 release, unless
the profile is for snap confinement. If the profile is for snap
confinement, the abstractions from /etc/apparmor.d/snap/abstractions
will be used and all of the mediation features will be enabled.
- 14.04-add-chromium-browser.patch,
  14.04-add-debian-integration-to-lighttpd.patch,
  14.04-etc-writable.patch,
  14.04-update-base-abstraction-for-signals-and-ptrace.patch,
  14.04-dnsmasq-libvirtd-signal-ptrace.patch,
  14.04-update-chromium-browser.patch,
  14.04-php5-Zend_semaphore-lp1401084.patch,
  14.04-dnsmasq-lxc_networking-lp1403468.patch,
  14.04-profiles-texlive_font_generation-lp1010909.patch,
  14.04-profiles-dovecot-updates-lp1296667.patch,
  14.04-profiles-adjust_X_for_lightdm-lp1339727.patch: Import all of the
  patches, from 14.04's 2.8.95~2430-0ubuntu5.3 

[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls

[Launchpad Bug Tracker]

This bug was fixed in the package libseccomp - 2.1.1-1ubuntu1~trusty3

---
libseccomp (2.1.1-1ubuntu1~trusty3) trusty-proposed; urgency=medium

  * Cherrypick various bpf fixes to support argument filtering on 64-bit
(LP: #1653487)
- debian/patches/bpf-use-state-arch.patch: use state->arch instead of
  db->arch in _gen_bpf_arch()
- debian/patches/db-require-filters-to-share-endianess.patch: require all
  filters in a collection to share the same endianess
- debian/patches/resolve-issues-caused-by-be.patch: resolve issues caused
  by big endian systems
- debian/patches/bpf-accumulator-check.patch: test the bpf accumulator
  checking logic
- debian/patches/bpf-track-accumulator-state.patch: track accumulator
  state and reload it when necessary. This is the fix for LP: #1653487. The
  previous patches are required by this patch.
- debian/patches/ensure-simulator-has-valid-arch.patch: ensure the
  simulator always has a valid architecture value. This fixes a regression
  in the testsuite introduced by resolve-issues-caused-by-be.patch
- debian/patches/bpf-accumulator-check-indep.patch: fix a regression in the
  testsuite introduced by bpf-accumulator-check.patch
- debian/patches/fix-audit-arch-i386.patch: fix arch token for 32-bit x86
  not being defined correctly for the tools

libseccomp (2.1.1-1ubuntu1~trusty1) trusty-proposed; urgency=medium

  * Bring libseccomp 2.1.1-1ubuntu1~vivid2, from Ubuntu 14.10, to Ubuntu
14.04 and add a couple patches to account for new syscalls found in the
4.4 based hardware enablement kernel. This allows for proper snap seccomp
confinement on Ubuntu 14.04 when using the hardware enablement kernel
(LP: #1450642)
- debian/patches/add-membarrier-and-userfaultfd.patch: Add membarrier and
  userfaultfd syscalls
- debian/patches/add-mlock2.patch: Add mlock2 syscall
- debian/tests/data/all-except-s390-4.4.filter: Add autopkgtest that
  verifies all syscalls found in the 4.4 kernel, except for the s390
  specific syscalls, are supported by libseccomp. The s390 specific
  syscalls are not needed since this version of libseccomp does not
  support the s390 architecture.
- debian/tests/test-filter: Skip the getrandom filter tests since
  SYS_getrandom is not defined in 14.04 environment and the getrandom(2)
  syscall is not even available in the 14.04 release kernel.

libseccomp (2.1.1-1ubuntu1~vivid2) vivid-proposed; urgency=medium

  * add-finit-module.patch: add finit_module syscalls to x86 and x86-64
syscall tables
  * update syscalls for modern kernels (skipping MIPS)
- update syscalls for 3.16:
  + update-x86-syscall-table.patch
  + update-x86_64-syscall-table.patch
  + update-arm-syscall-table.patch
  + update-x32-syscall-table.patch
  + sync-syscall-table-entries.patch
  + sync-syscall-table-entries-fixtypo.patch
- update syscalls for 3.17:
  + sync-syscall-table-entries-3.17.patch
- update syscalls for 3.19:
  + sync-syscall-table-entries-3.19.patch
- LP: #1450642
  * fix-segfault-with-unknown.patch: fix segfault when find unknown syscall
  * debian/patches/add-missing-arm-private-syscalls.path: add missing private
ARM syscalls
  * add autopkgtests for scmp_sys_resolver and filter testing and
SYS_getrandom() testing

libseccomp (2.1.1-1) unstable; urgency=low

  * New upstream release (Closes: 733293).
  * copyright: add a few missed people.
  * rules: adjusted for new test target.
  * libseccomp2.symbols: drop accidentally exported functions.
  * control:
- bump standards, no changes needed.
- add armel target

 -- Jamie Strandboge   Wed, 04 Jan 2017 21:11:30 +

** Changed in: libseccomp (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  seccomp missing many new syscalls

Status in Snappy:
  Fix Released
Status in Snappy 15.04 series:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  Fix Released
Status in libseccomp source package in Vivid:
  Fix Released
Status in libseccomp source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Several syscalls were discovered to be missing when using the launcher on 
snappy. These should be added so we may properly support seccomp filtering.

  [Test Case]
  seccomp itself has a comprehensive testsuite, and while it doesn't fail the 
build, regressions can be seen by looking at the build log. Eg:

  Regression Test Summary
  tests run: 6494
  tests skipped: 52
  tests passed: 6494
  tests failed: 0
  tests errored: 0

  Furthermore, on a snappy system, perform:
  # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed 
an

[Touch-packages] [Bug 1466812] Re: aa-logprof crash

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5~14.04.1

---
apparmor (2.10.95-0ubuntu2.5~14.04.1) trusty; urgency=medium

  * Bring apparmor 2.10.95-0ubuntu2.5, from Ubuntu 16.04, to Ubuntu 14.04.
- This allows for proper snap confinement on Ubuntu 14.04 when using the
  hardware enablement kernel (LP: #1641243)
  * Changes made on top of 2.10.95-0ubuntu2.5:
- debian/apparmor.upstart: Remove the upstart job and continue using the
  init script in 14.04
- debian/apparmor.postinst, debian/apparmor-profiles.postinst,
  debian/apparmor-profiles.postrm, debian/rules: Revert to using
  invoke-rc.d to load the profiles, rather than reloading them directly,
  since 14.04 will continue using the init script rather than the upstart
  job.
- debian/apparmor.init, debian/lib/apparmor/functions,
  debian/apparmor.postinst, debian/apparmor.postrm: Remove functionality
  dealing with AppArmor policy in system image based environments since
  this 14.04 package will not need to handle such environments. This
  removes the handle_system_policy_package_updates(),
  compare_previous_version(), compare_and_save_debsums() functions and
  their callers.
- debian/apparmor.init: Continue using running-in-container since
  systemd-detect-virt doesn't exist on 14.04
- debian/lib/apparmor/functions, debian/apparmor.init: Remove the
  is_container_with_internal_policy() function and adjust its call sites
  in apparmor.init so that AppArmor policy is not loaded inside of 14.04
  LXD containers (avoids bug #1641236)
- debian/lib/apparmor/profile-load, debian/apparmor.install: Remove
  profile-load as upstart's apparmor-profile-load is used in 14.04
- debian/patches/libapparmor-mention-dbus-method-in-getcon-man.patch:
  Continue applying this patch since the dbus version in 14.04 isn't new
  enough to support fetching the AppArmor context from
  org.freedesktop.DBus.GetConnectionCredentials().
- debian/patches/libapparmor-force-libtoolize-replacement.patch: Force
  libtoolize to replace existing files to fix a libapparmor FTBFS issue on
  14.04.
- debian/control: Retain the original 14.04 Breaks and ignore the new
  Breaks from 2.10.95-0ubuntu2.5 since they were put in place as part of
  the enablement of UNIX domain socket mediation. They're not needed in
  this upload since UNIX domain socket mediation is disabled by default so
  updates to the profiles included in those packages are not needed.
- Preserve the profiles and abstractions from 14.04's
  2.8.95~2430-0ubuntu5.3 apparmor package by recreating them in the
  top-level profiles-14.04/ directory of the source. They'll be installed
  to debian/tmp/etc/apparmor.d/ during the build process and then to
  /etc/apparmor.d/ on package install so that there are no changes to the
  shipped profiles or abstractions. The abstractions from
  2.10.95-0ubuntu2.5 will be installed into
  debian/tmp/snap/etc/apparmor.d/ during the build process and then into
  /etc/apparmor.d/snap/abstractions/ on package install for use with snap
  confinement. Snap confinement profiles, which includes AppArmor profiles
  loaded by snapd and profiles loaded by snaps that are allowed to manage
  AppArmor policy, will use the snap abstractions. All other AppArmor
  profiles will continue to use the 14.04 abstractions.
  - debian/rules: Adjust for new profiles-14.04/ directory
  - debian/apparmor-profiles.install: Adjust to install the profiles that
were installed in the 2.8.95~2430-0ubuntu5.3 package
  - debian/apparmor.install: Install the abstractions from the
2.10.95-0ubuntu2.5 package into /etc/apparmor.d/snap/abstractions/
  - debian/patches/14.04-profiles.patch: Preserve the 14.04 profiles and
abstractions from the 2.8.95~2430-0ubuntu5.3 apparmor package.
  - debian/patches/conditionalize-post-release-features.patch: Disable new
mediation features, implemented after the Ubuntu 14.04 release, unless
the profile is for snap confinement. If the profile is for snap
confinement, the abstractions from /etc/apparmor.d/snap/abstractions
will be used and all of the mediation features will be enabled.
- 14.04-add-chromium-browser.patch,
  14.04-add-debian-integration-to-lighttpd.patch,
  14.04-etc-writable.patch,
  14.04-update-base-abstraction-for-signals-and-ptrace.patch,
  14.04-dnsmasq-libvirtd-signal-ptrace.patch,
  14.04-update-chromium-browser.patch,
  14.04-php5-Zend_semaphore-lp1401084.patch,
  14.04-dnsmasq-lxc_networking-lp1403468.patch,
  14.04-profiles-texlive_font_generation-lp1010909.patch,
  14.04-profiles-dovecot-updates-lp1296667.patch,
  14.04-profiles-adjust_X_for_lightdm-lp1339727.patch: Import all of the
  patches, from 14.04's 2.8.95~2430-0ubuntu5.3 

[Touch-packages] [Bug 1653487] Update Released

[Robie Basak]

The verification of the Stable Release Update for libseccomp 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 libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1653487

Title:
  seccomp argument filtering not working on trusty amd64

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was 
exposed in the snapd build testsuite when run on amd64. It has to do with 
libseccomp's state machine not always working correctly when using argument 
filtering and there were no tests for this particular failure in 2.1. Once 
19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is 
applied to 2.1, you see the failures. Simple seccomp filters that just use the 
syscall name are not affected by the bug and we (currently) only use seccomp 
arg filtering in one interface which is why Tyler's testing of 
2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do 
exercise it, but seccomp argument filtering wasn't added until series 16 and 
seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine 
and all of snap-confine's arg filtering tests to trusty revealed the bug in 
seccomp 2.1.

  [Test Case]
  A test case is included in the build in 
debian/patches/bpf-accumulator-check.patch 
(19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log 
to verify no failures.

  You can also run the snapd testsuite:
  0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  1. enable deb-src trusty-proposed to get snapd 2.20
  2. apt-get source snapd
  3. cd ./snapd-2.20*
  4. apt-get build-dep snapd
  5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the 
problem)
  6. debian/rules build # this should fail on amd64
  ...
  FAIL: test_restrictions_working_args
  ...
  7. install libseccomp2 libseccomp-dev from trusty-proposed
  8. debian/rules clean ; debian/rules build # this should pass

  In addition, follow the testing procedures as outlined in bug #1450642

  [Regression Potential]

  The patch to fix this issue required several other supporting patches.
  This patches applied cleanly to trusty and the patches themselves are
  well tested under upstream and 16.04+. The regression potential should
  be relatively low since the testsuite during the build shows no errors
  or failures and snapd has a big testsuite. Manually testing with snaps
  and lxc (the biggest consumers of libseccomp) and running the
  libseccomp autopkgtests also shows no issues.

  = Original description =
  The snapd build on trusty for amd64 fails with the following error:
  """
  make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests'
  ...
  PASS: test_restrictions_working
  FAIL: test_restrictions_working_args
  """
  (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913)

  The same build works for i386 and armhf.

  I can reproduce this in a trusty chroot, upon further investigation it looks
  like the version of libseccomp (2.1.1) in trusty-proposed is the culprit.

  When I upgrade:
  """
  Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 
2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 
2.2.3-2ubuntu1~ubuntu14.04.1)
  
  all tests run fine. It looks like an issue with seccomp argument filtering 
(bpf) on 64 bit systems.
  This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include 
the missing fix,
  however I have not looked in detail what patch exactly we may need.

  Fwiw, we don't see this in spread because we build the package in the
  spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg-
  buildpackage` and we do not run the integration tests of snap-confine
  in anything else beside the package build (until
  https://github.com/snapcore/snapd/pull/2433/files is merged).

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

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

[Touch-packages] [Bug 1641243] Re: Provide full AppArmor confinement for snaps on 14.04

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5~14.04.1

---
apparmor (2.10.95-0ubuntu2.5~14.04.1) trusty; urgency=medium

  * Bring apparmor 2.10.95-0ubuntu2.5, from Ubuntu 16.04, to Ubuntu 14.04.
- This allows for proper snap confinement on Ubuntu 14.04 when using the
  hardware enablement kernel (LP: #1641243)
  * Changes made on top of 2.10.95-0ubuntu2.5:
- debian/apparmor.upstart: Remove the upstart job and continue using the
  init script in 14.04
- debian/apparmor.postinst, debian/apparmor-profiles.postinst,
  debian/apparmor-profiles.postrm, debian/rules: Revert to using
  invoke-rc.d to load the profiles, rather than reloading them directly,
  since 14.04 will continue using the init script rather than the upstart
  job.
- debian/apparmor.init, debian/lib/apparmor/functions,
  debian/apparmor.postinst, debian/apparmor.postrm: Remove functionality
  dealing with AppArmor policy in system image based environments since
  this 14.04 package will not need to handle such environments. This
  removes the handle_system_policy_package_updates(),
  compare_previous_version(), compare_and_save_debsums() functions and
  their callers.
- debian/apparmor.init: Continue using running-in-container since
  systemd-detect-virt doesn't exist on 14.04
- debian/lib/apparmor/functions, debian/apparmor.init: Remove the
  is_container_with_internal_policy() function and adjust its call sites
  in apparmor.init so that AppArmor policy is not loaded inside of 14.04
  LXD containers (avoids bug #1641236)
- debian/lib/apparmor/profile-load, debian/apparmor.install: Remove
  profile-load as upstart's apparmor-profile-load is used in 14.04
- debian/patches/libapparmor-mention-dbus-method-in-getcon-man.patch:
  Continue applying this patch since the dbus version in 14.04 isn't new
  enough to support fetching the AppArmor context from
  org.freedesktop.DBus.GetConnectionCredentials().
- debian/patches/libapparmor-force-libtoolize-replacement.patch: Force
  libtoolize to replace existing files to fix a libapparmor FTBFS issue on
  14.04.
- debian/control: Retain the original 14.04 Breaks and ignore the new
  Breaks from 2.10.95-0ubuntu2.5 since they were put in place as part of
  the enablement of UNIX domain socket mediation. They're not needed in
  this upload since UNIX domain socket mediation is disabled by default so
  updates to the profiles included in those packages are not needed.
- Preserve the profiles and abstractions from 14.04's
  2.8.95~2430-0ubuntu5.3 apparmor package by recreating them in the
  top-level profiles-14.04/ directory of the source. They'll be installed
  to debian/tmp/etc/apparmor.d/ during the build process and then to
  /etc/apparmor.d/ on package install so that there are no changes to the
  shipped profiles or abstractions. The abstractions from
  2.10.95-0ubuntu2.5 will be installed into
  debian/tmp/snap/etc/apparmor.d/ during the build process and then into
  /etc/apparmor.d/snap/abstractions/ on package install for use with snap
  confinement. Snap confinement profiles, which includes AppArmor profiles
  loaded by snapd and profiles loaded by snaps that are allowed to manage
  AppArmor policy, will use the snap abstractions. All other AppArmor
  profiles will continue to use the 14.04 abstractions.
  - debian/rules: Adjust for new profiles-14.04/ directory
  - debian/apparmor-profiles.install: Adjust to install the profiles that
were installed in the 2.8.95~2430-0ubuntu5.3 package
  - debian/apparmor.install: Install the abstractions from the
2.10.95-0ubuntu2.5 package into /etc/apparmor.d/snap/abstractions/
  - debian/patches/14.04-profiles.patch: Preserve the 14.04 profiles and
abstractions from the 2.8.95~2430-0ubuntu5.3 apparmor package.
  - debian/patches/conditionalize-post-release-features.patch: Disable new
mediation features, implemented after the Ubuntu 14.04 release, unless
the profile is for snap confinement. If the profile is for snap
confinement, the abstractions from /etc/apparmor.d/snap/abstractions
will be used and all of the mediation features will be enabled.
- 14.04-add-chromium-browser.patch,
  14.04-add-debian-integration-to-lighttpd.patch,
  14.04-etc-writable.patch,
  14.04-update-base-abstraction-for-signals-and-ptrace.patch,
  14.04-dnsmasq-libvirtd-signal-ptrace.patch,
  14.04-update-chromium-browser.patch,
  14.04-php5-Zend_semaphore-lp1401084.patch,
  14.04-dnsmasq-lxc_networking-lp1403468.patch,
  14.04-profiles-texlive_font_generation-lp1010909.patch,
  14.04-profiles-dovecot-updates-lp1296667.patch,
  14.04-profiles-adjust_X_for_lightdm-lp1339727.patch: Import all of the
  patches, from 14.04's 2.8.95~2430-0ubuntu5.3 

[Touch-packages] [Bug 1641243] Update Released

[Robie Basak]

The verification of the Stable Release Update for apparmor 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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1641243

Title:
  Provide full AppArmor confinement for snaps on 14.04

Status in apparmor package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  Fix Released
Status in dbus source package in Trusty:
  Fix Released

Bug description:
  = apparmor SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper AppArmor 
confinement for snaps when running under the 16.04 hardware enablement kernel. 
The apparmor userspace package in 14.04 is missing support key mediation 
features such as UNIX domain socket rules, AppArmor policy namespaces, and 
AppArmor profile stacking. UNIX domain socket mediation is needed by nearly all 
snaps. AppArmor policy namespaces and profile stacking are needed by the lxd 
snap.

  Unfortunately, it was not feasible to backport the individual features
  to the 14.04 apparmor package as they're quite complex and have a
  large number of dependency patches. Additionally, the AppArmor policy
  abstractions from Ubuntu 16.04 are needed to provide proper snap
  confinement. Because of these two reasons, the decision to bring
  16.04's apparmor package to 14.04 was (very carefully) made.

  [Test Case]

    https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor

  This update will go through the Test Plan as well as manual testing to
  verify that snap confinement on 14.04 does work. Manual tests include
  installing snapd in 14.04 and running simple snaps such as pwgen-
  tyhicks and hello-world, as well as a much more complex snap such as
  lxd.

  The following regression tests from lp:qa-regression-testing (these
  packages ship an AppArmor profile) can be used to verify that their
  respective packages do not regress:

   test-apache2-mpm-event.py
   test-apache2-mpm-itk.py
   test-apache2-mpm-perchild.py
   test-apache2-mpm-prefork.py
   test-apache2-mpm-worker.py
   test-bind9.py
   test-clamav.py
   test-cups.py
   test-dhcp.py
   test-mysql.py
   test-ntp.py
   test-openldap.py
   test-rsyslog.py
   test-squid.py
   test-strongswan.py
   test-tcpdump.py

  I have pushed changes to lp:qa-regression-testing which pulls in the
  parser and regression tests from the apparmor 2.8.95~2430-0ubuntu5.3
  package currently shipping in Trusty, in addition to the tests in the
  2.10.95 based package.

  Additionally, manually testing evince, which is confined by an
  AppArmor profile, should be done. The manual test should check basic
  functionality as well as for proper confinement (`ps auxZ` output).

  Finally, we need to test that 12.04 -> 14.04 upgrades continue to
  work. Specifically, the apparmor packages in trusty-proposed and the
  12.04 kernel need to be tested together.

  [Regression Potential]
  High. We must be extremely careful to not regress existing, confined 
applications in Ubuntu 14.04. We are lucky that the upstream AppArmor project 
has extensive regression tests and that the Ubuntu Security team adds even more 
testing via the AppArmor Test Plan.

  Care was taken to minimally change how the AppArmor policies are
  loaded during the boot process. I also verified that the abstractions
  shipped in apparmor and the profiles shipped in apparmor-profiles are
  the same across this SRU update.

  = dbus SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper D-Bus mediation 
for snaps when running under the 16.04 hardware enablement kernel. The dbus 
package in 14.04 is missing support for blocking unrequested reply messages. 
This functionality was added to the D-Bus AppArmor mediation patches after 
14.04 was released but before the patches were merged upstream in dbus. The 
idea is to prevent a malicious snap from attacking another snap, over D-Bus, 
with unrequested reply messages and also to prevent two connections from 
subverting the snap confinement by communicating via unrequested reply messages.

  [Test Case]

  The upstream AppArmor userspace project has thorough tests for D-Bus
  mediation, including unrequested replies. Its
  tests/regression/apparmor/dbus_*.sh tests should be ran before and
  after updating to the dbus SRU. Before updating, the
  dbus_unrequested_reply.sh should fail and should pass after updating.

  To run the dbus_*.sh tests:

  $ sudo apt-get install -y bzr libdbus-1-dev
  $ bzr branch lp:apparm

[Touch-packages] [Bug 1641243] Re: Provide full AppArmor confinement for snaps on 14.04

[Launchpad Bug Tracker]

This bug was fixed in the package dbus - 1.6.18-0ubuntu4.5

---
dbus (1.6.18-0ubuntu4.5) trusty; urgency=medium

  * debian/patches/unrequested-reply-mediation.patch: Don't let unrequested
reply messages through and don't audit them. Unrequested reply messages
are error or method_return messages that are sent from D-Bus connection A
to D-Bus connection B that do not correspond to any message ever sent by
D-Bus connection B. They should be quietly dropped as there's no use for
them outside of malicious activity. Patch based on upstream patches.
(LP: #1641243)

 -- Tyler Hicks   Wed, 30 Nov 2016 21:44:48 +

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

** Changed in: apparmor (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Provide full AppArmor confinement for snaps on 14.04

Status in apparmor package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  Fix Released
Status in dbus source package in Trusty:
  Fix Released

Bug description:
  = apparmor SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper AppArmor 
confinement for snaps when running under the 16.04 hardware enablement kernel. 
The apparmor userspace package in 14.04 is missing support key mediation 
features such as UNIX domain socket rules, AppArmor policy namespaces, and 
AppArmor profile stacking. UNIX domain socket mediation is needed by nearly all 
snaps. AppArmor policy namespaces and profile stacking are needed by the lxd 
snap.

  Unfortunately, it was not feasible to backport the individual features
  to the 14.04 apparmor package as they're quite complex and have a
  large number of dependency patches. Additionally, the AppArmor policy
  abstractions from Ubuntu 16.04 are needed to provide proper snap
  confinement. Because of these two reasons, the decision to bring
  16.04's apparmor package to 14.04 was (very carefully) made.

  [Test Case]

    https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor

  This update will go through the Test Plan as well as manual testing to
  verify that snap confinement on 14.04 does work. Manual tests include
  installing snapd in 14.04 and running simple snaps such as pwgen-
  tyhicks and hello-world, as well as a much more complex snap such as
  lxd.

  The following regression tests from lp:qa-regression-testing (these
  packages ship an AppArmor profile) can be used to verify that their
  respective packages do not regress:

   test-apache2-mpm-event.py
   test-apache2-mpm-itk.py
   test-apache2-mpm-perchild.py
   test-apache2-mpm-prefork.py
   test-apache2-mpm-worker.py
   test-bind9.py
   test-clamav.py
   test-cups.py
   test-dhcp.py
   test-mysql.py
   test-ntp.py
   test-openldap.py
   test-rsyslog.py
   test-squid.py
   test-strongswan.py
   test-tcpdump.py

  I have pushed changes to lp:qa-regression-testing which pulls in the
  parser and regression tests from the apparmor 2.8.95~2430-0ubuntu5.3
  package currently shipping in Trusty, in addition to the tests in the
  2.10.95 based package.

  Additionally, manually testing evince, which is confined by an
  AppArmor profile, should be done. The manual test should check basic
  functionality as well as for proper confinement (`ps auxZ` output).

  Finally, we need to test that 12.04 -> 14.04 upgrades continue to
  work. Specifically, the apparmor packages in trusty-proposed and the
  12.04 kernel need to be tested together.

  [Regression Potential]
  High. We must be extremely careful to not regress existing, confined 
applications in Ubuntu 14.04. We are lucky that the upstream AppArmor project 
has extensive regression tests and that the Ubuntu Security team adds even more 
testing via the AppArmor Test Plan.

  Care was taken to minimally change how the AppArmor policies are
  loaded during the boot process. I also verified that the abstractions
  shipped in apparmor and the profiles shipped in apparmor-profiles are
  the same across this SRU update.

  = dbus SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper D-Bus mediation 
for snaps when running under the 16.04 hardware enablement kernel. The dbus 
package in 14.04 is missing support for blocking unrequested reply messages. 
This functionality was added to the D-Bus AppArmor mediation patches after 
14.04 was released but before the patches were merged upstream in dbus. The 
idea is to prevent a malicious snap from attacking another snap, over D-Bus, 
with unrequested reply messages and also to prevent two connections from 
subverting the snap confinement by communicating via unrequested reply messages.

  [Test Case]

  The upstream AppArmor userspace project has thorough tests 

[Touch-packages] [Bug 1628295] Re: Change in kernel stacking behavior causes regression tests to fail

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5~14.04.1

---
apparmor (2.10.95-0ubuntu2.5~14.04.1) trusty; urgency=medium

  * Bring apparmor 2.10.95-0ubuntu2.5, from Ubuntu 16.04, to Ubuntu 14.04.
- This allows for proper snap confinement on Ubuntu 14.04 when using the
  hardware enablement kernel (LP: #1641243)
  * Changes made on top of 2.10.95-0ubuntu2.5:
- debian/apparmor.upstart: Remove the upstart job and continue using the
  init script in 14.04
- debian/apparmor.postinst, debian/apparmor-profiles.postinst,
  debian/apparmor-profiles.postrm, debian/rules: Revert to using
  invoke-rc.d to load the profiles, rather than reloading them directly,
  since 14.04 will continue using the init script rather than the upstart
  job.
- debian/apparmor.init, debian/lib/apparmor/functions,
  debian/apparmor.postinst, debian/apparmor.postrm: Remove functionality
  dealing with AppArmor policy in system image based environments since
  this 14.04 package will not need to handle such environments. This
  removes the handle_system_policy_package_updates(),
  compare_previous_version(), compare_and_save_debsums() functions and
  their callers.
- debian/apparmor.init: Continue using running-in-container since
  systemd-detect-virt doesn't exist on 14.04
- debian/lib/apparmor/functions, debian/apparmor.init: Remove the
  is_container_with_internal_policy() function and adjust its call sites
  in apparmor.init so that AppArmor policy is not loaded inside of 14.04
  LXD containers (avoids bug #1641236)
- debian/lib/apparmor/profile-load, debian/apparmor.install: Remove
  profile-load as upstart's apparmor-profile-load is used in 14.04
- debian/patches/libapparmor-mention-dbus-method-in-getcon-man.patch:
  Continue applying this patch since the dbus version in 14.04 isn't new
  enough to support fetching the AppArmor context from
  org.freedesktop.DBus.GetConnectionCredentials().
- debian/patches/libapparmor-force-libtoolize-replacement.patch: Force
  libtoolize to replace existing files to fix a libapparmor FTBFS issue on
  14.04.
- debian/control: Retain the original 14.04 Breaks and ignore the new
  Breaks from 2.10.95-0ubuntu2.5 since they were put in place as part of
  the enablement of UNIX domain socket mediation. They're not needed in
  this upload since UNIX domain socket mediation is disabled by default so
  updates to the profiles included in those packages are not needed.
- Preserve the profiles and abstractions from 14.04's
  2.8.95~2430-0ubuntu5.3 apparmor package by recreating them in the
  top-level profiles-14.04/ directory of the source. They'll be installed
  to debian/tmp/etc/apparmor.d/ during the build process and then to
  /etc/apparmor.d/ on package install so that there are no changes to the
  shipped profiles or abstractions. The abstractions from
  2.10.95-0ubuntu2.5 will be installed into
  debian/tmp/snap/etc/apparmor.d/ during the build process and then into
  /etc/apparmor.d/snap/abstractions/ on package install for use with snap
  confinement. Snap confinement profiles, which includes AppArmor profiles
  loaded by snapd and profiles loaded by snaps that are allowed to manage
  AppArmor policy, will use the snap abstractions. All other AppArmor
  profiles will continue to use the 14.04 abstractions.
  - debian/rules: Adjust for new profiles-14.04/ directory
  - debian/apparmor-profiles.install: Adjust to install the profiles that
were installed in the 2.8.95~2430-0ubuntu5.3 package
  - debian/apparmor.install: Install the abstractions from the
2.10.95-0ubuntu2.5 package into /etc/apparmor.d/snap/abstractions/
  - debian/patches/14.04-profiles.patch: Preserve the 14.04 profiles and
abstractions from the 2.8.95~2430-0ubuntu5.3 apparmor package.
  - debian/patches/conditionalize-post-release-features.patch: Disable new
mediation features, implemented after the Ubuntu 14.04 release, unless
the profile is for snap confinement. If the profile is for snap
confinement, the abstractions from /etc/apparmor.d/snap/abstractions
will be used and all of the mediation features will be enabled.
- 14.04-add-chromium-browser.patch,
  14.04-add-debian-integration-to-lighttpd.patch,
  14.04-etc-writable.patch,
  14.04-update-base-abstraction-for-signals-and-ptrace.patch,
  14.04-dnsmasq-libvirtd-signal-ptrace.patch,
  14.04-update-chromium-browser.patch,
  14.04-php5-Zend_semaphore-lp1401084.patch,
  14.04-dnsmasq-lxc_networking-lp1403468.patch,
  14.04-profiles-texlive_font_generation-lp1010909.patch,
  14.04-profiles-dovecot-updates-lp1296667.patch,
  14.04-profiles-adjust_X_for_lightdm-lp1339727.patch: Import all of the
  patches, from 14.04's 2.8.95~2430-0ubuntu5.3 

[Touch-packages] [Bug 1628285] Re: apparmor should be allowed to start in containers

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5~14.04.1

---
apparmor (2.10.95-0ubuntu2.5~14.04.1) trusty; urgency=medium

  * Bring apparmor 2.10.95-0ubuntu2.5, from Ubuntu 16.04, to Ubuntu 14.04.
- This allows for proper snap confinement on Ubuntu 14.04 when using the
  hardware enablement kernel (LP: #1641243)
  * Changes made on top of 2.10.95-0ubuntu2.5:
- debian/apparmor.upstart: Remove the upstart job and continue using the
  init script in 14.04
- debian/apparmor.postinst, debian/apparmor-profiles.postinst,
  debian/apparmor-profiles.postrm, debian/rules: Revert to using
  invoke-rc.d to load the profiles, rather than reloading them directly,
  since 14.04 will continue using the init script rather than the upstart
  job.
- debian/apparmor.init, debian/lib/apparmor/functions,
  debian/apparmor.postinst, debian/apparmor.postrm: Remove functionality
  dealing with AppArmor policy in system image based environments since
  this 14.04 package will not need to handle such environments. This
  removes the handle_system_policy_package_updates(),
  compare_previous_version(), compare_and_save_debsums() functions and
  their callers.
- debian/apparmor.init: Continue using running-in-container since
  systemd-detect-virt doesn't exist on 14.04
- debian/lib/apparmor/functions, debian/apparmor.init: Remove the
  is_container_with_internal_policy() function and adjust its call sites
  in apparmor.init so that AppArmor policy is not loaded inside of 14.04
  LXD containers (avoids bug #1641236)
- debian/lib/apparmor/profile-load, debian/apparmor.install: Remove
  profile-load as upstart's apparmor-profile-load is used in 14.04
- debian/patches/libapparmor-mention-dbus-method-in-getcon-man.patch:
  Continue applying this patch since the dbus version in 14.04 isn't new
  enough to support fetching the AppArmor context from
  org.freedesktop.DBus.GetConnectionCredentials().
- debian/patches/libapparmor-force-libtoolize-replacement.patch: Force
  libtoolize to replace existing files to fix a libapparmor FTBFS issue on
  14.04.
- debian/control: Retain the original 14.04 Breaks and ignore the new
  Breaks from 2.10.95-0ubuntu2.5 since they were put in place as part of
  the enablement of UNIX domain socket mediation. They're not needed in
  this upload since UNIX domain socket mediation is disabled by default so
  updates to the profiles included in those packages are not needed.
- Preserve the profiles and abstractions from 14.04's
  2.8.95~2430-0ubuntu5.3 apparmor package by recreating them in the
  top-level profiles-14.04/ directory of the source. They'll be installed
  to debian/tmp/etc/apparmor.d/ during the build process and then to
  /etc/apparmor.d/ on package install so that there are no changes to the
  shipped profiles or abstractions. The abstractions from
  2.10.95-0ubuntu2.5 will be installed into
  debian/tmp/snap/etc/apparmor.d/ during the build process and then into
  /etc/apparmor.d/snap/abstractions/ on package install for use with snap
  confinement. Snap confinement profiles, which includes AppArmor profiles
  loaded by snapd and profiles loaded by snaps that are allowed to manage
  AppArmor policy, will use the snap abstractions. All other AppArmor
  profiles will continue to use the 14.04 abstractions.
  - debian/rules: Adjust for new profiles-14.04/ directory
  - debian/apparmor-profiles.install: Adjust to install the profiles that
were installed in the 2.8.95~2430-0ubuntu5.3 package
  - debian/apparmor.install: Install the abstractions from the
2.10.95-0ubuntu2.5 package into /etc/apparmor.d/snap/abstractions/
  - debian/patches/14.04-profiles.patch: Preserve the 14.04 profiles and
abstractions from the 2.8.95~2430-0ubuntu5.3 apparmor package.
  - debian/patches/conditionalize-post-release-features.patch: Disable new
mediation features, implemented after the Ubuntu 14.04 release, unless
the profile is for snap confinement. If the profile is for snap
confinement, the abstractions from /etc/apparmor.d/snap/abstractions
will be used and all of the mediation features will be enabled.
- 14.04-add-chromium-browser.patch,
  14.04-add-debian-integration-to-lighttpd.patch,
  14.04-etc-writable.patch,
  14.04-update-base-abstraction-for-signals-and-ptrace.patch,
  14.04-dnsmasq-libvirtd-signal-ptrace.patch,
  14.04-update-chromium-browser.patch,
  14.04-php5-Zend_semaphore-lp1401084.patch,
  14.04-dnsmasq-lxc_networking-lp1403468.patch,
  14.04-profiles-texlive_font_generation-lp1010909.patch,
  14.04-profiles-dovecot-updates-lp1296667.patch,
  14.04-profiles-adjust_X_for_lightdm-lp1339727.patch: Import all of the
  patches, from 14.04's 2.8.95~2430-0ubuntu5.3 

[Touch-packages] [Bug 1653487] Re: seccomp argument filtering not working on trusty amd64

[Launchpad Bug Tracker]

This bug was fixed in the package libseccomp - 2.1.1-1ubuntu1~trusty3

---
libseccomp (2.1.1-1ubuntu1~trusty3) trusty-proposed; urgency=medium

  * Cherrypick various bpf fixes to support argument filtering on 64-bit
(LP: #1653487)
- debian/patches/bpf-use-state-arch.patch: use state->arch instead of
  db->arch in _gen_bpf_arch()
- debian/patches/db-require-filters-to-share-endianess.patch: require all
  filters in a collection to share the same endianess
- debian/patches/resolve-issues-caused-by-be.patch: resolve issues caused
  by big endian systems
- debian/patches/bpf-accumulator-check.patch: test the bpf accumulator
  checking logic
- debian/patches/bpf-track-accumulator-state.patch: track accumulator
  state and reload it when necessary. This is the fix for LP: #1653487. The
  previous patches are required by this patch.
- debian/patches/ensure-simulator-has-valid-arch.patch: ensure the
  simulator always has a valid architecture value. This fixes a regression
  in the testsuite introduced by resolve-issues-caused-by-be.patch
- debian/patches/bpf-accumulator-check-indep.patch: fix a regression in the
  testsuite introduced by bpf-accumulator-check.patch
- debian/patches/fix-audit-arch-i386.patch: fix arch token for 32-bit x86
  not being defined correctly for the tools

libseccomp (2.1.1-1ubuntu1~trusty1) trusty-proposed; urgency=medium

  * Bring libseccomp 2.1.1-1ubuntu1~vivid2, from Ubuntu 14.10, to Ubuntu
14.04 and add a couple patches to account for new syscalls found in the
4.4 based hardware enablement kernel. This allows for proper snap seccomp
confinement on Ubuntu 14.04 when using the hardware enablement kernel
(LP: #1450642)
- debian/patches/add-membarrier-and-userfaultfd.patch: Add membarrier and
  userfaultfd syscalls
- debian/patches/add-mlock2.patch: Add mlock2 syscall
- debian/tests/data/all-except-s390-4.4.filter: Add autopkgtest that
  verifies all syscalls found in the 4.4 kernel, except for the s390
  specific syscalls, are supported by libseccomp. The s390 specific
  syscalls are not needed since this version of libseccomp does not
  support the s390 architecture.
- debian/tests/test-filter: Skip the getrandom filter tests since
  SYS_getrandom is not defined in 14.04 environment and the getrandom(2)
  syscall is not even available in the 14.04 release kernel.

libseccomp (2.1.1-1ubuntu1~vivid2) vivid-proposed; urgency=medium

  * add-finit-module.patch: add finit_module syscalls to x86 and x86-64
syscall tables
  * update syscalls for modern kernels (skipping MIPS)
- update syscalls for 3.16:
  + update-x86-syscall-table.patch
  + update-x86_64-syscall-table.patch
  + update-arm-syscall-table.patch
  + update-x32-syscall-table.patch
  + sync-syscall-table-entries.patch
  + sync-syscall-table-entries-fixtypo.patch
- update syscalls for 3.17:
  + sync-syscall-table-entries-3.17.patch
- update syscalls for 3.19:
  + sync-syscall-table-entries-3.19.patch
- LP: #1450642
  * fix-segfault-with-unknown.patch: fix segfault when find unknown syscall
  * debian/patches/add-missing-arm-private-syscalls.path: add missing private
ARM syscalls
  * add autopkgtests for scmp_sys_resolver and filter testing and
SYS_getrandom() testing

libseccomp (2.1.1-1) unstable; urgency=low

  * New upstream release (Closes: 733293).
  * copyright: add a few missed people.
  * rules: adjusted for new test target.
  * libseccomp2.symbols: drop accidentally exported functions.
  * control:
- bump standards, no changes needed.
- add armel target

 -- Jamie Strandboge   Wed, 04 Jan 2017 21:11:30 +

** Changed in: libseccomp (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  seccomp argument filtering not working on trusty amd64

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was 
exposed in the snapd build testsuite when run on amd64. It has to do with 
libseccomp's state machine not always working correctly when using argument 
filtering and there were no tests for this particular failure in 2.1. Once 
19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is 
applied to 2.1, you see the failures. Simple seccomp filters that just use the 
syscall name are not affected by the bug and we (currently) only use seccomp 
arg filtering in one interface which is why Tyler's testing of 
2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do 
exercise it, but seccomp argument filtering wasn't added 

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Pat McGowan]

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

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

Title:
  webbrowser only partially loads some https sites

Status in Canonical System Image:
  In Progress
Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

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

[Ketil]

@Arul, I found something similar in my comment above, at
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1173915/comments/5.

But it's been almost 4 years since this issue was reported, and over 2
years since I added my comment, and it's clearly not fixed yet, or even
prioritised.

In fact, my general experience reporting Ubuntu issues here on launchpad
is that this is a black hole, issues are left hanging until they are
closed as irrelevant several years later. Critical issues undoubtedly
get more attention, but issues such as this are still a problem.
Annoying, so I don't really see the point in reporting issues here any
more.

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

Title:
  initctl continuously takes 100% of CPU

Status in upstart :
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

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

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

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

  Regards

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

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

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

[Touch-packages] [Bug 1657437] Re: Unprivileged containers run by non-root fail to start if trying to bind-mount a directory that contains a mounted ecryptfs

[Stéphane Graber]

Unfortunately the kernel overmounting security check won't let you do
so.

This security check is there in the event that /home/blah contains some
files which the /home/blah mount hides. Now allowing an unprivileged
user to bind-mount /home without /home/blah on top of it would un-hide
those files, causing a potential security issue.

The only workaround is to have a /home bind-mount setup by root at say
/mnt/home and then use /mnt/home as the source of the bind-mount for
your container.

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

Title:
  Unprivileged containers run by non-root fail to start if trying to
  bind-mount a directory that contains a mounted ecryptfs

Status in lxc package in Ubuntu:
  New

Bug description:
  Not sure if this is an lxc bug or an ecryptfs bug. Please reassign if
  necessary.

  I have an unprivileged container that is defined in the default
  location, ~/.share/local/lxc. It bind-mounts the host's /home
  directory to /home inside the container, like so:

  lxc.mount.entry = /home home none bind 0 0

  My /home directory contains an ecryptfs at ~/.Private, which is
  mounted to ~/Private with default options, at login, via pam_ecryptfs.

  lxc-start then results in the following error showing up in the log
  file:

lxc-start 20170118124950.117 ERRORlxc_utils - 
utils.c:safe_mount:1746 - Invalid argument - Failed to mount /home onto 
/usr/lib/x86_64-linux-gnu/lxc/home
lxc-start 20170118124950.117 ERRORlxc_conf - 
conf.c:mount_entry:1650 - Invalid argument - failed to mount '/home' on 
'/usr/lib/x86_64-linux-gnu/lxc/home'
lxc-start 20170118124950.117 ERRORlxc_conf - conf.c:lxc_setup:3790 
- failed to setup the mount entries for 'trusty-edx-devstack'
lxc-start 20170118124950.117 ERRORlxc_start - start.c:do_start:826 
- Failed to setup container "trusty-edx-devstack".
lxc-start 20170118124950.117 ERRORlxc_sync - sync.c:__sync_wait:57 
- An error occurred in another process (expected sequence number 3)
lxc-start 20170118124950.118 ERRORlxc_start - 
start.c:__lxc_start:1338 - Failed to spawn container "trusty-edx-devstack".
lxc-start 20170118124955.668 ERRORlxc_start_ui - 
tools/lxc_start.c:main:360 - The container failed to start.

  Unmounting the ecryptfs allows the container to start normally. After
  the container has been started, the ecryptfs can be remounted with
  ecryptfs-mount-private, which appears to have no ill effect on the
  container.

  I don't quite see why the mounted ecryptfs would prevent /home from
  being bind-mounted into the container. After all, bind-mounting /home
  to some other mount point in the host works just fine — with the
  Private directory simply being empty, save for the Access-Your-
  Private-Data.desktop and README.txt symlinks, in the bind mount
  location. This is also what happens in privileged containers whose
  configuration has the same lxc.mount.entry.

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

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

[Pat McGowan]

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

** Changed in: canonical-devices-system-image
Milestone: None => 15

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

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

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

[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

[Ken VanDine]

@mpt from my understanding of the original designs, content picking was
one of the use cases.  There was a desire to open the source app in a
trust prompt for the duration of the content picking operation.  Keeping
the users work flow from switching focus to another app, we are
embedding the source app in the app requesting the content.

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

Title:
  We need a "close" action for killing an app in a trust prompt

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

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 15

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => David Barth (dbarth)

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

Title:
  webbrowser only partially loads some https sites

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

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Julian Andres Klode]

Could you provide logs with -o debug::acquire::https=1 and
debug::acquire::http=1

Maybe thw redirect changed and the test case this started working again?
I'll check soon.

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space. This breaks packages 
like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Check that 

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649960] Re: Apport fails to upload some crash reports

[Brian Murray]

For which .crash files do you notice this happening with?  Its likely
the package has an apport package hook which is trying to use a UI to
ask you questions.

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

Title:
  Apport fails to upload some crash reports

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  For some reason I often find that if I try to report a .crash (which
  the GUI for some reason didn't alert me about) file this will happen
  (this happens with all the Apport tools to report a crash, this just
  so happens to be the apport-cli example):

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (6.7 MB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): S

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  
..

[Touch-packages] [Bug 1657516] [NEW] Cannot record videos

[Victor gonzalez]

Public bug reported:

Environment:

current build number: 124
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2017-01-18 08:13:48

Steps to reproduce:

1º Open camera app
2º Change to video mode and press record button

Current result: screen freezes, then after a while it starts to
record(the counter starts). When stop button is pressed a dialog window
says:"Capture failed: restarting your device might fix the problem".
Video is not saved and app freezes, you can close it though.

Expected result: Camera app should record a video 
Reproducibility 100%

Add info:

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

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

Title:
  Cannot record videos

Status in camera-app package in Ubuntu:
  New

Bug description:
  Environment:

  current build number: 124
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-18 08:13:48

  Steps to reproduce:

  1º Open camera app
  2º Change to video mode and press record button

  Current result: screen freezes, then after a while it starts to
  record(the counter starts). When stop button is pressed a dialog
  window says:"Capture failed: restarting your device might fix the
  problem". Video is not saved and app freezes, you can close it though.

  Expected result: Camera app should record a video 
  Reproducibility 100%

  Add info:

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

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

[Touch-packages] [Bug 1657509] [NEW] no recognized printer

[Bidault]

Public bug reported:

no recognized printer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jan 18 17:03:50 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family Integrated Graphics Controller [1462:7680]
InstallationDate: Installed on 2016-11-09 (70 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: MSI MS-7680
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f09943c1-4f0d-429f-9923-b783f37f4de4 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V12.0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-E23(G3)(MS-7680)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV12.0:bd03/21/2012:svnMSI:pnMS-7680:pvr2.0:rvnMSI:rnH61M-E23(G3)(MS-7680):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7680
dmi.product.version: 2.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jan 18 16:41:12 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputLogitech M345MOUSE, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

Title:
  no recognized printer

Status in xorg package in Ubuntu:
  New

Bug description:
  no recognized printer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jan 18 17:03:50 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family Integrated Graphics Controller [1462:7680]
  InstallationDate: Installed on 2016-11-09 (70 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: MSI MS-7680
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f09943c1-4f0d-429f-9923-b783f37f4de4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V12.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi

[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

[Brian Murray]

While the new version of the package worked for me, so did apt version
1.2.18 - shouldn't it have failed?


bdmurray@clean-xenial-amd64:~$ apt-cache policy apt
apt:
  Installed: 1.2.18
  Candidate: 1.2.18
  Version table:
 *** 1.2.18 500
500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1.2.15ubuntu0.2 500
500 http://192.168.10.7/ubuntu xenial-security/main amd64 Packages
 1.2.10ubuntu1 500
500 http://192.168.10.7/ubuntu xenial/main amd64 Packages
bdmurray@clean-xenial-amd64:~$ /usr/lib/apt/apt-helper download-file 
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb 
test.deb
Get:1 
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb 
[60.2 MB]
Fetched 60.2 MB in 10s (5,701 kB/s)

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

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space. This breaks packages 
like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Check that 

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1640849] Re: Enhanced coloring of differences

[Sworddragon]

** Description changed:

  I'm using Ubuntu 17.04 dev with diffutils 1:3.5-1 and currently only the
  lines are colored for added/removed ones. Maybe the differences in the
  lines which characters are added/removed can be colored too (for example
- with a higher opacity) to make them easier to see.
+ with a higher background or foreground opacity) to make them easier to
+ see.

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

Title:
  Enhanced coloring of differences

Status in diffutils package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 17.04 dev with diffutils 1:3.5-1 and currently only
  the lines are colored for added/removed ones. Maybe the differences in
  the lines which characters are added/removed can be colored too (for
  example with a higher background or foreground opacity) to make them
  easier to see.

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

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

[Touch-packages] [Bug 1657045] Re: Launcher hides pressing a bit the left edge

[Launchpad Bug Tracker]

** Branch linked: lp:~mzanetti/unity8/launcher-hiding-fix

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

Title:
  Launcher hides pressing a bit the left edge

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

Bug description:
  Video with steps to reproduce at https://www.youtube.com/watch?v=vs_o-
  K9Z-4I

  I think it may have something to do with having shown the appdrawer
  somewhat recently, but may be a false clue.

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

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

[Touch-packages] [Bug 1657045] Re: Launcher hides pressing a bit the left edge

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

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

Title:
  Launcher hides pressing a bit the left edge

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

Bug description:
  Video with steps to reproduce at https://www.youtube.com/watch?v=vs_o-
  K9Z-4I

  I think it may have something to do with having shown the appdrawer
  somewhat recently, but may be a false clue.

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

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

[Touch-packages] [Bug 1613789] Re: indicator-network broken on laptop unity8 session

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  indicator-network broken on laptop unity8 session

Status in indicator-network package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Enviroment:

  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Steps to reproduce:

  1º Open unity8 session
  2º Check the indicator-network status

  Current result: indicator-network does not respond and it does not
  load the proper logo

  Expected result: indicator-network should link to System settings/Wi-
  Fi || mobile data(dongle 3G/4G)

  Add info: picture attached

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

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

[Touch-packages] [Bug 1616475] Re: Enable tests on arm64

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: New => Fix Released

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

Title:
  Enable tests on arm64

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  From MIR bug 1612619, vivid/arm64 tests are broken, but xenial &
  yakkety are fine.  Right now we disable tests on arm64 for all
  distros, but we should be more nuanced and only disable them if the
  distro is vivid.

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

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