[Touch-packages] [Bug 1780017] [NEW] Hostname changes not persistent

[Sanjeev Gopal]

Public bug reported:

Only applicable to Ubuntu 18.04. Changes made via "hostnamectl set-
hostname" are not persistent - reverts after a reboot.

See results details below:

# hostnamectl status
   Static hostname: xxxlxd903
 Icon name: computer-vm
   Chassis: vm
Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
   Boot ID: 463b63d5bc3942a9abacdf34054644b4
Virtualization: vmware
  Operating System: Ubuntu 18.04 LTS
Kernel: Linux 4.15.0-24-generic
  Architecture: x86-64

# hostnamectl set-hostname xxxlxd903x

# hostnamectl status
   Static hostname: xxxlxd903x
 Icon name: computer-vm
   Chassis: vm
Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
   Boot ID: 463b63d5bc3942a9abacdf34054644b4
Virtualization: vmware
  Operating System: Ubuntu 18.04 LTS
Kernel: Linux 4.15.0-24-generic
  Architecture: x86-64

# shutdown -r now

...

$ hostnamectl status
   Static hostname: xxxlxd903
 Icon name: computer-vm
   Chassis: vm
Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
   Boot ID: ffb13e8eb23f40029a7685178229c2bb
Virtualization: vmware
  Operating System: Ubuntu 18.04 LTS
Kernel: Linux 4.15.0-24-generic
  Architecture: x86-64

Note: System is fully patched now. Was happening earlier too - with a
fresh install.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jul  4 12:52:19 2018
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic 
root=UUID=72a62618-633d-11e8-9a7c-005056911d79 ro maybe-ubiquity
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/05/2016
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/05/2016:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
modified.conffile..etc.systemd.timesyncd.conf: [modified]
mtime.conffile..etc.systemd.timesyncd.conf: 2018-05-29T20:59:09.725641

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


** Tags: amd64 apport-bug bionic uec-images

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

Title:
  Hostname changes not persistent

Status in systemd package in Ubuntu:
  New

Bug description:
  Only applicable to Ubuntu 18.04. Changes made via "hostnamectl set-
  hostname" are not persistent - reverts after a reboot.

  See results details below:

  # hostnamectl status
 Static hostname: xxxlxd903
   Icon name: computer-vm
 Chassis: vm
  Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
 Boot ID: 463b63d5bc3942a9abacdf34054644b4
  Virtualization: vmware
Operating System: Ubuntu 18.04 LTS
  Kernel: Linux 4.15.0-24-generic
Architecture: x86-64

  # hostnamectl set-hostname xxxlxd903x

  # hostnamectl status
 Static hostname: xxxlxd903x
   Icon name: computer-vm
 Chassis: vm
  Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
 Boot ID: 463b63d5bc3942a9abacdf34054644b4
  Virtualization: vmware
Operating System: Ubuntu 18.04 LTS
  Kernel: Linux 4.15.0-24-generic
Architecture: x86-64

  # shutdown -r now

  ...

  $ hostnamectl status
 Static hostname: xxxlxd903
   Icon name: computer-vm
 Chassis: vm
  Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
 Boot ID: ffb13e8eb23f40029a7685178229c2bb
  Virtualization: vmware
Operating System: Ubuntu 18.04 LTS
  Kernel: Linux 4.15.0-24-generic
Architecture: x86-64

  Note: System is fully patched now. Was happening earlier too - with a
  fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jul  4 12:52:19 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic 

[Touch-packages] [Bug 1779925] Re: Compiz not running

[Daniel van Vugt]

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

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

Title:
  Compiz not running

Status in compiz package in Ubuntu:
  New

Bug description:
  To whoever reading this, I assume that you are reading the below
  message after seeing the auto generated bug report. I'm just
  explaining below the scenario of how and when I got the error and how
  it got fixed. Till date I'm not sure what caused this error in first
  place.

  The details of the error:

  I used to get this error every time I started the system.
  Report error also used to fail. Ironically now report error is working when 
there is no longer an error.

  Coupled with this error one day my desktop user interface itself was
  not working as compiz was not running.

  I tried different solutions from many forums, community pages online.
  But none has worked.

  I had opened guest session out of curiosity to check if it works and it 
worked perfectly.
  Then I observed a differnce and made the below change in config file 
~/.config/compiz-1/compizconfig/config

  ## FROM
  profile = unity-lowgfx
  ## TO 
  profile = unity

  Then after re-start it started working. No errors since then.

  P.S. Ignore if the above doesn't make any sense or it is not related
  the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul  4 00:17:09 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.60, 4.4.0-122-generic, x86_64: installed
   ndiswrapper, 1.60, 4.4.0-128-generic, x86_64: installed
   ndiswrapper, 1.60, 4.4.0-130-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
  InstallationDate: Installed on 2014-09-25 (1377 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3521
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=9717b719-a04b-4f40-ac66-56a9b1165260 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 06RYX8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron3521:pvrA08:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Tue Jul  3 21:29:09 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 939 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1779949] Re: Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

[Daniel van Vugt]

Indeed, I can't see any evidence of Bluetooth hardware in the attached
files. It should be mentioned under "rfkill:" or in CurrentDmesg.txt or
in Lspci.txt or under "Lsusb:".

Your wifi card is an "Intel Corporation Centrino Advanced-N 6205", which
does not support Bluetooth either (https://ark.intel.com/products/59471
/Intel-Centrino-Advanced-N-6205-Dual-Band).

Are you sure your machine contains Bluetooth hardware at all? If the
hardware really is there then this would be a kernel bug (package
"linux"). But it sounds like maybe you never had Bluetooth hardware and
so it would be correct to not get an icon.

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Prompted to restart xubuntu after software install.

  APT log
  Start-Date: 2018-07-02  21:47:46
  Commandline: /usr/bin/unattended-upgrade
  Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), 
linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic)
  Upgrade: linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), 
linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-generic:amd64 
(4.15.0.23.25, 4.15.0.24.26)
  End-Date: 2018-07-02  21:48:26

  After restart Bluetooth Device and icon missing.
  Deamon not running. 

  > systemctl status bluetooth.service

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead)
  Condition: start condition failed at Tue 2018-07-03 23:37:32 CEST; 2min 43s 
