[Touch-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

[Warren Andrews]

EDIT: THIS IS THE WORKAROUND:
bind 'set enable-bracketed-paste off'

The proposed work around does NOT work for me. It could be due to the fact that 
it is over ssh?
I am sshing from 18.04 into 22.04.
Bash version on former is 4.4.20(1)-release
Bash version on latter is 5.1.16(1)-release

I CANNOT work with this 'feature' enabled. Please help. Thanks. (And
this security argument makes no sense to me... why would I paste text
into a terminal which I didn't select?)

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

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Invalid
Status in readline package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  [[Workaround]]

  * On 22.04, add 'set enable-bracketed-paste off' to /etc/inputrc
  * Starting 22.10, add 'set enable-active-region off' to /etc/inputrc

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Philippe Warren]

Here is another example of a tool that fails to work as expected because
it expects strict compliance to PEP 440: https://github.com/tox-
dev/pipdeptree/issues/235 .

This affects older Ubuntu releases like Bionic and Focal too.
I hope adding another example like this helps to justify fixing this on older 
versions of Ubuntu as well, even if setuptools is not affected there. 

** Bug watch added: github.com/tox-dev/pipdeptree/issues #235
   https://github.com/tox-dev/pipdeptree/issues/235

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package ver

[Touch-packages] [Bug 1894627] Re: Screen Distorted After Hibernation/Power Save when idle

[Kashad J Turner-Warren]

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

The fix is changing my background offten?

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

Title:
  Screen Distorted After Hibernation/Power Save when idle

Status in xorg package in Ubuntu:
  New

Bug description:
  my laptop goes to hibernation/power saver mode when my computer is idle. 
  every time I bring my computer back up, the screen distorted. I have to close 
all my browsers. Sometimes, shut down the computer.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 03:33:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-42-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8466]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] 
[103c:8466]
  InstallationDate: Installed on 2020-06-23 (75 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8466
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd04/24/2019:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 4CC49UA#ABA
  dmi.sys.vendor: HP
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1883054] Re: Built-in audio device not available until alsa is reloaded

[Stephen Warren]

For me, this issue has now been resolved; I assume due to the pulseaudio
package updates that I installed yesterday, but it might have been fixed
for a few days longer.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Fix Released

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

