[Touch-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4/

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Touch-packages] [Bug 1852010] Re: Progress bar in the XFCE panel generates high CPU usage

[Daniel van Vugt]

Also, please run:

apport-collect 1852010

on the affected machine.

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

Title:
  Progress bar in the XFCE panel generates high CPU usage

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Using GTK3 progress bars with either Radiance or Ambiance Themes generates 
high CPU usage which is weird.
  To reproduce the effect, I suggest to use xfce4-genmon-plugin calling a 
simple script with just the two following lines:

  echo "10%"
  #echo "10"

  And to alternatively toggle the comment while monitoring CPU load. A clear 
offset should appear.
  Using any other GTK3 theme do not generate this increase of CPU usage.

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

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

[Touch-packages] [Bug 1852010] Re: Progress bar in the XFCE panel generates high CPU usage

[Daniel van Vugt]

Which process exhibits the high CPU?

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Incomplete

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

Title:
  Progress bar in the XFCE panel generates high CPU usage

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Using GTK3 progress bars with either Radiance or Ambiance Themes generates 
high CPU usage which is weird.
  To reproduce the effect, I suggest to use xfce4-genmon-plugin calling a 
simple script with just the two following lines:

  echo "10%"
  #echo "10"

  And to alternatively toggle the comment while monitoring CPU load. A clear 
offset should appear.
  Using any other GTK3 theme do not generate this increase of CPU usage.

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

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

[Touch-packages] [Bug 398293]

[Will Thompson]

We (Telepathy upstream) do not support Gabble 0.8.x any more. So, does
the bug occur with a more modern version of Gabble? If so, please attach
debug logs from Gabble as per
, and describe which
aspect of “the problem” you are referring to.

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

Title:
  Empathy does not show all contacts in google talk account

Status in telepathy-gabble:
  Unknown
Status in telepathy-gabble package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: telepathy-gabble

  When starting empathy I noticed that some of my GTalk contacts were
  not showing up there (but were in pidgin). Most of them are there, but
  a few aren't. The log in empathy has a line like this for the ones
  that are not there:

  _gabble_roster_item_update: Google roster: discarding odd contact
  [name removed]

  ProblemType: Bug
  Architecture: i386
  Date: Sat Jul 11 18:16:01 2009
  DistroRelease: Ubuntu 9.10
  Package: telepathy-gabble 0.7.30-1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
  SourcePackage: telepathy-gabble
  Uname: Linux 2.6.31-2-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/398293/+subscriptions

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

[Touch-packages] [Bug 398293]

[Gitlab-migration]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/45.

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

Title:
  Empathy does not show all contacts in google talk account

Status in telepathy-gabble:
  Unknown
Status in telepathy-gabble package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: telepathy-gabble

  When starting empathy I noticed that some of my GTalk contacts were
  not showing up there (but were in pidgin). Most of them are there, but
  a few aren't. The log in empathy has a line like this for the ones
  that are not there:

  _gabble_roster_item_update: Google roster: discarding odd contact
  [name removed]

  ProblemType: Bug
  Architecture: i386
  Date: Sat Jul 11 18:16:01 2009
  DistroRelease: Ubuntu 9.10
  Package: telepathy-gabble 0.7.30-1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
  SourcePackage: telepathy-gabble
  Uname: Linux 2.6.31-2-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/398293/+subscriptions

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

[Touch-packages] [Bug 398293]

[Daniel T.]

The problem still occurs with version 0.8.12-0ubuntu1.1 on Ubuntu Lucid
10.04 LTS.

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

Title:
  Empathy does not show all contacts in google talk account

Status in telepathy-gabble:
  Unknown
Status in telepathy-gabble package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: telepathy-gabble

  When starting empathy I noticed that some of my GTalk contacts were
  not showing up there (but were in pidgin). Most of them are there, but
  a few aren't. The log in empathy has a line like this for the ones
  that are not there:

  _gabble_roster_item_update: Google roster: discarding odd contact
  [name removed]

  ProblemType: Bug
  Architecture: i386
  Date: Sat Jul 11 18:16:01 2009
  DistroRelease: Ubuntu 9.10
  Package: telepathy-gabble 0.7.30-1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
  SourcePackage: telepathy-gabble
  Uname: Linux 2.6.31-2-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/398293/+subscriptions

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

[Touch-packages] [Bug 398293] Re: Empathy does not show all contacts in google talk account

[Bug Watch Updater]

** Changed in: telepathy-gabble
   Status: Incomplete => Unknown

** Bug watch added: gitlab.freedesktop.org/telepathy/telepathy-gabble/issues #45
   https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/45

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

Title:
  Empathy does not show all contacts in google talk account

Status in telepathy-gabble:
  Unknown
Status in telepathy-gabble package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: telepathy-gabble

  When starting empathy I noticed that some of my GTalk contacts were
  not showing up there (but were in pidgin). Most of them are there, but
  a few aren't. The log in empathy has a line like this for the ones
  that are not there:

  _gabble_roster_item_update: Google roster: discarding odd contact
  [name removed]

  ProblemType: Bug
  Architecture: i386
  Date: Sat Jul 11 18:16:01 2009
  DistroRelease: Ubuntu 9.10
  Package: telepathy-gabble 0.7.30-1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
  SourcePackage: telepathy-gabble
  Uname: Linux 2.6.31-2-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/398293/+subscriptions

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

[Touch-packages] [Bug 1852399] Re: ?

[Daniel van Vugt]

This would be a web browser bug. Which web browser are you using?

Also, please explain what the problem is in more detail.

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

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

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

Title:
  ?

Status in Ubuntu:
  Incomplete

Bug description:
  There is problem with video play on facebook

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 09:09:59 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Integrated Graphics Controller [1043:1de0]
  InstallationDate: Installed on 2019-11-10 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540NA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=0d23bb72-2da5-41a9-b4cc-6c7a100ca090 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540NA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540NA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540NA.311:bd08/22/2018:svnASUSTeKCOMPUTERINC.:pnX540NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X540NA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1854883] Re: laptop sleeps when screen clsed during shutdown

[Francis Merlino]

not sure if pm-utils or kernel itself, as the system will suspend when
lid is closed while shutting down

** Package changed: kubuntu-meta (Ubuntu) => pm-utils (Ubuntu)

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

Title:
  laptop sleeps when screen clsed during shutdown

Status in pm-utils package in Ubuntu:
  New

Bug description:
  os: Kubuntu 19.10 - fresh install, all packages up to date as of 2 December 
2019
  hardware: Thinkpad T470 i7-75000, 8GB RAM

  when the laptop is shutdown, if I close the lid before finishing
  powering down the laptop will suspend rather than shutdown. When I
  next open the lid, the laptop wakes and finishes shutting down.

  was not doing this with any release from Kubuntu 18.04 - 19.04.

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

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

[Touch-packages] [Bug 1851451] Re: Performance is not good system freeze a lot of time

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => 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/1851451

Title:
  Performance is not good system freeze a lot of time

Status in Ubuntu:
  Invalid

Bug description:
  freeze mouse and keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 20:46:07 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee]
  InstallationDate: Installed on 2019-11-04 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 064e:c346 Suyin Corp. HP TrueVision HD
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=bef4cfb0-ebad-44d4-aad1-914b2839dba4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EE
  dmi.board.vendor: HP
  dmi.board.version: 62.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: 1AP08EA#BH5
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1851334] Re: Performance is not good system freeze a lot of time

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1851451
   Performance is not good system freeze a lot of time

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

Title:
  Performance is not good system freeze a lot of time

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Performance is not good system freeze a lot of time I am new to Ubuntu
  and don't know what to do please help

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 01:16:25 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee]
  InstallationDate: Installed on 2019-11-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Notebook
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=bef4cfb0-ebad-44d4-aad1-914b2839dba4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EE
  dmi.board.vendor: HP
  dmi.board.version: 62.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: 1AP08EA#BH5
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1854883] [NEW] laptop sleeps when screen clsed during shutdown

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

os: Kubuntu 19.10 - fresh install, all packages up to date as of 2 December 2019
hardware: Thinkpad T470 i7-75000, 8GB RAM

when the laptop is shutdown, if I close the lid before finishing
powering down the laptop will suspend rather than shutdown. When I next
open the lid, the laptop wakes and finishes shutting down.

was not doing this with any release from Kubuntu 18.04 - 19.04.

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment kubuntu
-- 
laptop sleeps when screen clsed during shutdown
https://bugs.launchpad.net/bugs/1854883
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pm-utils 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 1852933] Re: Failed to read time with suspend-then-hibernate fails

[Saber Taghvaeeyan]

I get
cat: /sys/class/rtc/rtc0/since_epoch: No such file or directory.
It seems that /sys/class/rtc 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/1852933

Title:
  Failed to read time with suspend-then-hibernate fails

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd version the issue has been seen with
  237

  Used distribution
  Ubuntu 18.04

  Expected behaviour you didn't see
  Running suspend-then-hibernate service should put the machine into sleep mode 
and then hibernate after the delay set in the sleep.conf file.

  Unexpected behaviour you saw
  suspend-then-hibernate fails. The status shows:

  systemd[1]: Starting Suspend; Idle into hibernate...
  systemd-sleep[13130]: Failed to read time: -9
  systemd[1]: systemd-suspend-then-hibernate.service: Main process exited, code
  systemd[1]: systemd-suspend-then-hibernate.service: Failed with result 'exit-
  systemd[1]: Failed to start Suspend; Idle into hibernate.
  Both suspend and hibernate services work fine.

  Steps to reproduce the problem
  Running sudo systemctl suspend-then-hibernate generates the error.

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

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

[Touch-packages] [Bug 1854537] Re: When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the running

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1854536
   When I ran "update-grub" after editing the grub.conf file to have 
GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and 
displayed the running taks with the green "OK" letters next to them

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

Title:
   When I ran "update-grub" after editing the grub.conf file to have
  GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to
  black and displayed the running taks with the green "OK" letters next
  to them

Status in xorg package in Ubuntu:
  New

Bug description:
  When I ran "sudo update-grub" after changing the line in grub.conf to
  be "GRUB_CMDLINE_LINUX="nomodeset", the screen turned to black and the
  windows would not appear. I was forced to open a tty session and
  reboot.

  Expected Results:
  The command runs but the screen does not turn black until I initiate a 
shutdown/reboot

  Actual Results:
  The screen turns black and the startup tasks and status appear over a black 
background, as it would when I push the up key when ubuntu starts up.

  This issue occurred at around 3:47 PM, EDT, on November 29, 2019.

  Description: Ubuntu 18.04.3 LTS
  Release: 18.04

  mutter:
Installed: 3.28.4-0ubuntu18.04.2
Candidate: 3.28.4-0ubuntu18.04.2
Version table:
   *** 3.28.4-0ubuntu18.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Fri Nov 29 15:40:27 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro radeon.modeset=0 splash quiet 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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

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

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

[Touch-packages] [Bug 1854976] Re: systemd-resolved doesn't work with "host -l" / AXFR queries

[ghomem]

Hi,

I work with Jose Manuel Santamaria Lema.

Thank you for taking your time to review.

Perhaps we should be a little cautious in regards what we call "normal"
and "reasonable". During the last 20+ years of Linux people able were to
do "host -l" against servers that were configured to allow so - for
example internal name servers that are authoritative for local (LAN
related) domains - using directly the local resolver

I would call the ability to do such queries "normal" and "reasonable"
because it has been common practice during the last 20+ years. Yesterday
was the first time that I have seen the possibility of such queries not
working (20.04 early builds). Linux Torvalds usually says "we don't
break user space" when changes in the kernel cause problems on user
space applications that have certain expectations regarding how the
kernel behaves because tradition is some kind of jurisprudence. I feel
this is kind of the same situation.

Apart from common practice we could think of other criteria for deciding
this. For example what the RFCs say. I am by no mean a DNS authority -
please feel free to correct me if I am wrong. Digging little bit I found
this:



An AXFR query is sent by a client whenever there is a reason to ask.
   This might be because of scheduled or triggered zone maintenance
   activities (see Section 4.3.5 of RFC 1034 and DNS NOTIFY [RFC1996],
   respectively) or as a result of a command line request, say for
   debugging.



Note that it mentions debugging and that ubuntu users are not the
average computer "end users" but often a more technical crowd that uses
computers to configure and debug. Also, the document refers to
"resolvers and servers" and doesn't say AXFR queries are exclusive to
authoritative servers.

In that context, does not seek like an accident that it worked with
dnsmasq - seems the dnsmasq implemented the feature, like bind and
others do.

Reference:

https://tools.ietf.org/html/rfc5936

Lastly, I would say that the decision to downgrade or not the local
resolver should come from Ubuntu, rather than systemd. This might not be
an "end of the world" situation but still it is a regression that should
be assessed, with gains and losses from the resolver change fairly
weighted.

Thank you,

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

Title:
  systemd-resolved doesn't work with "host -l" / AXFR queries

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  some time ago network-manager in Ubuntu switched from dnsmasq to
  systemd-resolved.

  When network-manager used dnsmasq to handle DNS, one could use "host
  -l" to list all the hosts in a DNS zone, something like this:

  $ host -l mydomain.lan
  mydomain.lan name server mydns.mydomain.lan
  host1.mydomain.lan has address x.x.x.x
  host2.mydomain.lan has address x.x.x.x
  host3.mydomain.lan has address x.x.x.x
  host4.mydomain.lan has address x.x.x.x
  [...]

  That, unfortunately, no longer works since the switch to systemd-resolved, it 
always fails like this:
  $ host -l mydomain.lan
  Host mydomain.lan not found: 4(NOTIMP)
  ; Transfer failed.

  And I think that's because systemd-resolved is "filtering" the AXFR
  queries issued by "host -l" (I checked the network traffic with tcdump
  and that "NOTIMP" comes from the loopback interface).

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

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

[Touch-packages] [Bug 1843479]

[Balint Reczey]

Created attachment 12101
Patch adjusting offset honoring page alignment

In my test with the previous patch p_offset mod page_size indeed did not
match p_vaddr mod page_size. However the tested binary (gzip) worked ok,
but I see that it is not guaranteed to work everywhere.

This newer patch ensures that p_offset's alignment is kept.

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

Title:
  gzip in Ubuntu Eoan results in Exec format error on WSL1

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  In Progress
Status in gzip package in Ubuntu:
  In Progress