ago
 └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
   Docs: man:bluetoothd(8)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul  3 23:50:01 2018
  InstallationDate: Installed on 2018-06-10 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 42363U9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a18ceafb-2cf7-4a61-8cc6-8fcea672193c ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET81WW (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42363U9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET81WW(1.51):bd04/05/2018:svnLENOVO:pn42363U9:pvrThinkPadT420:rvnLENOVO:rn42363U9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 42363U9
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  syslog:
   jul 03 23:37:23 think420 NetworkManager[955]:   [1530653843.8849] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   jul 03 23:42:09 think420 sudo[2186]:   magnus : TTY=pts/0 ; PWD=/home/magnus 
; USER=root ; COMMAND=/bin/systemctl start bluetooth

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

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

[Touch-packages] [Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module

[Daniel van Vugt]

Did you remember to install it first?

  sudo apt install pulseaudio-module-jack

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

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

Title:
  Missing pulseaudio-module-jack files, cannot load module

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  I'm on Ubuntu 16.04.04.

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

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

[Touch-packages] [Bug 1779708] Re: Screen becomes skewed and corrupt [nouveau + GeForce 7025]

[Daniel van Vugt]

Please continue following the steps in comment #2 and #3.

** Summary changed:

- My screen got deconfigurtated
+ Screen becomes skewed and corrupt [nouveau + GeForce 7025]

** Tags added: nouveau

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

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

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

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

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

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

Title:
  Screen becomes skewed and corrupt [nouveau + GeForce 7025]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  WHen I get into google or some other programs, my screen fails, and
  don't work any longer. It became a screen like that of the Tv shows
  when there is not signal, and it just doesn't respond any more. I
  can't do anything, and I must restart the PC, the screen doesn't allow
  me to do any other operation. I previously have the 16.04 LTS ubuntu
  with unity and conpiz, and I tried to actualize it to 18.04  LTS
  version, the bug began.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  2 10:07:31 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2015-04-16 (1172 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=78b08060-d316-4ee6-92e7-4f94861741cd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: M68MT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68MT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Jul  2 09:02:38 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1779708] [NEW] Screen becomes skewed and corrupt [nouveau + GeForce 7025]

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

WHen I get into google or some other programs, my screen fails, and
don't work any longer. It became a screen like that of the Tv shows when
there is not signal, and it just doesn't respond any more. I can't do
anything, and I must restart the PC, the screen doesn't allow me to do
any other operation. I previously have the 16.04 LTS ubuntu with unity
and conpiz, and I tried to actualize it to 18.04  LTS version, the bug
began.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jul  2 10:07:31 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
InstallationDate: Installed on 2015-04-16 (1172 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=78b08060-d316-4ee6-92e7-4f94861741cd ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: M68MT-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: M68MT-S2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Jul  2 09:02:38 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: nouveau

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug bionic nouveau third-party-packages ubuntu
-- 
Screen becomes skewed and corrupt [nouveau + GeForce 7025]
https://bugs.launchpad.net/bugs/1779708
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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

[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[John Gallagher]

> I'm not particularly familiar with this part of initramfs-tools, but
it seems to me that essentials like the loading of the virtio_pci module
would be short-circuited by your patch.

Yes, you're right, thanks for pointing that out. If the driver isn't
built-in to the kernel, it would be omitted. I think what we need to do
here is get a list of the devices that make up the root pool, probably
from the output of `zpool list -vPL`, and then call 'block_dev_mod_add'
on each device. I'll work on updating the patch.

> I was just pointed to
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS and told
that ZFS filesystems aren't expected to be in /etc/fstab according to
those instructions. Is this correct? I haven't checked but it seems that
initramfs-tools wouldn't then fail under these conditions.

It's true that we don't have the filesystems listed in /etc/fstab. Can
you elaborate on how you anticipate that would affect building the
initramfs?

> Could you provide exact steps to reproduce your problem, please?
Once you have a machine with zfs on root, this should be reproducible by 
running `apt install kdump-tools`. The post install hooks fail while trying to 
build an initramfs for the crash kernel. We build these ubuntu images that use 
zfs on root using live-build (https://github.com/delphix/appliance-build/), but 
our process currently relies on some packages internal to our organization. If 
need be, we might be able to modify the build to be usable externally as well.

> Does this apply and work correctly on the current Ubuntu development release 
> (Cosmic) please? We land changes there first and only once successful 
> consider backporting to existing releases as appropriate.
Is it possible to upgrade my machine to the development release? If not, I 
might be able to modify our build process to build an Cosmic image that uses 
zfs on root.

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 

[Touch-packages] [Bug 1779968] [NEW] /usr/bin/vim.basic:11:update_refs:collect:collect_with_callback:PyGC_Collect:Py_Finalize

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: xenial yakkety zesty

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

Title:
  
/usr/bin/vim.basic:11:update_refs:collect:collect_with_callback:PyGC_Collect:Py_Finalize

Status in vim package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1779956] Re: GDPR Compliance

[RXCE]

Thank you for your response,

While it is indeed correct and true that Ubuntu's configuration does
comply, this is more of a legal/policy bug than a technical one.

As the GDPR emphasizes privacy by design, how can Ubuntu ensure ongoing
compliance if its distro is built upon a project that neglects privacy
and seems to do what it wants?

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

Title:
  GDPR Compliance

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The systemd project is experimenting and working with various ideas
  that have privacy ramifications. This includes the work in systemd-
  resolved and systemd-timesyncd that creates a possibility for
  disclosure of personal information to Google or similar providers
  through default code paths. The data remitted such as client IP
  addresses, subdomains containing usernames or unique IDs, banking
  domains and similar data may be considered personal data under the
  GDPR and other EU law.

  These components are currently in a state where it is legally dubious
  whether they comply or can be made to comply. In particular, systemd's
  default configuration unless otherwise configured and compiled
  discloses personal information to Google without consent or methods to
  withdraw consent and without plain-language privacy policy. This
  design overall is considered flawed by the GDPR.

  I had reported this concern upstream as it impacts all distributions,
  but the systemd project has shown disinterest in working on "privacy
  by design" and making their work compliant. This lack of concern and
  future work by the systemd project may interfere with distributions'
  efforts to make their distributions compliant.

  As such, this work upstream and future work by upstream may interfere
  with any compliance efforts by Ubuntu to ensure compliance with the
  GDPR as systemd cannot be relied upon as "compliant out of the box"
  software.

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

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

[Touch-packages] [Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower

[Dimitri John Ledkov ]

This affects systemd-fsckd autopkgtest

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

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

Title:
  'nova reboot' on arm64 is just 'nova reboot --hard' but slower

Status in nova package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Within Canonical's multi-architecture compute cloud, I observed that
  arm64 instances were taking an unreasonable amount of time to return
  from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same
  cloud region).

  Digging into this, I find that a nova soft reboot request is doing
  nothing at all on arm64 (no events visible within the qemu guest, and
  no reboot is triggered within the guest), and then after some sort of
  timeout (~2m), 'nova reboot' falls back to a hard reset of the guest.

  Since this is entirely predictable on the arm64 platform (because
  there's no implementation of ACPI plumbed through), 'nova reboot' on
  arm64 should just skip straight to the hard reboot and save everyone
  some clock time.

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

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

[Touch-packages] [Bug 1779956] Re: GDPR Compliance

[Dimitri John Ledkov ]

Please do check our configuration first. As far as I can tell, this is
invalid.

Ubuntu Privacy references are located at
https://www.ubuntu.com/legal/dataprivacy

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

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

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

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

Title:
  GDPR Compliance

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The systemd project is experimenting and working with various ideas
  that have privacy ramifications. This includes the work in systemd-
  resolved and systemd-timesyncd that creates a possibility for
  disclosure of personal information to Google or similar providers
  through default code paths. The data remitted such as client IP
  addresses, subdomains containing usernames or unique IDs, banking
  domains and similar data may be considered personal data under the
  GDPR and other EU law.

  These components are currently in a state where it is legally dubious
  whether they comply or can be made to comply. In particular, systemd's
  default configuration unless otherwise configured and compiled
  discloses personal information to Google without consent or methods to
  withdraw consent and without plain-language privacy policy. This
  design overall is considered flawed by the GDPR.

  I had reported this concern upstream as it impacts all distributions,
  but the systemd project has shown disinterest in working on "privacy
  by design" and making their work compliant. This lack of concern and
  future work by the systemd project may interfere with distributions'
  efforts to make their distributions compliant.

  As such, this work upstream and future work by upstream may interfere
  with any compliance efforts by Ubuntu to ensure compliance with the
  GDPR as systemd cannot be relied upon as "compliant out of the box"
  software.

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

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

[Touch-packages] [Bug 1779956] [NEW] GDPR Compliance

[RXCE]

Public bug reported:

The systemd project is experimenting and working with various ideas that
have privacy ramifications. This includes the work in systemd-resolved
and systemd-timesyncd that creates a possibility for disclosure of
personal information to Google or similar providers through default code
paths. The data remitted such as client IP addresses, subdomains
containing usernames or unique IDs, banking domains and similar data may
be considered personal data under the GDPR and other EU law.

These components are currently in a state where it is legally dubious
whether they comply or can be made to comply. In particular, systemd's
default configuration unless otherwise configured and compiled discloses
personal information to Google without consent or methods to withdraw
consent and without plain-language privacy policy. This design overall
is considered flawed by the GDPR.

I had reported this concern upstream as it impacts all distributions,
but the systemd project has shown disinterest in working on "privacy by
design" and making their work compliant. This lack of concern and future
work by the systemd project may interfere with distributions' efforts to
make their distributions compliant.

As such, this work upstream and future work by upstream may interfere
with any compliance efforts by Ubuntu to ensure compliance with the GDPR
as systemd cannot be relied upon as "compliant out of the box" software.

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


** Tags: compliance gdpr legal

** Description changed:

  The systemd project is experimenting and working with various ideas that
  have privacy ramifications. This includes the work in systemd-resolved
  and systemd-timesyncd that creates a possibility for disclosure of
  personal information to Google or similar providers through default code
  paths. The data remitted such as client IP addresses, subdomains
  containing usernames or unique IDs, banking domains and similar data may
  be considered personal data under the GDPR and other EU law.
  
  These components are currently in a state where it is legally dubious
  whether they comply or can be made to comply. In particular, systemd's
  default configuration unless otherwise configured and compiled discloses
  personal information to Google without consent or methods to withdraw
- consent. This design overall is considered flawed by the GDPR.
+ consent and without plain-language privacy policy. This design overall
+ is considered flawed by the GDPR.
  
  I had reported this concern upstream as it impacts all distributions,
  but the systemd project has shown disinterest in working on "privacy by
  design" and making their work compliant. This lack of concern and future
  work by the systemd project may interfere with distributions' efforts to
  make their distributions compliant.
  
- As such, this work upstream may interfere with any compliance efforts by
- Ubuntu to ensure compliance with the GDPR as systemd cannot be relied
- upon as "compliant out of the box" software.
+ As such, this work upstream and future work by upstream may interfere
+ with any compliance efforts by Ubuntu to ensure compliance with the GDPR
+ as systemd cannot be relied upon as "compliant out of the box" software.

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

Title:
  GDPR Compliance

Status in systemd package in Ubuntu:
  New

Bug description:
  The systemd project is experimenting and working with various ideas
  that have privacy ramifications. This includes the work in systemd-
  resolved and systemd-timesyncd that creates a possibility for
  disclosure of personal information to Google or similar providers
  through default code paths. The data remitted such as client IP
  addresses, subdomains containing usernames or unique IDs, banking
  domains and similar data may be considered personal data under the
  GDPR and other EU law.

  These components are currently in a state where it is legally dubious
  whether they comply or can be made to comply. In particular, systemd's
  default configuration unless otherwise configured and compiled
  discloses personal information to Google without consent or methods to
  withdraw consent and without plain-language privacy policy. This
  design overall is considered flawed by the GDPR.

  I had reported this concern upstream as it impacts all distributions,
  but the systemd project has shown disinterest in working on "privacy
  by design" and making their work compliant. This lack of concern and
  future work by the systemd project may interfere with distributions'
  efforts to make their distributions compliant.

  As such, this work upstream and future work by upstream may interfere
  with any compliance efforts by Ubuntu to ensure compliance with the
  GDPR as systemd cannot be relied upon as "compliant 

[Touch-packages] [Bug 1779949] [NEW] Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

[Magnus Helander]

Public bug reported:

Prompted to restart xubuntu after software install.

APT log
Start-Date: 2018-07-02  21:47:46
Commandline: /usr/bin/unattended-upgrade
Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), 
linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic)
Upgrade: linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), 
linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-generic:amd64 
(4.15.0.23.25, 4.15.0.24.26)
End-Date: 2018-07-02  21:48:26

After restart Bluetooth Device and icon missing.
Deamon not running. 

> systemctl status bluetooth.service

bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Tue 2018-07-03 23:37:32 CEST; 2min 43s ago
   └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
 Docs: man:bluetoothd(8)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jul  3 23:50:01 2018
InstallationDate: Installed on 2018-06-10 (23 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: bluetooth
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 42363U9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a18ceafb-2cf7-4a61-8cc6-8fcea672193c ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/05/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET81WW (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42363U9
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr83ET81WW(1.51):bd04/05/2018:svnLENOVO:pn42363U9:pvrThinkPadT420:rvnLENOVO:rn42363U9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T420
dmi.product.name: 42363U9
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
hciconfig:
 
rfkill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
syslog:
 jul 03 23:37:23 think420 NetworkManager[955]:   [1530653843.8849] Loaded 
device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
 jul 03 23:42:09 think420 sudo[2186]:   magnus : TTY=pts/0 ; PWD=/home/magnus ; 
USER=root ; COMMAND=/bin/systemctl start bluetooth

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


** Tags: amd64 apport-bug bionic

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

Title:
  Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  Prompted to restart xubuntu after software install.

  APT log
  Start-Date: 2018-07-02  21:47:46
  Commandline: /usr/bin/unattended-upgrade
  Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), 
linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic)
  Upgrade: linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), 
linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-generic:amd64 
(4.15.0.23.25, 4.15.0.24.26)
  End-Date: 2018-07-02  21:48:26

  After restart Bluetooth Device and icon missing.
  Deamon not running. 

  > systemctl status bluetooth.service

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead)
  Condition: start condition failed at Tue 2018-07-03 23:37:32 CEST; 2min 43s 
ago
 └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
   Docs: man:bluetoothd(8)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  

[Touch-packages] [Bug 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)

[dana]

Hi Steve,

This build seems to work OK for me as well. Thanks!

% dpkg-query -Wf '${Package}: ${Version}\n' | rg systemd
libnss-systemd: 237-3ubuntu10.2
libpam-systemd: 237-3ubuntu10.2
libsystemd0: 237-3ubuntu10.2
python3-systemd: 234-1build1
systemd: 237-3ubuntu10.2
systemd-sysv: 237-3ubuntu10

% SYSTEMD_LOG_LEVEL=debug systemd-detect-virt
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Virtualization Xen found in DMI (/sys/class/dmi/id/sys_vendor)
Virtualization XEN, found /sys/hypervisor/properties/features with value 
2705, XENFEAT_dom0 (indicating the 'hardware domain') is not set.
Found VM virtualization xen
xen