Title:
  Built-in audio device not available until alsa is reloaded

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and
  audio worked fine, using either the built-in speakers/mic on the
  laptop or via a USB headset when that was plugged in.

  However, after upgrading to 20.04, the built-in audio device is no
  longer available until I run "sudo alsa force-reload". Wthhout that
  WAR, all I see is a dummy audio device. Luckily the USB headset works
  fine, if plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  swarren7664 F pulseaudio
   /dev/snd/controlC0:  swarren7664 F pulseaudio
   /dev/snd/pcmC0D0c:   swarren7664 F...m pulseaudio
   /dev/snd/pcmC0D0p:   swarren7664 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jun 10 23:57:08 2020
  InstallationDate: Installed on 2016-03-03 (1561 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1DETA6W (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ERCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P70
  dmi.product.name: 20ERCTO1WW
  dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70
  dmi.product.version: ThinkPad P70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

[Stephen Warren]

Sorry, please ignore my previous comment (comment 6); I'd copied the
netplan config from another machine and adjusted all the IPs, but forgot
to change the interface name, so the entries were ignored.

Basic IP connectivity was working since I have an encrypted volume
that's unlocked via the initrd, so the initrd sets up the
IP/netmask/gateway, and these simply carried over once the rootfs was
mounted; netplan/... didn't clear them out luckily.

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have a server that uses /etc/network/interfaces to configure static
  IP info, including DNS, via /etc/network/interfaces. This worked fine
  in 16.04 and 18.04. However, when I updated to 20.04 this no longer
  works; I have to run "systemd-resolve --set-dns=192.168.63.1
  --interface=enp3s0" to fix it after every boot.

  My /etc/network/interfaces is:

  
  # Loopback
  auto lo
  iface lo inet loopback

  # enp3s0: LAN (Motherboard)
  auto enp3s0
  iface enp3s0 inet static
  address 192.168.63.2
  netmask 255.255.255.0
  network 192.168.63.0
  broadcast 192.168.63.255
  gateway 192.168.63.1
  dns-nameservers 192.168.63.1

  iface enp3s0 inet6 static
  address 2001:470:bb52:63::2/64
  netmask 64

  # WiFi USB
  # FIXME: Probably will get renamed on boot
  #allow-hotplug ethFlashAirWifi
  #iface ethFlashAirWifi inet manual
  

  "systemd-resolve --status" outputs the following beforr I run the WAR
  command given above:

  
  Global
 LLMNR setting: no  
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
DNSSEC NTA: 10.in-addr.arpa 
16.172.in-addr.arpa 
168.192.in-addr.arpa
17.172.in-addr.arpa 
18.172.in-addr.arpa 
19.172.in-addr.arpa 
20.172.in-addr.arpa 
21.172.in-addr.arpa 
22.172.in-addr.arpa 
23.172.in-addr.arpa 
24.172.in-addr.arpa 
25.172.in-addr.arpa 
26.172.in-addr.arpa 
27.172.in-addr.arpa 
28.172.in-addr.arpa 
29.172.in-addr.arpa 
30.172.in-addr.arpa 
31.172.in-addr.arpa 
corp
d.f.ip6.arpa
home
internal
intranet
lan 
local   
private 
test

  Link 4 (tun0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 3 (lxcbr0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 2 (enp3s0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun 14 01:58:10 2020
  InstallationDate: Installed on 2016-04-12 (1524 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)
  dmi.bios.date: 06/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: 890GX Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: 

[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

[Stephen Warren]

Uggh. On a second system that I upgraded 16.04->18.04->20.04, I have
netplan installed and a configuration file in place. However, the DNS
entry in the netplan config is ignored, so even switching to netplan
doesn't fix this bug:-(

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have a server that uses /etc/network/interfaces to configure static
  IP info, including DNS, via /etc/network/interfaces. This worked fine
  in 16.04 and 18.04. However, when I updated to 20.04 this no longer
  works; I have to run "systemd-resolve --set-dns=192.168.63.1
  --interface=enp3s0" to fix it after every boot.

  My /etc/network/interfaces is:

  
  # Loopback
  auto lo
  iface lo inet loopback

  # enp3s0: LAN (Motherboard)
  auto enp3s0
  iface enp3s0 inet static
  address 192.168.63.2
  netmask 255.255.255.0
  network 192.168.63.0
  broadcast 192.168.63.255
  gateway 192.168.63.1
  dns-nameservers 192.168.63.1

  iface enp3s0 inet6 static
  address 2001:470:bb52:63::2/64
  netmask 64

  # WiFi USB
  # FIXME: Probably will get renamed on boot
  #allow-hotplug ethFlashAirWifi
  #iface ethFlashAirWifi inet manual
  

  "systemd-resolve --status" outputs the following beforr I run the WAR
  command given above:

  
  Global
 LLMNR setting: no  
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
DNSSEC NTA: 10.in-addr.arpa 
16.172.in-addr.arpa 
168.192.in-addr.arpa
17.172.in-addr.arpa 
18.172.in-addr.arpa 
19.172.in-addr.arpa 
20.172.in-addr.arpa 
21.172.in-addr.arpa 
22.172.in-addr.arpa 
23.172.in-addr.arpa 
24.172.in-addr.arpa 
25.172.in-addr.arpa 
26.172.in-addr.arpa 
27.172.in-addr.arpa 
28.172.in-addr.arpa 
29.172.in-addr.arpa 
30.172.in-addr.arpa 
31.172.in-addr.arpa 
corp
d.f.ip6.arpa
home
internal
intranet
lan 
local   
private 
test

  Link 4 (tun0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 3 (lxcbr0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 2 (enp3s0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun 14 01:58:10 2020
  InstallationDate: Installed on 2016-04-12 (1524 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)
  dmi.bios.date: 06/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: 890GX Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd06/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn89

[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

[Stephen Warren]

The system has resolvconf 1.82 installed. /etc/resolv.conf claims that
it's generated by resolvconf, at least after I switched the system to
netplan, and I'm pretty sure it did before to. I also have ifupdown
0.8.35ubuntu1 installed.

A thought on deprecation: A deprecated package is simply something that
isn't suitable for new use. If the package still exists, it must still
work correctly; known non-working software shouldn't be shipped. At the
point that's no longer possible, it can be removed (hopefully with an
automated transition plan in do-release-upgrade).

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have a server that uses /etc/network/interfaces to configure static
  IP info, including DNS, via /etc/network/interfaces. This worked fine
  in 16.04 and 18.04. However, when I updated to 20.04 this no longer
  works; I have to run "systemd-resolve --set-dns=192.168.63.1
  --interface=enp3s0" to fix it after every boot.

  My /etc/network/interfaces is:

  
  # Loopback
  auto lo
  iface lo inet loopback

  # enp3s0: LAN (Motherboard)
  auto enp3s0
  iface enp3s0 inet static
  address 192.168.63.2
  netmask 255.255.255.0
  network 192.168.63.0
  broadcast 192.168.63.255
  gateway 192.168.63.1
  dns-nameservers 192.168.63.1

  iface enp3s0 inet6 static
  address 2001:470:bb52:63::2/64
  netmask 64

  # WiFi USB
  # FIXME: Probably will get renamed on boot
  #allow-hotplug ethFlashAirWifi
  #iface ethFlashAirWifi inet manual
  

  "systemd-resolve --status" outputs the following beforr I run the WAR
  command given above:

  
  Global
 LLMNR setting: no  
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
DNSSEC NTA: 10.in-addr.arpa 
16.172.in-addr.arpa 
168.192.in-addr.arpa
17.172.in-addr.arpa 
18.172.in-addr.arpa 
19.172.in-addr.arpa 
20.172.in-addr.arpa 
21.172.in-addr.arpa 
22.172.in-addr.arpa 
23.172.in-addr.arpa 
24.172.in-addr.arpa 
25.172.in-addr.arpa 
26.172.in-addr.arpa 
27.172.in-addr.arpa 
28.172.in-addr.arpa 
29.172.in-addr.arpa 
30.172.in-addr.arpa 
31.172.in-addr.arpa 
corp
d.f.ip6.arpa
home
internal
intranet
lan 
local   
private 
test

  Link 4 (tun0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 3 (lxcbr0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 2 (enp3s0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun 14 01:58:10 2020
  InstallationDate: Installed on 2016-04-12 (1524 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)
  dmi.bios.date: 06/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: 890GX Extreme

[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

[Stephen Warren]

Switching to netplan does avoid this issue, but doesn't directly solve
it.

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  New

Bug description:
  I have a server that uses /etc/network/interfaces to configure static
  IP info, including DNS, via /etc/network/interfaces. This worked fine
  in 16.04 and 18.04. However, when I updated to 20.04 this no longer
  works; I have to run "systemd-resolve --set-dns=192.168.63.1
  --interface=enp3s0" to fix it after every boot.

  My /etc/network/interfaces is:

  
  # Loopback
  auto lo
  iface lo inet loopback

  # enp3s0: LAN (Motherboard)
  auto enp3s0
  iface enp3s0 inet static
  address 192.168.63.2
  netmask 255.255.255.0
  network 192.168.63.0
  broadcast 192.168.63.255
  gateway 192.168.63.1
  dns-nameservers 192.168.63.1

  iface enp3s0 inet6 static
  address 2001:470:bb52:63::2/64
  netmask 64

  # WiFi USB
  # FIXME: Probably will get renamed on boot
  #allow-hotplug ethFlashAirWifi
  #iface ethFlashAirWifi inet manual
  

  "systemd-resolve --status" outputs the following beforr I run the WAR
  command given above:

  
  Global
 LLMNR setting: no  
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
DNSSEC NTA: 10.in-addr.arpa 
16.172.in-addr.arpa 
168.192.in-addr.arpa
17.172.in-addr.arpa 
18.172.in-addr.arpa 
19.172.in-addr.arpa 
20.172.in-addr.arpa 
21.172.in-addr.arpa 
22.172.in-addr.arpa 
23.172.in-addr.arpa 
24.172.in-addr.arpa 
25.172.in-addr.arpa 
26.172.in-addr.arpa 
27.172.in-addr.arpa 
28.172.in-addr.arpa 
29.172.in-addr.arpa 
30.172.in-addr.arpa 
31.172.in-addr.arpa 
corp
d.f.ip6.arpa
home
internal
intranet
lan 
local   
private 
test

  Link 4 (tun0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 3 (lxcbr0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 2 (enp3s0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun 14 01:58:10 2020
  InstallationDate: Installed on 2016-04-12 (1524 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)
  dmi.bios.date: 06/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: 890GX Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd06/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn890GXExtreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.produ

[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

[Stephen Warren]

Oh, and /etc/resolv.conf contains:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  New

Bug description:
  I have a server that uses /etc/network/interfaces to configure static
  IP info, including DNS, via /etc/network/interfaces. This worked fine
  in 16.04 and 18.04. However, when I updated to 20.04 this no longer
  works; I have to run "systemd-resolve --set-dns=192.168.63.1
  --interface=enp3s0" to fix it after every boot.

  My /etc/network/interfaces is:

  
  # Loopback
  auto lo
  iface lo inet loopback

  # enp3s0: LAN (Motherboard)
  auto enp3s0
  iface enp3s0 inet static
  address 192.168.63.2
  netmask 255.255.255.0
  network 192.168.63.0
  broadcast 192.168.63.255
  gateway 192.168.63.1
  dns-nameservers 192.168.63.1

  iface enp3s0 inet6 static
  address 2001:470:bb52:63::2/64
  netmask 64

  # WiFi USB
  # FIXME: Probably will get renamed on boot
  #allow-hotplug ethFlashAirWifi
  #iface ethFlashAirWifi inet manual
  

  "systemd-resolve --status" outputs the following beforr I run the WAR
  command given above:

  
  Global
 LLMNR setting: no  
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
DNSSEC NTA: 10.in-addr.arpa 
16.172.in-addr.arpa 
168.192.in-addr.arpa
17.172.in-addr.arpa 
18.172.in-addr.arpa 
19.172.in-addr.arpa 
20.172.in-addr.arpa 
21.172.in-addr.arpa 
22.172.in-addr.arpa 
23.172.in-addr.arpa 
24.172.in-addr.arpa 
25.172.in-addr.arpa 
26.172.in-addr.arpa 
27.172.in-addr.arpa 
28.172.in-addr.arpa 
29.172.in-addr.arpa 
30.172.in-addr.arpa 
31.172.in-addr.arpa 
corp
d.f.ip6.arpa
home
internal
intranet
lan 
local   
private 
test

  Link 4 (tun0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 3 (lxcbr0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 2 (enp3s0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun 14 01:58:10 2020
  InstallationDate: Installed on 2016-04-12 (1524 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)
  dmi.bios.date: 06/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: 890GX Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:

[Touch-packages] [Bug 1883412] [NEW] 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve

[Stephen Warren]

Public bug reported:

I have a server that uses /etc/network/interfaces to configure static IP
info, including DNS, via /etc/network/interfaces. This worked fine in
16.04 and 18.04. However, when I updated to 20.04 this no longer works;
I have to run "systemd-resolve --set-dns=192.168.63.1
--interface=enp3s0" to fix it after every boot.

My /etc/network/interfaces is:


# Loopback
auto lo
iface lo inet loopback

# enp3s0: LAN (Motherboard)
auto enp3s0
iface enp3s0 inet static
address 192.168.63.2
netmask 255.255.255.0
network 192.168.63.0
broadcast 192.168.63.255
gateway 192.168.63.1
dns-nameservers 192.168.63.1

iface enp3s0 inet6 static
address 2001:470:bb52:63::2/64
netmask 64

# WiFi USB
# FIXME: Probably will get renamed on boot
#allow-hotplug ethFlashAirWifi
#iface ethFlashAirWifi inet manual


"systemd-resolve --status" outputs the following beforr I run the WAR
command given above:


Global
   LLMNR setting: no  
MulticastDNS setting: no  
  DNSOverTLS setting: no  
  DNSSEC setting: no  
DNSSEC supported: no  
  DNSSEC NTA: 10.in-addr.arpa 
  16.172.in-addr.arpa 
  168.192.in-addr.arpa
  17.172.in-addr.arpa 
  18.172.in-addr.arpa 
  19.172.in-addr.arpa 
  20.172.in-addr.arpa 
  21.172.in-addr.arpa 
  22.172.in-addr.arpa 
  23.172.in-addr.arpa 
  24.172.in-addr.arpa 
  25.172.in-addr.arpa 
  26.172.in-addr.arpa 
  27.172.in-addr.arpa 
  28.172.in-addr.arpa 
  29.172.in-addr.arpa 
  30.172.in-addr.arpa 
  31.172.in-addr.arpa 
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan 
  local   
  private 
  test

Link 4 (tun0)
  Current Scopes: none
DefaultRoute setting: no  
   LLMNR setting: yes 
MulticastDNS setting: no  
  DNSOverTLS setting: no  
  DNSSEC setting: no  
DNSSEC supported: no  

Link 3 (lxcbr0)
  Current Scopes: none
DefaultRoute setting: no  
   LLMNR setting: yes 
MulticastDNS setting: no  
  DNSOverTLS setting: no  
  DNSSEC setting: no  
DNSSEC supported: no  

Link 2 (enp3s0)
  Current Scopes: none
DefaultRoute setting: no  
   LLMNR setting: yes 
MulticastDNS setting: no  
  DNSOverTLS setting: no  
  DNSSEC setting: no  
DNSSEC supported: no  


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Jun 14 01:58:10 2020
InstallationDate: Installed on 2016-04-12 (1524 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/severn_vg2016-lv_root ro
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago)
dmi.bios.date: 06/18/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.40
dmi.board.name: 890GX Extreme3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd06/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn890GXExtreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: 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.

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


** Tags: amd64 apport-bug focal

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

Title:
  20.04: DNS servers from /etc/network/interfaces not honored by
  systemd-resolve

Status in systemd package in Ubuntu:
  New

Bug description:
  I have a server that uses /etc/network/interfaces to configure static

[Touch-packages] [Bug 1883054] Re: Built-in audio device not available until alsa is reloaded

[Stephen Warren]

My headset (which works fine) is USB.

Which bug do you believe this is a duplicate of? I did find something
similar, but it was on 16.04, and my issue is definitely a regression
between 18.04 and 20.04.

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

Title:
  Built-in audio device not available until alsa is reloaded

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and
  audio worked fine, using either the built-in speakers/mic on the
  laptop or via a USB headset when that was plugged in.

  However, after upgrading to 20.04, the built-in audio device is no
  longer available until I run "sudo alsa force-reload". Wthhout that
  WAR, all I see is a dummy audio device. Luckily the USB headset works
  fine, if plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  swarren7664 F pulseaudio
   /dev/snd/controlC0:  swarren7664 F pulseaudio
   /dev/snd/pcmC0D0c:   swarren7664 F...m pulseaudio
   /dev/snd/pcmC0D0p:   swarren7664 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jun 10 23:57:08 2020
  InstallationDate: Installed on 2016-03-03 (1561 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1DETA6W (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ERCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P70
  dmi.product.name: 20ERCTO1WW
  dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70
  dmi.product.version: ThinkPad P70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1883054] Re: Built-in audio device not available until alsa is reloaded

[Stephen Warren]

I ran alsa-info before/after running "sudo alsa force-reload" to see if
there were any obvious differences in the output. While there are a few
differences, nothing really stands out as causing this issue.

** Attachment added: "diff for alsa-info output before/after reloading alsa"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+attachment/5382790/+files/alsa-info-diff.txt

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

Title:
  Built-in audio device not available until alsa is reloaded

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and
  audio worked fine, using either the built-in speakers/mic on the
  laptop or via a USB headset when that was plugged in.

  However, after upgrading to 20.04, the built-in audio device is no
  longer available until I run "sudo alsa force-reload". Wthhout that
  WAR, all I see is a dummy audio device. Luckily the USB headset works
  fine, if plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  swarren7664 F pulseaudio
   /dev/snd/controlC0:  swarren7664 F pulseaudio
   /dev/snd/pcmC0D0c:   swarren7664 F...m pulseaudio
   /dev/snd/pcmC0D0p:   swarren7664 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jun 10 23:57:08 2020
  InstallationDate: Installed on 2016-03-03 (1561 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1DETA6W (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ERCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P70
  dmi.product.name: 20ERCTO1WW
  dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70
  dmi.product.version: ThinkPad P70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1883054] [NEW] Built-in audio device not available until alsa is reloaded

[Stephen Warren]

Public bug reported:

I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio
worked fine, using either the built-in speakers/mic on the laptop or via
a USB headset when that was plugged in.

However, after upgrading to 20.04, the built-in audio device is no
longer available until I run "sudo alsa force-reload". Wthhout that WAR,
all I see is a dummy audio device. Luckily the USB headset works fine,
if plugged in.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  swarren7664 F pulseaudio
 /dev/snd/controlC0:  swarren7664 F pulseaudio
 /dev/snd/pcmC0D0c:   swarren7664 F...m pulseaudio
 /dev/snd/pcmC0D0p:   swarren7664 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Jun 10 23:57:08 2020
InstallationDate: Installed on 2016-03-03 (1561 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago)
dmi.bios.date: 08/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1DETA6W (2.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ERCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P70
dmi.product.name: 20ERCTO1WW
dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70
dmi.product.version: ThinkPad P70
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Built-in audio device not available until alsa is reloaded

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and
  audio worked fine, using either the built-in speakers/mic on the
  laptop or via a USB headset when that was plugged in.

  However, after upgrading to 20.04, the built-in audio device is no
  longer available until I run "sudo alsa force-reload". Wthhout that
  WAR, all I see is a dummy audio device. Luckily the USB headset works
  fine, if plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  swarren7664 F pulseaudio
   /dev/snd/controlC0:  swarren7664 F pulseaudio
   /dev/snd/pcmC0D0c:   swarren7664 F...m pulseaudio
   /dev/snd/pcmC0D0p:   swarren7664 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jun 10 23:57:08 2020
  InstallationDate: Installed on 2016-03-03 (1561 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1DETA6W (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ERCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P70
  dmi.product.name: 20ERCTO1WW
  dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70
  dmi.product.version: ThinkPad P70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1749597] Re: [aarch64] gas: Error: non-constant expression in ".if" statement

[Stephen Warren]

For my own understanding, I'm curious:

a) Whether Ubuntu toolchains are usually updated for bugs like this

b) Roughly how often toolchain updates are usually released. I suppose
you're busy with Spectre stuff right now though?

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

Title:
  [aarch64] gas: Error: non-constant expression in ".if" statement

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  New

Bug description:
  gas in binutils 2.26 contains a bug that prevents compilation of ARM
  Trusted Firmware in particular, or any code that references the "."
  symbol following a .align statement that specifies explicit padding
  data.

  ATF bug report: https://github.com/ARM-software/tf-issues/issues/401
  binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364

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

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

[Touch-packages] [Bug 1749597] [NEW] [aarch64] gas: Error: non-constant expression in ".if" statement

[Stephen Warren]

Public bug reported:

gas in binutils 2.26 contains a bug that prevents compilation of ARM
Trusted Firmware in particular, or any code that references the "."
symbol following a .align statement that specifies explicit padding
data.

ATF bug report: https://github.com/ARM-software/tf-issues/issues/401
binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364

** Affects: binutils
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: Sourceware.org Bugzilla #20364
   https://sourceware.org/bugzilla/show_bug.cgi?id=20364

** Also affects: binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=20364
   Importance: Unknown
   Status: Unknown

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

Title:
  [aarch64] gas: Error: non-constant expression in ".if" statement

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  New

Bug description:
  gas in binutils 2.26 contains a bug that prevents compilation of ARM
  Trusted Firmware in particular, or any code that references the "."
  symbol following a .align statement that specifies explicit padding
  data.

  ATF bug report: https://github.com/ARM-software/tf-issues/issues/401
  binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364

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

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

[Touch-packages] [Bug 1741775] Re: bad symlink "/etc/resolvconf/resolv.conf.d/original"

[Warren]

I searched through /var/log/apt history files and resolvconf gets sucked
in as a dependency when I install the proprietary vpn-unlimited
application from Keepsolid.

If I remove resolvconf, is it necessary to re-install or re-configure
any other components? I realize that might break vpn-unlimited but
that's not a Ubuntu matter.

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

Title:
  bad symlink "/etc/resolvconf/resolv.conf.d/original"

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 amd_64
  resolvconf 1.79ubuntu8

  The symlink at "/etc/resolvconf/resolv.conf.d/original" points to
  "../run/systemd/resolve/stub-resolv.conf". This is a broken link as
  the relative path does not exist. This causes resolvconf to improperly
  (re-)generate "/run/resolvconf/resolv.conf". The link should probably
  instead point to the absolute path "/run/systemd/resolve/stub-
  resolv.conf".

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

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

[Touch-packages] [Bug 1741775] [NEW] bad symlink "/etc/resolvconf/resolv.conf.d/original"

[Warren]

Public bug reported:

Ubuntu 17.10 amd_64
resolvconf 1.79ubuntu8

The symlink at "/etc/resolvconf/resolv.conf.d/original" points to
"../run/systemd/resolve/stub-resolv.conf". This is a broken link as the
relative path does not exist. This causes resolvconf to improperly
(re-)generate "/run/resolvconf/resolv.conf". The link should probably
instead point to the absolute path "/run/systemd/resolve/stub-
resolv.conf".

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

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

Title:
  bad symlink "/etc/resolvconf/resolv.conf.d/original"

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 amd_64
  resolvconf 1.79ubuntu8

  The symlink at "/etc/resolvconf/resolv.conf.d/original" points to
  "../run/systemd/resolve/stub-resolv.conf". This is a broken link as
  the relative path does not exist. This causes resolvconf to improperly
  (re-)generate "/run/resolvconf/resolv.conf". The link should probably
  instead point to the absolute path "/run/systemd/resolve/stub-
  resolv.conf".

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

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

[Touch-packages] [Bug 1677455] [NEW] lose of sound

[warren]

Public bug reported:

loose of sound completely every update its becoming more difficult to
restore

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
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 Mar 30 01:24:20 2017
DistUpgraded: 2016-11-11 10:42:31,618 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:8336]
   Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:8336]
InstallationDate: Installed on 2015-03-14 (746 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
MachineType: ASUSTeK Computer INC. CM5570
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=b082e838-a6db-4326-b1f1-8b770239bbab ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-11-11 (138 days ago)
dmi.bios.date: 08/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: CM5570
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd08/11/2009:svnASUSTeKComputerINC.:pnCM5570:pvrRevX.0x:rvnASUSTeKComputerINC.:rnCM5570:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: CM5570
dmi.product.version: Rev X.0x
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
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 Mar 30 00:36:18 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 8
 inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 9
 inputUSB Optical MouseMOUSE, 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/1677455

Title:
  lose  of sound

Status in xorg package in Ubuntu:
  New

Bug description:
  loose of sound completely every update its becoming more difficult to
  restore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  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 Mar 30 01:24:20 2017
  DistUpgraded: 2016-11-11 10:42:31,618 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK 

[Touch-packages] [Bug 1673666] [NEW] after update the printer quit tried reloading cups but didn, hve enough experience to do it successfully

[warren]

Public bug reported:

updated computer than tried printing a floor plan from the internet.
"print to file" was displayed in print window , clicked on printer icon
and it said no printer connected to server.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups (not installed)
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
CurrentDesktop: Unity
Date: Fri Mar 17 00:09:54 2017
InstallationDate: Installed on 2015-03-14 (733 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cups
UpgradeStatus: Upgraded to xenial on 2016-11-11 (125 days ago)

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


** Tags: apport-bug i386 xenial

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

Title:
  after update the printer quit  tried reloading  cups but didn,hve
  enough experience to do it successfully

Status in cups package in Ubuntu:
  New

Bug description:
  updated computer than tried printing a floor plan from the internet.
  "print to file" was displayed in print window , clicked on printer
  icon and it said no printer connected to server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Mar 17 00:09:54 2017
  InstallationDate: Installed on 2015-03-14 (733 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2016-11-11 (125 days ago)

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

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

[Touch-packages] [Bug 1665196] Re: Wifi password must entered and saved from edit connections gui

[warren]

I retested to make sure this bug is valid on my hardware. Apparently it
would seem there is a time limit for entering the Wi-Fi password, if the
Wi-Fi password is entered within the time limit the Wi-Fi password is
accepted otherwise password must be entered and saved from the Edit
Connections GUI.

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

Title:
  Wifi password must entered and saved from edit connections gui

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.2 Live Session ISO test
  Entered WI-FI password twice does connect
  Then using from network menu right portion of top panel choosing Edit 
Connections >> Edit >>WI-FI >> Edit >> Wi-Fi security manually entering and 
saving Wi-Fi password.
  The Ubuntu 16.04.2 Live session then connects to the Wi-Fi network.

  Network-manager Version: 1.2.2-0ubuntu0.16.04.3
  Ubuntu Desktop amd64 20170215.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  CurrentDesktop: Unity
  Date: Thu Feb 16 01:58:28 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.106  
metric 600
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Ubuntu-One  9d036b67-c7ca-4f50-8d85-f5c1914f670a  802-11-wireless  
1487210288  Thu 16 Feb 2017 01:58:08 AM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/2 
   Wired connection 1  6d2a43a6-66f1-3ac0-814f-2bdf988dfa4a  802-3-ethernet   
1487210129  Thu 16 Feb 2017 01:55:29 AM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Ubuntu-One  9d036b67-c7ca-4f50-8d85-f5c1914f670a  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1665196] [NEW] Wifi password must entered and saved from edit connections gui

[warren]

Public bug reported:

Ubuntu 16.04.2 Live Session ISO test
Entered WI-FI password twice does connect
Then using from network menu right portion of top panel choosing Edit 
Connections >> Edit >>WI-FI >> Edit >> Wi-Fi security manually entering and 
saving Wi-Fi password.
The Ubuntu 16.04.2 Live session then connects to the Wi-Fi network.

Network-manager Version: 1.2.2-0ubuntu0.16.04.3
Ubuntu Desktop amd64 20170215.2

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
CurrentDesktop: Unity
Date: Thu Feb 16 01:58:28 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.106  
metric 600
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
 Ubuntu-One  9d036b67-c7ca-4f50-8d85-f5c1914f670a  802-11-wireless  
1487210288  Thu 16 Feb 2017 01:58:08 AM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/2 
 Wired connection 1  6d2a43a6-66f1-3ac0-814f-2bdf988dfa4a  802-3-ethernet   
1487210129  Thu 16 Feb 2017 01:55:29 AM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Ubuntu-One  9d036b67-c7ca-4f50-8d85-f5c1914f670a  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --  
----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  Wifi password must entered and saved from edit connections gui

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.2 Live Session ISO test
  Entered WI-FI password twice does connect
  Then using from network menu right portion of top panel choosing Edit 
Connections >> Edit >>WI-FI >> Edit >> Wi-Fi security manually entering and 
saving Wi-Fi password.
  The Ubuntu 16.04.2 Live session then connects to the Wi-Fi network.

  Network-manager Version: 1.2.2-0ubuntu0.16.04.3
  Ubuntu Desktop amd64 20170215.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  CurrentDesktop: Unity
  Date: Thu Feb 16 01:58:28 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.106  
metric 600
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xter

[Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

After updating to the latest packages, this issue is solve. I can lxc-
start, lxc-attach, lxc-stop, and lxc-execute.

I do get some warning/error spew when running lxc-execute though. If
this looks unexpected, I can open a separate bug for it:

$ lxc-execute -n t1 -- /bin/bash
lxc-execute: utils.c: safe_mount: 1691 Invalid argument - Failed to mount 
/sys/kernel/debug onto /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug
lxc-execute: utils.c: safe_mount: 1691 Device or resource busy - Failed to 
mount mqueue onto /usr/lib/x86_64-linux-gnu/lxc/dev/mqueue
init.lxc.static: initutils.c: mount_fs: 36 failed to mount /proc : Device or 
resource busy
init.lxc.static: initutils.c: mount_fs: 36 failed to mount /dev/mqueue : Device 
or resource busy

The first two of those show up in the container log file upon lxc-start
too:

lxc-start 20160316211700.325 ERRORlxc_utils - utils.c:safe_mount:1691 - 
Invalid argument - Failed to mount /sys/kernel/debug onto 
/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug
lxc-start 20160316211700.325 ERRORlxc_utils - utils.c:safe_mount:1691 - 
Device or resource busy - Failed to mount mqueue onto 
/usr/lib/x86_64-linux-gnu/lxc/dev/mqueue

Thanks very much for fix and bug comments; this has been one of the most
productive bug reports I've ever filed:-)

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  Triaged
Status in lxcfs package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 

[Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Thanks. The chown solves the issue. I didn't need to make the
modification to the pam config file at all. I do need to do the chown
every time I log in though, with or without the pam change.

FWIW, when I ssh into the working server, the relevant /sys directory is
owned by swarren:swarren without any intervention. On my laptop, it's
always owned by root:root.

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  Triaged
Status in lxcfs package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 
327681
lxc-start 20160312

[Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Could you please expand on "Then re-chown your current systemd cgroup"?
I'm not sure exactly how/where cgroups get mounted, so I'm not sure what
path I should chown.

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  Triaged
Status in lxcfs package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - A

[Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Yes, I'm running lightdm.

$ cat /etc/pam.d/common-session 
session [default=1] pam_permit.so
session requisite   pam_deny.so
session requiredpam_permit.so
session optionalpam_umask.so
session requiredpam_unix.so 
session optionalpam_systemd.so 
session optionalpam_cgfs.so -c freezer,memory,name=systemd

(comments all stripped for brevity

That file should be unmodified relative to the package defaults, or put
another way, I haven't fiddled with it.

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lx

[Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Switching the linode system to the Ubuntu kernel (booted via pv-grub)
didn't make that system fail. Perhaps the difference is cgroup setup via
ssh vs XFCE/GUI login?

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for delete_module action 
32768

[Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

I have 2 Xenial systems. They are both fully up-to-date as of 5 minutes
ago. The failing system is a laptop running XFCE GUI, and I'm attempting
to use LXC from a GUI terminal. The other system is a linode that I
access via ssh, and LXC works fine there. I believe I've configured the
two systems the same way w.r.t. lxc (e.g. /etc/subuid, /etx/lxc/lxc-
usernet, ~/.config/lxc/default.conf, etc.). The primary difference is
that the Linode system is running a Linode-provided kernel, whereas my
laptop is running an Ubuntu-provided kernel.

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO 

[Touch-packages] [Bug 1556447] [NEW] lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Public bug reported:

On Ubuntu Xenial pre-release, I see the following, so can't start a
container:

[swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a amd64
Using image from local cache
Unpacking the rootfs

---
You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

To enable sshd, run: apt-get install openssh-server

For security reason, container images ship without user accounts
and without a root password.

Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.


swarren@sprint ~]$ lxc-start -n t2 -d
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.


[swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
  lxc-start 20160312101415.704 INFO lxc_start_ui - lxc_start.c:main:264 
- using rcfile /home/swarren/.local/share/lxc/t2/config
  lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
  lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
  lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
  lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for delete_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for delete_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:456 - Merging in the compat seccomp ctx into the main 
one
  lxc-start 20160312101415.708 DEBUGlxc_start - 
start.c:setup_signal_fd:289 - sigchild handler set
  lxc-start 20160312101415.708 DEBUGlxc_console - 
console.c:lxc_console_peer_default:437 - opening /dev/tty for console peer
  lxc-start 20160312101415.708 INFO lxc_caps -

[Touch-packages] [Bug 1452941] Re: PPTP VPN fails to connect in 15.04, but works in 14.04/14.10

[Jared Warren]

Scratch that, loading the modules allows it to work with a *single* IPv4
route, but I get the same error if I try to connect with multiple roots.
My NetworkManager output to syslog is attached.

** Attachment added: "NetworkManager.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452941/+attachment/4542372/+files/NetworkManager.log

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

Title:
  PPTP VPN fails to connect in 15.04, but works in 14.04/14.10

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can create a PPTP VPN connection and connect to a remote network in
  Ubuntu 14.04/14.10 (Unity live boot DVD) but the connection does not
  work in Ubuntu 15.04 (Unity live boot USB), even though I am using the
  exact same GUI configuration settings in the Network-Manager (I have
  confirmed this several times).  In addition to the live boot
  instances, the PPTP VPN connected without problems for me on my
  14.04/14.10 installs, but failed on a fresh harddisk install of Ubuntu
  MATE 15.04.

  The error that I get in a notification pop-up window when trying to
  connect on 15.04 is: "The VPN connection 'VPN connection 1' failed
  because the VPN service returned invalid configuration."

  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  ubuntu@ubuntu:~$ apt-cache policy network-manager
  network-manager:
Installed: 0.9.10.0-4ubuntu15
Candidate: 0.9.10.0-4ubuntu15
Version table:
   *** 0.9.10.0-4ubuntu15 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CurrentDesktop: Unity
  Date: Thu May  7 22:55:12 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.20 
   207.173.246.134 via 192.168.0.1 dev wlan0  src 192.168.0.20
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
LANbeforetime  1fefef93-2d1c-41eb-ad55-3f6c234d7023  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
 
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1452941] Re: PPTP VPN fails to connect in 15.04, but works in 14.04/14.10

[Jared Warren]

I needed to load all three of these modules to get it to work:
nf_nat_pptp, nf_conntrack_pptp, nf_conntrack_proto_gre

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

Title:
  PPTP VPN fails to connect in 15.04, but works in 14.04/14.10

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can create a PPTP VPN connection and connect to a remote network in
  Ubuntu 14.04/14.10 (Unity live boot DVD) but the connection does not
  work in Ubuntu 15.04 (Unity live boot USB), even though I am using the
  exact same GUI configuration settings in the Network-Manager (I have
  confirmed this several times).  In addition to the live boot
  instances, the PPTP VPN connected without problems for me on my
  14.04/14.10 installs, but failed on a fresh harddisk install of Ubuntu
  MATE 15.04.

  The error that I get in a notification pop-up window when trying to
  connect on 15.04 is: "The VPN connection 'VPN connection 1' failed
  because the VPN service returned invalid configuration."

  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  ubuntu@ubuntu:~$ apt-cache policy network-manager
  network-manager:
Installed: 0.9.10.0-4ubuntu15
Candidate: 0.9.10.0-4ubuntu15
Version table:
   *** 0.9.10.0-4ubuntu15 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CurrentDesktop: Unity
  Date: Thu May  7 22:55:12 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.20 
   207.173.246.134 via 192.168.0.1 dev wlan0  src 192.168.0.20
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
LANbeforetime  1fefef93-2d1c-41eb-ad55-3f6c234d7023  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
 
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1504444] Re: package gconf2 3.2.6-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Warren Turkal]

Here's some more info:

I ran "dpkg --configure -a" as root, which failed.

Then I ran "sudo dpkg --configure -a" as my user with sudo privileges
and it worked. Now my system is not in an unconfigured state.

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

Title:
  package gconf2 3.2.6-3ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in gconf package in Ubuntu:
  New

Bug description:
  This package failed to be configured during an upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: gconf2 3.2.6-3ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
  Uname: Linux 4.2.0-12-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Fri Oct  9 01:34:43 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-03-08 (944 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.10.2ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago)

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

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

[Touch-packages] [Bug 1504444] [NEW] package gconf2 3.2.6-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Warren Turkal]

Public bug reported:

This package failed to be configured during an upgrade.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: gconf2 3.2.6-3ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-12-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Fri Oct  9 01:34:43 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
DuplicateSignature: package:gconf2:3.2.6-3ubuntu3:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-03-08 (944 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
RelatedPackageVersions:
 dpkg 1.18.2ubuntu4
 apt  1.0.10.2ubuntu1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago)

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


** Tags: amd64 apport-package need-duplicate-check wily

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

Title:
  package gconf2 3.2.6-3ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in gconf package in Ubuntu:
  New

Bug description:
  This package failed to be configured during an upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: gconf2 3.2.6-3ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
  Uname: Linux 4.2.0-12-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Fri Oct  9 01:34:43 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-03-08 (944 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.10.2ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago)

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

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

[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel

[Warren Turkal]

I just found that the apparmor profile for docker was disabled for some
reason. After removing the symlink from /etc/apparmor.d/disable/docker,
it works. I don't remember ever adding docker to the apparmor disable
links.

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

Title:
  docker.io doesn't work with apparmor 3.0 RC1 kernel

Status in “apparmor” package in Ubuntu:
  Invalid
Status in “docker.io” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce (from
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor):

  1. sudo apt-get install docker.io # 1.2.0~dfsg1-1

  2. sudo docker pull ubuntu:trusty

  3. sudo docker run ubuntu:trusty uptime
  2014/09/18 15:48:48 Error response from daemon: Cannot start container 
fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor 
profile docker-default: permission denied

  What is expected? uptime to return something like:
  $ sudo docker run ubuntu:trusty uptime
   20:31:21 up 1 min,  0 users,  load average: 0.09, 0.06, 0.03

  I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing
  apparmor related in the logs. If I boot an earlier kernel without the
  3.0 RC1 patches, it works.

  FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic,
  which will affect docker.io in Ubuntu. Workaround until this bug is
  fixed is to boot into 3.16.0-16.22 or earlier.

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

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

[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel

[Warren Turkal]

Just so you know, here's the docker.io package version also:
ii  docker.io  1.2.0~dfsg1-1ubuntu1 amd64Linux container runtime

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

Title:
  docker.io doesn't work with apparmor 3.0 RC1 kernel

Status in “apparmor” package in Ubuntu:
  Invalid
Status in “docker.io” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce (from
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor):

  1. sudo apt-get install docker.io # 1.2.0~dfsg1-1

  2. sudo docker pull ubuntu:trusty

  3. sudo docker run ubuntu:trusty uptime
  2014/09/18 15:48:48 Error response from daemon: Cannot start container 
fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor 
profile docker-default: permission denied

  What is expected? uptime to return something like:
  $ sudo docker run ubuntu:trusty uptime
   20:31:21 up 1 min,  0 users,  load average: 0.09, 0.06, 0.03

  I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing
  apparmor related in the logs. If I boot an earlier kernel without the
  3.0 RC1 patches, it works.

  FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic,
  which will affect docker.io in Ubuntu. Workaround until this bug is
  fixed is to boot into 3.16.0-16.22 or earlier.

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

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

[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel

[Warren Turkal]

I also tried the 3.17.0-031700-generic #2001410060605 linked above. It
also does not work on that kernel.

# docker run -i -t ubuntu /bin/bash
Unable to find image 'ubuntu' locally
Pulling repository ubuntu
1357f421be38: Download complete 
511136ea3c5a: Download complete 
1de2bd7201a2: Download complete 
b70ad18cfc2a: Download complete 
3b39241dab7c: Download complete 
23f1840ed5a5: Download complete 
dfa12c637781: Download complete 
set apparmor profile docker-default: no such file or directory2014/10/13 
11:24:00 Error response from daemon: Cannot start container 
37fdd08fdb5ef28e9a564eb25723acf2363478d2e188f57c7587d416a2ec7825: set apparmor 
profile docker-default: no such file or directory

# uname -a
Linux braindead 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

Just so you know, I did rm -rf /var/lib/docker and reinstalled the
docker.io package between each try.

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

Title:
  docker.io doesn't work with apparmor 3.0 RC1 kernel

Status in “apparmor” package in Ubuntu:
  Invalid
Status in “docker.io” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce (from
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor):

  1. sudo apt-get install docker.io # 1.2.0~dfsg1-1

  2. sudo docker pull ubuntu:trusty

  3. sudo docker run ubuntu:trusty uptime
  2014/09/18 15:48:48 Error response from daemon: Cannot start container 
fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor 
profile docker-default: permission denied

  What is expected? uptime to return something like:
  $ sudo docker run ubuntu:trusty uptime
   20:31:21 up 1 min,  0 users,  load average: 0.09, 0.06, 0.03

  I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing
  apparmor related in the logs. If I boot an earlier kernel without the
  3.0 RC1 patches, it works.

  FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic,
  which will affect docker.io in Ubuntu. Workaround until this bug is
  fixed is to boot into 3.16.0-16.22 or earlier.

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

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

[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel

[Warren Turkal]

I am getting the following still.
# docker run -i -t ubuntu /bin/bash
set apparmor profile docker-default: no such file or directory2014/10/13 
11:05:41 Error response from daemon: Cannot start container 
7981801146ab1771470fd72bc97e6582ff573fa159199f6cb86afaa7eaa74ea9: set apparmor 
profile docker-default: no such file or directory

Here's uname -a:
# uname -a
Linux braindead 3.16.0-22-generic #29-Ubuntu SMP Thu Oct 9 16:26:18 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

As seen above, I am running 3.16.0-22.29. Is there something I need to
do manually to fix this?

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

Title:
  docker.io doesn't work with apparmor 3.0 RC1 kernel

Status in “apparmor” package in Ubuntu:
  Invalid
Status in “docker.io” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce (from
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor):

  1. sudo apt-get install docker.io # 1.2.0~dfsg1-1

  2. sudo docker pull ubuntu:trusty

  3. sudo docker run ubuntu:trusty uptime
  2014/09/18 15:48:48 Error response from daemon: Cannot start container 
fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor 
profile docker-default: permission denied

  What is expected? uptime to return something like:
  $ sudo docker run ubuntu:trusty uptime
   20:31:21 up 1 min,  0 users,  load average: 0.09, 0.06, 0.03

  I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing
  apparmor related in the logs. If I boot an earlier kernel without the
  3.0 RC1 patches, it works.

  FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic,
  which will affect docker.io in Ubuntu. Workaround until this bug is
  fixed is to boot into 3.16.0-16.22 or earlier.

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

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

[Touch-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

[Warren]

I discovered this problem this morning while trying to set up my laptop
with a bluetooth headset (Moto S305) for a pending video conference.
Some Googling led me to this thread and comment #93, and the fix works
just fine. "Trusty" being a LTS release, there are sure to be many other
people affected indefinitely until an update appears in the standard
"Trusty" ppa's. Hope that will be soon.

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in “blueman” package in Ubuntu:
  Fix Released
Status in “gnome-bluetooth” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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