Bug description:
  Summary:

  Running gzip on WSL1 results in the following error:

  $ gzip
  -bash: /bin/gzip: cannot execute binary file: Exec format error

  What I expect to happen:

  gzip executes correctly on WSL1.

  What happens instead:

  gzip fails with an Exec format error.

  Notes:

  I suspect a change in how gzip is being built for Eoan is causing
  issues with ELF parsing on the WSL1 translation layer. For example:

  On Disco with gzip 1.9-3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped

  On Eoan with gzip 1.10-0ubuntu3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, 
stripped

  Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
  not believe this is an issue in 1.10 because this error does not occur
  when building gzip from GNU project source on Ubuntu Eoan.

  Justifications:

  WSL1 will need to be patched in future Windows builds for this change
  in ELF. However that patch will likely not be backported to older
  builds of Windows, including Windows Enterprise/Server 2019.

  To ensure Eoan can run on current and older builds of Windows Ubuntu
  should consider looking at how it's building gzip and see if it can be
  made to 'play nice' until WSL1 can be updated.

  This was originally reported here:
  https://github.com/microsoft/WSL/issues/4461

  Details:

  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10

  gzip:
Installed: 1.10-0ubuntu3
Candidate: 1.10-0ubuntu3
Version table:
   *** 1.10-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Dan Streetman]

> In my case, "ifconfig enp4s0" shows a line like this:
>   inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20

this is normal, when ipv6 is enabled; all interfaces get a link-local
address.

> run "host $(hostname)" and it is likely to return...the link local
inet6 address.

Your assumption that systemd-resolved will perform $(hostname)
resolution to the system's ipv6 link local addresses is wrong; it
doesn't do that, unless you've configured things that way.  If your
system does do that, something else is going on.  Can you provide a
*specific* example of what you are seeing on your system, instead of
trying to generalize your problem.

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1641417] Re: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.

[indigocat]

Hi, #3 is *still* an issue, as I can't access my iPod, which is
recognized by the USB subsystem, but file managers in general only seem
to access it via gphoto2:// protocol instead of afc:// (which seems to
be recognized as a network protocol).

Syncing files via Rhythmbox or Banshee isn't possible anymore due to this bug.
Entering afc://{devide_uuid} on any file manager allows for accessing the 
iPod's filesystem and copying the music folder manually, but this is only 
useful as a music backup procedure.

Transferring music *to* the iPod in a way that the device will recognize
is impossible, and has been so at least for the past 3 years.

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

Title:
  Ubuntu 16.04 unable to detect/connect  to and work properly with
  iPhone 4.

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  
  Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. 
  Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via 
gphoto2, where access is limited to viewing and copying photos and videos. The 
2nd connection that is mounted via afc fail to work, hence other folders in 
iPhone are not accessible.

  Action 2: Unplugged and re-plugged iPhone 4 to the workstation.
  Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount 
point appear.

  Checks and Remedy used: 
  1. "ideviceinfo" and lsusb command show iPhone 4 is connected.
  2. "idevicepair validate" command shows "SUCCESS: Validated pairing with 
device [UDID]"
  3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in 
Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 
appears and are accessible.

  I believe the 1st mounting of iPhone 4 on Nautilus is due to the
  "gvfs-backends" package. W/o it, auto detection/connection of iPhone 4
  would not occur and appear in Nautilus. However, the afc mount failed
  to work

  The 2nd mounting is caused by ifuse. This works perfectly but requires
  manual mounting and unmounting.

  
  Questions: 
  1. How to overcome issues/failures mentioned in Result 1 & 2? 
  2. Ideally, i would like the automatic detection-connection between Ubuntu 
and iPhone to work. If not, is there a way to automate connection via ifuse? 

  
  System and package info:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  $ uname -or
  4.4.0-47-generic GNU/Linux

  $ dpkg -l | grep iPhone
  ii  ifuse1.1.2-0.1build3 amd64  FUSE module for 
iPhone and iPod Touch devices
  ii  libimobiledevice-utils   1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with iPhone and iPod Touch devices
  ii  libimobiledevice6:amd64  1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with the iPhone and iPod Touch
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  usbmuxd  1.1.0-2 amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices

  $ dpkg -l | grep libusb
  ii  libgusb2:amd64   0.2.9-0ubuntu1  amd64   GLib wrapper around 
libusb1
  ii  libusb-0.1-4:amd64   2:0.1.12-28 amd64   userspace USB 
programming library
  ii  libusb-1.0-0:amd64   2:1.0.20-1  amd64   userspace USB 
programming library
  ii  libusb-1.0-0:i3862:1.0.20-1  i386userspace USB 
programming library
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  libusbredirhost1:amd64   0.7.1-1 amd64   Implementing the 
usb-host (*) side of a usbredir connection (runtime)
  ii  libusbredirparser1:amd64 0.7.1-1 amd64   Parser for the 
usbredir protocol (runtime)

  $ dpkg -l | grep gvfs
  ii  gvfs:amd64  1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - GIO module
  ii  gvfs-backends   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - backends
  ii  gvfs-bin1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - binaries
  ii  gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual 
filesystem - common data files
  ii  gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - servers
  ii  gvfs-fuse   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - fuse server
  ii  gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64  userspace 

[Touch-packages] [Bug 1855026] [NEW] package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de sal

[Andrea Velazco]

Public bug reported:

error to install package initiframes

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: initramfs-tools 0.133ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
AptOrdering:
 amd64-microcode:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Dec  3 17:21:20 2019
ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2019-11-26 (7 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package eoan

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

Title:
  package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el
  subproceso instalado paquete initramfs-tools script post-installation
  devolvió el código de salida de error 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error to install package initiframes

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  AptOrdering:
   amd64-microcode:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Dec  3 17:21:20 2019
  ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2019-11-26 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510511] Re: machinectl pull-raw fails: No space left on device

[Philip Freeman]

Apparently this will never get fixed upstream:

From
https://github.com/systemd/systemd/issues/5859#issuecomment-553377937

poettering: "So we dropped the automatic btrfs loopback file support in
machined a while back. Let's close this hence."


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

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

Title:
  machinectl pull-raw fails: No space left on device

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
  /trusty-server-cloudimg-amd64-disk1.img

  fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
  fails to complete:

  SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
  gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
  gpg: Good signature from "UEC Image Automatic Signing Key 
" [unknown]
  gpg: WARNING: Using untrusted key!
  Signature verification succeeded.
  Unpacking QCOW2 file.
  Failed to convert qcow2 image: No space left on device
  Exiting.

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

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

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

I wonder if this behaviour is not observe in Eoan because it is the
first Ubuntu release introducing the removal of lvmetad[0] (starting
v2_03_00) in favour of 'event_activation'[1] (starting v2_03_03) in
lvm2.

Seems like a lot happened between lvm2 found in disco and eoan in term
of development in the activation area.

[0]
e6be10ffd man: remove scattered lvmetad references
cbee4d3d8 man pvscan: replace lvmetad text
1c0b02e36 man: remove lvmetad
81ca0cb16 Remove init scripts related to clvm and lvmetad
07d2794a1 tests: remove lvmetad variation
b070c14a8 tests: drop lvmetad parts of system_id test
3bcc6c7e6 tests: drop lvmetad bits
97506a7e2 build: Remove lvmetad leftovers
bf4be8066 spec: Remove lvmetad
63ec42f42 tests: remove lvmetad tests
117160b27 Remove lvmetad

[1]
commit 4b5d6de86b3fd3a06b913708e477b603627c8614
Author: David Teigland 
Date: Mon Nov 26 12:49:39 2018 -0600

pvscan systemd service for event based activation

The pvscan systemd service for autoactivation was
mistakenly dropped along with the lvmetad related
services.

The activation generator program now looks at the new
lvm.conf setting "event_activation" (default 1) to
switch between event activation and direct activation.

Previously, the old use_lvmetad setting was used to
switch between event and direct activation.


commit fc482406ec4e0607a9d7335ac927c64b361cad1c
Author: Zdenek Kabelac 
Date: Thu Nov 29 23:08:05 2018 +0100

make: generate config update


conf/example.conf.in:
-   # Configuration option global/use_lvmetad.
-   # This setting is no longer used.
-   use_lvmetad = 0
+   # Configuration option global/event_activation.
+   # Activate LVs based on system-generated device events.
+   # When a device appears on the system, a system-generated event runs
+   # the pvscan command to activate LVs if the new PV completes the VG.
+   # Use auto_activation_volume_list to select which LVs should be
+   # activated from these events (the default is all.)
+   # When event_activation is disabled, the system will generally run
+   # a direct activation command to activate LVs in complete VGs.
+   event_activation = 1
 
-   # Configuration option global/lvmetad_update_wait_time.
-   # This setting is no longer used.

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Only the lv for root volume get activated, because of the grub
  parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
  --lv"

  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
  => + mountroot_status=0
  + [ ]
  + log_end_msg
  + _log_msg done.\n
  + [ n = y ]
  + printf done.\n
  done.
  + read_fstab_entry /usr
  + found=1
  + [ -f /root/etc/fstab ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = /usr ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /usr = /usr ]
  + [ -n ]
  + found=0
  + break 2
  + return 0
  + log_begin_msg Mounting /usr file system
  + _log_msg Begin: Mounting /usr file system ...

  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if
  found.

  initramfs-tools:init
  271 maybe_break mount
  272 log_begin_msg "Mounting root file system"
  273 # Always load local and nfs (since these might be needed for /etc or
  274 # /usr, irrespective of the boot script used to mount the rootfs).
  275 . /scripts/local
  276 . /scripts/nfs
  277 . /scripts/${BOOT}
  278 parse_numeric "${ROOT}"
  279 maybe_break mountroot
  280 mount_top
  281 mount_premount
  282 mountroot
  283 log_end_msg
  284
  => 285 if read_fstab_entry /usr; then
  => 286 log_begin_msg "Mounting /usr file system"
  => 287 mountfs /usr
  => 288 log_end_msg
  => 289 fi

  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr
  couldn't be mounted.

  It clearly seems to 

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

I wonder if this behaviour is not observe in Eoan because it is the
first Ubuntu release introducing the removal of lvmetad[0] (starting
v2_03_00) in favour of 'event_activation'[1] (starting v2_03_03) in
lvm2.

Seems like a lot happened between lvm2 found in disco and eoan in term
of development in the activation area.


[0]
e6be10ffd man: remove scattered lvmetad references
cbee4d3d8 man pvscan: replace lvmetad text
1c0b02e36 man: remove lvmetad
81ca0cb16 Remove init scripts related to clvm and lvmetad
07d2794a1 tests: remove lvmetad variation
b070c14a8 tests: drop lvmetad parts of system_id test
3bcc6c7e6 tests: drop lvmetad bits
97506a7e2 build: Remove lvmetad leftovers
bf4be8066 spec: Remove lvmetad
63ec42f42 tests: remove lvmetad tests
117160b27 Remove lvmetad

 
[1]
commit 4b5d6de86b3fd3a06b913708e477b603627c8614
Author: David Teigland 
Date:   Mon Nov 26 12:49:39 2018 -0600

pvscan systemd service for event based activation

The pvscan systemd service for autoactivation was
mistakenly dropped along with the lvmetad related
services.

The activation generator program now looks at the new
lvm.conf setting "event_activation" (default 1) to
switch between event activation and direct activation.

Previously, the old use_lvmetad setting was used to
switch between event and direct activation.


commit fc482406ec4e0607a9d7335ac927c64b361cad1c
Author: Zdenek Kabelac 
Date:   Thu Nov 29 23:08:05 2018 +0100

make: generate config update