% systemctl is-active xe-daemon
active


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

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

Title:
  systemd sometimes misdetects Xen VMs (fixed up-stream)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * XEN virtualization missidentified as hyperv
   * This may cause units limited to a virtualisation not to be started; or 
redundant units for the other type of virtualisation to be started instead.
   * Previously xen & hyper-v were detected correctly separately, even when xen 
emulates/suggests that it is hyper-v.

  [Test Case]

   * Execute systemd-detect-virt and check that it detects Xen & Hyperv

  [Regression Potential]

   * Things that "fake" xen might not work as the detection code
  branches are changed, but it would affect previous releases and future
  releases of systemd-detect-virt. So far such things are not known to
  exist, and if such things appear in the future support for them would
  need to land upstream first.

  [Other Info]
   
   * Original bug report

  Cherrypick
  
https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a

  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this
  CPUID information when detecting Xen, and thus it erroneously assumes
  that the guest is running under Hyper-V. This causes Xen-related
  services (and anything else that relies on systemd's VM-detection
  functionality) to fail.

  I *believe* this is a regression from systemd 229 as used in Xenial —
  we have at least a few Xen-based VMs that report as Hyper-V via CPUID
  and don't have this issue on that version — but i haven't confirmed
  that for certain.

  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:

  https://github.com/systemd/systemd/issues/8844

  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.

  Thanks!

  See also:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573

  ---

  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  % apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10
    Candidate: 237-3ubuntu10
    Version table:
   *** 237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1779942] Re: package python3-apt 1.6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-apt 1.6.1 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in python-apt package in Ubuntu:
  New

Bug description:
  I was trying to install virtualbox then I received a message that I
  needed to run dpkg manually and then it reported the the python3-apt
  was in error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue Jul  3 18:01:23 2018
  DuplicateSignature:
   package:python3-apt:1.6.1
   Setting up make (4.1-9.1ubuntu1) ...
   dpkg: error processing package python3-apt (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-07-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: python-apt
  Title: package python3-apt 1.6.1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779942] [NEW] package python3-apt 1.6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[valdomiro de freitas sampaio]

Public bug reported:

I was trying to install virtualbox then I received a message that I
needed to run dpkg manually and then it reported the the python3-apt was
in error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-apt 1.6.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Tue Jul  3 18:01:23 2018
DuplicateSignature:
 package:python3-apt:1.6.1
 Setting up make (4.1-9.1ubuntu1) ...
 dpkg: error processing package python3-apt (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-07-03 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: python-apt
Title: package python3-apt 1.6.1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package python3-apt 1.6.1 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in python-apt package in Ubuntu:
  New

Bug description:
  I was trying to install virtualbox then I received a message that I
  needed to run dpkg manually and then it reported the the python3-apt
  was in error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue Jul  3 18:01:23 2018
  DuplicateSignature:
   package:python3-apt:1.6.1
   Setting up make (4.1-9.1ubuntu1) ...
   dpkg: error processing package python3-apt (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-07-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: python-apt
  Title: package python3-apt 1.6.1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779936] [NEW] mkinitramfs fails on Raspian 9 "Stretch"

[Rob Roschewsk]

Public bug reported:

Atempting to install kdump-tools fails due to error in mkinitramfs:

/usr/sbin/mkinitramfs -v -d /var/lib/kdump/initramfs-tools -o
/var/lib/kdump/initrd.img-4.14.30-v7+.new -4.14.30-v7+

mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools/

Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'

>From traces  it seems it's getting tripped up because the root
device specified in /proc/cmdline is in the form:
root=PARTUUID=6ddc62b3-02

I changed the boot command line to read: root=/dev/mmcblk0p2

and kdump-tools installed correctly.

Attaching output of /proc/mounts and mount for good measure.


root@raspberrypi:/usr/share/initramfs-tools# mount
/dev/mmcblk0p2 on / type ext4 (rw,noatime,data=ordered)
devtmpfs on /dev type devtmpfs 
(rw,relatime,size=470128k,nr_inodes=117532,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mmcblk0p1 on /boot type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1001 type tmpfs 
(rw,nosuid,nodev,relatime,size=94944k,mode=700,uid=1001,gid=100)

root@raspberrypi:~# cat /proc/mounts
/dev/root / ext4 rw,noatime,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=470128k,nr_inodes=117532,mode=755 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup 
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup 
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs 
rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
/dev/mmcblk0p1 /boot vfat 
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
 0 0
tmpfs /run/user/1001 tmpfs 
rw,nosuid,nodev,relatime,size=94944k,mode=700,uid=1001,gid=100 0 0

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

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

Title:
  mkinitramfs fails on Raspian 9 "Stretch"

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Atempting to install kdump-tools fails due to error in mkinitramfs:

  /usr/sbin/mkinitramfs -v -d /var/lib/kdump/initramfs-tools -o
  /var/lib/kdump/initrd.img-4.14.30-v7+.new -4.14.30-v7+

  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is 

[Touch-packages] [Bug 1777839] Re: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When i try to install audio driver, i found this issue

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jun 20 11:10:12 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  DpkgHistoryLog:
   Start-Date: 2018-06-20  11:08:35
   Requested-By: anandharaj (1001)
   Upgrade: snapd:amd64 (2.32.9+18.04, 2.33+18.04), initramfs-tools-bin:amd64 
(0.130ubuntu3.1, 0.130ubuntu3.2), libgcrypt20:amd64 (1.8.1-4ubuntu1, 
1.8.1-4ubuntu1.1), libgcrypt20:i386 (1.8.1-4ubuntu1, 1.8.1-4ubuntu1.1), 
libmozjs-52-0:amd64 (52.3.1-7fakesync1, 52.8.1-0ubuntu0.18.04.1), 
initramfs-tools-core:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2), 
initramfs-tools:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2)
   Remove: linux-image-extra-4.4.0-127-generic:amd64 (4.4.0-127.153)
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=fb742fda-003f-4ce7-a4d6-52b47cd24bbb
  InstallationDate: Installed on 2016-08-23 (665 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 413c:2501 Dell Computer Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5470
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed 
root=UUID=7ec171db-716a-4bcf-b66d-9249ce6ae583 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.6
  dmi.board.name: 0MT53G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.6:bd12/08/2017:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0MT53G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1779933] [NEW] Unable to log in through guest network captive portal

[Prasant Muralidhar]

Public bug reported:

I have this issue with starbucks wifi, and my university public wifi
when trying to connect via the guest network. The workaround linked
below as detailed by Stepan works to fix the problem at both locations.

https://askubuntu.com/a/1020934

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Jul  3 15:39:48 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-06-28 (4 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 172.18.0.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 172.18.0.0/19 dev wlp2s0 proto kernel scope link src 172.18.21.63 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
UDel_Guest  c1faa267-4d97-4ee4-80f1-52367f39cca0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug bionic

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

Title:
  Unable to log in through guest network captive portal

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have this issue with starbucks wifi, and my university public wifi
  when trying to connect via the guest network. The workaround linked
  below as detailed by Stepan works to fix the problem at both
  locations.

  https://askubuntu.com/a/1020934

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Jul  3 15:39:48 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-28 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 172.18.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.18.0.0/19 dev wlp2s0 proto kernel scope link src 172.18.21.63 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
UDel_Guest  c1faa267-4d97-4ee4-80f1-52367f39cca0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Steve Langasek]

debug error log attached.  I believe the failed print job starts at
03/Jul/2018:12:22:01.

I've also discovered in the course of reproducing this that it appears
to only be affecting jobs printed from evince, and not e.g. directly
from chromium.  I don't remember if I had tested printing directly from
chromium before.  So perhaps this is an evince bug rather than cups
proper.

And this looks possibly relevant.
D [03/Jul/2018:12:22:01 -0700] [Job 489] Unrecoverable error: rangecheck in 
setpagedevice


** Attachment added: "error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1763520/+attachment/5159288/+files/error_log

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

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups package in Ubuntu:
  New

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Leonidas S. Barbosa]

https://usn.ubuntu.com/3701-1/

** Changed in: libsoup2.4 (Ubuntu Xenial)
   Status: Confirmed => Fix Released

** Changed in: libsoup2.4 (Ubuntu Artful)
   Status: Confirmed => Fix Released

** Changed in: libsoup2.4 (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Fix Released
Status in libsoup2.4 source package in Artful:
  Fix Released
Status in libsoup2.4 source package in Bionic:
  Fix Released

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1779925] [NEW] Compiz not running

[Vishnu Prasad Rao]

Public bug reported:

To whoever reading this, I assume that you are reading the below message
after seeing the auto generated bug report. I'm just explaining below
the scenario of how and when I got the error and how it got fixed. Till
date I'm not sure what caused this error in first place.

The details of the error:

I used to get this error every time I started the system.
Report error also used to fail. Ironically now report error is working when 
there is no longer an error.

Coupled with this error one day my desktop user interface itself was not
working as compiz was not running.

I tried different solutions from many forums, community pages online.
But none has worked.

I had opened guest session out of curiosity to check if it works and it worked 
perfectly.
Then I observed a differnce and made the below change in config file 
~/.config/compiz-1/compizconfig/config

## FROM
profile = unity-lowgfx
## TO 
profile = unity

Then after re-start it started working. No errors since then.

P.S. Ignore if the above doesn't make any sense or it is not related the
bug report.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jul  4 00:17:09 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 ndiswrapper, 1.60, 4.4.0-122-generic, x86_64: installed
 ndiswrapper, 1.60, 4.4.0-128-generic, x86_64: installed
 ndiswrapper, 1.60, 4.4.0-130-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
InstallationDate: Installed on 2014-09-25 (1377 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 3521
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=9717b719-a04b-4f40-ac66-56a9b1165260 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 06RYX8
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron3521:pvrA08:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA08:
dmi.product.name: Inspiron 3521
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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: Tue Jul  3 21:29:09 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 939 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  Compiz not running

Status in xorg package in Ubuntu:
  New

Bug description:
  To whoever reading this, I assume that you are reading the below
  message after seeing the auto generated bug report. I'm just
  explaining below the scenario of how and when I got the error and how
  it got fixed. Till date I'm not sure what caused this error in first
  place.

  The details of the error:

  I used to get this error every time I started the system.
  Report error also used to fail. Ironically now report error is working when 
there is no longer an error.

  Coupled with this error one day my desktop user interface itself was
  not working as compiz was not running.

  I tried different solutions from many 

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[August Pamplona]

The issue also showed up with on my laptop. I was running Mint 19 (still
on the BETA) which is based on Bionic Beaver, kernel is
4.15.0-24-generic x86_64 bits with Cinnamon 3.8.6. I did try booting
with 4.15.0-22 and it made no difference (which, after reading the
comments here, I see is as expected)

The laptop is a Latitude E6400. It's one with the nVidia graphics. I
don't remember what the Bluetooth adapter is (it's something I added,
not necessarily something that would have come from Dell).

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Confirmed
Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

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

[Stéphane Graber]

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

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

Title:
  SRU of LXC 3.0.1 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Bionic:
  Fix Released
Status in lxc source package in Cosmic:
  Fix Released

Bug description:
  LXC upstream released LXC 3.0.1 as a bugfix release with following changelog:
  - tools: fix unitialized variable
  - storage: fix lvm fs uuid generation
  - lxc-oci: fix Cmd/Entrypoint parsing
  - lxc-oci: make umoci less verbose
  - lxclock: use thread-safe OFD fcntl() locks
  - locktests: fix test suite
  - conf: ensure umounts don’t propagate to host
  - doc: Tweak Japanese translation in lxc.container.conf(5)
  - fix signal sending in lxc.init
  - rootfs pinning: On NFS, make file hidden but don’t delete it
  - conf: fix temporary file creation
  - ringbuf: fix temporary file creation
  - Fix compilation with static libcap and shared gnutls
  - attach: always drop supplementary groups
  - lxc init: remove dead code
  - storage/rsync: free memory on error
  - tools/utils: free memory on error
  - lxc init: coding style
  - utils: define __NR_setns if missing on old glibcs
  - attach: try to always drop supplementary groups
  - conf: ret-try devpts mount without gid=5 on error
  - execute: fix app containers without root mapping
  - conf: fix net type checks in run_script_argv()
  - seccomp: handle arch inversion
  - seccomp: handle all errors
  - seccomp: cleanup compat architecture handling
  - seccomp: improve logging
  - tools: document -d/–daemonize for lxc-execute
  - seccomp: non-functional changes
  - seccomp: handle arch inversion II
  - lxc-oci: mkdir the download directory
  - do_lxcapi_create: set umask
  - lxc/tools/lxc_monitor: include missing 
  - pam-cgfs: ignore the system umask when creating the cgroup hierarchy
  - Also pass action scripts to CRIU on checkpointing
  - Fix the memory leak in cgfsng_attach
  - Fix memory leak in list_active_containers
  - Fix tool_utils.c build when HAVE_SETNS is unset
  - coverity: #1435210
  - coverity: #1435208
  - coverity: #1435207
  - coverity: #1435206
  - coverity: #1435205
  - coverity: #1435203
  - coverity: #1435200
  - coverity: #1435198
  - coverity: #1426734
  - lxccontainer: non-functional changes
  - lxccontainer: use thread-safe OFD locks
  - lxccontainer: non-functional changes
  - lxccontainer: do_lxcapi_is_running()
  - lxccontainer: do_lxcapi_freeze()
  - lxccontainer: do_lxcapi_unfreeze()
  - lxccontainer: non-functional changes
  - lxccontainer: use thread-safe open() + write()
  - lxccontainer: non-functional changes
  - lxccontainer: non-functional changes
  - lxccontainer: non-functional changes
  - coverity: #1435263
  - fix logic for execute log file
  - utils: add LXC_PROC_PID_FD_LEN
  - execute: use static buffer
  - execute: do not check inherited fds again
  - add some TRACE/ERROR reporting
  - execute: account for -o path option count
  - execute: set init_path when existing init is found
  - genl: remove
  - coverity: #1248104
  - coverity: #1248105
  - coverity: #1425744
  - utils: account for terminating \0 byte
  - confile: satisfy gcc-8
  - network: silence gcc-8
  - network: adhere to IFNAMSIZ limit
  - support case ignored suffix for sizes
  - utils: fix parse_byte_size_string() coding style
  - strlcpy: add strlcpy() implementation
  - tree-wide: s/strncpy()/strlcpy()/g
  - CODING_STYLE: add section about using strlcpy()
  - tools: s/strncpy()/strlcpy()/g
  - Revert “tools: s/strncpy()/strlcpy()/g”
  - tools: s/strncpy()/memcpy()/
  - doc: Add “-d/–daemon” option to Japanese lxc-execute(1)
  - doc: Fix size unit style in Japanese lxc.container.conf(5)
  - coverity: #1435604
  - coverity: #1435603
  - coverity: #1435602
  - coverity: #1425844
  - config: allow read-write /sys in user namespace
  - coverity: #1425836
  - coverity: #1248106
  - capabilities: raise ambient capabilities
  - coverity: #1425802
  - cgroups: refactor cgroup handling
  - cgroups: remove freezer_state()
  - seccomp: #ifdef SCMP_ARCH_AARCH64
  - conf: simplify write_id_mapping()
  - log: enable per-thread container name prefix
  - lxc-init: skip signals that can’t be caught
  - execute: use execveat() syscall if supported
  - tools: only create log file when requested
  - seccomp: fix off-by-one error in array 

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Leonidas S. Barbosa]

Hi,

We already have updates going through QA. Soon as possibly they'll be
published.

Thanks!

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Confirmed
Status in libsoup2.4 source package in Artful:
  Confirmed
Status in libsoup2.4 source package in Bionic:
  Confirmed

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1779901] [NEW] CVE-2018-12910

[Iain Lane]

*** This bug is a security vulnerability ***

Public security bug reported:

If you have appropriate permissions, you can view details at the
following links:

https://gitlab.gnome.org/GNOME/libsoup/issues/3
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

** Affects: libsoup2.4 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: libsoup2.4 (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: libsoup2.4 (Ubuntu Artful)
 Importance: Undecided
 Status: New

** Affects: libsoup2.4 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12910

** Also affects: libsoup2.4 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libsoup2.4 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: libsoup2.4 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: libsoup2.4 (Ubuntu)
   Status: New => Fix Released

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  New
Status in libsoup2.4 source package in Artful:
  New
Status in libsoup2.4 source package in Bionic:
  New

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1764628] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From sthou...@in.ibm.com 2018-06-27 01:45 EDT---
(In reply to comment #16)
> Srikanth, Seeteena,
>
> Canonical has asked for an update to this bug.  Could you provide one?
> Specifically, their question is... "please can you provide some more details
> why this is fixed with this util-linux version?"  Thanks.

Barry, I am not able to see any commit that went with 
util-linux_2.27.1-6ubuntu3.5 version. but from the testing perspective we are 
able to recreate the issue with the util-linux package that comes with 16.04.04.
Later we checked with upstream/util-linux_2.27.1-6ubuntu3.5 level and not able 
to see the issue. Hence we mirror this bug to canonical to pick or use this 
package for 16.04.04.

http://launchpadlibrarian.net/356140271/util-
linux_2.27.1-6ubuntu3.5_source.changes

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

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

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

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Iain Lane]

I could have added Bug-Ubuntu I guess. Anyway, there you go.

Michael supplied a test so I included that in the debdiffs to give some
confidence.

Tested build, install, upgrade.

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Confirmed
Status in libsoup2.4 source package in Artful:
  Confirmed
Status in libsoup2.4 source package in Bionic:
  Confirmed

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Iain Lane]

** Patch added: "1779901-bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+attachment/5159215/+files/1779901-bionic.debdiff