conf/example.conf.in:
# Configuration option global/event_activation.
# Activate LVs based on system-generated device events.
# When a device appears on the system, a system-generated event runs
# the pvscan command to activate LVs if the new PV completes the VG.
# Use auto_activation_volume_list to select which LVs should be
# activated from these events (the default is all.)
# When event_activation is disabled, the system will generally run
# a direct activation command to activate LVs in complete VGs.
event_activation = 1

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Only the lv for root volume get activated, because of the grub
  parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
  --lv"

  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
  => + mountroot_status=0
  + [ ]
  + log_end_msg
  + _log_msg done.\n
  + [ n = y ]
  + printf done.\n
  done.
  + read_fstab_entry /usr
  + found=1
  + [ -f /root/etc/fstab ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = /usr ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /usr = /usr ]
  + [ -n ]
  + found=0
  + break 2
  + return 0
  + log_begin_msg Mounting /usr file system
  + _log_msg Begin: Mounting /usr file system ...

  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if
  found.

  initramfs-tools:init
  271 maybe_break mount
  272 log_begin_msg "Mounting root file system"
  273 # Always load local and nfs (since these might be needed for /etc or
  274 # /usr, irrespective of the boot script used to mount the rootfs).
  275 . /scripts/local
  276 . /scripts/nfs
  277 . /scripts/${BOOT}
  278 parse_numeric "${ROOT}"
  279 maybe_break mountroot
  280 mount_top
  281 mount_premount
  282 mountroot
  283 log_end_msg
  284
  => 285 if read_fstab_entry /usr; then
  => 286 log_begin_msg "Mounting /usr file system"
  => 287 mountfs /usr
  => 288 log_end_msg
  => 289 fi

  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr
  couldn't be mounted.

  It clearly seems to be an 'auto-activation' issue at boot.

  For other such as /home, /var, it's not a big deal cause they can be
  activated later on in the process and they are (I haven't check but I
  guess systemd or 

[Touch-packages] [Bug 1510511] Re: machinectl pull-raw fails: No space left on device

[Philip Freeman]

marble@bravo:~$ sudo machinectl pull-tar 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz
Enqueued transfer job 1. Press C-c to continue download in background.
Pulling 
'https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz',
 saving as 'trusty-server-cloudimg-amd64-root'.
Downloading 186.4M for 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
Downloading 253B for 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.nspawn.
HTTP request to 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.nspawn
 failed with code 404.
Settings file could not be retrieved, proceeding without.
Downloading 260B for 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.sha256.
Downloading 836B for 
https://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.gpg.
Download of https://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.gpg 
complete.
Set up default quota hierarchy for /var/lib/machines/.#tarb32b45621ce56d91.
Downloading 3.0K for https://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.
Download of https://cloud-images.ubuntu.com/trusty/current/SHA256SUMS complete.
Got 1% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 5min 33s left at 566.3K/s.
Got 2% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 3min 52s left at 804.6K/s.
Got 3% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 3min 21s left at 920.3K/s.
Got 4% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 3min 9s left at 969.1K/s.
Got 5% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 2min 57s left at 1021.9K/s.
Got 6% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 2min 49s left at 1.0M/s.
Got 7% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 2min 48s left at 1.0M/s.

Got 51% of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz.
 1min 54s left at 814.3K/s.
tar: usr/share/ca-certificates/mozilla/Staat_der_Nederlanden_Root_CA_-_G2.crt: 
Cannot open: No space left on device
tar: usr/share/ca-certificates/mozilla/OpenTrust_Root_CA_G2.crt: Cannot open: 
No space left on device
tar: usr/share/ca-certificates/mozilla/CA_Disig_Root_R1.crt: Cannot open: No 
space left on device
tar: usr/share/ca-certificates/mozilla/AddTrust_Public_Services_Root.crt: 
Cannot open: No space left on device


marble@bravo:~$ df -h
Filesystem  Size  Used Avail Use% Mounted on
udev 16G 0   16G   0% /dev
tmpfs   3.2G  1.4M  3.2G   1% /run
/dev/sda2   439G   11G  406G   3% /
tmpfs16G 0   16G   0% /dev/shm
tmpfs   5.0M 0  5.0M   0% /run/lock
tmpfs16G 0   16G   0% /sys/fs/cgroup
/dev/loop0   89M   89M 0 100% /snap/core/7270
/dev/sda1   511M  6.1M  505M   2% /boot/efi
tmpfs   3.2G 0  3.2G   0% /run/user/1000
/dev/loop1  500M  335M  130M  73% /var/lib/machines
marble@bravo:~$ sudo ls -la /var/lib/machine*
-rw--- 1 root root 524288000 Dec  4 00:20 /var/lib/machines.raw

/var/lib/machines:
total 24
drwx--  1 root root   94 Dec  4 00:16 .
drwxr-xr-x 37 root root 4096 Dec  4 00:02 ..
-rw-r--r--  1 root root  253 Dec  4 00:16 .#settings280eb06251545046
drwxr-xr-x  1 root root  152 Dec  4 00:19 .#tarb32b45621ce56d91

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

Title:
  machinectl pull-raw fails: No space left on device

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
  /trusty-server-cloudimg-amd64-disk1.img

  fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
  fails to complete:

  SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
  gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
  gpg: Good signature from "UEC Image Automatic Signing Key 
" [unknown]
  gpg: WARNING: Using untrusted key!
  Signature verification succeeded.
  Unpacking QCOW2 file.
  Failed to convert qcow2 image: No space left on device
  Exiting.

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

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

[Touch-packages] [Bug 1510511] Re: machinectl pull-raw fails: No space left on device

[Philip Freeman]

This effects me on a brand new Ubuntu Server 18.04.3 Install

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

Title:
  machinectl pull-raw fails: No space left on device

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
  /trusty-server-cloudimg-amd64-disk1.img

  fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
  fails to complete:

  SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
  gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
  gpg: Good signature from "UEC Image Automatic Signing Key 
" [unknown]
  gpg: WARNING: Using untrusted key!
  Signature verification succeeded.
  Unpacking QCOW2 file.
  Failed to convert qcow2 image: No space left on device
  Exiting.

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

If you see the bare inet6 link local address, but just can't see a problem with 
it,
then try:
$ telnet $(hostname)# some port that isn't listened on.
Trying 192.168.0.1...
Trying fe80::4687:fcff:fe9e:4ac7...
telnet: Unable to connect to remote host: Invalid argument

The symptom being here that you get "Invalid argument" instead of
"Connection refused".

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

The premis is that you have a network device with a "link local" (aka:
"scopeid 0x20") inet6 address.

In my case, "ifconfig enp4s0" shows a line like this:
   inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  scopeid 0x20

If your machine does NOT have such a line, then I must admit, I don't
know how to produce one. Mine had it from default setup.

If your machine DOES have an inet6 link local address, then (in a shell)
run "host $(hostname)" and it is likely to return an inet (ipv4) address
(that's just fine) AND the link local inet6 address.

If your "host $(hostname)" doesn't give you any inet6 address, or gives
you one with %network-name appended, then you might have a different
version of "systemd" than 237-3ubuntu10.33 (as included in 18.04)

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1855009] [NEW] autopkgtests all fail on s390x

[Dan Streetman]

Public bug reported:

[impact]

most or all autopkgtests fail on s390x

[test case]

check autopkgtest logs, e.g.
http://autopkgtest.ubuntu.com/packages/network-manager

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/s390x/n/network-
manager/20191130_001946_a5512@/log.gz

[regression potential]

TBD

** Affects: network-manager (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: network-manager (Ubuntu Xenial)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: network-manager (Ubuntu Bionic)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: network-manager (Ubuntu Disco)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: network-manager (Ubuntu Eoan)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: network-manager (Ubuntu Focal)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Changed in: network-manager (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Focal)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: network-manager (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: network-manager (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: network-manager (Ubuntu Disco)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: network-manager (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu Disco)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  In Progress
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  most or all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  [regression potential]

  TBD

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

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

[Touch-packages] [Bug 1846232] Re: networkd pads interface MTU by 4 bytes for vlan even when told not to

[Dan Streetman]

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

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

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

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

Title:
  networkd pads interface MTU by 4 bytes for vlan even when told not to

Status in curtin:
  Invalid
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  From https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-
  amd64/916/console:

  ==
  FAIL: test_ip_output (vmtests.test_network_vlan.EoanTestNetworkVlan)
  --
  Traceback (most recent call last):
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 311, in test_ip_output
  routes)
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 337, in check_interface
  int(ipcfg[key]))
  AssertionError: 1500 != 1504
   >> begin captured stdout << -
  parsed ip_a dict:
  interface0:
  broadcast: 10.245.175.255
  group: default
  inet4:
  -   address: 10.245.168.16
  prefixlen: '21'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface0
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:13
  mtu: '1500'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1:
  broadcast: 10.245.188.255
  group: default
  inet4:
  -   address: 10.245.188.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1504'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1.2667:
  broadcast: 10.245.184.255
  group: default
  inet4:
  -   address: 10.245.184.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2667
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2668:
  broadcast: 10.245.185.255
  group: default
  inet4:
  -   address: 10.245.185.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2668
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2669:
  broadcast: 10.245.186.255
  group: default
  inet4:
  -   address: 10.245.186.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2669
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2670:
  broadcast: 10.245.187.255
  group: default
  inet4:
  -   address: 10.245.187.2
  prefixlen: '24'
   

[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files

[Mauricio Faria de Oliveira]

For documentation purposes,

The systemd upload for this LP bug also resolves LP bug 1847512
(xenial: leftover scope units for Kubernetes transient mounts).

Verification steps posted on that bug.

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

Title:
  systemd-logind leaves leftover sessions and scope files

Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Scope file leakage can cause SSH delays and reduce performance in systemd

  [Description]
  The current systemd-logind version present in Xenial can leave abandoned SSH
  sessions and scope files in cases where the host sees a lot of concurrent SSH
  connections. These leftover sessions can slow down systemd performance
  greatly, and can have an impact on sshd handling a great number of concurrent
  connections.

  To fix this issue, patches are needed in both dbus and systemd. These improve 
the
  performance of the communication between dbus and systemd, so that they can
  handle a better volume of events (e.g. SSH logins). All of those patches are
  already present from Bionic onwards, so we only need those fixes for Xenial.

  == Systemd ==
  Upstream patches:
  - core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification 
(d8fdc62037b5)

  $ git describe --contains d8fdc62037b5
  v230~71^2~2

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.21 | xenial-security | source, ...
   systemd | 229-4ubuntu21.22 | xenial-updates  | source, ... <
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.29 | bionic-security | source, ...
   systemd | 237-3ubuntu10.29 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...

  == DBus ==
  Upstream patches:
  - Only read one message at a time if there are fds pending (892f084eeda0)
  - bus: Fix timeout restarts  (529600397bca)
  - DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)

  $ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
  dbus-1.11.10~44
  dbus-1.11.10~45
  dbus-1.11.16~2

  $ rmadison dbus
   dbus | 1.10.6-1ubuntu3| xenial   | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-security  | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-updates   | source, ... <
   dbus | 1.12.2-1ubuntu1| bionic   | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-security  | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-updates   | source, ...

  [Test Case]
  1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
  multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost 
sleep 1 & done

  2) Check for leaked sessions in /run/systemd/system/:
  multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
  ...

  [Regression Potential]
  As the patches change the communication socket between dbus and systemd, 
possible regressions could cause systemd to 

[Touch-packages] [Bug 1847512] Re: xenial: leftover scope units for Kubernetes transient mounts

[Mauricio Faria de Oliveira]

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

Verification done with fix for bug 1846787 on xenial-proposed (systemd
229-4ubuntu21.23).

With the new systemd packages there are no leaked scope units for
transient mounts.

cheers,
Mauricio


Setup
---

$ sudo snap install --beta --classic multipass

$ multipass launch --cpus 16 --mem 8G --disk 8G --name lp1847512 xenial

$ multipass shell lp1847512
$ sudo apt update && sudo apt -y upgrade && sudo apt -y install 
linux-generic-hwe-16.04 && sudo reboot

$ multipass shell lp1847512

$ lsb_release -cs
xenial

$ uname -rv
4.15.0-72-generic #81~16.04.1-Ubuntu SMP Tue Nov 26 16:34:21 UTC 2019

$ sudo snap install microk8s --channel=1.16/stable --classic
$ sudo snap alias microk8s.kubectl kubectl
$ sudo usermod -a -G microk8s $USER
$ newgrp microk8s

$ kubectl create secret generic secret-for-pod --from-literal=key=value

$ cat < pod-with-secret.yaml
apiVersion: v1
kind: Pod
metadata:
  name: pod-with-secret
spec:
  containers:
  - name: container
image: debian:stretch
args: ["/bin/true"]
volumeMounts:
- name: secret
  mountPath: /secret
  volumes:
  - name: secret
secret:
  secretName: secret-for-pod
  restartPolicy: Never
EOF


xenial-updates: there are leaked scope units over time. (bad)
---

$ multipass shell lp1847512

$ dpkg -s systemd | grep ^Version:
Version: 229-4ubuntu21.22

No scope units at the beginning:

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$


Test #1: leaked one unit.

$ kubectl create -f pod-with-secret.yaml

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  11s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
run-rf2ba6bb83e014123818fedcdde24ef63.scope loaded active running Kubernetes 
transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/62cea6e6-bb30-4a48-a61b-0242d10f0546/volumes/kubernetes.io~secret/secret

$ kubectl delete pods pod-with-secret
pod "pod-with-secret" deleted


Test #2: leaked zero units.

$ kubectl create -f pod-with-secret.yaml
pod/pod-with-secret created

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  5s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
run-rf2ba6bb83e014123818fedcdde24ef63.scope loaded active running Kubernetes 
transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/62cea6e6-bb30-4a48-a61b-0242d10f0546/volumes/kubernetes.io~secret/secret

$ kubectl delete pods pod-with-secret
pod "pod-with-secret" deleted


Test #3: leaked one more unit.

$ kubectl create -f pod-with-secret.yaml
pod/pod-with-secret created

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  4s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
run-r181f6242dd644256be6f8405eab60ed7.scope loaded active running Kubernetes 
transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/a35aee3e-cc0a-443c-a33d-556b94730e1e/volumes/kubernetes.io~secret/secret
run-rf2ba6bb83e014123818fedcdde24ef63.scope loaded active running Kubernetes 
transient mount for 
/var/snap/microk8s/common/var/lib/kubelet/pods/62cea6e6-bb30-4a48-a61b-0242d10f0546/volumes/kubernetes.io~secret/secret

$ kubectl delete pods pod-with-secret


Clean up the leaked units.

$ sudo systemctl stop run-r181f6242dd644256be6f8405eab60ed7.scope 
run-rf2ba6bb83e014123818fedcdde24ef63.scope
$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$ 




xenial-proposed: there are NO leaked scope units over time. (good)
---

$ echo 'deb http://archive.ubuntu.com/ubuntu xenial-proposed main' | sudo tee 
/etc/apt/sources.list.d/xenial-proposed.list
$ sudo apt update
$ sudo apt -y install systemd
$ sudo systemctl daemon-reexec

$ dpkg -s systemd | grep ^Version:
Version: 229-4ubuntu21.23

No scope units at the beginning:

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$ 


Test #1: no leaked zero units.

$ kubectl create -f pod-with-secret.yaml
pod/pod-with-secret created

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  4s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$ 

$ kubectl delete pods pod-with-secret
pod "pod-with-secret" deleted


Test #2: no leaked zero units.

$ kubectl create -f pod-with-secret.yaml
pod/pod-with-secret created

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  7s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount for'
$

$ kubectl delete pods pod-with-secret
pod "pod-with-secret" deleted


Test #3: no leaked zero units.

$ kubectl create -f pod-with-secret.yaml
pod/pod-with-secret created

$ kubectl get pods
NAME  READY   STATUS  RESTARTS   AGE
pod-with-secret   0/1 Completed   0  4s

$ systemctl list-units --type=scope | grep 'Kubernetes transient mount 

[Touch-packages] [Bug 1800836] Re: systemd-networkd doesn't process IPv6 RA properly

[Dan Streetman]

> After a failover

can you explain what exactly happens during the failover?  What specific
commands are executed on the old system to remove the VIP and/or adjust
anything else?

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

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

Title:
  systemd-networkd doesn't process IPv6 RA properly

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The gateways/firewalls in our DC are highly available and when there
  is a failover their IPv6 VIP (fe80::1) moves from the master to the
  backup one.

  We found that only our Bionic VMs behind those gateways had issues
  after a failover. Those Bionic VMs were all running systemd-networkd
  (from netplan) and before the failover they had:

  $ ip -6 route
  ...
  default via fe80::1 dev eth0 proto ra metric 1024 pref medium

  But after a failover:

  $ ip -6 route
  ...
  default proto ra metric 1024
  nexthop via fe80::1 dev eth0 weight 1
  nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1

  And after another failover:

  $ ip -6 route
  ...
  default proto ra metric 1024
  nexthop via fe80::1 dev eth0 weight 1
  nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1
  nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1

  
  This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as 
their default gateway even when this gateway is unavailable:

  $ ip -6 route get ::
  :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src 
fe80::a800:ff:fe51:8c37 metric 1024 pref medium

  
  We concluded it was a systemd-networkd bug after checking that the following 
combinations were NOT affected:

  1) Xenial+4.4 kernel
  2) Xenial+4.15 kernel
  3) Bionic+ifupdown

  
  Additional information:

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

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 31 08:47:28 2018
  Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=43b7ee2e-2ab1-4505-8e0b-d9fe0563a034 ro console=ttyS0 net.ifnames=0 