** Changed in: libsoup2.4 (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: libsoup2.4 (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: libsoup2.4 (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Confirmed
Status in libsoup2.4 source package in Artful:
  Confirmed
Status in libsoup2.4 source package in Bionic:
  Confirmed

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Iain Lane]

** Patch added: "1779901-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+attachment/5159214/+files/1779901-artful.debdiff

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Confirmed
Status in libsoup2.4 source package in Artful:
  Confirmed
Status in libsoup2.4 source package in Bionic:
  Confirmed

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

[Iain Lane]

** Patch added: "1779901-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+attachment/5159213/+files/1779901-xenial.debdiff

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Confirmed
Status in libsoup2.4 source package in Artful:
  Confirmed
Status in libsoup2.4 source package in Bionic:
  Confirmed

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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

[Touch-packages] [Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module

[Todd Chaffee]

Commands I used to load modules:

pactl load-module module-jack-sink
pactl load-module module-jack-source

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

Title:
  Missing pulseaudio-module-jack files, cannot load module

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  I'm on Ubuntu 16.04.04.

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

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

[Touch-packages] [Bug 1779905] [NEW] Missing pulseaudio-module-jack files, cannot load module

[Todd Chaffee]

Public bug reported:

When I try to load pulseaudio-module-jack modules, I get an error:

Failure: Module initialization failed

When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

I'm on Ubuntu 16.04.04.

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

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

Title:
  Missing pulseaudio-module-jack files, cannot load module

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  I'm on Ubuntu 16.04.04.

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

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

[Touch-packages] [Bug 1779902] Re: package rfkill 0.5-1ubuntu3.1 failed to install/upgrade: package rfkill is not ready for configuration cannot configure (current status 'half-installed')

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package rfkill 0.5-1ubuntu3.1 failed to install/upgrade: package
  rfkill is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in rfkill package in Ubuntu:
  New

Bug description:
  after Upgrading interepted dUe to power failUre

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rfkill 0.5-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   trigger-rally: Remove
   rfkill: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Tue Jul  3 21:15:52 2018
  DuplicateSignature:
   package:rfkill:0.5-1ubuntu3.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package rfkill (--configure):
package rfkill is not ready for configuration
  ErrorMessage: package rfkill is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-04-16 (443 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: rfkill
  Title: package rfkill 0.5-1ubuntu3.1 failed to install/upgrade: package 
rfkill is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu3

---
console-setup (1.178ubuntu3) cosmic; urgency=medium

  * debian/keyboard-configuration.postinst:
- Don't change /etc/default/keyboard at package upgrades on
  desktops, since it may conflict with how desktops deal with
  keyboard configuration (LP: #1762952).

 -- Gunnar Hjalmarsson   Tue, 15 May 2018 01:12:00
+0200

** Changed in: console-setup (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  New
Status in gnome-control-center source package in Bionic:
  New

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

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

[Touch-packages] [Bug 1779902] [NEW] package rfkill 0.5-1ubuntu3.1 failed to install/upgrade: package rfkill is not ready for configuration cannot configure (current status 'half-installed')

[jiljith]

Public bug reported:

after Upgrading interepted dUe to power failUre

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rfkill 0.5-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 trigger-rally: Remove
 rfkill: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Tue Jul  3 21:15:52 2018
DuplicateSignature:
 package:rfkill:0.5-1ubuntu3.1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package rfkill (--configure):
  package rfkill is not ready for configuration
ErrorMessage: package rfkill is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-04-16 (443 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: rfkill
Title: package rfkill 0.5-1ubuntu3.1 failed to install/upgrade: package rfkill 
is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package rfkill 0.5-1ubuntu3.1 failed to install/upgrade: package
  rfkill is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in rfkill package in Ubuntu:
  New

Bug description:
  after Upgrading interepted dUe to power failUre

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rfkill 0.5-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   trigger-rally: Remove
   rfkill: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Tue Jul  3 21:15:52 2018
  DuplicateSignature:
   package:rfkill:0.5-1ubuntu3.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package rfkill (--configure):
package rfkill is not ready for configuration
  ErrorMessage: package rfkill is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-04-16 (443 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: rfkill
  Title: package rfkill 0.5-1ubuntu3.1 failed to install/upgrade: package 
rfkill is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[Robie Basak]

I was just pointed to
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS and told
that ZFS filesystems aren't expected to be in /etc/fstab according to
those instructions. Is this correct? I haven't checked but it seems that
initramfs-tools wouldn't then fail under these conditions. Could you
provide exact steps to reproduce your problem, please?

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
  debugfs on /sys/kernel/debug type debugfs (rw,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
  rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/srv on /srv type zfs (rw,noatime,xattr,noacl)
  rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl)
  rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl)
  tmpfs on /run/user/1000 type tmpfs 

[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Łukasz Zemczak]

Once this migrates to cosmic release, I'll SRU it to bionic.

** Also affects: console-setup (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  New
Status in gnome-control-center source package in Bionic:
  New

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

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

[Touch-packages] [Bug 1774617] Re: Filter out snaps from GNOME Software

[Brian Murray]

** Package changed: software-properties (Ubuntu) => gnome-software
(Ubuntu)

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

Title:
  Filter out snaps from GNOME Software

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  An option should be provided in Software & Updates to filter out snaps
  from GNOME Software. Perhaps this should also affect the command-line
  (just as disabling restricted and multiverse would affect the command-
  line). Perhaps a dialogue box should be created when turning off snaps
  and the dialogue should ask whether to remove snapd entirely (first
  removing the snaps) or to set the refresh timer to monthly ( which is
  as close to turning it off as possible, timer CLI is here:
  https://snapdocs.labix.org/configuration-options/87 ), or to remove
  all snaps, or just to remove them from GNOME Software (for snaps, this
  could just hide apps that have their source listed as 'Snap Store').

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Jun  1 10:33:24 2018
  InstallationDate: Installed on 2017-08-03 (301 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (40 days ago)

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

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

[Touch-packages] [Bug 1774499] Re: /usr/bin/software-properties-gtk:IndexError:check_line:__init__:parse

[Brian Murray]

Here's the Traceback:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogAdd.py", 
line 86, in check_line
source_entry = SourceEntry(line)
  File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 104, in 
__init__
self.parse(line)
  File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 210, in 
parse
self.dist = pieces[2].strip()
IndexError: list index out of range

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

Title:
  /usr/bin/software-properties-gtk:IndexError:check_line:__init__:parse

Status in software-properties package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1777479] Re: RFE: add "allow-unauthenticated" option to add-apt-repository

[Brian Murray]

** Tags added: cosmic

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  RFE: add "allow-unauthenticated" option to add-apt-repository

Status in software-properties package in Ubuntu:
  New

Bug description:
  The apt command has an "--allow-unauthenticated" option.

  It would be great to add "--allow-unauthenticated" to "add-apt-
  repository" as well. This could add the "[trusted=yes]" option to the
  /etc/apt/sources.list.d/my_trusted_repo.list definition. Like so:

deb [trusted=yes] https://example.com/ bionic main

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

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

[Touch-packages] [Bug 1779302] Re: should retry reading key from keyserver (in _recv_key)

[Brian Murray]

** Tags added: rls-cc-incoming

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

Title:
  should retry reading key from keyserver (in _recv_key)

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Some recent events have made keyservers less reliable than they were
  previously:
    https://bitbucket.org/skskeyserver/sks-keyserver/issues/57
    https://bitbucket.org/skskeyserver/sks-keyserver/issues/60

  We have seen a greatly increased failure rate of retreiving keys
  from the key servers, both in cloud-init and with using apt-add-repository.

  
  Here is an example failure:

https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-nocloud-kvm-x/191/console

  The stdout/stderr that is a result of running:
  $ add-apt-repository --yes ppa:cloud-init-deve/daily

  gpg: keyring `/tmp/tmp4s88x_yf/secring.gpg' created
  gpg: keyring `/tmp/tmp4s88x_yf/pubring.gpg' created
  gpg: requesting key E4D304DF from hkp server keyserver.ubuntu.com
  gpgkeys: key 1FF0D8535EF7E719E5C81B9C083D06FBE4D304DF can't be retrieved
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver helper general error
  gpg: keyserver communications error: unknown pubkey algorithm
  gpg: keyserver receive failed: unknown pubkey algorithm
  Failed to add key.

  Retries on reading the key make sense here to be more resilient to
  transient network or remote service resources.  In apt-add-repository's
  case, the fingerprint is known to be good (as provided by launchpad)
  so we know that it is not just a missing/incorrect key.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-common 0.96.24.33
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 22:28:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1072 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Łukasz Zemczak]

I somehow forgot about this bug! Ok, I think I know now what you're
aiming for. Normally just checking for the existence of $2 would be
sufficient but not if we're expecting the config changes to happen on
package reinstall. I guess it's just a matter of design here - I
obviously was thinking of more that reinstallation/reconfiguration
should follow the same rules as an upgrade, as first install was already
responsible for modification of the /etc/default/keyboard file. But
there's also the approach of reinstall causing a complete 'fresh
install' of the config, which indeed might sound a bit better.

Let's get this sponsored!

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

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

[Touch-packages] [Bug 1779582] Re: Unable to create unpriviledged container

[Alex Garel]

I close it for it does not happen with other name. So there should have
been a specific problem for the first vm, which maybe pre-exists in some
way.

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

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

Title:
  Unable to create unpriviledged container

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  I already have a lot of unpriviledged container initialized while on
  versions prior to 18.04.

  I normally got all necessary pieces:

  $ cat /etc/subuid
  alex:165536:65536
  $ cat /etc/subgid
  alex:165536:65536
  $ cat .config/lxc/default.conf 
  lxc.net.0.type = veth
  lxc.net.0.link = lxcbr0
  lxc.net.0.flags = up
  lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
  lxc.idmap = u 0 165536 65536
  lxc.idmap = g 0 165536 65536

  
  I tried to create a new container and it failed.

  $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64
  Error creating container gym

  $ cat .local/share/lxc/gym/gym.log 
  lxc-create gym 20180701213443.653 INFO lxc_confile - 
confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 
range 65536
  lxc-create gym 20180701213443.653 INFO lxc_confile - 
confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 
range 65536
  lxc-create gym 20180701213443.653 DEBUGlxc_conf - 
conf.c:chown_mapped_root:3086 - trying to chown 
"/home/alex/.local/share/lxc/gym" to 1001

  I got this:

  $ ls -ld .local/share/lxc/gym
  drwxr-xr-x 2 165536 alex 4096 juil.  1 22:34 .local/share/lxc/gym

  So I don't know where it's failing and why !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lxc 3.0.1-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul  1 22:36:11 2018
  InstallationDate: Installed on 2015-11-10 (964 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  KernLog:
   
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago)
  defaults.conf:
   lxc.net.0.type = veth
   lxc.net.0.link = lxcbr0
   lxc.net.0.flags = up
   lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1779582] Re: Unable to create unpriviledged container

[Alex Garel]

Here it is !

But

1. at the time being a container named gym already exist (for I used
lxc-copy to create it)

So I tried:

$ lxc-create -n gym2 -o lxc.debug -l DEBUG -t download -- -d ubuntu -r
xenial -a amd64

and to my surprise it worked.

So there might have been something specific to the "gym" folder and I
propose to close the ticket !

** Attachment added: "lxc.debug"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+attachment/5159146/+files/lxc.debug

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

Title:
  Unable to create unpriviledged container

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  I already have a lot of unpriviledged container initialized while on
  versions prior to 18.04.

  I normally got all necessary pieces:

  $ cat /etc/subuid
  alex:165536:65536
  $ cat /etc/subgid
  alex:165536:65536
  $ cat .config/lxc/default.conf 
  lxc.net.0.type = veth
  lxc.net.0.link = lxcbr0
  lxc.net.0.flags = up
  lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
  lxc.idmap = u 0 165536 65536
  lxc.idmap = g 0 165536 65536

  
  I tried to create a new container and it failed.

  $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64
  Error creating container gym

  $ cat .local/share/lxc/gym/gym.log 
  lxc-create gym 20180701213443.653 INFO lxc_confile - 
confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 
range 65536
  lxc-create gym 20180701213443.653 INFO lxc_confile - 
confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 
range 65536
  lxc-create gym 20180701213443.653 DEBUGlxc_conf - 
conf.c:chown_mapped_root:3086 - trying to chown 
"/home/alex/.local/share/lxc/gym" to 1001

  I got this:

  $ ls -ld .local/share/lxc/gym
  drwxr-xr-x 2 165536 alex 4096 juil.  1 22:34 .local/share/lxc/gym

  So I don't know where it's failing and why !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lxc 3.0.1-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul  1 22:36:11 2018
  InstallationDate: Installed on 2015-11-10 (964 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  KernLog:
   
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago)
  defaults.conf:
   lxc.net.0.type = veth
   lxc.net.0.link = lxcbr0
   lxc.net.0.flags = up
   lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Marc Deslauriers]

Hello?

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed
Status in debirf package in Ubuntu:
  Confirmed
Status in busybox source package in Bionic:
  Confirmed
Status in debirf source package in Bionic:
  New
Status in busybox source package in Cosmic:
  Confirmed
Status in debirf source package in Cosmic:
  Confirmed

Bug description:
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

[Robie Basak]

Thank you for taking the time to file this patch and helping to make
Ubuntu better.

Does this apply and work correctly on the current Ubuntu development
release (Cosmic) please? We land changes there first and only once
successful consider backporting to existing releases as appropriate.

> With this change I was able to build a image using "MODULES=dep" and
successfully create a crash dump with zfs on root.

What sort of block device was backing your filesystem in your test case
please? I'm not particularly familiar with this part of initramfs-tools,
but it seems to me that essentials like the loading of the virtio_pci
module would be short-circuited by your patch. Do you have an opinion on
this?

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  
  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
  debugfs on /sys/kernel/debug type debugfs (rw,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
  rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl)
  rpool/srv on /srv type zfs (rw,noatime,xattr,noacl)
  

[Touch-packages] [Bug 1779582] Re: Unable to create unpriviledged container

[Stéphane Graber]

Can you run:
  lxc-create -n gym -o lxc.debug -l DEBUG -t download -- -d ubuntu -r xenial -a 
amd64

And attach the "lxc.debug" file?

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

Title:
  Unable to create unpriviledged container

Status in lxc package in Ubuntu:
  New

Bug description:
  I already have a lot of unpriviledged container initialized while on
  versions prior to 18.04.

  I normally got all necessary pieces:

  $ cat /etc/subuid
  alex:165536:65536
  $ cat /etc/subgid
  alex:165536:65536
  $ cat .config/lxc/default.conf 
  lxc.net.0.type = veth
  lxc.net.0.link = lxcbr0
  lxc.net.0.flags = up
  lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
  lxc.idmap = u 0 165536 65536
  lxc.idmap = g 0 165536 65536

  
  I tried to create a new container and it failed.

  $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64
  Error creating container gym

  $ cat .local/share/lxc/gym/gym.log 
  lxc-create gym 20180701213443.653 INFO lxc_confile - 
confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 
range 65536
  lxc-create gym 20180701213443.653 INFO lxc_confile - 
confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 
range 65536
  lxc-create gym 20180701213443.653 DEBUGlxc_conf - 
conf.c:chown_mapped_root:3086 - trying to chown 
"/home/alex/.local/share/lxc/gym" to 1001

  I got this:

  $ ls -ld .local/share/lxc/gym
  drwxr-xr-x 2 165536 alex 4096 juil.  1 22:34 .local/share/lxc/gym

  So I don't know where it's failing and why !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lxc 3.0.1-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul  1 22:36:11 2018
  InstallationDate: Installed on 2015-11-10 (964 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  KernLog:
   
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago)
  defaults.conf:
   lxc.net.0.type = veth
   lxc.net.0.link = lxcbr0
   lxc.net.0.flags = up
   lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

[Will Cooke]

We will get this fix as part of the next stable updated.


** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing

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

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1773334/+subscriptions

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Dimitri John Ledkov ]

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

** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov  (xnox)

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Benjamin Drung]

Full log output:

root@ubuntu:~# SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Bus n/a: changing state UNSET → OPENING
Bus n/a: changing state OPENING → AUTHENTICATING
Failed to open configuration file '/etc/systemd/networkd.conf': No such file or 
directory
timestamp of '/etc/systemd/network' changed
timestamp of '/run/systemd/network' changed
Ignoring /run/systemd/network/10-netplan-all.network, because it's not a 
regular file with suffix .netdev.
Ignoring /lib/systemd/network/80-container-vz.network, because it's not a 
regular file with suffix .netdev.
Ignoring /lib/systemd/network/80-container-ve.network, because it's not a 
regular file with suffix .netdev.
Ignoring /lib/systemd/network/80-container-host0.network, because it's not a 
regular file with suffix .netdev.
Ignoring /lib/systemd/network/99-default.link, because it's not a regular file 
with suffix .netdev.
Ignoring /lib/systemd/network/99-default.link, because it's not a regular file 
with suffix .network.
ens6: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
ens6: Link 2 added
ens6: udev initialized link
ens6: Saved original MTU: 64000
lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
lo: Link 1 added
lo: udev initialized link
lo: Saved original MTU: 0
ens6: Adding address: fe80::1:71ff:fe8f:cc72/64 (valid forever)
ens6: Gained IPv6LL
lo: Adding address: ::1/128 (valid forever)
lo: Adding address: 127.0.0.1/8 (valid forever)
rtnl: received address with invalid family 129, ignoring
Enumeration completed
Bus n/a: changing state AUTHENTICATING → HELLO
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName 
cookie=2 reply_cookie=0 signature=su error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch 
cookie=3 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_32 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=4 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_31 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_32 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=6 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=7 reply_cookie=0 signature=sa{sv}as 
error-name=n/a error-message=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.46 
path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s 
error-name=n/a error-message=n/a
Bus n/a: changing state HELLO → RUNNING
ens6: Link state is up-to-date
lo: Link does not request DHCPv6 prefix delegation
LLDP: Started LLDP client
ens6: Started LLDP.
ens6: Acquiring DHCPv4 lease
DHCP CLIENT (0x33b0d848): STARTED on ifindex 2
ens6: Discovering IPv6 routers
NDISC: Started IPv6 Router Solicitation client
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_32 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=8 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_32 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=9 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_32 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
NDISC: Sent Router Solicitation, next solicitation in 4s
DHCP CLIENT (0x33b0d848): DISCOVER
DHCP CLIENT (0x33b0d848): received lease lacks address, server address or lease 
lifetime, ignoring
Got message type=signal sender=org.freedesktop.DBus.Local destination=n/a 
path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local 
member=Connected cookie=4294967295 reply_cookie=0 signature=n/a error-name=n/a 
error-message=n/a
Got message type=signal sender=org.freedesktop.DBus destination=:1.46 

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Benjamin Drung]

$ sudo env SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
[...]
DHCP CLIENT (0x...): received lease lacks address, server address or lease 
lifetime, ignoring

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

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

[Colin Underhill]

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Colin Underhill (daisybank)

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

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

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

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

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

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

[Marc Peña]

I've been using e2fsprogs-xenial from Simon PPA for a month without
issues so far.

I'm using the an external drive for journal an this options in my fstab
for the volume:

errors=remount-
ro,data=journal,journal_async_commit,nobarrier,commit=60,noatime 0

Thanks for this!

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

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

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Benjamin Drung]

Setting 'dhcp-identifier: mac' (translates to networkd
'ClientIdentifier=mac' option) makes no difference. One specialty is
that the subnet-mask is 255.255.255.255 (i.e. /32).

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1779853] Re: package resolvconf (not installed) failed to install/upgrade: package resolvconf is not ready for configuration cannot configure (current status 'half-installed')

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package resolvconf (not installed) failed to install/upgrade: package
  resolvconf is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Was trying to install this in order to get openvpn client working.
  Ultimately I think I resolved this but every time I start up the machine it 
requests that I report this bug - so I did.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Mon Jul  2 09:18:15 2018
  DuplicateSignature:
   package:resolvconf:(not installed)
   Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ...
   dpkg: error processing package resolvconf (--configure):
package resolvconf is not ready for configuration
  ErrorMessage: package resolvconf is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-06-02 (31 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: resolvconf
  Title: package resolvconf (not installed) failed to install/upgrade: package 
resolvconf is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: 
2011-07-27T03:21:01
  mtime.conffile..etc.network.if-down.d.resolvconf: 2011-07-25T16:26:15
  mtime.conffile..etc.network.if-up.d.000resolvconf: 2011-07-25T16:26:15
  mtime.conffile..etc.ppp.ip-down.d.000resolvconf: 2011-07-25T16:26:15
  mtime.conffile..etc.ppp.ip-up.d.000resolvconf: 2011-07-25T16:26:15

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

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

[Touch-packages] [Bug 1779853] [NEW] package resolvconf (not installed) failed to install/upgrade: package resolvconf is not ready for configuration cannot configure (current status 'half-installed')

[Jeffrey L Sussman]

Public bug reported:

Was trying to install this in order to get openvpn client working.
Ultimately I think I resolved this but every time I start up the machine it 
requests that I report this bug - so I did.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf (not installed)
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Mon Jul  2 09:18:15 2018
DuplicateSignature:
 package:resolvconf:(not installed)
 Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ...
 dpkg: error processing package resolvconf (--configure):
  package resolvconf is not ready for configuration
ErrorMessage: package resolvconf is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2018-06-02 (31 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: resolvconf
Title: package resolvconf (not installed) failed to install/upgrade: package 
resolvconf is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: 2011-07-27T03:21:01
mtime.conffile..etc.network.if-down.d.resolvconf: 2011-07-25T16:26:15
mtime.conffile..etc.network.if-up.d.000resolvconf: 2011-07-25T16:26:15
mtime.conffile..etc.ppp.ip-down.d.000resolvconf: 2011-07-25T16:26:15
mtime.conffile..etc.ppp.ip-up.d.000resolvconf: 2011-07-25T16:26:15

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


** Tags: apport-package i386 xenial

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

Title:
  package resolvconf (not installed) failed to install/upgrade: package
  resolvconf is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Was trying to install this in order to get openvpn client working.
  Ultimately I think I resolved this but every time I start up the machine it 
requests that I report this bug - so I did.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Mon Jul  2 09:18:15 2018
  DuplicateSignature:
   package:resolvconf:(not installed)
   Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ...
   dpkg: error processing package resolvconf (--configure):
package resolvconf is not ready for configuration
  ErrorMessage: package resolvconf is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-06-02 (31 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: resolvconf
  Title: package resolvconf (not installed) failed to install/upgrade: package 
resolvconf is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: 
2011-07-27T03:21:01
  mtime.conffile..etc.network.if-down.d.resolvconf: 2011-07-25T16:26:15
  mtime.conffile..etc.network.if-up.d.000resolvconf: 2011-07-25T16:26:15
  mtime.conffile..etc.ppp.ip-down.d.000resolvconf: 2011-07-25T16:26:15
  mtime.conffile..etc.ppp.ip-up.d.000resolvconf: 2011-07-25T16:26:15

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

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

[Touch-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support

[Timo Aaltonen]

I finally received the WHL test machine, and can confirm that things are
working fine with xenial-proposed

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

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

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

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Dimitri John Ledkov ]

The dhclient lease looks ok. It has a largish MTU, but that should be
fine.

Does the dhcp server in question require MAC based client identifiers?

Could you please try:

network:
  version: 2
  renderer: networkd
  ethernets:
all:
  match:
name: ens*
  dhcp4: yes
  dhcp-identifier: mac

Note the additional 'dhcp-identifier: mac' key.


Failing that, a package capture using wireshark inside the guest would be 
needed; under systemd-networkd, and again under dhclient. Packet capture should 
reveal what sort of things systemd-networkd is doing different to dhclient.

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Benjamin Drung]

/run/systemd/netif/leases is empty

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Daniel van Vugt]

Great, thanks.

The next step is for someone (a developer probably) to diff the kernel
source between 4.14.52 and 4.15-rc1 and look for relevant changes.

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Daniel van Vugt]

Yes, the binary package is named "i965-va-driver". It is built from
source package "intel-vaapi-driver".

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   

[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Timo Aaltonen]

i965-va-driver is the binary package name, built from intel-vaapi-driver
sources

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Dimitri John Ledkov ]

Ok, i must be mistaken about empty match stuff then.

This does look odd.

systemd-networkd should have forked, to run its own dhcp client
implementation. And there should be state data in /run/systemd/netif/
e.g. /leases/ folder should have a lease.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Russell Jones]

I can't find this package with "apt search intel-vaapi-driver". Is it
renamed to i965-va-driver?

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Vasilis]

This is what I am running right now (v4.15-rc1) and the keyboard is reporting 0%
 
Linux pceet070.cern.ch 4.15.0-041500rc1-generic #201711262030 SMP Mon Nov 27 
01:32:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Benjamin Drung]

Just checked the initial configuration:

```
root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
all:
  match: {}
  dhcp4: yes
root@ubuntu:~# networkctl
IDX LINK  TYPE OPERATIONAL SETUP
  1 loloopback carrier configured
  2 ens6  etherdegradedconfiguring

2 links listed.
```

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Benjamin Drung]

My interpretation of the documentation was that an empty match entry
matches everything. I changed the configuration to enforce the matching
and it still fails:

```
root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml  
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
all:
  match:
name: ens*
  dhcp4: yes
root@ubuntu:~# networkctl 
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 ens6 ether  degradedconfiguring

2 links listed.
root@ubuntu:~# networkctl status ens6
* 2: ens6
   Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-all.network
Type: ether
   State: degraded (configuring)
Path: pci-:00:06.0
  Driver: virtio_net
  Vendor: Red Hat, Inc.
   Model: Virtio network device
  HW Address: 02:01:71:8f:cc:72
 Address: fe80::1:71ff:fe8f:cc72
root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network
[Match]
Name=ens*

[Network]
DHCP=ipv4

[DHCP]
UseMTU=true
RouteMetric=100
root@ubuntu:~# journalctl -u systemd-networkd
Jul 03 08:52:33 ubuntu systemd[1]: Starting Network Service...
Jul 03 08:52:33 ubuntu systemd-networkd[447]: Enumeration completed
Jul 03 08:52:33 ubuntu systemd[1]: Started Network Service.
Jul 03 08:52:33 ubuntu systemd-networkd[447]: lo: Link is not managed by us
Jul 03 08:52:33 ubuntu systemd-networkd[447]: ens6: IPv6 successfully enabled
Jul 03 08:52:33 ubuntu systemd-networkd[447]: ens6: Gained carrier
Jul 03 08:52:35 ubuntu systemd-networkd[447]: ens6: Gained IPv6LL
```

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1729357]