vsyscall=none kaslr nmi_watchdog=0 possible_cpus=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

** Description changed:

  Only the lv for root volume get activated, because of the grub parameter
  that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
  
  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.
  
  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.
  
  At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
  
  Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
  and allow one to successfully boot.
  
  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
  => + mountroot_status=0
  + [ ]
  + log_end_msg
  + _log_msg done.\n
  + [ n = y ]
  + printf done.\n
  done.
  + read_fstab_entry /usr
  + found=1
  + [ -f /root/etc/fstab ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = /usr ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /usr = /usr ]
  + [ -n ]
  + found=0
  + break 2
  + return 0
  + log_begin_msg Mounting /usr file system
  + _log_msg Begin: Mounting /usr file system ...
  
  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if found.
  
  initramfs-tools:init
  271 maybe_break mount
  272 log_begin_msg "Mounting root file system"
  273 # Always load local and nfs (since these might be needed for /etc or
  274 # /usr, irrespective of the boot script used to mount the rootfs).
  275 . /scripts/local
  276 . /scripts/nfs
  277 . /scripts/${BOOT}
  278 parse_numeric "${ROOT}"
  279 maybe_break mountroot
  280 mount_top
  281 mount_premount
  282 mountroot
  283 log_end_msg
  284
  => 285 if read_fstab_entry /usr; then
  => 286 log_begin_msg "Mounting /usr file system"
  => 287 mountfs /usr
  => 288 log_end_msg
  => 289 fi
  
  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr couldn't
  be mounted.
  
  It clearly seems to be an 'auto-activation' issue at boot.
  
  For other such as /home, /var, it's not a big deal cause they can be
  activated later on in the process and they are (I haven't check but I
  guess systemd or systemd unit/generator is taking care of it at some
  point), but /usr is a important piece to have mounted before the pivot
  since it contains most of the crucial binary, especially that nowadays
  /sbin, /bin, and /lib are pointing to /usr:
  
  lrwxrwxrwx   1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib64 -> usr/lib64
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib32 -> usr/lib32
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 lib -> usr/lib
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 bin -> usr/bin
  lrwxrwxrwx   1 root root  8 Aug 26 13:51 sbin -> usr/sbin
  
  NOTE:
  
  * That doesn't affect /usr found in /etc/fstab on its separate partition
  when no LVM involve (e.g. /dev/vdb /usr ext4 ). It only cause issue
  when /usr is in a LVM context.
  
  * I was able to reproduce on Bionic and Disco so far.
  Eoan doesn't seem to exhibit the situation so far in my testing.
+ 
+ * While certain release such as Bionic, Xenial doesn't come implicitly
+ with the user merge approach, one can install package 'usrmerge' and
+ make their system /usr merged. I don't think removing the
+ read_fstable_entry for /usr is an option here, as some user could
+ potentially decide to convert their system with 'usrmerge' pkg.

** Description changed:

  Only the lv for root volume get activated, because of the grub parameter
  that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
  
  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.
  
  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.
  
  At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
  
  Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
  and allow one to successfully boot.
  
  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
  => + mountroot_status=0
  + [ ]
  + log_end_msg
  + _log_msg done.\n
  + [ n = y ]
  + printf done.\n
  done.
  + read_fstab_entry /usr
  + found=1
  + [ -f /root/etc/fstab ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = /usr ]
  + read MNT_FSNAME 

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

** Description changed:

  Only the lv for root volume get activated, because of the grub parameter
  that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
  
  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.
  
  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.
  
  At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
  
  Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
  and allow one to successfully boot.
  
  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
  => + mountroot_status=0
  + [ ]
  + log_end_msg
  + _log_msg done.\n
  + [ n = y ]
  + printf done.\n
  done.
  + read_fstab_entry /usr
  + found=1
  + [ -f /root/etc/fstab ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = /usr ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /usr = /usr ]
  + [ -n ]
  + found=0
  + break 2
  + return 0
  + log_begin_msg Mounting /usr file system
  + _log_msg Begin: Mounting /usr file system ...
  
  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if found.
  
  initramfs-tools:init
  271 maybe_break mount
  272 log_begin_msg "Mounting root file system"
  273 # Always load local and nfs (since these might be needed for /etc or
  274 # /usr, irrespective of the boot script used to mount the rootfs).
  275 . /scripts/local
  276 . /scripts/nfs
  277 . /scripts/${BOOT}
  278 parse_numeric "${ROOT}"
  279 maybe_break mountroot
  280 mount_top
  281 mount_premount
  282 mountroot
  283 log_end_msg
  284
  => 285 if read_fstab_entry /usr; then
  => 286 log_begin_msg "Mounting /usr file system"
  => 287 mountfs /usr
  => 288 log_end_msg
  => 289 fi
  
  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr couldn't
  be mounted.
  
  It clearly seems to be an 'auto-activation' issue at boot.
  
  For other such as /home, /var, it's not a big deal cause they can be
- activated later on in the process and they are, but /usr is a important
- piece to have mounted before the pivot since it contains most of the
- crucial binary, especially that nowadays /sbin, /bin, and /lib are
- pointing to /usr:
+ activated later on in the process and they are (I haven't check but I
+ guess systemd or systemd unit/generator is taking care of it at some
+ point), but /usr is a important piece to have mounted before the pivot
+ since it contains most of the crucial binary, especially that nowadays
+ /sbin, /bin, and /lib are pointing to /usr:
  
  lrwxrwxrwx   1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib64 -> usr/lib64
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib32 -> usr/lib32
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 lib -> usr/lib
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 bin -> usr/bin
  lrwxrwxrwx   1 root root  8 Aug 26 13:51 sbin -> usr/sbin
- 
  
  NOTE:
  
  * That doesn't affect /usr found in /etc/fstab on its separate partition
  when no LVM involve (e.g. /dev/vdb /usr ext4 ). It only cause issue
  when /usr is in a LVM context.
  
  * I was able to reproduce on Bionic and Disco so far.
  Eoan doesn't seem to exhibit the situation so far in my testing.

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Only the lv for root volume get activated, because of the grub
  parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
  --lv"

  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
  => + mountroot_status=0
  + [ ]
  + log_end_msg
  + 

[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files

[Mauricio Faria de Oliveira]

Verification done on xenial-proposed.

With the new systemd and dbus packages, there are no leaked sessions
after the test-case of ssh loop.

The autopkgtests regressions reported previously are unrelated to this
change (comments #11 to #16).

cheers,
Mauricio

Setup
---

$ sudo snap install --beta --classic multipass

$ multipass launch --cpus 2 --mem 8G --disk 8G --name lp1846787 xenial
$ multipass shell lp1846787

$ lsb_release -cs
xenial

$ ssh-keygen -t rsa -f ~/.ssh/id_rsa -N ''
$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
$ sudo apt update && sudo apt -y upgrade && sudo reboot


xenial-updates: there are leaked sessions after ssh loop. (bad)
---

$ multipass shell lp1846787

$ dpkg -s systemd dbus | grep ^Version:
Version: 229-4ubuntu21.22
Version: 1.10.6-1ubuntu3.4

$ find /run/systemd/system/ -name 'session-*.scope.d' | wc -l
1

$ find /run/systemd/system/ -name '*.scope.d'
/run/systemd/system/session-1.scope.d

$ for i in {1..1000}; do sleep 0.01; ssh localhost sleep 1 & done
...
[1000] 12191

$ jobs
$

$ find /run/systemd/system/ -name 'session-*.scope.d' | wc -l
32

$ find /run/systemd/system/ -name 'session-*.scope.d' 
/run/systemd/system/session-906.scope.d
/run/systemd/system/session-896.scope.d
/run/systemd/system/session-848.scope.d
...
/run/systemd/system/session-1.scope.d


xenial-proposed: there are NO leaked sessions after ssh loop. (good; tested 3x)
---

$ echo 'deb http://archive.ubuntu.com/ubuntu xenial-proposed main' | sudo tee 
/etc/apt/sources.list.d/xenial-proposed.list
$ sudo apt update && sudo apt -y install systemd dbus && sudo reboot

$ multipass shell lp1846787

$ dpkg -s systemd dbus | grep ^Version:
Version: 229-4ubuntu21.23
Version: 1.10.6-1ubuntu3.5

$ find /run/systemd/system/ -name 'session-*.scope.d' | wc -l
1

$ find /run/systemd/system/ -name 'session-*.scope.d' 
/run/systemd/system/session-1.scope.d

$ for i in {1..1000}; do sleep 0.01; ssh localhost sleep 1 & done
...
[1000] 12462

$ jobs
$

$ find /run/systemd/system/ -name 'session-*.scope.d' | wc -l
1

$ find /run/systemd/system/ -name 'session-*.scope.d' 
/run/systemd/system/session-1.scope.d

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

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

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

Title:
  systemd-logind leaves leftover sessions and scope files

Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Scope file leakage can cause SSH delays and reduce performance in systemd

  [Description]
  The current systemd-logind version present in Xenial can leave abandoned SSH
  sessions and scope files in cases where the host sees a lot of concurrent SSH
  connections. These leftover sessions can slow down systemd performance
  greatly, and can have an impact on sshd handling a great number of concurrent
  connections.

  To fix this issue, patches are needed in both dbus and systemd. These improve 
the
  performance of the communication between dbus and systemd, so that they can
  handle a better volume of events (e.g. SSH logins). All of those patches are
  already present from Bionic onwards, so we only need those fixes for Xenial.

  == Systemd ==
  Upstream patches:
  - core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification 
(d8fdc62037b5)

  $ git describe --contains d8fdc62037b5
  v230~71^2~2

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.21 | xenial-security | source, ...
   systemd | 229-4ubuntu21.22 | xenial-updates  | source, ... <
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.29 | bionic-security | source, ...
   systemd | 237-3ubuntu10.29 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...

  == DBus ==
  Upstream patches:
  - Only read one message at a time if there are fds pending (892f084eeda0)
  - bus: Fix timeout restarts  (529600397bca)
  - DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)

  $ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
  dbus-1.11.10~44
  dbus-1.11.10~45
  dbus-1.11.16~2

  $ rmadison dbus
   dbus | 1.10.6-1ubuntu3| xenial   | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-security  | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-updates   | source, ... <
   dbus | 1.12.2-1ubuntu1| bionic   | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-security  | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-updates   | source, ...

  [Test Case]
  1) Simulate a lot of concurrent SSH connections with 

[Touch-packages] [Bug 1854582] Re: systemd-timesyncd.service not starting

[Dan Streetman]

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

This isn't exactly the same issue as bug 1849156 (that is about ntp
condition check conflict, this is virtualbox), but it's close enough as
the cause is the same - the drop-in file simply checking for the
presence of specific executable files, instead of checking for running
process/service.

I'm duping to that bug, but if you disagree please feel free to un-dup.

** This bug has been marked a duplicate of bug 1849156
   systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

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

Title:
  systemd-timesyncd.service not starting

Status in systemd package in Ubuntu:
  New

Bug description:
  Kubuntu -19.10 (though I believe the problem also exists on prior
  versions)

  Time synchronization not working:

  --
  greenman@Crynfyd19.10 /lib/systemd/system$ timedatectl status
 Local time: Sat 2019-11-30 08:21:57 PST
 Universal time: Sat 2019-11-30 16:21:57 UTC
   RTC time: Sat 2019-11-30 16:21:57
  Time zone: America/Los_Angeles (PST, -0800)
  System clock synchronized: no
NTP service: inactive
RTC in local TZ: no

  greenman@Crynfyd19.10 /lib/systemd/system$ sudo systemctl status 
systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead) since Sat 2019-11-30 08:21:28 PST; 2min 0s ago
  Condition: start condition failed at Sat 2019-11-30 08:23:15 PST; 12s ago
 └─ ConditionFileIsExecutable=!/usr/sbin/VBoxService was not met
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 813 (code=exited, status=0/SUCCESS)
 Status: "Shutting down..."

  Nov 30 07:29:50 Crynfyd systemd[1]: Starting Network Time Synchronization...
  Nov 30 07:29:51 Crynfyd systemd[1]: Started Network Time Synchronization.
  Nov 30 07:30:21 Crynfyd systemd-timesyncd[813]: Synchronized to time server 
for the first time 91.189.
  Nov 30 08:21:28 Crynfyd systemd[1]: Stopping Network Time Synchronization...
  Nov 30 08:21:28 Crynfyd systemd[1]: systemd-timesyncd.service: Succeeded.
  Nov 30 08:21:28 Crynfyd systemd[1]: Stopped Network Time Synchronization.
  Nov 30 08:23:15 Crynfyd systemd[1]: Condition check resulted in Network Time 
Synchronization being ski

  --

  The problem has to do with the file 
  /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf;

  --
  greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ cat 
disable-with-time-daemon.conf
  [Unit]
  # don't run timesyncd if we have another NTP daemon installed
  ConditionFileIsExecutable=!/usr/sbin/ntpd
  ConditionFileIsExecutable=!/usr/sbin/openntpd
  ConditionFileIsExecutable=!/usr/sbin/chronyd
  ConditionFileIsExecutable=!/usr/sbin/VBoxService
  --

  I do have virtualbox installed, but not running, so VBoxService is not 
running.
  This means that although the binary is there, it is not providing time sync 
services, so the system is not time syncing.  If I remove the line 
"ConditionFileIsExecutable=!/usr/sbin/VBoxService" from the file and restart, 
all is well:

  --
  greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ sudo 
systemctl daemon-reload
  greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ sudo 
systemctl restart systemd-timesyncd.service
  greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ 