[Mvetter]

I think this can be closed.

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

Title:
  unprivileged user can drop supplementary groups

Status in shadow package in Ubuntu:
  Confirmed
Status in shadow package in openSUSE:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04.3 LTS
  Kernel: 4.4.0-97-generic
  uidmap package version: 1:4.2-3.1ubuntu5.3

  The newgidmap setuid executable allows any user to write a single
  mapping line to the gid_map of a process whose identity is the same as
  the calling process, as long as that mapping line maps the process's
  own GID outside of the user namespace to GID 0 inside the user
  namespace.

  Newgidmap will write the mapping regardless of the content of
  /proc/$process_being_mapped/setgroups, which will initially contain
  the string "allow". After this mapping is performed, and also after
  the process' uid_map is written with newuidmap, the process in the
  user namespace will be able to use the setgroups system call to drop
  supplementary groups.

  This is possible even if there is no entry for the user in
  /etc/subgid, because no subordinate GIDs are actually being used.

  This allows any user to circumvent the use of supplementary groups as
  blacklists, e.g. for some file owned by root:blacklist with permission
  bits 0604 (octal). Normally any process whose identity included the
  group "blacklist" in its supplementary groups would not be able to
  read that file. By performing this exploit using newgidmap, they can
  drop all supplementary groups and read that file.

  If newgidmap was not available, unprivileged users would not be able
  to write a process's gid_map until writing "deny" to
  /proc/$pid/setgroups. A fix for this might be for newgidmap to check
  the content of /proc/$process_being_mapped/setgroups is "deny", but we
  have not tried to patch this ourselves.

  An example using 2 login shells for a user named "someone" on Ubuntu
  Xenial, with the uidmap package installed:

  Shell 1

  someone@ubuntu-xenial:~$ id
  uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted)

  someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict
  -rwr-- 1 root restricted 8 Nov  1 12:23 /tmp/should_restrict

  someone@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  someone@ubuntu-xenial:~$ unshare -U --setgroups allow #
  /proc/self/setgroups already contains 'allow', but let's be explicit

  nobody@ubuntu-xenial:~$ echo $$
  1878

  Shell 2

  someone@ubuntu-xenial:~$ cat /etc/subuid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  someone@ubuntu-xenial:~$ cat /etc/subgid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  # There are no entries in /etc/sub{u,g}id for someone, but this
  doesn't matter that much as subordinate IDs are not being requested.

  someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1

  someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1

  Back to shell 1

  nobody@ubuntu-xenial:~$ id
  uid=0(root) gid=0(root) groups=0(root),65534(nogroup)

  # The presence of the "nogroup" supplementary group indicates that
  some unmapped GIDs are present as supplementary GIDs. The kernel knows
  that this process still has "restricted" in its supplementary groups,
  so it can't read the restricted file yet.

  nobody@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  # The process has gained CAP_SETGID in its user namespace by becoming
  UID 0. /proc/$pid/setgroups contains "allow", so it can call
  setgroups(2). By su-ing to root (itself, in the user namespace), it
  can drop the supplementary groups. It can't read /root/.bashrc as that
  file is owned by UID 0 in the initial user namespace, which creates
  some distracting error output but doesn't matter in this case.

  nobody@ubuntu-xenial:~$ su root
  su: Authentication failure
  (Ignored)
  bash: /root/.bashrc: Permission denied

  # Supplementary groups have been dropped

  root@ubuntu-xenial:~# id
  uid=0(root) gid=0(root) groups=0(root)

  # It can read the restricted file

  root@ubuntu-xenial:~# cat /tmp/should_restrict
  content

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

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

[Touch-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial

[Ubuntu Foundations Team Bug Bot]

The attachment "proposed-fix-1771764-1771783.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  iproute2: unable to add ip lwt mpls route on xenial

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  The following command does not work:

  $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
  Error: "nexthop" or end of line is expected instead of "encap"

  In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
  $ ip -V
  ip utility, iproute2-ss151103

  =>
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

  With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
  $ modprobe mpls_iptunnel
  $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
  $ ./ip/ip r
  [snip]
  10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

  At least, this patch is missing:
  1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

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

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

[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

Status in OEM Priority Project:
  Triaged
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * It should be possible to change DRM driver without rebooting.
   * It should be possible to correctly suspend & resume, whilst preserving 
driver state.
   * This bug is for userspace/logind fixes, required to get above working.
   * Related kernel change is 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658
   * 
https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59

  [Test Case]

   * Test and verify that on machines with Nvidia discrete graphics, one
  can change performance/power-saving modes without rebooting.

  [Regression Potential]

   * There are changes to the fd handling that are passed to logind. At
  worst, fd to the NVIDIA driver will still be held, and thus one would
  continue to not be able to switch graphics modes without rebooting.

  [Other Info]
   
   * original bug report:

  refer to https://github.com/systemd/systemd/issues/6908

  we need that solution to make NVIDIA dGPU switching works.

  impacted issue:
  https://bugs.launchpad.net/somerville/+bug/1774326

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

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

[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd

[Sebastien Bacher]

looks like that has been uploaded? unsubscribing the sponsors

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

Title:
  [SRU] debhelper support override from /etc/tmpfiles.d for systemd

Status in debhelper:
  Fix Released
Status in debhelper package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in debhelper source package in Xenial:
  Won't Fix
Status in rsyslog source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Confirmed
Status in debhelper source package in Artful:
  Won't Fix
Status in rsyslog source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Confirmed
Status in debhelper source package in Bionic:
  Won't Fix
Status in rsyslog source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  /var/log's Permission is going back to 755
  after upgrading systemd
  if there are rsyslog's configuration on /var/lib/tmpfiles.d/

  Affected X, A, B, C

  This is because rsyslog's pkg has 00rsyslog.conf and copied it on 
/var/lib/tmpfiles.d/ when it is installing.
  after upgrading systemd, systemd only refresh it's own tmpfiles so disappear 
conf for 00rsyslog.conf ( it doesn't remove file itself )
  so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back 
permission to 775

  [Test Case]

  1. deploy 16.04 vm
  2. check ll /var (775)
  3. apt install --reinstall systemd
  4. check ll /var (755)

  [Regression Potential]
  This fix changes debhelper's override process by using absolute path to 
filename. so if the other pkgs using debhelper e.g systemd are there, It should 
be re-build with new debhelper after patching in theory, now only systemd is 
affected. but building is not affected. also, pkg like rsyslog which is using 
systemd's tmpfile system need to be changed to use 
/etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 
00rsyslog.conf.

  [Others]

  For this issue, need to fix below pkgs

  debhelper
  systemd ( rebuilding with new debhelper is needed )
  rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, 
to support override supported by debhelper )

  [Original description]

  Upgrading or reinstalling the systemd package when using rsyslogd
  results in bad permissions (0755 instead of 0775) being set on
  /var/log/. As a consequence of this, rsyslogd can no longer create new
  files within this directory, resulting in lost log messages.

  The default configuration of rsyslogd provided by Ubuntu runs the
  daemon as syslog:syslog and sets ownership of /var/log to syslog:adm
  with mode 0775.

  Systemd's default tmpfiles configuration sets /var/log to 0755 in
  /usr/lib/tmpfiles.d/var.conf, however this is overridden in
  /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package
  rsyslog.

  It looks as though an upgrade of the systemd package fails to take
  /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated
  below. This results in /var/log receiving mode 0755 instead of the
  expected 0775:

  nick @ log2.be1.ams1:~ $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  nick @ log2.be1.ams1:~ $ apt policy systemd
  systemd:
    Installed: 229-4ubuntu21.1
    Candidate: 229-4ubuntu21.1
    Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  nick @ log2.be1.ams1:~ $ apt policy rsyslog
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf
  d /var/log 0755 - - -
  f /var/log/wtmp 0664 root utmp -
  f /var/log/btmp 0600 root utmp -

  nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf
  # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by
  # the syslog group, so that rsyslog can run as user.
  # See tmpfiles.d(5) for details.

  # Type PathMode UID  GID  Age Argument
  d /var/log 0775 root syslog -

  nick @ log2.be1.ams1:~ $ ls -ld /var/log
  drwxrwxr-x 8 root syslog 4096 Feb  7 13:45 /var/log

  nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 

[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)

[Sebastien Bacher]

Subscribing the security team to get their input since that changes the
apparmor profile

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  Confirmed

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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

[Touch-packages] [Bug 1770839] Re: Syncevolution does not run in Ubuntu 18.04

[Sebastien Bacher]

there is nothing to sponsor there, unsubscribing the sponsors

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

Title:
  Syncevolution does not run in Ubuntu 18.04

Status in syncevolution package in Ubuntu:
  Confirmed

Bug description:
  There is a problem with the package syncevolution (1.5.3-1ubuntu2) in
  Ubuntu 18.04 :

  Step to reproduce:
  >$ sudo apt install syncevolution

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les paquets supplémentaires suivants seront installés : 
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution-common syncevolution-libs syncevolution-libs-gnome
  Les NOUVEAUX paquets suivants seront installés :
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution syncevolution-common syncevolution-libs syncevolution-libs-gnome
  0 mis à jour, 9 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 2'230 ko dans les archives.
  Après cette opération, 10.2 Mo d'espace disque supplémentaires seront 
utilisés.
  Souhaitez-vous continuer ? [O/n] O
  [...]
  Paramétrage de syncevolution (1.5.3-1ubuntu2) ...
  [...]

  > $ syncevolution --version
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-peers
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-config
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  Please note that this bug semms corrected in a new release of syncevolution :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043

  Would it be possible to have the corrected verion in Ubuntu 18.04 ?

  Thanks in advance for your help

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

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

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  Triaged
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

[Touch-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support

[Timo Aaltonen]

server is in proposed, just need to handle tracking manually

** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

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

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

[Touch-packages] [Bug 1710132] Re: setxkbmap combo keys are broken after dist-upgrade to 16.04.3

[Launchpad Bug Tracker]

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

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

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

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

Title:
  setxkbmap combo keys are broken after dist-upgrade to 16.04.3

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using next configuration:

  setxkbmap -layout '' -option 
  setxkbmap -layout 'us,ru' -option 'grp:ctrl_shift_toggle'

  with awesome wm. When system was upgraded to 16.04.3, Ctrl+Shift
  started to prevent working any more keys in combination
  (Ctrl+Shift+Tab, for example).

  I guess Ctrl+Shift now reacts on keypress, not on release.

  I also used clean virtualbox to reproduce this bug. In 16.04.3 without
  dist-upgrade all works OK. But after dist-upgrade Ctrl+Shift is
  broken.

  These packages are installed during dist-upgrade:

  elwood@elwood-VirtualBox:~$ sudo apt-get dist-upgrade 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following package was automatically installed and is no longer required:
snap-confine
  Use 'sudo apt autoremove' to remove it.
  The following NEW packages will be installed:
libcapnp-0.5.3 libinput-bin libllvm4.0 libmircommon7 libmircore1 libxfont2 
linux-headers-4.10.0-32 linux-headers-4.10.0-32-generic 
linux-image-4.10.0-32-generic linux-image-extra-4.10.0-32-generic
xserver-xorg-legacy-hwe-16.04
  The following packages will be upgraded:
libegl1-mesa libgbm1 libgl1-mesa-dri libinput10 libmirclient9 
libwayland-egl1-mesa libxatracker2 linux-generic-hwe-16.04 
linux-headers-generic-hwe-16.04 linux-image-generic-hwe-16.04
xserver-xorg-core-hwe-16.04 xserver-xorg-hwe-16.04 
xserver-xorg-input-evdev-hwe-16.04 xserver-xorg-input-synaptics-hwe-16.04 
xserver-xorg-input-wacom-hwe-16.04 xserver-xorg-video-amdgpu-hwe-16.04
xserver-xorg-video-ati-hwe-16.04 xserver-xorg-video-fbdev-hwe-16.04 
xserver-xorg-video-intel-hwe-16.04 xserver-xorg-video-nouveau-hwe-16.04 
xserver-xorg-video-qxl-hwe-16.04
xserver-xorg-video-radeon-hwe-16.04 xserver-xorg-video-vesa-hwe-16.04 
xserver-xorg-video-vmware-hwe-16.04
  24 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
  Need to get 83,1 MB of archives.
  After this operation, 368 MB of additional disk space will be used.
  Do you want to continue? [Y/n]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 11 12:56:22 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.10.0-30-generic, x86_64: installed
   virtualbox, 5.0.40, 4.10.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb]
  InstallationDate: Installed on 2017-07-06 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Latitude E7440
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=14e49ffe-990e-4b72-8546-b902fc8c2bc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Steve Langasek]

Hello Mario, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  New
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Steve Langasek]

Hello Dmitriy, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd

[Steve Langasek]

Hello Nick, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  [SRU] debhelper support override from /etc/tmpfiles.d for systemd

Status in debhelper:
  Fix Released
Status in debhelper package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in debhelper source package in Xenial:
  Won't Fix
Status in rsyslog source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Confirmed
Status in debhelper source package in Artful:
  Won't Fix
Status in rsyslog source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Confirmed
Status in debhelper source package in Bionic:
  Won't Fix
Status in rsyslog source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  /var/log's Permission is going back to 755
  after upgrading systemd
  if there are rsyslog's configuration on /var/lib/tmpfiles.d/

  Affected X, A, B, C

  This is because rsyslog's pkg has 00rsyslog.conf and copied it on 
/var/lib/tmpfiles.d/ when it is installing.
  after upgrading systemd, systemd only refresh it's own tmpfiles so disappear 
conf for 00rsyslog.conf ( it doesn't remove file itself )
  so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back 
permission to 775

  [Test Case]

  1. deploy 16.04 vm
  2. check ll /var (775)
  3. apt install --reinstall systemd
  4. check ll /var (755)

  [Regression Potential]
  This fix changes debhelper's override process by using absolute path to 
filename. so if the other pkgs using debhelper e.g systemd are there, It should 
be re-build with new debhelper after patching in theory, now only systemd is 
affected. but building is not affected. also, pkg like rsyslog which is using 
systemd's tmpfile system need to be changed to use 
/etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 
00rsyslog.conf.

  [Others]

  For this issue, need to fix below pkgs

  debhelper
  systemd ( rebuilding with new debhelper is needed )
  rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, 
to support override supported by debhelper )

  [Original description]

  Upgrading or reinstalling the systemd package when using rsyslogd
  results in bad permissions (0755 instead of 0775) being set on
  /var/log/. As a consequence of this, rsyslogd can no longer create new
  files within this directory, resulting in lost log messages.

  The default configuration of rsyslogd provided by Ubuntu runs the
  daemon as syslog:syslog and sets ownership of /var/log to syslog:adm
  with mode 0775.

  Systemd's default tmpfiles configuration sets /var/log to 0755 in
  /usr/lib/tmpfiles.d/var.conf, however this is overridden in
  /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package
  rsyslog.

  It looks as though an upgrade of the systemd package fails to take
  /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated
  below. This results in /var/log receiving mode 0755 instead of the
  expected 0775:

  nick @ log2.be1.ams1:~ $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  nick @ log2.be1.ams1:~ $ apt policy systemd
  systemd:
    Installed: 229-4ubuntu21.1
    Candidate: 229-4ubuntu21.1
    Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 

[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

[Steve Langasek]

Hello Alex, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

Status in OEM Priority Project:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * It should be possible to change DRM driver without rebooting.
   * It should be possible to correctly suspend & resume, whilst preserving 
driver state.
   * This bug is for userspace/logind fixes, required to get above working.
   * Related kernel change is 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658
   * 
https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59

  [Test Case]

   * Test and verify that on machines with Nvidia discrete graphics, one
  can change performance/power-saving modes without rebooting.

  [Regression Potential]

   * There are changes to the fd handling that are passed to logind. At
  worst, fd to the NVIDIA driver will still be held, and thus one would
  continue to not be able to switch graphics modes without rebooting.

  [Other Info]
   
   * original bug report:

  refer to https://github.com/systemd/systemd/issues/6908

  we need that solution to make NVIDIA dGPU switching works.

  impacted issue:
  https://bugs.launchpad.net/somerville/+bug/1774326

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

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

[Touch-packages] [Bug 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

[Steve Langasek]

Hello Julian, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

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

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Steve Langasek]

Hello Pete, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)

[Steve Langasek]

Hello dana, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

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

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

Title:
  systemd sometimes misdetects Xen VMs (fixed up-stream)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * XEN virtualization missidentified as hyperv
   * This may cause units limited to a virtualisation not to be started; or 
redundant units for the other type of virtualisation to be started instead.
   * Previously xen & hyper-v were detected correctly separately, even when xen 
emulates/suggests that it is hyper-v.

  [Test Case]

   * Execute systemd-detect-virt and check that it detects Xen & Hyperv

  [Regression Potential]

   * Things that "fake" xen might not work as the detection code
  branches are changed, but it would affect previous releases and future
  releases of systemd-detect-virt. So far such things are not known to
  exist, and if such things appear in the future support for them would
  need to land upstream first.

  [Other Info]
   
   * Original bug report

  Cherrypick
  
https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a

  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this
  CPUID information when detecting Xen, and thus it erroneously assumes
  that the guest is running under Hyper-V. This causes Xen-related
  services (and anything else that relies on systemd's VM-detection
  functionality) to fail.

  I *believe* this is a regression from systemd 229 as used in Xenial —
  we have at least a few Xen-based VMs that report as Hyper-V via CPUID
  and don't have this issue on that version — but i haven't confirmed
  that for certain.

  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:

  https://github.com/systemd/systemd/issues/8844

  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.

  Thanks!

  See also:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573

  ---

  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  % apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10
    Candidate: 237-3ubuntu10
    Version table:
   *** 237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1779690] Re: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127

[Julian Andres Klode]

The system seems to be in a broken state. awk is pseudo-essential, as
base-files depends on it, so it should not be (possible to) removed
(it).

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

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

Title:
  package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 127

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Prompt to send bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1441 F pulseaudio
eric   2355 F pulseaudio
  Date: Mon Jul  2 07:10:03 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  InstallationDate: Installed on 2018-04-27 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f3:24c6 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 04f2:b59c Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Q534UXK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=272c1568-fcce-4cb1-829d-2fb04fdcdd33 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: apt
  Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q534UXK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q534UXK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ534UXK.304:bd12/05/2016:svnASUSTeKCOMPUTERINC.:pnQ534UXK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ534UXK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: Q
  dmi.product.name: Q534UXK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1768610] Update Released

[Steve Langasek]

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

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  In Progress
Status in nux source package in Bionic:
  Fix Released
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Launchpad Bug Tracker]

This bug was fixed in the package nux - 4.0.8+18.04.20180613.5-0ubuntu1

---
nux (4.0.8+18.04.20180613.5-0ubuntu1) bionic; urgency=medium

  * debian/50_check_unity_support:
- various changes to fix (LP: #1768610):
  + export LIBGL_ALWAYS_SOFTWARE=1 only on command failure
  + run only when called inside an unity session

 -- Marco Trevisan (Treviño)   Wed, 13 Jun 2018 12:20:33
+

** Changed in: nux (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  In Progress
Status in nux source package in Bionic:
  Fix Released
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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