timedatectl status
 Local time: Sat 2019-11-30 08:29:43 PST
 Universal time: Sat 2019-11-30 16:29:43 UTC
   RTC time: Sat 2019-11-30 16:29:43
  Time zone: America/Los_Angeles (PST, -0800)
  System clock synchronized: yes
NTP service: active
RTC in local TZ: no
  --

  So instead of testing just for the existence of the binary, which is
  resulting in no time sync service, what it probably should do is check
  for a running process, and allow the service to start if no other time
  syncing service is running.

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

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

[Touch-packages] [Bug 1854998] [NEW] snd_hda_codec_hdmi hdaudioC0D3: No i915 binding for Intel HDMI/DP codec

[CHANTELOSE]

Public bug reported:

hdaudio hdaudioC0D3: Unable to bind the codec

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Tue Dec  3 21:28:01 2019
InstallationDate: Installed on 2019-04-28 (219 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to eoan on 2019-11-03 (29 days ago)
dmi.bios.date: 07/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P09ABE
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP350E7C-S0BFR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350E7C-S0BFR:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: Eureka
dmi.product.name: 350V5C/351V5C/3540VC/3440VC
dmi.product.sku: P09ABE.012.CP
dmi.product.version: P09ABE.012.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug eoan

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

Title:
  snd_hda_codec_hdmi hdaudioC0D3: No i915 binding for Intel HDMI/DP
  codec

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  hdaudio hdaudioC0D3: Unable to bind the codec

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec  3 21:28:01 2019
  InstallationDate: Installed on 2019-04-28 (219 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (29 days ago)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABE
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350E7C-S0BFR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350E7C-S0BFR:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 350V5C/351V5C/3540VC/3440VC
  dmi.product.sku: P09ABE.012.CP
  dmi.product.version: P09ABE.012.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1854195] Re: pc wont resolve any names until /etc/resolv.conf is edited by hand

[Dan Streetman]

> Looks like systemd-resolved is broken by design.

er, no.

Without editing resolv.conf, what do these commands show:

$ systemctl --no-pager status systemd-resolved

$ resolvectl --no-pager

$ resolvectl query google.com


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

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

Title:
  pc wont resolve any names until /etc/resolv.conf is edited by hand

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  In /etc/systemd/resolved.conf I've entered the nameserver to use:
  [Resolve]
  DNS=172.18.8.1
  #FallbackDNS=
  Domains=fritz.box
  #LLMNR=no
  #MulticastDNS=no
  #DNSSEC=no
  #DNSOverTLS=no
  #Cache=yes
  #DNSStubListener=yes
  #ReadEtcHosts=yes

  In /etc/resolv.conf after rebooting:
  nameserver 127.0.0.53
  options edns0
  search fritz.box

  No names from anywhere are solved. This systemd-resolver just does
  nothing. It does not even forward any request to 172.18.8.1!

  As soon as I edit /etc/resolv.conf, replacing 127.0.0.53 with
  172.18.8.1 it starts to work as it is expected to. Looks like systemd-
  resolved is broken by design.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 27 19:16:22 2019
  InstallationDate: Installed on 2019-09-09 (79 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-23-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  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:bd07/29/2019: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.
  mtime.conffile..etc.systemd.resolved.conf: 2019-09-24T10:52:27.095603

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

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

[Touch-packages] [Bug 421567]

[Gitlab-migration]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/68.

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

Title:
  Audio/Video chat does not work with iChat users

Status in Empathy:
  Unknown
Status in Pidgin:
  New
Status in telepathy-farsight:
  Invalid
Status in telepathy-gabble:
  Unknown
Status in telepathy-gabble package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: empathy

  iChat users don't appear as having audio or video chat available

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

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

[Touch-packages] [Bug 421567] Re: Audio/Video chat does not work with iChat users

[Bug Watch Updater]

** Changed in: telepathy-gabble
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/telepathy/telepathy-gabble/issues #68
   https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/68

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

Title:
  Audio/Video chat does not work with iChat users

Status in Empathy:
  Unknown
Status in Pidgin:
  New
Status in telepathy-farsight:
  Invalid
Status in telepathy-gabble:
  Unknown
Status in telepathy-gabble package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: empathy

  iChat users don't appear as having audio or video chat available

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

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

[Touch-packages] [Bug 1852933] Re: Failed to read time with suspend-then-hibernate fails

[Dan Streetman]

What does this return on your system:

$ cat /sys/class/rtc/rtc0/since_epoch

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

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

Title:
  Failed to read time with suspend-then-hibernate fails

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd version the issue has been seen with
  237

  Used distribution
  Ubuntu 18.04

  Expected behaviour you didn't see
  Running suspend-then-hibernate service should put the machine into sleep mode 
and then hibernate after the delay set in the sleep.conf file.

  Unexpected behaviour you saw
  suspend-then-hibernate fails. The status shows:

  systemd[1]: Starting Suspend; Idle into hibernate...
  systemd-sleep[13130]: Failed to read time: -9
  systemd[1]: systemd-suspend-then-hibernate.service: Main process exited, code
  systemd[1]: systemd-suspend-then-hibernate.service: Failed with result 'exit-
  systemd[1]: Failed to start Suspend; Idle into hibernate.
  Both suspend and hibernate services work fine.

  Steps to reproduce the problem
  Running sudo systemctl suspend-then-hibernate generates the error.

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

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

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

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

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

** Description changed:

  Only the lv for root volume get activated, because of the grub parameter
  that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
  
  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
-   This argument tells the kernel what device is to be used as
-   the root filesystem while booting.
+   This argument tells the kernel what device is to be used as
+   the root filesystem while booting.
  
  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.
  
  At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
  
  Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
  and allow one to successfully boot.
  
  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
  => + mountroot_status=0
  + [ ]
  + log_end_msg
  + _log_msg done.\n
  + [ n = y ]
  + printf done.\n
  done.
  + read_fstab_entry /usr
  + found=1
  + [ -f /root/etc/fstab ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ / = /usr ]
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
  + [ /usr = /usr ]
  + [ -n ]
  + found=0
  + break 2
  + return 0
  + log_begin_msg Mounting /usr file system
  + _log_msg Begin: Mounting /usr file system ...
  
  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if found.
  
  initramfs-tools:init
  271 maybe_break mount
  272 log_begin_msg "Mounting root file system"
  273 # Always load local and nfs (since these might be needed for /etc or
  274 # /usr, irrespective of the boot script used to mount the rootfs).
  275 . /scripts/local
  276 . /scripts/nfs
  277 . /scripts/${BOOT}
  278 parse_numeric "${ROOT}"
  279 maybe_break mountroot
  280 mount_top
  281 mount_premount
  282 mountroot
  283 log_end_msg
  284
  => 285 if read_fstab_entry /usr; then
  => 286 log_begin_msg "Mounting /usr file system"
  => 287 mountfs /usr
  => 288 log_end_msg
  => 289 fi
  
  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr couldn't
  be mounted.
  
  It clearly seems to be an 'auto-activation' issue at boot.
  
  For other such as /home, /var, it's not a big deal cause they can be
  activated later on in the process and they are, but /usr is a important
  piece to have mounted before the pivot since it contains most of the
  crucial binary, especially that nowadays /sbin, /bin, and /lib are
  pointing to /usr:
  
  lrwxrwxrwx   1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib64 -> usr/lib64
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib32 -> usr/lib32
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 lib -> usr/lib
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 bin -> usr/bin
  lrwxrwxrwx   1 root root  8 Aug 26 13:51 sbin -> usr/sbin
  
- I was able to reproduce on Bionic and Disco so far.
- Eoan doesn't seem to exhibit the situation so far in my testing.
- 
  
  NOTE:
- That doesn't affect /usr found in /etc/fstab on its separate partition when 
no LVM involve (e.g. /dev/vdb /usr ext4 ). It only cause issue when /usr is 
in a LVM context.
+ 
+ * That doesn't affect /usr found in /etc/fstab on its separate partition
+ when no LVM involve (e.g. /dev/vdb /usr ext4 ). It only cause issue
+ when /usr is in a LVM context.
+ 
+ * I was able to reproduce on Bionic and Disco so far.
+ Eoan doesn't seem to exhibit the situation so far in my testing.

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Only the lv for root volume get activated, because of the grub
  parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
  --lv"

  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully 

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

** Description changed:

- Only the lv for root volume get activated, most likely because of the
- grub parameter that specifies it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
+ Only the lv for root volume get activated, because of the grub parameter
+ that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
+ 
+ http://man7.org/linux/man-pages/man7/bootparam.7.html
+ 'root=...'
+   This argument tells the kernel what device is to be used as
+   the root filesystem while booting.
  
  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.
  
  At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
  
  Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
  and allow one to successfully boot.
  
- Adding 'debug' parameter, we clearly we see /root being detected and mounted: 
- initramfs.debug: 
- => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root 
- => + mountroot_status=0 
- + [ ] 
- + log_end_msg 
- + _log_msg done.\n 
- + [ n = y ] 
- + printf done.\n 
- done. 
- + read_fstab_entry /usr 
- + found=1 
- + [ -f /root/etc/fstab ] 
- + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
- + [ / = /usr ] 
- + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
- + [ /usr = /usr ] 
- + [ -n ] 
- + found=0 
- + break 2 
- + return 0 
- + log_begin_msg Mounting /usr file system 
- + _log_msg Begin: Mounting /usr file system ... 
+ Adding 'debug' parameter, we clearly we see /root being detected and mounted:
+ initramfs.debug:
+ => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
+ => + mountroot_status=0
+ + [ ]
+ + log_end_msg
+ + _log_msg done.\n
+ + [ n = y ]
+ + printf done.\n
+ done.
+ + read_fstab_entry /usr
+ + found=1
+ + [ -f /root/etc/fstab ]
+ + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ + [ / = /usr ]
+ + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ + [ /usr = /usr ]
+ + [ -n ]
+ + found=0
+ + break 2
+ + return 0
+ + log_begin_msg Mounting /usr file system
+ + _log_msg Begin: Mounting /usr file system ...
  
  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if found.
  
- initramfs-tools:init 
- 271 maybe_break mount 
- 272 log_begin_msg "Mounting root file system" 
- 273 # Always load local and nfs (since these might be needed for /etc or 
- 274 # /usr, irrespective of the boot script used to mount the rootfs). 
- 275 . /scripts/local 
- 276 . /scripts/nfs 
- 277 . /scripts/${BOOT} 
- 278 parse_numeric "${ROOT}" 
- 279 maybe_break mountroot 
- 280 mount_top 
- 281 mount_premount 
- 282 mountroot 
- 283 log_end_msg 
- 284 
- => 285 if read_fstab_entry /usr; then 
- => 286 log_begin_msg "Mounting /usr file system" 
- => 287 mountfs /usr 
- => 288 log_end_msg 
- => 289 fi 
+ initramfs-tools:init
+ 271 maybe_break mount
+ 272 log_begin_msg "Mounting root file system"
+ 273 # Always load local and nfs (since these might be needed for /etc or
+ 274 # /usr, irrespective of the boot script used to mount the rootfs).
+ 275 . /scripts/local
+ 276 . /scripts/nfs
+ 277 . /scripts/${BOOT}
+ 278 parse_numeric "${ROOT}"
+ 279 maybe_break mountroot
+ 280 mount_top
+ 281 mount_premount
+ 282 mountroot
+ 283 log_end_msg
+ 284
+ => 285 if read_fstab_entry /usr; then
+ => 286 log_begin_msg "Mounting /usr file system"
+ => 287 mountfs /usr
+ => 288 log_end_msg
+ => 289 fi
  
  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr couldn't
  be mounted.
- 
  
  It clearly seems to be an 'auto-activation' issue at boot.
  
  For other such as /home, /var, it's not a big deal cause they can be
  activated later on in the process and they are, but /usr is a important
  piece to have mounted before the pivot since it contains most of the
  crucial binary, especially that nowadays /sbin, /bin, and /lib are
  pointing to /usr:
  
  lrwxrwxrwx   1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib64 -> usr/lib64
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib32 -> usr/lib32
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 lib -> usr/lib
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 bin -> usr/bin
  lrwxrwxrwx   1 root root  8 Aug 26 13:51 sbin -> usr/sbin
  
  I was able to reproduce on Bionic and Disco so far.
  Eoan doesn't seem to exhibit the situation so far in my testing.
+ 
+ 
+ NOTE:
+ That doesn't affect /usr found in /etc/fstab on its separate partition when 
no LVM involve (e.g. /dev/vdb /usr ext4 ). It only cause issue when /usr is 
in a LVM context.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Thales Rocha]

Hi all, I have the same problem,

My notebook is the same @dkajah, a new dell-g3-3590 with fresh Ubuntu
18.04LTS install (I already test with 19.10, the result was the same.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1853861] Re: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels

[Daniel Richard G.]

Thanks Balint. I've installed the bionic-proposed package, and have not
observed any silently-failed upgrades as before (but of course verifying
it in my use case is tantamount to proving a negative).

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

Title:
  [SRU] Unattended-upgrades silently does not apply updates when
  MinimalSteps is disabled and there are autoremovable kernels

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Released
Status in unattended-upgrades source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When autoremovable kernel packages are present on the system, there are 
updates to apply and Unattended-Upgrade::MinimalSteps is set to "false", the 
autoremovable kernel packages are not removed and the updates are not applied.
   * The root cause is u-u not cleaning the dirty cache between operations and 
also relying on having a cache with packages marked to be installed when 
applying updates in one shot.
   * The fix is clearing the cache between operations and marking packages 
before installing them in one shot.

  [Test Case]

   * Install kernel-related packages, mark them as automatically installed to 
make them auto-removable ones.
   * Downgrade a few packages to a version lower than what is present in the 
security pocket.
   * Set Unattended-Upgrade::MinimalSteps to "false":
 # echo 'Unattended-Upgrade::MinimalSteps "false";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-oneshot

   * Run u-u:
 # unattended-upgrade --verbose --debug

   * Observe fixed versions removing the kernel packages properly and
  also upgrading packages.

  [Regression Potential]

   * The changes introduce marking packages to install/upgrade and clearing the 
cache more often. The added operations slow down u-u, but clearing the cache 
adds a few 100 milliseconds on typical hardware and marking upgradable packages 
is also in the same range.
   * Functional regressions are unlikely due to those changes since the fixes 
are present in 19.04 and later releases and the extensive autopkgtest also 
covers when upgrades are performed in minimal steps.

  [Other Info]

   * While this bug has a security impact by holding back installation of 
security updates I don't recommend releasing the fix via the security pocket 
because this bug occurs only when the local configuration file of u-u is 
changed and u-u does not hold back upgrades with UCF-managed config file 
conflicts.
See: https://github.com/mvo5/unattended-upgrades/issues/168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1853861/+subscriptions

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

[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core

[Dan Streetman]

systemd crashed while trying to serialize, on a service that appears to
not be provided by Ubuntu, '/lib/systemd/system/keepsessions.service'.
It looks like it's part of a 'sitetools' package (the exec command is
"/opt/sitetools/keepsessions").

This is probably a bug in systemd, but it would help to see the specific
details of that service file; can you attach or paste it here?

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

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

Title:
  systemd Caught , dumped core

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 
237-3ubuntu10.31
  This caused systemd to segfault and stop receiving any systemctl command 
(they timeout).

  [  198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 
7ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000]
  [  278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification 
message: Connection refused
  [  368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification 
message: Transport endpoint is not connected
  [  458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification 
message: Transport endpoint is not connected

  I downgraded to 237-3ubuntu10.29 to no avail.
  Then I downgraded to 237-3ubuntu10:
  apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 
systemd-sysv=237-3ubuntu10 libsystemd0:amd64=237-3ubuntu10 
libudev1:amd64=237-3ubuntu10 libnss-systemd:amd64=237-3ubuntu10

  and that did not help either.
  The machine is unusable at the moment.

  Attaching coredump of systemd (version 237-3ubuntu10.31)

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

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

[Touch-packages] [Bug 1854976] Re: systemd-resolved doesn't work with "host -l" / AXFR queries

[Steve Langasek]

An AXFR is not a normal end-user operation, and for most public DNS
servers these queries are denied for security reasons.  I don't think
it's reasonable to expect an AXFR query to work against your local
forwarding resolver; I think it was accidental that this worked under
dnsmasq.

You should be able to execute a 'host -l' against an actual
authoritative nameserver for the domain, if the nameserver is configured
to support this, by listing its name as an additional argument to 'host'
i.e.:

  host -l mydomain.lan mydns.mydomain.lan

So I think this bug should be closed as 'wontfix', but I'm leaving it
for the systemd maintainers to make that determination.

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

Title:
  systemd-resolved doesn't work with "host -l" / AXFR queries

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  some time ago network-manager in Ubuntu switched from dnsmasq to
  systemd-resolved.

  When network-manager used dnsmasq to handle DNS, one could use "host
  -l" to list all the hosts in a DNS zone, something like this:

  $ host -l mydomain.lan
  mydomain.lan name server mydns.mydomain.lan
  host1.mydomain.lan has address x.x.x.x
  host2.mydomain.lan has address x.x.x.x
  host3.mydomain.lan has address x.x.x.x
  host4.mydomain.lan has address x.x.x.x
  [...]

  That, unfortunately, no longer works since the switch to systemd-resolved, it 
always fails like this:
  $ host -l mydomain.lan
  Host mydomain.lan not found: 4(NOTIMP)
  ; Transfer failed.

  And I think that's because systemd-resolved is "filtering" the AXFR
  queries issued by "host -l" (I checked the network traffic with tcdump
  and that "NOTIMP" comes from the loopback interface).

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

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

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

initramfs.debug_DISCO

** Attachment added: "initramfs.debug_DISCO"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854981/+attachment/5309607/+files/initramfs.debug

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Only the lv for root volume get activated, most likely because of the
  grub parameter that specifies it "root=/dev/mapper/ubuntu-vg-ubuntu--
  lv"

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected and mounted: 
  initramfs.debug: 
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root 
  => + mountroot_status=0 
  + [ ] 
  + log_end_msg 
  + _log_msg done.\n 
  + [ n = y ] 
  + printf done.\n 
  done. 
  + read_fstab_entry /usr 
  + found=1 
  + [ -f /root/etc/fstab ] 
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
  + [ / = /usr ] 
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
  + [ /usr = /usr ] 
  + [ -n ] 
  + found=0 
  + break 2 
  + return 0 
  + log_begin_msg Mounting /usr file system 
  + _log_msg Begin: Mounting /usr file system ... 

  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if
  found.

  initramfs-tools:init 
  271 maybe_break mount 
  272 log_begin_msg "Mounting root file system" 
  273 # Always load local and nfs (since these might be needed for /etc or 
  274 # /usr, irrespective of the boot script used to mount the rootfs). 
  275 . /scripts/local 
  276 . /scripts/nfs 
  277 . /scripts/${BOOT} 
  278 parse_numeric "${ROOT}" 
  279 maybe_break mountroot 
  280 mount_top 
  281 mount_premount 
  282 mountroot 
  283 log_end_msg 
  284 
  => 285 if read_fstab_entry /usr; then 
  => 286 log_begin_msg "Mounting /usr file system" 
  => 287 mountfs /usr 
  => 288 log_end_msg 
  => 289 fi 

  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr
  couldn't be mounted.

  
  It clearly seems to be an 'auto-activation' issue at boot.

  For other such as /home, /var, it's not a big deal cause they can be
  activated later on in the process and they are, but /usr is a
  important piece to have mounted before the pivot since it contains
  most of the crucial binary, especially that nowadays /sbin, /bin, and
  /lib are pointing to /usr:

  lrwxrwxrwx   1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib64 -> usr/lib64
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib32 -> usr/lib32
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 lib -> usr/lib
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 bin -> usr/bin
  lrwxrwxrwx   1 root root  8 Aug 26 13:51 sbin -> usr/sbin

  I was able to reproduce on Bionic and Disco so far.
  Eoan doesn't seem to exhibit the situation so far in my testing.

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

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

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

For context about the /usr merge:

https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Only the lv for root volume get activated, most likely because of the
  grub parameter that specifies it "root=/dev/mapper/ubuntu-vg-ubuntu--
  lv"

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected and mounted: 
  initramfs.debug: 
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root 
  => + mountroot_status=0 
  + [ ] 
  + log_end_msg 
  + _log_msg done.\n 
  + [ n = y ] 
  + printf done.\n 
  done. 
  + read_fstab_entry /usr 
  + found=1 
  + [ -f /root/etc/fstab ] 
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
  + [ / = /usr ] 
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
  + [ /usr = /usr ] 
  + [ -n ] 
  + found=0 
  + break 2 
  + return 0 
  + log_begin_msg Mounting /usr file system 
  + _log_msg Begin: Mounting /usr file system ... 

  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if
  found.

  initramfs-tools:init 
  271 maybe_break mount 
  272 log_begin_msg "Mounting root file system" 
  273 # Always load local and nfs (since these might be needed for /etc or 
  274 # /usr, irrespective of the boot script used to mount the rootfs). 
  275 . /scripts/local 
  276 . /scripts/nfs 
  277 . /scripts/${BOOT} 
  278 parse_numeric "${ROOT}" 
  279 maybe_break mountroot 
  280 mount_top 
  281 mount_premount 
  282 mountroot 
  283 log_end_msg 
  284 
  => 285 if read_fstab_entry /usr; then 
  => 286 log_begin_msg "Mounting /usr file system" 
  => 287 mountfs /usr 
  => 288 log_end_msg 
  => 289 fi 

  In this case, /usr is present in /etc/fstab but the logical volume is
  not available, so it is mounting a filesystem without his backend
  device, thus goes straight to the initramfs prompt because /usr
  couldn't be mounted.

  
  It clearly seems to be an 'auto-activation' issue at boot.

  For other such as /home, /var, it's not a big deal cause they can be
  activated later on in the process and they are, but /usr is a
  important piece to have mounted before the pivot since it contains
  most of the crucial binary, especially that nowadays /sbin, /bin, and
  /lib are pointing to /usr:

  lrwxrwxrwx   1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib64 -> usr/lib64
  lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib32 -> usr/lib32
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 lib -> usr/lib
  lrwxrwxrwx   1 root root  7 Aug 26 13:51 bin -> usr/bin
  lrwxrwxrwx   1 root root  8 Aug 26 13:51 sbin -> usr/sbin

  I was able to reproduce on Bionic and Disco so far.
  Eoan doesn't seem to exhibit the situation so far in my testing.

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

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

[Touch-packages] [Bug 1854985] [NEW] pm-utils overrides runtime power management mode for audio devices

[Daniel Dadap]

Public bug reported:

In newer Ubuntu 18.04 HWE kernels, it is possible for GPU HDA
controllers to be dynamically runtime-suspended if the HDA's
power/control mode is set to "auto". However, pm-utils explicitly sets
this to "on" when resuming, which prevents runtime power management of
these devices from working as intended.

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  pm-utils overrides runtime power management mode for audio devices

Status in pm-utils package in Ubuntu:
  New

Bug description:
  In newer Ubuntu 18.04 HWE kernels, it is possible for GPU HDA
  controllers to be dynamically runtime-suspended if the HDA's
  power/control mode is set to "auto". However, pm-utils explicitly sets
  this to "on" when resuming, which prevents runtime power management of
  these devices from working as intended.

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Andreas Hasenack]

** Merge proposal unlinked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/talloc/+git/talloc/+merge/376296

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in talloc package in Ubuntu:
  Fix Released
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1440381] Re: please build bindings for Python3

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/talloc/+git/talloc/+merge/376296

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in talloc package in Ubuntu:
  Fix Released
Status in tdb package in Ubuntu:
  Fix Released
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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

[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved

[Paride Legovini]

** Changed in: dnsmasq (Ubuntu)
   Status: Confirmed => 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/1785383

Title:
  missing EDNS0 record confuses systemd-resolved

Status in dnsmasq package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty
  answer for a domain it is authoritative for. systemd-resolved seems to
  get confused by this in certain circumstances; when using the stub
  resolver and requesting an address for which there are no 
  records, there can sometimes be a five second hang in resolution.

  This is fixed by upstream commit
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78

  Not sure if it is worth cherry picking? I imagine the most likely
  trigger will be dnsmasq on routers which are not likely to be running
  Ubuntu, but maybe just in case.

  I also think there are some logic issues in systemd-resolved, upstream
  bug filed:

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

  Simple-ish test case:

  ---
  IFACE=dummy0
  SUBNET=10.0.0

  ip link add $IFACE type dummy
  ifconfig $IFACE ${SUBNET}.1/24
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 &

  dig -t a test.test @10.0.0.1 | grep EDNS
  # should return "; EDNS ..."
  dig -t  test.test @10.0.0.1 | grep EDNS
  # again, should return "; EDNS ..." but doesn't
  ---

  To reproduce the systemd-resolved side of the problem

  ---
  # as above, but
  # now configure systemd-resolved to look at only 10.0.0.1, then

  systemd-resolve --reset-server-features
  # should exhibit five second delay then connect, assuming sshd is running :)
  ssh test.test
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq-base 2.79-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
  Date: Sat Aug  4 11:33:56 2018
  InstallationDate: Installed on 2018-05-31 (64 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1854981] [NEW] system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

Public bug reported:

Only the lv for root volume get activated, most likely because of the
grub parameter that specifies it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"

If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.

At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.

Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
and allow one to successfully boot.

Adding 'debug' parameter, we clearly we see /root being detected and mounted: 
initramfs.debug: 
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root 
=> + mountroot_status=0 
+ [ ] 
+ log_end_msg 
+ _log_msg done.\n 
+ [ n = y ] 
+ printf done.\n 
done. 
+ read_fstab_entry /usr 
+ found=1 
+ [ -f /root/etc/fstab ] 
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
+ [ / = /usr ] 
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
+ [ /usr = /usr ] 
+ [ -n ] 
+ found=0 
+ break 2 
+ return 0 
+ log_begin_msg Mounting /usr file system 
+ _log_msg Begin: Mounting /usr file system ... 

then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if found.

initramfs-tools:init 
271 maybe_break mount 
272 log_begin_msg "Mounting root file system" 
273 # Always load local and nfs (since these might be needed for /etc or 
274 # /usr, irrespective of the boot script used to mount the rootfs). 
275 . /scripts/local 
276 . /scripts/nfs 
277 . /scripts/${BOOT} 
278 parse_numeric "${ROOT}" 
279 maybe_break mountroot 
280 mount_top 
281 mount_premount 
282 mountroot 
283 log_end_msg 
284 
=> 285 if read_fstab_entry /usr; then 
=> 286 log_begin_msg "Mounting /usr file system" 
=> 287 mountfs /usr 
=> 288 log_end_msg 
=> 289 fi 

In this case, /usr is present in /etc/fstab but the logical volume is
not available, so it is mounting a filesystem without his backend
device, thus goes straight to the initramfs prompt because /usr couldn't
be mounted.


It clearly seems to be an 'auto-activation' issue at boot.

For other such as /home, /var, it's not a big deal cause they can be
activated later on in the process and they are, but /usr is a important
piece to have mounted before the pivot since it contains most of the
crucial binary, especially that nowadays /sbin, /bin, and /lib are
pointing to /usr:

lrwxrwxrwx   1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib64 -> usr/lib64
lrwxrwxrwx   1 root root  9 Aug 26 13:51 lib32 -> usr/lib32
lrwxrwxrwx   1 root root  7 Aug 26 13:51 lib -> usr/lib
lrwxrwxrwx   1 root root  7 Aug 26 13:51 bin -> usr/bin
lrwxrwxrwx   1 root root  8 Aug 26 13:51 sbin -> usr/sbin

I was able to reproduce on Bionic and Disco so far.
Eoan doesn't seem to exhibit the situation so far in my testing.

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

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


** Tags: sts

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

** Tags added: sts

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Only the lv for root volume get activated, most likely because of the
  grub parameter that specifies it "root=/dev/mapper/ubuntu-vg-ubuntu--
  lv"

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected and mounted: 
  initramfs.debug: 
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root 
  => + mountroot_status=0 
  + [ ] 
  + log_end_msg 
  + _log_msg done.\n 
  + [ n = y ] 
  + printf done.\n 
  done. 
  + read_fstab_entry /usr 
  + found=1 
  + [ -f /root/etc/fstab ] 
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
  + [ / = /usr ] 
  + read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK 
  + [ /usr = /usr ] 
  + [ -n ] 
  + found=0 
  + break 2 
  + return 0 
  + log_begin_msg Mounting /usr file system 
  + _log_msg Begin: Mounting /usr file system ... 

  then the code read /etc/fstab and specifically search for /usr (most
  likely because of the /usr binary merged) and try to mount if if
  found.

  initramfs-tools:init 
  271 maybe_break mount 
  272 log_begin_msg "Mounting root file system" 
  273 # Always load local and nfs (since these 

[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files

[Mauricio Faria de Oliveira]

The remaining autopkgtests regressions (nplan/amd64 and gvfs/s390x) are
also unrelated to this change.

- nplan/amd64 passed with 3 retests:

Before:

  test_mix_bridge_on_bond (__main__.TestNetworkManager) ... FAIL
  ...
  integration.py   FAIL non-zero exit status 1

After:

  test_mix_bridge_on_bond (__main__.TestNetworkManager) ... ok
  ...
  integration.py   PASS


- gvfs/s390x has a long history of flaky/likely failures on these 2 tests, as 
seen in

  https://autopkgtest.ubuntu.com/packages/gvfs/xenial/s390x

So it is OK to ignore this one, it's not a regression from _this_
change.

Examples:

1.28.2-1ubuntu1~16.04.3 systemd/229-4ubuntu21.23
2019-12-02 13:31:15 UTC 0h 41m 38s  mfo fail

  trash:// deletion, attributes, restoring for a file in $HOME (API) ... FAIL
  trash:// deletion, attributes, restoring for a file in $HOME (CLI) ... FAIL

1.28.2-1ubuntu1~16.04.3 systemd/229-4ubuntu21.23
2019-11-27 22:19:05 UTC 0h 02m 29s  ddstreetfail

  trash:// deletion, attributes, restoring for a file in $HOME (API) ... ok
  trash:// deletion, attributes, restoring for a file in $HOME (CLI) ... FAIL

with a previous, anecdotal entry of 6 retests until passing on:

1.28.2-1ubuntu1~16.04.2 apache2/2.4.18-2ubuntu3.9   2018-06-29 
18:31:14 UTC 0h 
02m 47s ahasenack   pass

  trash:// deletion, attributes, restoring for a file in $HOME (API) ... ok
  trash:// deletion, attributes, restoring for a file in $HOME (CLI) ... ok

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

Title:
  systemd-logind leaves leftover sessions and scope files

Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Scope file leakage can cause SSH delays and reduce performance in systemd

  [Description]
  The current systemd-logind version present in Xenial can leave abandoned SSH
  sessions and scope files in cases where the host sees a lot of concurrent SSH
  connections. These leftover sessions can slow down systemd performance
  greatly, and can have an impact on sshd handling a great number of concurrent
  connections.

  To fix this issue, patches are needed in both dbus and systemd. These improve 
the
  performance of the communication between dbus and systemd, so that they can
  handle a better volume of events (e.g. SSH logins). All of those patches are
  already present from Bionic onwards, so we only need those fixes for Xenial.

  == Systemd ==
  Upstream patches:
  - core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification 
(d8fdc62037b5)

  $ git describe --contains d8fdc62037b5
  v230~71^2~2

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.21 | xenial-security | source, ...
   systemd | 229-4ubuntu21.22 | xenial-updates  | source, ... <
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.29 | bionic-security | source, ...
   systemd | 237-3ubuntu10.29 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...

  == DBus ==
  Upstream patches:
  - Only read one message at a time if there are fds pending (892f084eeda0)
  - bus: Fix timeout restarts  (529600397bca)
  - DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)

  $ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
  dbus-1.11.10~44
  dbus-1.11.10~45
  dbus-1.11.16~2

  $ rmadison dbus
   dbus | 1.10.6-1ubuntu3| xenial   | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-security  | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-updates   | source, ... <
   dbus | 1.12.2-1ubuntu1| bionic   | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-security  | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-updates   | source, ...

  [Test Case]
  1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
  multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost 
sleep 1 & done

  2) Check for leaked sessions in /run/systemd/system/:
  multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
  drwxr-xr-x 2 root root 160 

[Touch-packages] [Bug 1854976] [NEW] systemd-resolved doesn't work with "host -l" / AXFR queries

[Jose Manuel Santamaria Lema]

Public bug reported:

Hello,

some time ago network-manager in Ubuntu switched from dnsmasq to
systemd-resolved.

When network-manager used dnsmasq to handle DNS, one could use "host -l"
to list all the hosts in a DNS zone, something like this:

$ host -l mydomain.lan
mydomain.lan name server mydns.mydomain.lan
host1.mydomain.lan has address x.x.x.x
host2.mydomain.lan has address x.x.x.x
host3.mydomain.lan has address x.x.x.x
host4.mydomain.lan has address x.x.x.x
[...]

That, unfortunately, no longer works since the switch to systemd-resolved, it 
always fails like this:
$ host -l mydomain.lan
Host mydomain.lan not found: 4(NOTIMP)
; Transfer failed.

And I think that's because systemd-resolved is "filtering" the AXFR
queries issued by "host -l" (I checked the network traffic with tcdump
and that "NOTIMP" comes from the loopback interface).

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

Title:
  systemd-resolved doesn't work with "host -l" / AXFR queries

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  some time ago network-manager in Ubuntu switched from dnsmasq to
  systemd-resolved.

  When network-manager used dnsmasq to handle DNS, one could use "host
  -l" to list all the hosts in a DNS zone, something like this:

  $ host -l mydomain.lan
  mydomain.lan name server mydns.mydomain.lan
  host1.mydomain.lan has address x.x.x.x
  host2.mydomain.lan has address x.x.x.x
  host3.mydomain.lan has address x.x.x.x
  host4.mydomain.lan has address x.x.x.x
  [...]

  That, unfortunately, no longer works since the switch to systemd-resolved, it 
always fails like this:
  $ host -l mydomain.lan
  Host mydomain.lan not found: 4(NOTIMP)
  ; Transfer failed.

  And I think that's because systemd-resolved is "filtering" the AXFR
  queries issued by "host -l" (I checked the network traffic with tcdump
  and that "NOTIMP" comes from the loopback interface).

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

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

[Touch-packages] [Bug 1854877] Re: External HDMI display not working with Intel GPU

[Brian Murray]

** Package changed: kernel-package (Ubuntu) => xorg (Ubuntu)

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

Title:
  External HDMI display not working with Intel GPU

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Asus UX580 laptop with intel and nvidia 1050 video cards under Ubuntu 
19.10. 
  For some reason dual monitor setup with external monitor via HDMI only works 
if I switch to Nvidia only. If I select Intel GPU or "on-demand" in Nvidia 
server settings HDMI out is not working at all - xrandr shows HDMI out 
disconnected.

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

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

[Touch-packages] [Bug 1854877] [NEW] External HDMI display not working with Intel GPU

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have Asus UX580 laptop with intel and nvidia 1050 video cards under Ubuntu 
19.10. 
For some reason dual monitor setup with external monitor via HDMI only works if 
I switch to Nvidia only. If I select Intel GPU or "on-demand" in Nvidia server 
settings HDMI out is not working at all - xrandr shows HDMI out disconnected.

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


** Tags: bot-comment
-- 
External HDMI display not working with Intel GPU
https://bugs.launchpad.net/bugs/1854877
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1853861] Re: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels

[Balint Reczey]

Verified 1.1ubuntu1.18.04.7~16.04.5 on Xenial:

root@uu-x-non-minimal-lp-1838917:~# apt list --upgradable 
Listing... Done
dbus/xenial-proposed 1.10.6-1ubuntu3.5 amd64 [upgradable from: 
1.10.6-1ubuntu3.4]
libdbus-1-3/xenial-proposed 1.10.6-1ubuntu3.5 amd64 [upgradable from: 
1.10.6-1ubuntu3.4]
libglib2.0-0/xenial-proposed 2.48.2-0ubuntu4.5 amd64 [upgradable from: 
2.48.2-0ubuntu4.4]
libglib2.0-data/xenial-proposed 2.48.2-0ubuntu4.5 all [upgradable from: 
2.48.2-0ubuntu4.4]
libpam-modules/xenial-proposed 1.1.8-3.2ubuntu2.2 amd64 [upgradable from: 
1.1.8-3.2ubuntu2.1]
libpam-modules-bin/xenial-proposed 1.1.8-3.2ubuntu2.2 amd64 [upgradable from: 
1.1.8-3.2ubuntu2.1]
libpam-runtime/xenial-proposed 1.1.8-3.2ubuntu2.2 all [upgradable from: 
1.1.8-3.2ubuntu2.1]
libpam-systemd/xenial-proposed 229-4ubuntu21.23 amd64 [upgradable from: 
229-4ubuntu21.22]
libpam0g/xenial-proposed 1.1.8-3.2ubuntu2.2 amd64 [upgradable from: 
1.1.8-3.2ubuntu2.1]
libsqlite3-0/xenial-updates,xenial-security 3.11.0-1ubuntu1.3 amd64 [upgradable 
from: 3.11.0-1ubuntu1.2]
libsystemd0/xenial-proposed 229-4ubuntu21.23 amd64 [upgradable from: 
229-4ubuntu21.22]
libudev1/xenial-proposed 229-4ubuntu21.23 amd64 [upgradable from: 
229-4ubuntu21.22]
linux-tools-common/xenial-updates,xenial-proposed,xenial-security 4.4.0-170.199 
all [upgradable from: 4.4.0-169.198]
login/xenial-proposed 1:4.2-3.1ubuntu5.5 amd64 [upgradable from: 
1:4.2-3.1ubuntu5.4]
passwd/xenial-proposed 1:4.2-3.1ubuntu5.5 amd64 [upgradable from: 
1:4.2-3.1ubuntu5.4]
python3-distupgrade/xenial-updates 1:16.04.29 all [upgradable from: 1:16.04.27]
python3-update-manager/xenial-updates 1:16.04.17 all [upgradable from: 
1:16.04.16]
snapd/xenial-proposed 2.42.1 amd64 [upgradable from: 2.40]
sosreport/xenial-updates 3.6-1ubuntu0.16.04.4 amd64 [upgradable from: 
3.6-1ubuntu0.16.04.3]
systemd/xenial-proposed 229-4ubuntu21.23 amd64 [upgradable from: 
229-4ubuntu21.22]
systemd-sysv/xenial-proposed 229-4ubuntu21.23 amd64 [upgradable from: 
229-4ubuntu21.22]
tshark/xenial-updates,xenial-security 2.6.10-1~ubuntu16.04.0 amd64 [upgradable 
from: 2.0.2+ga16e22e-1]
ubuntu-core-launcher/xenial-proposed 2.42.1 amd64 [upgradable from: 2.40]
ubuntu-release-upgrader-core/xenial-updates 1:16.04.29 all [upgradable from: 
1:16.04.27]
udev/xenial-proposed 229-4ubuntu21.23 amd64 [upgradable from: 229-4ubuntu21.22]
uidmap/xenial-proposed 1:4.2-3.1ubuntu5.5 amd64 [upgradable from: 
1:4.2-3.1ubuntu5.4]
update-manager-core/xenial-updates 1:16.04.17 all [upgradable from: 1:16.04.16]
wireshark-common/xenial-updates,xenial-security 2.6.10-1~ubuntu16.04.0 amd64 
[upgradable from: 2.0.2+ga16e22e-1]
root@uu-x-non-minimal-lp-1838917:~# apt autoremove 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  libdw1 libunwind8 linux-hwe-edge-tools-4.13.0-16 
linux-hwe-edge-tools-4.13.0-17 linux-hwe-edge-tools-4.13.0-19 
linux-tools-4.13.0-16-generic linux-tools-4.13.0-17-generic
  linux-tools-4.13.0-19-generic linux-tools-common
0 upgraded, 0 newly installed, 9 to remove and 27 not upgraded.
After this operation, 14.1 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@uu-x-non-minimal-lp-1838917:~# unattended-upgrade --verbose --debug
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
Using 
(^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^linux-image-unsigned-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*|^linux-buildinfo-[0-9]+\.[0-9\.]+-.*|^linux-source-[0-9]+\.[0-9\.]+-.*|^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^linux-image-unsigned-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*|^linux-buildinfo-[0-9]+\.[0-9\.]+-.*|^linux-source-[0-9]+\.[0-9\.]+-.*)
 regexp to find kernel packages
Using 

[Touch-packages] [Bug 1853861] Re: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels

[Balint Reczey]

Tested 1.1ubuntu1.18.04.13 on Bionic:

root@uu-non-minimal-lp-1838917:~# echo 'Unattended-Upgrade::MinimalSteps 
"false";' > /etc/apt/apt.conf.d/51unattended-upgrades-oneshot
root@uu-non-minimal-lp-1838917:~# yes no | apt autoremove 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  libdw1 libfreetype6 libmaxminddb0 linux-hwe-tools-4.18.0-13 
linux-hwe-tools-4.18.0-14 linux-hwe-tools-4.18.0-15 linux-hwe-tools-4.18.0-16 
linux-hwe-tools-4.18.0-17
  linux-hwe-tools-4.18.0-18 linux-tools-4.18.0-13-generic 
linux-tools-4.18.0-14-generic linux-tools-4.18.0-15-generic 
linux-tools-4.18.0-16-generic
  linux-tools-4.18.0-17-generic linux-tools-4.18.0-18-generic linux-tools-common
0 upgraded, 0 newly installed, 16 to remove and 18 not upgraded.
After this operation, 133 MB disk space will be freed.
Do you want to continue? [Y/n] Abort.
root@uu-non-minimal-lp-1838917:~# apt list --upgradable 
Listing... Done
libnss-systemd/bionic-updates 237-3ubuntu10.33 amd64 [upgradable from: 
237-3ubuntu10.31]
libpam-systemd/bionic-updates 237-3ubuntu10.33 amd64 [upgradable from: 
237-3ubuntu10.31]
libpython3.6/bionic-updates 3.6.9-1~18.04 amd64 [upgradable from: 
3.6.8-1~18.04.3]
libpython3.6-minimal/bionic-updates 3.6.9-1~18.04 amd64 [upgradable from: 
3.6.8-1~18.04.3]
libpython3.6-stdlib/bionic-updates 3.6.9-1~18.04 amd64 [upgradable from: 
3.6.8-1~18.04.3]
libsystemd0/bionic-updates 237-3ubuntu10.33 amd64 [upgradable from: 
237-3ubuntu10.31]
libudev1/bionic-updates 237-3ubuntu10.33 amd64 [upgradable from: 
237-3ubuntu10.31]
linux-tools-common/bionic-updates,bionic-security 4.15.0-72.81 all [upgradable 
from: 4.15.0-70.79]
python3-distupgrade/bionic-updates 1:18.04.36 all [upgradable from: 1:18.04.34]
python3.6/bionic-updates 3.6.9-1~18.04 amd64 [upgradable from: 3.6.8-1~18.04.3]
python3.6-minimal/bionic-updates 3.6.9-1~18.04 amd64 [upgradable from: 
3.6.8-1~18.04.3]
snapd/bionic-updates 2.42.1+18.04 amd64 [upgradable from: 2.40+18.04]
sosreport/bionic-updates 3.6-1ubuntu0.18.04.4 amd64 [upgradable from: 
3.6-1ubuntu0.18.04.3]
systemd/bionic-updates 237-3ubuntu10.33 amd64 [upgradable from: 
237-3ubuntu10.31]
systemd-sysv/bionic-updates 237-3ubuntu10.33 amd64 [upgradable from: 
237-3ubuntu10.31]
tshark/bionic-updates,bionic-security 2.6.10-1~ubuntu18.04.0 amd64 [upgradable 
from: 2.4.5-1]
ubuntu-release-upgrader-core/bionic-updates 1:18.04.36 all [upgradable from: 
1:18.04.34]
udev/bionic-updates 237-3ubuntu10.33 amd64 [upgradable from: 237-3ubuntu10.31]
wireshark-common/bionic-updates,bionic-security 2.6.10-1~ubuntu18.04.0 amd64 
[upgradable from: 2.4.5-1]
root@uu-non-minimal-lp-1838917:~# unattended-upgrade --verbose --debug
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
Using 
(^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^linux-image-unsigned-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*|^linux-buildinfo-[0-9]+\.[0-9\.]+-.*|^linux-source-[0-9]+\.[0-9\.]+-.*|^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^linux-image-unsigned-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*|^linux-buildinfo-[0-9]+\.[0-9\.]+-.*|^linux-source-[0-9]+\.[0-9\.]+-.*)
 regexp to find kernel packages
Using 

[Touch-packages] [Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`

[Brian Murray]

** Tags removed: rls-ff-incoming

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

Title:
  bash completion shows `awk: line 18: function gensub never defined` on
  `umount /dev/`

Status in bash-completion package in Ubuntu:
  Triaged
Status in gawk package in Ubuntu:
  Invalid
Status in mawk package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in bash-completion source package in Focal:
  Triaged
Status in gawk source package in Focal:
  Invalid
Status in mawk source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Invalid
Status in Debian:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 19.10 using minimal desktop option
  2. Open terminal and enter `umount /dev/s` and then hit 

  Expected result:
  * bash completion works as expected

  Actual results:
  * bash completion does not work :

  $ umount /dev/awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  
  $ umount /meawk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bash-completion 1:2.9-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Sep 26 18:46:59 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-09-26 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package udev 242-7ubuntu3.2 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

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

Bug description:
  error during boot

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: udev 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Wed Nov 27 11:46:55 2019
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  MachineType: LENOVO 20HHS08K00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=026e18db-56ea-4610-9832-7874316245ad ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python3.6, Python 3.6.7, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: systemd
  Title: package udev 242-7ubuntu3.2 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (62 days ago)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET72W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHS08K00
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET72W(1.46):bd10/04/2018:svnLENOVO:pn20HHS08K00:pvrThinkPadP51:rvnLENOVO:rn20HHS08K00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHS08K00
  dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1650961] Re: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106

[maarten]

affects me on 19.10

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

Title:
  ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS
  endpoint with error -106

Status in apport package in Ubuntu:
  Invalid

Bug description:
  caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux
  caravena@caravena-530U3C-530U4C:~$ 
[12375:12409:1218/134054:ERROR:nss_util.cc(809)] After loading Root Certs, 
loaded==false: NSS error code: -8018
  Se creó una nueva ventana en la sesión existente del navegador.
  [7185:7220:1218/142107:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -106
  [7185:7318:1218/142111:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7318:1218/142115:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7220:1218/142117:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -105
  [7185:7220:1218/143613:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -106
  [7185:7318:1218/144540:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7220:1218/145430:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -106
  [7185:7318:1218/162533:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7220:1218/162540:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -21
  [7185:7318:1218/162540:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux
  caravena@caravena-530U3C-530U4C:~$ 
[18327:18362:1218/165822:ERROR:nss_util.cc(809)] After loading Root Certs, 
loaded==false: NSS error code: -8018

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 18 17:32:53 2016
  InstallationDate: Installed on 2015-07-26 (511 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago)

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

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

[Touch-packages] [Bug 1854590] Re: No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)

[Brian Murray]

** Package changed: update-manager (Ubuntu) => xorg (Ubuntu)

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

Title:
  No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately
  equal)

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know much, so forgive me if I use the wrong terminology.

  Problem:
  There is no ComposeKey mapping for the symbols ≈ (Unicode 2248) and ≅ 
(Unicode 2248) in Compose Tables.

  Details:
  According to  https://help.ubuntu.com/community/ComposeKey  the files such as 
 /usr/share/X11/locale/en_US.UTF-8/Compose  have all ComposeKey combinations to 
type special symbols, characters and graphemes.
  Two standard graphemes (≈ and ≅) seem to be missing from multiple compose 
files although their negated versions (are present mapped to compositions

  Solution?!: I propose this (but wouldn't know how to commit it except by 
filing a bug - if it's straightforward to improve Linux, then please tell me 
how!  I'd love to commit something to the code!
  I added these lines to a copy of the  compose  file that I made at ~/.Xcompose
  I propose that they should be added to the multiple, original  Compose  files 
in:
/usr/share/X11/locale/en_US.UTF-8/Compose
/usr/share/X11/locale/iso8859-1/Compose
/usr/share/X11/locale/iso8859-15/Compose
   etc etc etc

  # _Added by Jackalux_
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
 : "≈"   U2248 # ALMOST EQUAL TO
  # End of Jackalux's additions

  
  Notes:
  The list at 
https://www.x.org/releases/X11R7.7/doc/libX11/i18n/compose/en_US.UTF-8.html 
also misses combinations for ≈ and ≅ .   Perhaps that should be updated too if 
it is a reference list.

  I also wanted to add:
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
  But I've realised that they create clashes with other compositions, as the 
composition forms before the ComposeKey is released.
  If this can be corrected and added at the same time, then that would be 
amazing as I don't know how to access the actual compositions listed for those 
characters.

  Co-operatively,
  Jackalux

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Dan Streetman]

I can't reproduce this, can you provide specific cmdline steps to
reproduce please.


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

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1854506] Re: package udev 242-7ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

[Dan Streetman]

You appear to have a problem in the kernel, this isn't a bug in
systemd/udev:

[1015211.431369] printk: systemd: 94 output lines suppressed due to ratelimiting
[1015211.435009] systemd[1]: systemd 242 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 
default-hierarchy=hybrid)
[1015211.453068] systemd[1]: Detected architecture x86-64.
[1015352.369048] INFO: task systemd:1 blocked for more than 120 seconds.
[1015352.369055]   Tainted: P   OE 5.3.0-23-generic #25-Ubuntu
[1015352.369058] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[1015352.369062] systemd D0 1  0 0x
[1015352.369066] Call Trace:
[1015352.369079]  __schedule+0x2b9/0x6c0
[1015352.369086]  ? page_add_file_rmap+0xe4/0x170
[1015352.369092]  schedule+0x42/0xb0
[1015352.369097]  schedule_preempt_disabled+0xe/0x10
[1015352.369102]  __mutex_lock.isra.0+0x182/0x4f0
[1015352.369106]  ? _cond_resched+0x19/0x30
[1015352.369113]  ? security_capable+0x47/0x70
[1015352.369118]  __mutex_lock_slowpath+0x13/0x20
[1015352.369123]  mutex_lock+0x2e/0x40
[1015352.369129]  __do_sys_reboot+0xaf/0x210
[1015352.369135]  ? ep_insert+0x33e/0x4c0
[1015352.369139]  ? ep_show_fdinfo+0x90/0x90
[1015352.369145]  ? __x64_sys_epoll_ctl+0x2f8/0x840
[1015352.369151]  __x64_sys_reboot+0x1e/0x20
[1015352.369157]  do_syscall_64+0x5a/0x130
[1015352.369164]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[1015352.369169] RIP: 0033:0x7f499f94f5f7
[1015352.369179] Code: Bad RIP value.
[1015352.369182] RSP: 002b:7ffcbd047a38 EFLAGS: 0246 ORIG_RAX: 
00a9
[1015352.369186] RAX: ffda RBX: 5597fa0fa690 RCX: 
7f499f94f5f7
[1015352.369188] RDX:  RSI: 28121969 RDI: 
fee1dead
[1015352.369190] RBP:  R08: 5597fa0fb760 R09: 

[1015352.369192] R10: 7ffcbd0479cc R11: 0246 R12: 

[1015352.369194] R13: 7ffcbd047a80 R14: 003e R15: 
003f


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

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

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

Title:
  package udev 242-7ubuntu3.2 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  error during boot

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: udev 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules
  Date: Wed Nov 27 11:46:55 2019
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  MachineType: LENOVO 20HHS08K00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=026e18db-56ea-4610-9832-7874316245ad ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python3.6, Python 3.6.7, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: systemd
  Title: package udev 242-7ubuntu3.2 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (62 days ago)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET72W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHS08K00
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET72W(1.46):bd10/04/2018:svnLENOVO:pn20HHS08K00:pvrThinkPadP51:rvnLENOVO:rn20HHS08K00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHS08K00
  dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1854590] [NEW] No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I don't know much, so forgive me if I use the wrong terminology.

Problem:
There is no ComposeKey mapping for the symbols ≈ (Unicode 2248) and ≅ (Unicode 
2248) in Compose Tables.

Details:
According to  https://help.ubuntu.com/community/ComposeKey  the files such as  
/usr/share/X11/locale/en_US.UTF-8/Compose  have all ComposeKey combinations to 
type special symbols, characters and graphemes.
Two standard graphemes (≈ and ≅) seem to be missing from multiple compose files 
although their negated versions (are present mapped to compositions

Solution?!: I propose this (but wouldn't know how to commit it except by filing 
a bug - if it's straightforward to improve Linux, then please tell me how!  I'd 
love to commit something to the code!
I added these lines to a copy of the  compose  file that I made at ~/.Xcompose
I propose that they should be added to the multiple, original  Compose  files 
in:
  /usr/share/X11/locale/en_US.UTF-8/Compose
  /usr/share/X11/locale/iso8859-1/Compose
  /usr/share/X11/locale/iso8859-15/Compose
 etc etc etc

# _Added by Jackalux_
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
 : "≈"   U2248 # ALMOST EQUAL TO
# End of Jackalux's additions


Notes:
The list at 
https://www.x.org/releases/X11R7.7/doc/libX11/i18n/compose/en_US.UTF-8.html 
also misses combinations for ≈ and ≅ .   Perhaps that should be updated too if 
it is a reference list.

I also wanted to add:
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
But I've realised that they create clashes with other compositions, as the 
composition forms before the ComposeKey is released.
If this can be corrected and added at the same time, then that would be amazing 
as I don't know how to access the actual compositions listed for those 
characters.

Co-operatively,
Jackalux

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

-- 
No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)
https://bugs.launchpad.net/bugs/1854590
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1815110] Re: CMake configuration files are missing

[Nero Burner]

v0.4.0 cmake does not create and install a pkgconfig/libglog.pc file

current master generates the pkgconfig file since commit
https://github.com/google/glog/commit/82d0860b76cf7a35d6911fecdccae15a4296cfd2

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

Title:
  CMake configuration files are missing

Status in google-glog package in Ubuntu:
  Confirmed

Bug description:
  The CMake configuration files are only generated if CMake is used when 
building this package instead of autotools (see [1]).
  I think it would be really nice if the ubunu package would include the cmake 
configure files in /lib/cmake/glog/ either by maually adding them or by 
switching the package build to CMake.

  [1] https://github.com/google/glog/issues/4#issuecomment-442001197

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-glog/+bug/1815110/+subscriptions

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

[Touch-packages] [Bug 1815110] Re: CMake configuration files are missing

[Launchpad Bug Tracker]

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

** Changed in: google-glog (Ubuntu)
   Status: New => Confirmed

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

Title:
  CMake configuration files are missing

Status in google-glog package in Ubuntu:
  Confirmed

Bug description:
  The CMake configuration files are only generated if CMake is used when 
building this package instead of autotools (see [1]).
  I think it would be really nice if the ubunu package would include the cmake 
configure files in /lib/cmake/glog/ either by maually adding them or by 
switching the package build to CMake.

  [1] https://github.com/google/glog/issues/4#issuecomment-442001197

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-glog/+bug/1815110/+subscriptions

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

[Touch-packages] [Bug 1764172] Re: Unable to change hostname from the one specified during Bionic server installation

[Michael Hudson-Doyle]

Ah oops, this one fell through the cracks. Should try to do a quick fix.

** Package changed: subiquity (Ubuntu) => subiquity

** Changed in: subiquity
   Status: New => Triaged

** Changed in: subiquity
   Importance: Undecided => High

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

Title:
  Unable to change hostname from the one specified during Bionic server
  installation

Status in subiquity:
  Triaged
Status in Release Notes for Ubuntu:
  New
Status in hostname package in Ubuntu:
  Confirmed

Bug description:
  In Bionic Beta 2 I am not able on a host or in a guest VM to change
  the hostname of a Bionic Beta 2 installation by changing
  /etc/hostname. The name in the file can be changed but it always
  reverts to the hostname configured during installation.

  In the following thread on the topic it is suggested to remove a
  number of cloud packages. When doing this in a VM install I could
  change the hostname again via /etc/hostname.

  https://ubuntuforums.org/showthread.php?t=2389098=2

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

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