[Touch-packages] [Bug 1656024] Re: Units using PrivateNetwork=yes don't work inside user namespaces

[Michael]

This might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635382

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

Title:
  Units using PrivateNetwork=yes don't work inside user namespaces

Status in systemd package in Ubuntu:
  Won't Fix
Status in varnish package in Ubuntu:
  New

Bug description:
  lxd host is Ubuntu 17.04 Alpha amd64
  lxd container is ubuntu:16.10

  hostnamectl does not work inside the lxd container:

  $ hostnamectl status
  $ sudo hostnamectl set-hostname server.example.com
  Could not set property: Connection timed out

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


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

[Touch-packages] [Bug 1635382] Re: PrivateNetwork=yes (hostnamed, localed) does not work in lxd

[Michael]

This might actually be apparmor on the LXD host denying the container?

Look for messages like:

   2023-06-23T09:53:56.040427+08:00 grook kernel: [772843.931461] audit: 
type=1400 audit(1687485236.036:118): apparmor="DENIED" operation="file_lock" 
profile="lxd-pat_" pid=3334600 comm="(.plocate)" family="unix" 
sock_type="dgram" protocol=0 requested_mask="send"
   2023-06-23T09:53:56.040437+08:00 grook kernel: [772843.931469] audit: 
type=1400 audit(1687485236.036:119): apparmor="DENIED" operation="file_lock" 
profile="lxd-pat_" pid=3334600 comm="(.plocate)" family="unix" 
sock_type="dgram" protocol=0 requested_mask="send"

In my case, plocate-updatedb.service (and systemd-hostnamed.service)
fails to run inside containers when PrivateNetwork is enabled).

See also https://bugs.debian.org/1038315

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

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

Title:
  PrivateNetwork=yes (hostnamed, localed) does not work in lxd

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  $ lxc launch ubuntu-daily:yakkety y-hostname1
  $ sleep 10
  $ lxc exec y-hostname1 -- hostnamectl set-hostname smoser
  
  Could not set property: Connection timed out

  $ lxc exec y-hostname1 -- systemctl status --no-pager -l systemd-hostnamed 
  ● systemd-hostnamed.service - Hostname Service
 Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2016-10-20 19:19:16 UTC; 1min 
9s ago
   Docs: man:systemd-hostnamed.service(8)
 man:hostname(5)
 man:machine-info(5)
 http://www.freedesktop.org/wiki/Software/systemd/hostnamed
Process: 561 ExecStart=/lib/systemd/systemd-hostnamed (code=exited, 
status=225/NETWORK)
   Main PID: 561 (code=exited, status=225/NETWORK)

  Oct 20 19:19:16 y-hostname1 systemd[1]: Starting Hostname Service...
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Main 
process exited, code=exited, status=225/NETWORK
  Oct 20 19:19:16 y-hostname1 systemd[1]: Failed to start Hostname Service.
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Unit 
entered failed state.
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Failed 
with result 'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 20 19:02:29 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

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


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

[Touch-packages] [Bug 2024558] Re: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

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

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  sdo do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-75-generic 5.15.0-75.82
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 21 10:56 seq
   crw-rw 1 root audio 116, 33 Jun 21 10:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Wed Jun 21 10:58:36 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /sys/bus/usb/devices/usb1/rx_lanes: No such file or directory
   /sys/bus/usb/devices/usb1/tx_lanes: No such file or directory
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: DigitalOcean Droplet
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz boot=live skipconfig 
fromiso=live/rescue_rootfs.squashfs net.ifnames=0 ---
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-06-21 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.board.asset.tag: 360900599
  dmi.board.name: Droplet
  dmi.board.vendor: DigitalOcean
  dmi.board.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-6.1
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:rvnDigitalOcean:rnDroplet:rvr20171212:cvnQEMU:ct1:cvrpc-i440fx-6.1:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

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


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

[Touch-packages] [Bug 2024898] [NEW] Manual updates blocked by unattended-upgrade

[Menno]

Public bug reported:

Observed behaviour:

When I boot my PC or wake it from suspend, it usually gives a desktop 
notification about available updates.
Trying to apply the updates often results in this kind of error:

E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process
3522905 (unattended-upgr)

lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04

Desired behaviour: have these two play nice with each other.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: unattended-upgrades 2.9.1+nmu2ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
Uname: Linux 6.2.0-23-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Jun 23 14:02:24 2023
InstallationDate: Installed on 2021-02-06 (866 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: Upgraded to lunar on 2023-04-23 (61 days ago)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "1";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2023-04-23T13:43:35.349235

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar

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

Title:
  Manual updates blocked by unattended-upgrade

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Observed behaviour:

  When I boot my PC or wake it from suspend, it usually gives a desktop 
notification about available updates.
  Trying to apply the updates often results in this kind of error:

  E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by
  process 3522905 (unattended-upgr)

  lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04

  Desired behaviour: have these two play nice with each other.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: unattended-upgrades 2.9.1+nmu2ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Jun 23 14:02:24 2023
  InstallationDate: Installed on 2021-02-06 (866 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (61 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2023-04-23T13:43:35.349235

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


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

[Touch-packages] [Bug 2024889] Re: Laptop screen show an one pixel row corruption

[Ubuntu Foundations Team Bug Bot]

** Package changed: 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/2024889

Title:
  Laptop screen show an one pixel row corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Asus TUF F15 RTX4060 gaming laptop with external LG 4k monitor.
  All runs very smooth until today appears only on laptop screen one pixel row 
corruption.
  What is weird on this row? It show up at any resolution and copy X-position 
of window Color by movement any windows on screen.

  I think is from Xorg. because I restarted many times and replaced
  nvidia open-source to proprietary drivers. Still appears this row.

  I have dual boot with Windows 11 and here it not happen any screen issues.
  So must be in Ubuntu OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Jun 23 11:33:43 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:277d]
   NVIDIA Corporation Device [10de:28e0] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:277d]
  InstallationDate: Installed on 2023-06-13 (9 days ago)
  InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX507ZV4_FX507ZV4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=7a64d27e-63d8-449f-b29f-df2b76bfaab2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2023
  dmi.bios.release: 5.26
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX507ZV4.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX507ZV4
  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.ec.firmware.release: 0.67
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX507ZV4.315:bd05/11/2023:br5.26:efr0.67:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX507ZV4_FX507ZV4:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX507ZV4:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX507ZV4_FX507ZV4
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface

[Danilo Egea Gondolfo]

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

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

Title:
  Unable to configure Wireguard connection at NetworkManager interface

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Repro steps:

  1) Open NetworkManager GUI.
  2) Click "Add new Connection" and select "Wireguard" connection type.
  3) Then you have to configure new connection. Basic configuration looks like 
that:
  a) Write down connection name,
  b) Write down local private key,
  c) Create new peer and populate peer's parameters: public key of the 
peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port.
  4) Click "OK" and "Save".
  5) Open "Peers" again. Ensure that settings were not stored. All fields are 
empty.

  Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager 
interface.
  netplan.io 0.106.1-2
  network-manager 1.42.4-1ubuntu7

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


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

[Touch-packages] [Bug 2023462] Re: chromeos_pstore.service started on non chrome platform hardware.

[Nick Rosbrook]

Yeah, fair enough. This does also result in extra kernel modules being
loaded that are not needed, even when systemd-pstore.service is skipped
since /sys/fs/pstore is empty. I don't think this is a huge deal, but it
would probably be nice to clean it up for an LTS indeed.

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

** Changed in: systemd (Ubuntu Jammy)
   Importance: Wishlist => Low

** Tags added: systemd-sru-next

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

Title:
  chromeos_pstore.service started on non chrome platform hardware.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged

Bug description:
  systemd-analyze blame | grep pstore

  110ms modprobe@chromeos_pstore.service
  5ms modprobe@efi_pstore.service
  5ms modprobe@pstore_blk.service
  3ms modprobe@pstore_zone.service

  /lib/systemd/system/systemd-pstore.service

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


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

[Touch-packages] [Bug 1966775] Re: systemd-resolved fails resolution via TCP

[Nick Rosbrook]

I cannot reproduce this on Focal:

root@focal:~# nslookup pod51041.outlook.com
;; Truncated, retrying in TCP mode.
Server: 127.0.0.53
Address:127.0.0.53#53

Non-authoritative answer:
Name:   pod51041.outlook.com
Address: 52.96.122.34
Name:   pod51041.outlook.com
Address: 52.96.163.50
[... snip ...]

root@focal:~# time dig +noanswer _noedns toomany.ddstreet.org

; <<>> DiG 9.16.1-Ubuntu <<>> +noanswer _noedns toomany.ddstreet.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61517
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;_noedns.   IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Fri Jun 23 15:07:15 UTC 2023
;; MSG SIZE  rcvd: 36

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60109
;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;toomany.ddstreet.org.  IN  A

;; Query time: 176 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Fri Jun 23 15:07:16 UTC 2023
;; MSG SIZE  rcvd: 689


real0m0.204s
user0m0.011s
sys 0m0.019s
root@focal:~# resolvectl status
Global
   LLMNR setting: no  
MulticastDNS setting: no  
  DNSOverTLS setting: no  
  DNSSEC setting: no  
DNSSEC supported: no  
  DNSSEC NTA: 10.in-addr.arpa 
  16.172.in-addr.arpa 
  168.192.in-addr.arpa
  17.172.in-addr.arpa 
  18.172.in-addr.arpa 
  19.172.in-addr.arpa 
  20.172.in-addr.arpa 
  21.172.in-addr.arpa 
  22.172.in-addr.arpa 
  23.172.in-addr.arpa 
  24.172.in-addr.arpa 
  25.172.in-addr.arpa 
  26.172.in-addr.arpa 
  27.172.in-addr.arpa 
  28.172.in-addr.arpa 
  29.172.in-addr.arpa 
  30.172.in-addr.arpa 
  31.172.in-addr.arpa 
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan 
  local   
  private 
  test

Link 8 (eth0)
  Current Scopes: DNS
DefaultRoute setting: yes
   LLMNR setting: yes
MulticastDNS setting: no 
  DNSOverTLS setting: no 
  DNSSEC setting: no 
DNSSEC supported: no 
  Current DNS Server: 10.136.78.1
 DNS Servers: 10.136.78.1
  DNS Domain: lxd 

Are you still seeing this issue?

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

Title:
  systemd-resolved fails resolution via TCP

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  It happened in one of our production instances.
  Suddenly fails to resolve the hostname.
  Later I found it has happened if the DNS response message is bigger than 512 
bytes.
  But never reproduced from other instances which have the same instance 
template.

  with nslookup
  ```bash
  $ nslookup pod51041.outlook.com
  ;; Truncated, retrying in TCP mode.
  ;; Connection to 127.0.0.53#53(127.0.0.53) for pod51041.outlook.com failed: 
timed out.
  ```

  and dig with another address.
  ```bash
  $ time dig +noanswer +noedns toomany.ddstreet.org
  ;; Truncated, retrying in TCP mode.
  ;; Connection to 127.0.0.53#53(127.0.0.53) for toomany.ddstreet.org failed: 
timed out.

  real0m7.070s
  user0m0.004s
  sys 0m0.004s
  ```

  system versions
  ```bash
  $ systemctl --version
  systemd 245 (245.4-4ubuntu3.15)
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 
default-hierarchy=hybrid
  $ cat /etc/os-release
  NAME="Ubuntu"
  VERSION="20.04.2 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.2 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  $ uname -r
  5.8.0-1041-aws
  ```

  status
  ```bash
  $ resolvectl status

[Touch-packages] [Bug 1965328] Re: transient scope could not be started error in bionic lxd container

[Nick Rosbrook]

Is this still an issue? I tried running a bionic LXD container from a
Lunar host, and in the container I was able to run the snap without
issues.

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

Title:
  transient scope could not be started error in bionic lxd container

Status in Snappy:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On my impish development host machine I tend to use lxd containers to
  support snap building and other tasks targeting different releases.
  Today I came to use a bionic container as per usual and found that I
  could not invoke any snap applications. I installed hello-world as the
  most simple test of running a snap app:

  ```
  ubuntu@b:~$ hello-world
  internal error, please report: running "hello-world" failed: transient scope 
could not be started, job /org/freedesktop/systemd1/job/44 finished with result 
failed
  ```

  I made sure the container had up to date packages in it (apt & snaps)
  and rebooted it. But the problem persisted. I then created a second
  container and installed hello-world in it and again the problem was
  reproducible. At the time of producing the following attachments I had
  not attempted to reboot the host.

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


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

[Touch-packages] [Bug 1967640] Re: package udev 249.11-0ubuntu2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

[Nick Rosbrook]

This is from when Jammy was still the devel series. Sorry that this
wasn't looked at then.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package udev 249.11-0ubuntu2 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I don't know anything Ubuntu just told me there was a bug and I just
  sent a report

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.snapd.rules
  Date: Sun Mar 27 21:35:10 2022
  Df:
   Sys. de fichiers blocs de 1K   Utilisé Disponible Uti% Monté sur
   tmpfs 340860  1108 339752   1% /run
   /dev/sda6  402122632 115920796  265959416  31% /
   tmpfs1704296 01704296   0% /dev/shm
   tmpfs   5120 0   5120   0% /run/lock
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2022-03-27 (6 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=4082b1cb-5861-4f76-b7d1-278936a44624 ro quiet splash vt.handoff=7
  Python3Details: /usr/local/bin/python3.10, Python 3.10.4, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu1
   apt  2.4.3
  SourcePackage: systemd
  Title: package udev 249.11-0ubuntu2 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 81B3
  dmi.board.vendor: HP
  dmi.board.version: 00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/03/2017:br4.6:svnHP:pn:pvr:rvnHP:rn81B3:rvr00:cvnHP:ct3:cvr:sku:
  dmi.product.family: 103C_53316J
  dmi.sys.vendor: HP

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


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

[Touch-packages] [Bug 1938058] Re: systemd-time-wait-sync.service should be part of systemd-timesyncd package

[Nick Rosbrook]

** Changed in: systemd (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  systemd-time-wait-sync.service should be part of systemd-timesyncd
  package

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  [impact]

  systemd-time-wait-sync service never completes when systemd-timesyncd
  package is not installed

  [test case]

  remove the systemd-timesyncd package and enable the systemd-time-wait-
  sync service, and reboot. Check status of the service to see it's
  stuck in 'activating' state, e.g.:

  ubuntu@lp1937238-f:~$ sudo systemctl status systemd-time-wait-sync.service
  ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
   Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; 
enabled; vendor preset: enabled)
   Active: activating (start) since Fri 2021-07-23 15:32:12 UTC; 19s ago

  [regression potential]

  TBD

  [scope]

  this is needed in f and later

  the systemd-timesyncd package was split out from the main systemd
  package starting in focal, so this problem exists in f and later

  the service doesn't exist in b, so this is not needed there

  [other info]

  originally noticed in bug 1937238, but create this new bug in case
  that bug was actually a separate problem

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


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

[Touch-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface

[Danilo Egea Gondolfo]

After some more digging, turns out it's not a problem with Netplan.
Although, the problem will manifest depending on how Netplan generates
the configuration for Network Manager.

When selecting the option to store the private key in the KDE wallet
agent, the option "private-key-flags=1" will be added to the resulting
.nmconnection file and the private key will be omitted.

In this case, all the properties set in the group [wireguard] in the
keyfile are not supported by the netplan's keyfile parser and will be
left to be added to the keyfile *after* the wireguard peers, like this:

-
[connection]
id=wg0
type=wireguard
...

[wireguard-peer.M9nt4YujIOmNrRmpIRTmYSfMdrpvE7u6WkG8FY8WjG4=]
endpoint=10.20.30.40:51820
allowed-ips=0.0.0.0/0;

[wireguard]
#Netplan: passthrough setting
private-key-flags=1
#Netplan: passthrough setting
listen-port=51820
---

For some reason, Network Manager will load the connection but *will not*
load the wireguard-peer section.

Moving the [wireguard] section to above [wireguard-peer...] resolves the
issue.

I can't find a reference that says that [wireguard] is supposed to come
before [wireguard-peer].

A workaround you can use while we work on a fix is not use the option to
encrypt the private key and store it in the network manager
.nmconnection file.

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

Title:
  Unable to configure Wireguard connection at NetworkManager interface

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Repro steps:

  1) Open NetworkManager GUI.
  2) Click "Add new Connection" and select "Wireguard" connection type.
  3) Then you have to configure new connection. Basic configuration looks like 
that:
  a) Write down connection name,
  b) Write down local private key,
  c) Create new peer and populate peer's parameters: public key of the 
peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port.
  4) Click "OK" and "Save".
  5) Open "Peers" again. Ensure that settings were not stored. All fields are 
empty.

  Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager 
interface.
  netplan.io 0.106.1-2
  network-manager 1.42.4-1ubuntu7

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


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

[Touch-packages] [Bug 1932176] Re: localed-locale test fails for hirsute systemd armhf

[Nick Rosbrook]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  localed-locale test fails for hirsute systemd armhf

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  For both systemd in release (247.3-3ubuntu3) and proposed
  (247.3-3ubuntu3.1) armhf tests seem to either time out or fail on
  localed-locale:

  autopkgtest [18:35:04]: test localed-locale: [---
  Generating locales (this might take a while)...
en_US.UTF-8... done
  Generation complete.
  locale 'de_DE.UTF-8' not available
  de_DE.UTF-8 UTF-8
  FAIL: expected: '' actual: 'Failed to issue method call: Connection 
timed out'
  autopkgtest [18:37:14]: test localed-locale: ---]
  autopkgtest [18:37:20]: test localed-locale:  - - - - - - - - - - results - - 
- - - - - - - -
  localed-locale   FAIL non-zero exit status 1
  autopkgtest [18:37:20]: test localed-locale:  - - - - - - - - - - stderr - - 
- - - - - - - -
  FAIL: expected: '' actual: 'Failed to issue method call: Connection 
timed out'

  Example logs:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210607_164324_2051c@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210602_161751_0b805@/log.gz

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


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

[Touch-packages] [Bug 1938058] Re: systemd-time-wait-sync.service should be part of systemd-timesyncd package

[Nick Rosbrook]

Not sure yet about SRU'ing this, but this should at least be fixed in
devel.

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

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

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

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

** Tags added: foundations-todo

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

Title:
  systemd-time-wait-sync.service should be part of systemd-timesyncd
  package

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Focal:
  Triaged
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  [impact]

  systemd-time-wait-sync service never completes when systemd-timesyncd
  package is not installed

  [test case]

  remove the systemd-timesyncd package and enable the systemd-time-wait-
  sync service, and reboot. Check status of the service to see it's
  stuck in 'activating' state, e.g.:

  ubuntu@lp1937238-f:~$ sudo systemctl status systemd-time-wait-sync.service
  ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
   Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; 
enabled; vendor preset: enabled)
   Active: activating (start) since Fri 2021-07-23 15:32:12 UTC; 19s ago

  [regression potential]

  TBD

  [scope]

  this is needed in f and later

  the systemd-timesyncd package was split out from the main systemd
  package starting in focal, so this problem exists in f and later

  the service doesn't exist in b, so this is not needed there

  [other info]

  originally noticed in bug 1937238, but create this new bug in case
  that bug was actually a separate problem

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


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

[Touch-packages] [Bug 696098] Re: cron @reboot rules fail for users wuth autofs homes, due to missing upstart dependancy

[Peter Benie]

I am using systemd rather than upstart, but the bug is the same: cron
depends on remote-fs.target, autofs depends on remote-fs.target, so they
start together. The result is that the job is run with the working
directory set to /var/spool/cron.

What cron should be waiting for is home directories being available, but
there doesn't seem to be a suitable systemd target for to achieve this.

The attached patch makes cron detect failure to chdir to the home
directory; failure to chdir is treated as a critical error and the job
is not started.

In addition, if some reboot jobs don't start due to the home directory
not being available, this will try them for up to 5 times before giving
up (about 5 minutes).


** Patch added: "cron-reboot.patch"
   
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/696098/+attachment/5681677/+files/cron-reboot.patch

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

Title:
  cron @reboot rules fail for users wuth autofs homes, due to missing
  upstart dependancy

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cron

  If a user has a @reboot cron entry like:
  ===
  @reboot date >> date.log
  ===

  And their home directory is mounted by autofs into /home

  then, the job will fail during a machine reboot because the
  cron service starts before autofs service.

  I think this is a missing dependency between in the cron upstart
  configuration, to fix this I think that cron should be started after
  autofs (only when autofs is enabled).

  
  ProblemType: Bug
  Architecture: amd64
  Date: Fri Dec 31 12:32:49 2010
  Dependencies:
   adduser 3.112ubuntu1
   base-files 5.0.0ubuntu23
   base-passwd 3.5.22
   coreutils 8.5-1ubuntu3
   debconf 1.5.32ubuntu3
   debconf-i18n 1.5.32ubuntu3
   debianutils 3.2.3
   dpkg 1.15.8.4ubuntu3
   findutils 4.4.2-1ubuntu1
   gcc-4.5-base 4.5.1-7ubuntu2
   libacl1 2.2.49-3
   libattr1 1:2.4.44-2
   libbz2-1.0 1.0.5-4ubuntu1
   libc-bin 2.12.1-0ubuntu10
   libc6 2.12.1-0ubuntu10
   libdb4.8 4.8.30-1
   libgcc1 1:4.5.1-7ubuntu2
   liblocale-gettext-perl 1.05-6
   liblzma2 4.999.9beta+20100527-1
   libncurses5 5.7+20100626-0ubuntu1
   libpam-modules 1.1.1-4ubuntu2
   libpam-runtime 1.1.1-4ubuntu2
   libpam0g 1.1.1-4ubuntu2
   libselinux1 2.0.94-1
   libtext-charwidth-perl 0.04-6
   libtext-iconv-perl 1.7-2
   libtext-wrapi18n-perl 0.06-7
   lsb-base 4.0-0ubuntu8
   ncurses-bin 5.7+20100626-0ubuntu1
   passwd 1:4.1.4.2-1ubuntu3
   perl-base 5.10.1-12ubuntu2
   sed 4.2.1-7
   sensible-utils 0.0.4ubuntu1
   tzdata 2010o-0ubuntu0.10.10
   xz-utils 4.999.9beta+20100527-1
   zlib1g 1:1.2.3.4.dfsg-3ubuntu1
  DistroRelease: Ubuntu 10.10
  NonfreeKernelModules: nvidia
  Package: cron 3.0pl1-114ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  SourcePackage: cron
  Tags: maverick
  Uname: Linux 2.6.35-24-generic x86_64

  
  /etc/init/cron.conf
  ===
  # cron - regular background program processing daemon
  #
  # cron is a standard UNIX program that runs user-specified programs at
  # periodic scheduled times

  description "regular background program processing daemon"

  start on runlevel [2345]
  stop on runlevel [!2345]

  expect fork
  respawn

  exec cron
  ===

  ps aux | grep -E '(automount|cron)'
  root  1542  0.0  0.0  21128   628 ?Ss   Dec23   0:01 cron
  root  1867  0.0  0.0 123208  1044 ?Ssl  Dec23   0:02 
/usr/sbin/automount

  cron has a lower pid so it started first...

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


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

[Touch-packages] [Bug 1934456] Re: The "hostnamectl" command does not modify the hosts file.

[Nick Rosbrook]

This was also suggested upstream[1], but it seems that this is the
desired behavior from upstream's perspective.

[1] https://github.com/systemd/systemd/issues/12793

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

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  The "hostnamectl" command does not modify the hosts file.

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  When you want to change the name of the server with the "hostnamectl" command:
  The /etc/hostname file is changing as it should.
  However, the old name of the server remains in the /etc/hosts file.

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


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

[Touch-packages] [Bug 1936236] Re: Repeated segfault in udev_rule_line_free

[Nick Rosbrook]

Sorry this was not looked at sooner. Please re-open if still an issue.

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

Title:
  Repeated segfault in udev_rule_line_free

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Ubuntu version: 20.04 focal (Distro: Linux Mint 20.1 Ulyssa)

  systemd version: 245.4-4ubuntu3.7

  What happened: systemd-udevd underwent repeated segfaults and
  coredumps for unknown reasons. Loop stopped by forcing restart of
  udevd. Coredump information:

 PID: 381 (systemd-udevd)
 UID: 0 (root)
 GID: 0 (root)
  Signal: 11 (SEGV)
   Timestamp: Wed 2021-07-14 00:12:29 EDT (9h ago)
Command Line: /lib/systemd/systemd-udevd
  Executable: /lib/systemd/systemd-udevd
   Control Group: /system.slice/systemd-udevd.service
Unit: systemd-udevd.service
   Slice: system.slice
 Boot ID: abaa4a5b0c6641cda2c58d7c307cfc38
  Machine ID: b76cc7b1bbdc489e93909d2043031de8
Hostname: Ampere-Limux
 Storage: 
/var/lib/systemd/coredump/core.systemd-udevd.0.abaa4a5b0c6641cda2c58d7c307cfc38.381.1626235949.lz4
 Message: Process 381 (systemd-udevd) of user 0 dumped core.
  
  Stack trace of thread 381:
  #0  0x5635cdf522eb in udev_rule_line_free (rule_line=0x5635cec9db20) at 
../src/udev/udev-rules.c:270
  #1  0x5635cdf53d0c in udev_rule_file_free (rule_file=0x5635cecb2760) at 
../src/udev/udev-rules.c:289
  #2  udev_rules_free (rules=0x5635cea0ad10) at ../src/udev/udev-rules.c:302
  #3  0x5635cdf60875 in manager_free (manager=manager@entry=0x5635ce9fde60) 
at ../src/udev/udevd.c:306
  #4  0x5635cdf63e34 in manager_freep (p=) at 
../src/udev/udevd.c:314
  #5  run (argc=, argv=) at 
../src/udev/udevd.c:1703
  #6  0x5635cdf0721a in main (argc=, argv=) 
at ../src/udev/udevd.c:1817

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


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

[Touch-packages] [Bug 1938810] Re: Reverse lookup of 127.0.0.1 does not work

[Nick Rosbrook]

This appears to be fixed in newer releases.

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

Title:
  Reverse lookup of 127.0.0.1 does not work

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I expected a reverse lookup of 127.0.0.1 to return localhost, instead
  it returned nothing.

  ```
  root:~# dig -x 127.0.0.1

  ; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60017
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;1.0.0.127.in-addr.arpa.IN  PTR

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Aug 03 09:25:20 CDT 2021
  ;; MSG SIZE  rcvd: 51

  ```

  If I explicitly lookup using 127.0.0.1 instead of the default
  127.0.0.53, I do get a record as expected.

  ```
  root:~# dig -x 127.0.0.1 @127.0.0.1

  ; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1 @127.0.0.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51602
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;1.0.0.127.in-addr.arpa.IN  PTR

  ;; ANSWER SECTION:
  1.0.0.127.in-addr.arpa. 10800   IN  PTR localhost.

  ;; Query time: 3 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Tue Aug 03 09:25:15 CDT 2021
  ;; MSG SIZE  rcvd: 74

  ```

  I have an entry in /etc/hosts.

  ```
  root:~# grep 127.0.0.1 /etc/hosts
  127.0.0.1   localhost
  ```

  Looks like unbound which seems to work as expected is running on
  127.0.0.1:53, and systemd-resolv which is not working is on
  127.0.0.53:53.

  ```
  tcp0  0 127.0.0.1:530.0.0.0:*   LISTEN
  1839/unbound
  tcp0  0 127.0.0.53:53   0.0.0.0:*   LISTEN
  1511/systemd-resolv 

  ```

  I am running 20.04.2:

  ```
  root:~# lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  ```

  With systemd version 245.4-4ubuntu3.7

  ```
  root@:~# apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3.7
Candidate: 245.4-4ubuntu3.11
Version table:
   245.4-4ubuntu3.11 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   *** 245.4-4ubuntu3.7 100
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
   237-3ubuntu10.50 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages

  ```

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


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

[Touch-packages] [Bug 1932354] Re: systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21 (Test dependencies are unsatisfiable)

[Nick Rosbrook]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
  (Test dependencies are unsatisfiable)

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
    amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210617_171802_98347@/log.gz
    armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210616_224930_60c1e@/log.gz

  
  storage  PASS
  networkd-test.py FAIL non-zero exit status 1
  build-login  FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  boot-and-servicesFAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  udev FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  root-unittests   FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  tests-in-lxd SKIP installation fails and skip-not-installable set
  upstream FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  boot-smoke   FAIL badpkg
  blame: systemd
  badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
  systemd-fsckdSKIP exit status 77 and marked as skippable

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


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

[Touch-packages] [Bug 1926998] Re: package libpam-systemd:i386 237-3ubuntu10.46 failed to install/upgrade: installed libpam-systemd:i386 package post-installation script subprocess returned error exit

[Nick Rosbrook]

There have been several updates to systemd in bionic since this version.
This also doesn't look like it was a problem with src:systemd:

Setting up libpam-systemd:i386 (237-3ubuntu10.46) ...
^[[B^[[A
^[[B^[[A


Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 109.
Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
dpkg: error processing package libpam-systemd:i386 (--configure):
 installed libpam-systemd:i386 package post-installation script subprocess 
returned error exit status 128

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

Title:
  package libpam-systemd:i386 237-3ubuntu10.46 failed to
  install/upgrade: installed libpam-systemd:i386 package post-
  installation script subprocess returned error exit status 128

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  package libpam-systemd:i386 237-3ubuntu10.46 failed to
  install/upgrade: installed libpam-systemd:i386 package post-
  installation script subprocess returned error exit status 128

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libpam-systemd:i386 237-3ubuntu10.46
  ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
  Uname: Linux 4.15.0-142-generic i686
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: i386
  Date: Tue May  4 00:13:30 2021
  ErrorMessage: installed libpam-systemd:i386 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2021-05-03 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.13
  SourcePackage: systemd
  Title: package libpam-systemd:i386 237-3ubuntu10.46 failed to 
install/upgrade: installed libpam-systemd:i386 package post-installation script 
subprocess returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1912855] Re: debugfs shouldn't be mounted by default

[Nick Rosbrook]

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

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

Title:
  debugfs shouldn't be mounted by default

Status in systemd package in Ubuntu:
  New

Bug description:
  On modern Ubuntu systems, /sys/kernel/debug is mounted by default due
  to sys-kernel-debug.mount being enabled by default.

  AFAIK, this FS doesn't need to be mounted for normal operations and
  back in the day, there were concerns about the security implications
  of having it enabled/mounted by default
  (https://lists.ubuntu.com/archives/kernel-
  team/2011-January/013418.html).

  Would it be possible to not have it mounted by default?

  
  $ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3.4
Candidate: 245.4-4ubuntu3.4
Version table:
   *** 245.4-4ubuntu3.4 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

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


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

[Touch-packages] [Bug 696098] Re: cron @reboot rules fail for users wuth autofs homes, due to missing upstart dependancy

[Ubuntu Foundations Team Bug Bot]

The attachment "cron-reboot.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  cron @reboot rules fail for users wuth autofs homes, due to missing
  upstart dependancy

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cron

  If a user has a @reboot cron entry like:
  ===
  @reboot date >> date.log
  ===

  And their home directory is mounted by autofs into /home

  then, the job will fail during a machine reboot because the
  cron service starts before autofs service.

  I think this is a missing dependency between in the cron upstart
  configuration, to fix this I think that cron should be started after
  autofs (only when autofs is enabled).

  
  ProblemType: Bug
  Architecture: amd64
  Date: Fri Dec 31 12:32:49 2010
  Dependencies:
   adduser 3.112ubuntu1
   base-files 5.0.0ubuntu23
   base-passwd 3.5.22
   coreutils 8.5-1ubuntu3
   debconf 1.5.32ubuntu3
   debconf-i18n 1.5.32ubuntu3
   debianutils 3.2.3
   dpkg 1.15.8.4ubuntu3
   findutils 4.4.2-1ubuntu1
   gcc-4.5-base 4.5.1-7ubuntu2
   libacl1 2.2.49-3
   libattr1 1:2.4.44-2
   libbz2-1.0 1.0.5-4ubuntu1
   libc-bin 2.12.1-0ubuntu10
   libc6 2.12.1-0ubuntu10
   libdb4.8 4.8.30-1
   libgcc1 1:4.5.1-7ubuntu2
   liblocale-gettext-perl 1.05-6
   liblzma2 4.999.9beta+20100527-1
   libncurses5 5.7+20100626-0ubuntu1
   libpam-modules 1.1.1-4ubuntu2
   libpam-runtime 1.1.1-4ubuntu2
   libpam0g 1.1.1-4ubuntu2
   libselinux1 2.0.94-1
   libtext-charwidth-perl 0.04-6
   libtext-iconv-perl 1.7-2
   libtext-wrapi18n-perl 0.06-7
   lsb-base 4.0-0ubuntu8
   ncurses-bin 5.7+20100626-0ubuntu1
   passwd 1:4.1.4.2-1ubuntu3
   perl-base 5.10.1-12ubuntu2
   sed 4.2.1-7
   sensible-utils 0.0.4ubuntu1
   tzdata 2010o-0ubuntu0.10.10
   xz-utils 4.999.9beta+20100527-1
   zlib1g 1:1.2.3.4.dfsg-3ubuntu1
  DistroRelease: Ubuntu 10.10
  NonfreeKernelModules: nvidia
  Package: cron 3.0pl1-114ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  SourcePackage: cron
  Tags: maverick
  Uname: Linux 2.6.35-24-generic x86_64

  
  /etc/init/cron.conf
  ===
  # cron - regular background program processing daemon
  #
  # cron is a standard UNIX program that runs user-specified programs at
  # periodic scheduled times

  description "regular background program processing daemon"

  start on runlevel [2345]
  stop on runlevel [!2345]

  expect fork
  respawn

  exec cron
  ===

  ps aux | grep -E '(automount|cron)'
  root  1542  0.0  0.0  21128   628 ?Ss   Dec23   0:01 cron
  root  1867  0.0  0.0 123208  1044 ?Ssl  Dec23   0:02 
/usr/sbin/automount

  cron has a lower pid so it started first...

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


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

[Touch-packages] [Bug 1905179] Re: SDcard show wrong date (one month ahead)

[Nick Rosbrook]

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

Title:
  SDcard show wrong date (one month ahead)

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

Bug description:
  When mount an SD card date is wrong shown on SD-card (it is shown as to be 
one month ahead). Very strange.
  There is already some report about here, but I don't find a bug here in 
launchpad.
  https://www.explorelinux.com/ubuntu-wrong-date-from-sd-card-pictures/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1077 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (197 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b560 Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook Folio G1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=UUID=92c467dc-e394-4f19-a6a2-e7cf918f0ffb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-54-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: 07/12/2020
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.49
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.49:bd07/12/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: V1C39EA#ABD
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1078 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1078 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (199 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: HP HP EliteBook Folio G1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=UUID=92c467dc-e394-4f19-a6a2-e7cf918f0ffb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  StagingDrivers: exfat
  Tags:  focal staging
  Uname: Linux 5.4.0-54-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: 07/12/2020
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.49
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.49:bd07/12/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: V1C39EA#ABD
  dmi.sys.vendor: HP

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


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

[Touch-packages] [Bug 1937270] Re: package systemd 245.4-4ubuntu3.10 failed to install/upgrade: fin de fichero en la entrada estándar al preguntar sobre conffiles

[Nick Rosbrook]

Sorry this was not looked at sooner, but there have been several updates
to systemd in Focal since this report.

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

Title:
  package systemd 245.4-4ubuntu3.10 failed to install/upgrade: fin de
  fichero en la entrada estándar al preguntar sobre conffiles

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  que hago

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.10
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jul 21 08:02:50 2021
  ErrorMessage: fin de fichero en la entrada estándar al preguntar sobre 
conffiles
  InstallationDate: Installed on 2021-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 13d3:3490 IMC Networks 
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X456UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic 
root=UUID=be5f897f-4aae-4219-a58e-b30f13cb338f ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 245.4-4ubuntu3.10 failed to install/upgrade: fin de 
fichero en la entrada estándar al preguntar sobre conffiles
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X456UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X456UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX456UA.206:bd01/28/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnX456UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX456UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X456UA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.dhcp.dhclient-enter-hooks.d.resolved: 2021-01-06T15:47:39
  mtime.conffile..etc.pam.d.systemd-user: 2020-04-22T04:04:26
  mtime.conffile..etc.systemd.journald.conf: 2020-04-22T04:04:26
  mtime.conffile..etc.systemd.logind.conf: 2020-04-22T04:04:26
  mtime.conffile..etc.systemd.networkd.conf: 2020-04-01T12:23:42
  mtime.conffile..etc.systemd.pstore.conf: 2020-04-01T12:23:42
  mtime.conffile..etc.systemd.resolved.conf: 2021-01-06T15:47:39
  mtime.conffile..etc.systemd.sleep.conf: 2020-04-01T12:23:42
  mtime.conffile..etc.systemd.system.conf: 2020-04-22T04:04:26
  mtime.conffile..etc.systemd.user.conf: 2020-04-22T04:04:26

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


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

[Touch-packages] [Bug 1923485] Re: unable to reconize Asgard NVME with short serial

[Nick Rosbrook]

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

** Changed in: systemd (Ubuntu Impish)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Focal)
   Status: New => Won't Fix

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

Title:
  unable to reconize Asgard NVME with short serial

Status in curtin:
  New
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  check this:
  
https://discourse.maas.io/t/unable-to-deploy-valueerror-failed-to-find-storage-volume-id-nvme0n1/4442/4

  Maybe the line os.listdir should be changed with os.walk to discover all 
child directories?
  Or maybe this is just a BUG of MAAS?

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


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

[Touch-packages] [Bug 1911137] Re: alt-tab not working after left mouse click

[Nick Rosbrook]

I do see this behavior on Focal still, but I don't think systemd is the
correct package.

** Package changed: systemd (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  alt-tab not working after left mouse click

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  Steps:
  1. Click left mouse
  2. Wait for ~1 second
  3. Press and release Alt + Tab

  Actual: Stay on the same window/task/application
  Expected: Change to another window/task/application

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.snap-store.rules 
70-snap.canonical-livepatch.rules
  Date: Tue Jan 12 17:08:41 2021
  InstallationDate: Installed on 2021-01-09 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude 5410
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=669124d8-c9e0-4fd0-a562-a35d8545db4c ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.2
  dmi.board.name: 06KF2W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 701428
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.2:bd11/09/2020:br1.4:svnDellInc.:pnLatitude5410:pvr:rvnDellInc.:rn06KF2W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5410
  dmi.product.sku: 09A0
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1906729] Re: Suspend and hibernate work, but hybrid-suspend does not

[Nick Rosbrook]

Sorry this was not looked at sooner. Is this still an issue for you?

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

Title:
  Suspend and hibernate work, but hybrid-suspend does not

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have a Lenovo e585, if it's relevant.

  I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`.

  Suspend on my system doesn't wake up consistently, but hibernate does.

  Hybrid suspend would make an excellent fallback if wake fails.

  Since both work independently, they *should* work together.

  Happy to help debug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 16:58:44 2020
  InstallationDate: Installed on 2020-05-06 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic 
root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ 
resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/usr/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET74W (1.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET74W(1.54):bd07/23/2019:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.sleep.conf: 2020-12-03T16:22:33.696671

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


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

[Touch-packages] [Bug 1938810] Re: Reverse lookup of 127.0.0.1 does not work

[Nick Anderson]

Indeed, I do not see this behavior any longer.

```
$ dig -x 127.0.0.1

; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> -x 127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12678
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
1.0.0.127.in-addr.arpa. 0   IN  PTR localhost.
1.0.0.127.in-addr.arpa. 0   IN  PTR kubernetes.docker.internal.

;; Query time: 3 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Fri Jun 23 11:29:26 CDT 2023
;; MSG SIZE  rcvd: 114

$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.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/1938810

Title:
  Reverse lookup of 127.0.0.1 does not work

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I expected a reverse lookup of 127.0.0.1 to return localhost, instead
  it returned nothing.

  ```
  root:~# dig -x 127.0.0.1

  ; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60017
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;1.0.0.127.in-addr.arpa.IN  PTR

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Aug 03 09:25:20 CDT 2021
  ;; MSG SIZE  rcvd: 51

  ```

  If I explicitly lookup using 127.0.0.1 instead of the default
  127.0.0.53, I do get a record as expected.

  ```
  root:~# dig -x 127.0.0.1 @127.0.0.1

  ; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1 @127.0.0.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51602
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;1.0.0.127.in-addr.arpa.IN  PTR

  ;; ANSWER SECTION:
  1.0.0.127.in-addr.arpa. 10800   IN  PTR localhost.

  ;; Query time: 3 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Tue Aug 03 09:25:15 CDT 2021
  ;; MSG SIZE  rcvd: 74

  ```

  I have an entry in /etc/hosts.

  ```
  root:~# grep 127.0.0.1 /etc/hosts
  127.0.0.1   localhost
  ```

  Looks like unbound which seems to work as expected is running on
  127.0.0.1:53, and systemd-resolv which is not working is on
  127.0.0.53:53.

  ```
  tcp0  0 127.0.0.1:530.0.0.0:*   LISTEN
  1839/unbound
  tcp0  0 127.0.0.53:53   0.0.0.0:*   LISTEN
  1511/systemd-resolv 

  ```

  I am running 20.04.2:

  ```
  root:~# lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  ```

  With systemd version 245.4-4ubuntu3.7

  ```
  root@:~# apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3.7
Candidate: 245.4-4ubuntu3.11
Version table:
   245.4-4ubuntu3.11 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   *** 245.4-4ubuntu3.7 100
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
   237-3ubuntu10.50 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages

  ```

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


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

[Touch-packages] [Bug 1929101] Re: systemd-networkd can't set ip6tnl interface mode as any

[Nick Rosbrook]

Is this still an issue? If so, can you please enable debug logs on
systemd-networkd, and then reboot, and attach those recent logs?

$ systemctl edit systemd-networkd.service
# Add the following when the editor opens:
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

$ reboot
[...]
$ journalctl -b -u systemd-networkd.service > logs.txt

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

Title:
  systemd-networkd can't set ip6tnl interface mode as any

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd-networkd provides "Mode=" configuration for a virtual device
  of "Kind=ip6tnl". But setting mode to "any" doesn't work, tunnel mode
  stay as ipv6/ipv6:

  20/05/21 18:08:33 darkyman@mnt-myt-focal ~ > ip -6 tun show
  ip6tnl0: ipv6/ipv6 remote :: local :: encaplimit 0 hoplimit inherit tclass 
0x00 flowlabel 0x0 (flowinfo 0x)

  I'm expecting it to be in any/ipv6 mode like:

  ip6tnl0: any/ipv6 remote :: local :: encaplimit 0 hoplimit inherit
  tclass 0x00 flowlabel 0x0 (flowinfo 0x)

  Config file attached (00-ip6tnl0.netdev), I'm using systemd `systemd 245 
(245.4-4ubuntu3.6)` on a `Ubuntu 20.04.2 LTS`.
  Currently I'm using systemd service as a workaround this issue, which sets 
mode to "any" by calling

  /usr/sbin/ip -6 tunnel change ip6tnl0 mode any

  And that's what networkctl thinks about this tunnel interface

  ● 7: ip6tnl0 
   Link File: /usr/lib/systemd/network/99-default.link 
Network File: /etc/systemd/network/01-ip6tnl0.network  
Type: tunnel6  
   State: degraded (configured)
 MTU: 9000 (min: 68, max: 65407)   
Queue Length (Tx/Rx): 1/1  
 Address: fe80::3063:1eff:febf:8aaa

  May 20 17:55:36 mnt-myt-focal.example.com systemd-udevd[1062]: ip6tnl0: Could 
not generate persistent MAC: No data available
  May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: 
netdev ready
  May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: 
netdev could not be created: Invalid argument
  May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: 
IPv6 successfully enabled
  May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: 
Link UP
  May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: 
Gained carrier
  May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: 
Gained IPv6LL

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


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

[Touch-packages] [Bug 1940008] Re: systemd lsb-base integration script leaking shell variable changes which can break consumers

[Nick Rosbrook]

Is this still relevant?

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

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

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

Title:
  systemd lsb-base integration script leaking shell variable changes
  which can break consumers

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I am using systemd version 248.3-1ubuntu3 from the impish repository.

  It was compiled and built in the following manner:
  # add impish deb-src repository to apt sources
  apt build-dep systemd/impish
  apt source -b systemd/impish

  Once built, it was installed over the top of systemd 245.4-4ubuntu3.

  I am running ubuntu 20.04.2.

  The source tarball of systemd includes a file
  (./debian/systemd/lib/lsb/init-functions.d/40-systemd) which is
  intended to be installed into the drop-in script directory provided by
  the lsb-base package (/lib/lsb/init-functions.d).

  The problem that I am having is that this file (which is sourced by
  any script which sources /lib/lsb/init-functions) is setting
  variables, and in doing so, accidentally overwriting variables which
  are configured by the calling script.

  
https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L19

  I noticed this when investigating why ipmiutil_wdt.service (provided
  by package ipmiutil) was failing to start. The problem is that the
  ipmiutil_wdt script, which makes use of init-functions, was statically
  setting some variables for later use, including one called $prog.
  $prog is then inadvertently overwritten by 40-systemd when
  ipmiutil_wdt sources /lib/lsb/init-functions.

  I think this is systemd's bug because systemd's lsb-base drop-in is
  not being a "good neighbor" to the scripts with which it shares a
  controlling shell. Even if ipmiutil were to rewrite its ipmiutil-wdt
  script, any other such script provided by another package which tries
  to use a variable called $prog (or $executable, or $argument, or
  $service, or $state, or any of a handful of others) will find its feet
  being stepped on by systemd's drop-in.

  I propose that the drop-in be modified to encapsulate all of this
  behavior where variables are assigned to within a function or subshell
  or something, so they can't accidentally contaminate the outside
  world.

  Other related package versions:
  lsb-base: 11.1.0ubuntu2
  ipmiutil: 3.1.5-1

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


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

[Touch-packages] [Bug 1963825] Re: udev does not create devices plugged into USB 3.0 ports

[Nick Rosbrook]

This was reported aginst systemd 248.3-1ubuntu8.2 in Impish, which is no
longer supported. If this is still relevant in a supported release,
please open a new bug report.

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

Title:
  udev does not create devices plugged into USB 3.0 ports

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hotplugging devices into USB 3.0/1/2 Ports does not create devices in
  /dev. The plugged device is not accessible afterwards. This is for all
  of them: USB-Disks (HD, CDROM, Tapes), USB to serial converters,
  Audio, Video, Cameras.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udev 248.3-1ubuntu8.2
  ProcVersionSignature: Ubuntu 5.13.0-32.35-generic 5.13.19
  Uname: Linux 5.13.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CustomUdevRuleFiles: 49-micronucleus.rules 70-snap.core.rules 
51-android.rules 70-snap.chromium.rules
  Date: Sun Mar  6 16:55:19 2022
  InstallationDate: Installed on 2011-10-19 (3790 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Acer TravelMate P643-M
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-32-generic 
root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios 
ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to impish on 2019-04-27 (1044 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.release: 2.15
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

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


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

[Touch-packages] [Bug 1959725] Re: Segfault from Native.sd_journal_get_fd

[Nick Rosbrook]

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

This was fixed in bug 1946388.

** This bug has been marked a duplicate of bug 1946388
   Journalctl -f --file some.journal causes coredump

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

Title:
  Segfault from Native.sd_journal_get_fd

Status in systemd package in Ubuntu:
  New

Bug description:
  The version of libsystemd0 Ubuntu 20.04 has the following issue
  present in the package:

  https://github.com/systemd/systemd/issues/15528
  https://github.com/ledbettj/systemd-journal/issues/88

  It was fixed here:

  
https://github.com/systemd/systemd/commit/2b6df46d21abe8a8b7481e420588a9a129699cf9

  It would be great to get this fixed in the LTS.

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


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

[Touch-packages] [Bug 1981531] Re: package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1

[Nick Rosbrook]

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 1

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Upgrading from 21.10 to 22.04, root-on-zfs.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-amd64 2.06-2ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-52.59-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jul 13 06:37:26 2022
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-07-13 (0 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2022-04-06T10:45:01.573806

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


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

[Touch-packages] [Bug 2024642] Re: Upgrading libx11-6_2:1.6.2-1ubuntu2.1+esm3 failed

[Marc Deslauriers]

Updates were pushed to fix this issue. Please re-open this bug if this
problem is still occurring.

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

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

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

Title:
  Upgrading libx11-6_2:1.6.2-1ubuntu2.1+esm3 failed

Status in libx11 package in Ubuntu:
  Invalid
Status in libx11 source package in Trusty:
  Fix Released

Bug description:
  Upgrading esm3 on Trusty is failed.

  Preparing to unpack .../libx11-6_2%3a1.6.2-1ubuntu2.1+esm3_amd64.deb ...
  Unpacking libx11-6:amd64 (2:1.6.2-1ubuntu2.1+esm3) over (2:1.6.2-1ubuntu2.1) 
...
  dpkg: error processing archive 
/var/cache/apt/archives/libx11-6_2%3a1.6.2-1ubuntu2.1+esm3_amd64.deb (--unpack):
   trying to overwrite shared '/usr/share/doc/libx11-6/changelog.Debian.gz', 
which is different from other instances of package libx11-6:amd64
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libx11-6_2%3a1.6.2-1ubuntu2.1+esm3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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


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

[Touch-packages] [Bug 1998957] Re: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: pakket systemd is reeds geïnstalleerd en geconfigureerd

[Nick Rosbrook]

There have been several updates since this version of the package, so
this is no longer relevant.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package systemd 249.11-0ubuntu3.6 failed to install/upgrade: pakket
  systemd is reeds geïnstalleerd en geconfigureerd

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I don't know what the problem is.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Dec  6 19:03:51 2022
  DpkgTerminalLog:
   dpkg: fout bij verwerken van pakket systemd (--configure):
pakket systemd is reeds geïnstalleerd en geconfigureerd
  ErrorMessage: pakket systemd is reeds geïnstalleerd en geconfigureerd
  InstallationDate: Installed on 2022-12-06 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7D22
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=761228fd-f419-4259-b184-f54c7d42d38b ro quiet splash
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: systemd
  Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: pakket 
systemd is reeds geïnstalleerd en geconfigureerd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 3.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: H510M-A PRO (MS-7D22)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.B0:bd10/21/2022:br5.19:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D22:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH510M-APRO(MS-7D22):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D22
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Touch-packages] [Bug 1983242] Re: package systemd 249.11-0ubuntu3.4 failed to install/upgrade: package systemd is already installed and configured

[Nick Rosbrook]

There have been several updates to the package in Jammy since this was
reported, so this is no longer relevant.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package systemd 249.11-0ubuntu3.4 failed to install/upgrade: package
  systemd is already installed and configured

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Get this error on boot and when try to make update with "Software
  Updater"

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.4
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu39
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   600:0:124:351912:2022-07-29 20:22:29.942999124 +0300:2022-07-29 
20:22:30.942999124 +0300:/var/crash/libapparmor1:amd64.0.crash
   600:0:124:351890:2022-07-29 20:22:29.966999053 +0300:2022-07-29 
20:22:30.966999053 +0300:/var/crash/systemd.0.crash
  Date: Fri Jul 29 20:22:30 2022
  ErrorMessage: package systemd is already installed and configured
  InstallationDate: Installed on 2022-07-29 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5621 Realtek Semiconductor Corp. HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros 
QCA9377 Bluetooth
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=a302d707-ed76-476f-a461-446ac736e4af ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.6
  SourcePackage: systemd
  Title: package systemd 249.11-0ubuntu3.4 failed to install/upgrade: package 
systemd is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.release: 1.21
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd08/08/2018:br1.21:efr1.15:svnAcer:pnAspireA515-51G:pvrV1.21:rvnKBL:rnCharmander_KL:rvrV1.21:cvnAcer:ct10:cvrV1.21:sku:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer

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


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

[Touch-packages] [Bug 1983046] Re: Incorrect username for systemd-journal-upload.service

[Nick Rosbrook]

If this is still relevant, can you share the output from the failed
service? The systemd-journal-upload.service unit should have
DynamicUser=yes, which should take care of the user at runtime (i.e. I
would not expect to see systemd-journal-upload listed in /etc/passwd).

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

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

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

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

Title:
  Incorrect username for systemd-journal-upload.service

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Starting the systemd-journal-upload service fails. The username
  specified in the Ubuntu systemd-journal-upload.service does not exist
  after the systemd-journal-remote package is installed.

  
  Ubuntu systemd-journal-upload.service:

  User=systemd-journal-upload


  Corrent systemd-journal-upload.service:

  User=systemd-journal-remote

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-journal-remote 249.11-0ubuntu3.4
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Jul 28 17:44:06 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: Upgraded to jammy on 2022-07-28 (0 days ago)
  modified.conffile..etc.systemd.journal-upload.conf: [modified]
  mtime.conffile..etc.systemd.journal-upload.conf: 2022-07-28T07:02:44.608776

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


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

[Touch-packages] [Bug 2006133] Re: package libnss-systemd:amd64 249.11-0ubuntu3.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Nick Rosbrook]

There have been several package updates since this report, so this is no
longer relevant. If you experience similar issues with newer versions,
please open a new bug report.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package libnss-systemd:amd64 249.11-0ubuntu3.6 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Everytime i try to update my ubuntu this package generate a problem.
  Kindly resolve it because this package effects my work also. So its my
  humble request kindly help me with this.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libnss-systemd:amd64 249.11-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Feb  6 20:02:56 2023
  DuplicateSignature:
   package:libnss-systemd:amd64:249.11-0ubuntu3.6
   Setting up libjavascriptcoregtk-4.0-18:amd64 (2.38.3-0ubuntu0.22.04.1) ...
   dpkg: error processing package libnss-systemd:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-10-12 (116 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: systemd
  Title: package libnss-systemd:amd64 249.11-0ubuntu3.6 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1990679] Re: package systemd-sysv 249.11-0ubuntu3.4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Nick Rosbrook]

There have been several package updates since this report, so this is no
longer relevant. If you experience similar issues with newer versions,
please open a new bug report.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package systemd-sysv 249.11-0ubuntu3.4 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On first boot of the day an update prompt offered to install a fairly
  large batch and I accepted. Shortly after, during said update, the
  computer froze. I could not shortcut to a terminal.

  Simultaneously to the update I was editing a text file in Sublime, had
  Chrome open in the background, Skype running on startup. I wouldn't
  normally report it but a crash of systemd on update at startup is
  pretty unusual and severe.

  

  ProblemType: Package
  Architecture: amd64
  Date: Fri Sep 23 08:48:34 2022
  Package: systemd-sysv 249.11-0ubuntu3.6
  SourcePackage: systemd
  ErrorMessage:
   dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  DpkgTerminalLog:

  

   Preparing to unpack .../00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb ...
   Unpacking systemd-sysv (249.11-0ubuntu3.6) over (249.11-0ubuntu3.4) ...
   dpkg-deb: error: failed to read archive 
'/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb': No 
such file or directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb 
(--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2

  

  DuplicateSignature:
   package:systemd-sysv:249.11-0ubuntu3.4
   Unpacking systemd-sysv (249.11-0ubuntu3.6) over (249.11-0ubuntu3.4) ...
   dpkg-deb: error: failed to read archive 
'/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb': No 
such file or directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb 
(--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2

  
  Title: package systemd-sysv 249.11-0ubuntu3.4 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  Uname: Linux 5.15.0-48-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (146 days ago)
  _MarkForUpload: True

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: systemd-sysv 249.11-0ubuntu3.4
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Sep 23 08:48:34 2022
  DpkgTerminalLog:
   Preparing to unpack .../00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb ...
   Unpacking systemd-sysv (249.11-0ubuntu3.6) over (249.11-0ubuntu3.4) ...
   dpkg-deb: error: failed to read archive 
'/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb': No 
such file or directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb 
(--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  DuplicateSignature:
   package:systemd-sysv:249.11-0ubuntu3.4
   Unpacking systemd-sysv (249.11-0ubuntu3.6) over (249.11-0ubuntu3.4) ...
   dpkg-deb: error: failed to read archive 
'/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb': No 
such file or directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9ra7tt/00-systemd-sysv_249.11-0ubuntu3.6_amd64.deb 
(--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2022-03-21 (186 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: systemd
  Title: package systemd-sysv 249.11-0ubuntu3.4 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (146 days ago)

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


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

[Touch-packages] [Bug 1995097] Re: systemd

[Nick Rosbrook]

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

Title:
  systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
  Errors were encountered while processing:
   systemd
   systemd-timesyncd
   libpam-systemd:amd64
   systemd-oomd
   snapd
   systemd-sysv
   libnss-systemd:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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


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

[Touch-packages] [Bug 1973266] Re: package libsystemd0 245.4-4ubuntu3.17 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different from

[Nick Rosbrook]

There have been several package updates since this report. If you
experience similar issues with newer versions, please open a new bug
report.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package libsystemd0 245.4-4ubuntu3.17 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different
  from other instances of package libsystemd0:amd64

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  fails during 'apt upgrade'

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libsystemd0 245.4-4ubuntu3.17
  ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21
  Uname: Linux 5.14.0-1036-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 13 08:48:07 2022
  DpkgTerminalLog:
   Preparing to unpack .../libsystemd0_245.4-4ubuntu3.17_amd64.deb ...
   Unpacking libsystemd0:amd64 (245.4-4ubuntu3.17) over (245.4-4ubuntu3.17) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libsystemd0_245.4-4ubuntu3.17_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different from other 
instances of package libsystemd0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different from other 
instances of package libsystemd0:amd64
  InstallationDate: Installed on 2021-09-07 (247 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: systemd
  Title: package libsystemd0 245.4-4ubuntu3.17 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libsystemd0/changelog.Debian.gz', 
which is different from other instances of package libsystemd0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1956268] Re: package systemd 248.3-1ubuntu8 failed to install/upgrade: o subprocesso instalado, do pacote systemd, o script post-installation retornou erro do status de saída 127

[Nick Rosbrook]

This version of systemd is no longer supported in any Ubuntu releases.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package systemd 248.3-1ubuntu8 failed to install/upgrade: o
  subprocesso instalado, do pacote systemd, o script post-installation
  retornou erro do status de saída 127

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  nunca completa as atualizações

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Jan  3 22:27:50 2022
  ErrorMessage: o subprocesso instalado, do pacote systemd, o script 
post-installation retornou erro do status de saída 127
  InstallationDate: Installed on 2019-08-17 (870 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5659 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic 
root=UUID=dadf5e69-ec04-414c-bf27-44bc7f2b4936 ro mem_sleep_default=deep 
nvidia-drm.modeset=1 quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.2.4ubuntu0.1
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Title: package systemd 248.3-1ubuntu8 failed to install/upgrade: o 
subprocesso instalado, do pacote systemd, o script post-installation retornou 
erro do status de saída 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd03/24/2019:br1.6:svnDellInc.:pnInspiron7580:pvr:sku08A6:rvnDellInc.:rn0W83FH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1951303] Re: package systemd 245.4-4ubuntu3.13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Nick Rosbrook]

There have been several package updates since this report. If you
experience similar issues with newer versions, please open a new bug
report.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package systemd 245.4-4ubuntu3.13 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.13
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   libsystemd0:amd64: Install
   libsystemd0:amd64: Configure
   systemd-timesyncd:amd64: Configure
   systemd:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov 18 00:09:29 2021
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2021-11-01 (16 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic 
root=UUID=5afca73e-6839-4538-b36d-630cbde5f567 ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/open-vm-tools.service → 
/usr/lib/systemd/system/open-vm-tools.service.d/desktop.conf
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: package systemd 245.4-4ubuntu3.13 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Touch-packages] [Bug 1955085] Re: package systemd 245.4-4ubuntu3.13 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127

[Nick Rosbrook]

There have been several package updates since this report. If you
experience similar issues with newer versions, please open a new bug
report.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package systemd 245.4-4ubuntu3.13 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 127

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  New to Ubuntu/linux, got an error that asked to report. I did. I do
  not have any detailed information about this error.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.13
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 15 03:31:02 2021
  DuplicateSignature:
   package:systemd:245.4-4ubuntu3.13
   Installing new version of config file 
/etc/dhcp/dhclient-enter-hooks.d/resolved ...
   systemd-machine-id-setup: error while loading shared libraries: libpam.so.0: 
cannot open shared object file: No such file or directory
   dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned 
error exit status 127
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 127
  InstallationDate: Installed on 2021-12-15 (1 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic 
root=UUID=5a0eb9db-11d1-4e63-a3c3-c001c342f9fe ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/open-vm-tools.service → 
/usr/lib/systemd/system/open-vm-tools.service.d/desktop.conf
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: package systemd 245.4-4ubuntu3.13 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 
127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Touch-packages] [Bug 1962387] Re: EFI is not on the drive

[Nick Rosbrook]

I don't think this is a problem with systemd. It would likely be related
to the installer, I think. If this is still an issue please open a new
bug report against the relevant installer package.

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

Title:
  EFI is not on the drive

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello
  I just installed the latest release jammy made on Feb 26 in an ZFS external 
hard drive. I would have liked the part of BOOT EFI to also go to the external 
hard drive and not to the internal hard drive. It is true that it is an error 
which certainly dates from the creation of the EFI

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


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

[Touch-packages] [Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory

[Nick Rosbrook]

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

Title:
  Key load error: Failed to open key material file: No such file or
  directory

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello
  This morning I downloaded the UBUNTU JAMMY version which had just been made 
an hour earlier. I installed it asking for encryption.

  When I boot, the password is asked. He is accepted. But root mount is denied.
  ...
  find: /dev/zvol: No such file or directory
  key load error: Failed to open key matéral file No such file or directory

  Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted:
  permission denied

  Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg

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


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

[Touch-packages] [Bug 1952542] Re: systemd randomly crashes

[Nick Rosbrook]

This was reported against Impish, which is no longer supported. If you
experience this problem on a supported release please open a new bug
report.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  systemd randomly crashes

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  When screensaver is on, I often can't wake the system back up again.
  Screen comes, up, clock shows but frozen and login does nothing.

  I have a file `/var/crash/_usr_lib_systemd_systemd.0.crash` from
  around the incident time, so I guess it's systemd itself that's
  crashing.

  Trying to dig into the crash report, this is how far I get:

  ```
  $ gdb `cat ExecutablePath` CoreDump
  GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/lib/systemd/systemd...
  (No debugging symbols found in /usr/lib/systemd/systemd)
  [New LWP 2241488]
  [New LWP 1]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/sbin/init recovery dis_ucode_ldr'.
  Program terminated with signal SIGABRT, Aborted.
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  120   ../sysdeps/unix/syscall-template.S: No such file or directory.
  [Current thread is 1 (LWP 2241488)]
  (gdb) bt
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  #1  0x561ece72cb5c in ?? ()
  #2  
  #3  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=139637107291648) at pthread_kill.c:44
  #4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
  #5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
  #6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #7  0x7effcc9777b7 in __GI_abort () at abort.c:79
  #8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
  #9  0x561ece7758c4 in ?? ()
  #10 0x561ece77a7aa in ?? ()
  #11 0x561ece72b8a7 in ?? ()
  #12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
  #13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, 
argc=3, argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)
  at ../csu/libc-start.c:409
  #14 0x561ece72c6f5 in ?? ()
  (gdb) 
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  #1  0x561ece72cb5c in ?? ()
  #2  
  #3  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=139637107291648) at pthread_kill.c:44
  #4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
  #5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
  #6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #7  0x7effcc9777b7 in __GI_abort () at abort.c:79
  #8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
  #9  0x561ece7758c4 in ?? ()
  #10 0x561ece77a7aa in ?? ()
  #11 0x561ece72b8a7 in ?? ()
  #12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
  #13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, 
argc=3, argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)
  at ../csu/libc-start.c:409
  #14 0x561ece72c6f5 in ?? ()
  quit) 
  ```
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2016-12-28 (1795 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: wl nvidia_modeset nvidia
  Package: systemd 248.3-1ubuntu8
  PackageArchitecture

[Touch-packages] [Bug 1953226] Re: systemd journal uses all space

[Nick Rosbrook]

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

Title:
  systemd journal uses all space

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  /var/log/journal is getting bigger and bigger!

  SET SOME FUCKIN DEFAULTS FOR JOURNALCTL !

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


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

[Touch-packages] [Bug 2024926] [NEW] add-apt-repository has a misleading error message when the launchpad api is down

[Stephane]

Public bug reported:

On Ubuntu 22.04.2
Package software-properties-common 0.99.22.7
During the launchpad outage on the 23rd June 2023, add-apt-repository was 
crashing with the following:
Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 364, in 
sys.exit(0 if addaptrepo.main() else 1)
  File "/usr/bin/add-apt-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
40, in shortcut_handler
return handler(shortcut, **kwargs)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, in 
__init__
if self.lpppa.publish_debug_symbols:
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120, in 
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107, in 
lpteam
self._lpteam = self.lp.people(self.teamname)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, in 
lp
self._lp = login_func("%s.%s" % (self.__module__, self.__class__.__name__),
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494, in 
login_anonymously
return cls(
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 230, in 
__init__
super(Launchpad, self).__init__(
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
477, in __init__
self._browser.get(root_resource), 'application/json')
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
439, in get
response, content = self._request(url, extra_headers=headers)
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
389, in _request
response, content = self._request_and_retry(
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
359, in _request_and_retry
response, content = self._connection.request(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1725, in 
request
(response, content) = self._request(
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 144, in 
_request
response, content = super(LaunchpadOAuthAwareHttp, self)._request(
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
184, in _request
return super(RestfulHttp, self)._request(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1441, in 
_request
(response, content) = self._conn_request(conn, request_uri, method, body, 
headers)
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1363, in 
_conn_request
conn.connect()
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1139, in 
connect
address_info = socket.getaddrinfo(host, port, 0, socket.SOCK_STREAM)
  File "/usr/lib/python3.10/socket.py", line 955, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
OSError: [Errno 16] Device or resource busy


This was misleading as it seemed to indicate a problem with the client and not 
with the server. The error message should be improved as to make it clear where 
the error is located.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  add-apt-repository has a misleading error message when the launchpad
  api is down

Status in software-properties package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04.2
  Package software-properties-common 0.99.22.7
  During the launchpad outage on the 23rd June 2023, add-apt-repository was 
crashing with the following:
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 347, in main
  shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
40, in shortcut_handler
  return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, 
in __init__
  if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107, 
in lpteam
  self._lpteam = self.lp.people(self.teamname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, 
in lp
  self._lp = login_func("%s.%s" % (self.__module__, 
self.__class__.__name__),
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494, 
in login_anonymously
  return cls(
File "/usr/lib/python3/dist-

[Touch-packages] [Bug 2024929] [NEW] dhclient does not reup valid_lft on service restart, kernel reaps IP

[Steven Haber]

Public bug reported:

Between Bionic and Focal, dhclient was patched to set the valid_lft on
ipv4 addresses, which is a timer in the kernel that tells the kernel
when to reap the IP. dhclient then is supposed to issue repeated `ip
addr add` commands to reset this lft and prevent the kernel from
releasing the IP. However, if you restart the dhclient service, it
acquires a lease and then does *not* reup the lft. It only reups after a
lease the currently running service knows about expires. So if you
restart the dhclient service on a cadence that is faster than the DHCP
leases in your network environment, you never see a lease expire during
the lifetime of the service, which means the kernel will eventually rip
the address out from under the server, causing a network outage. In some
environments, the DCHP lease can be longer than a service restart
cadence, and this bug can be very severe.

I'm using the most up-to-date version of Focal's dhclient package.

I'm not familiar with how the patch management for Ubuntu works, but the
bug was introduced here:

commit 41013cf19647ec323a7100fb61d50779d8c8a205 (tag: import/4.4.1-2)
Author: Michael Gilbert 
Date:   Tue Dec 11 03:55:12 2018 +

4.4.1-2 (patches unapplied)

Imported using git-ubuntu import.

These changes specifically:

diff --git a/debian/dhclient-script.linux b/debian/dhclient-script.linux
index 9b0d3f89..f9b734ab 100644
--- a/debian/dhclient-script.linux
+++ b/debian/dhclient-script.linux
@@ -246,6 +246,8 @@ case "$reason" in
 # new IP has been leased or leased IP changed => set it
 ip -4 addr add 
${new_ip_address}${new_subnet_mask:+/$new_subnet_mask} \
 ${new_broadcast_address:+broadcast $new_broadcast_address} \
+${new_dhcp_lease_time:+valid_lft $new_dhcp_lease_time} \
+${new_dhcp_lease_time:+preferred_lft $new_dhcp_lease_time} \
 dev ${interface} label ${interface}

 if [ -n "$new_interface_mtu" ]; then
@@ -277,6 +279,12 @@ case "$reason" in
fi
done
fi
+else # RENEW||REBIND
+ip -4 addr change 
${new_ip_address}${new_subnet_mask:+/$new_subnet_mask} \
+${new_broadcast_address:+broadcast $new_broadcast_address} \
+${new_dhcp_lease_time:+valid_lft $new_dhcp_lease_time} \
+${new_dhcp_lease_time:+preferred_lft $new_dhcp_lease_time} \
+dev ${interface} label ${interface}
 fi

 if [ -n "$alias_ip_address" ] &&
@@ -323,6 +331,8 @@ case "$reason" in
 # set IP from recorded lease
 ip -4 addr add ${new_ip_address}${new_subnet_mask:+/$new_subnet_mask} \
 ${new_broadcast_address:+broadcast $new_broadcast_address} \
+${new_dhcp_lease_time:+valid_lft $new_dhcp_lease_time} \
+${new_dhcp_lease_time:+preferred_lft $new_dhcp_lease_time} \
 dev ${interface} label ${interface}

 if [ -n "$new_interface_mtu" ]; then

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  dhclient does not reup valid_lft on service restart, kernel reaps IP

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Between Bionic and Focal, dhclient was patched to set the valid_lft on
  ipv4 addresses, which is a timer in the kernel that tells the kernel
  when to reap the IP. dhclient then is supposed to issue repeated `ip
  addr add` commands to reset this lft and prevent the kernel from
  releasing the IP. However, if you restart the dhclient service, it
  acquires a lease and then does *not* reup the lft. It only reups after
  a lease the currently running service knows about expires. So if you
  restart the dhclient service on a cadence that is faster than the DHCP
  leases in your network environment, you never see a lease expire
  during the lifetime of the service, which means the kernel will
  eventually rip the address out from under the server, causing a
  network outage. In some environments, the DCHP lease can be longer
  than a service restart cadence, and this bug can be very severe.

  I'm using the most up-to-date version of Focal's dhclient package.

  I'm not familiar with how the patch management for Ubuntu works, but
  the bug was introduced here:

  commit 41013cf19647ec323a7100fb61d50779d8c8a205 (tag: import/4.4.1-2)
  Author: Michael Gilbert 
  Date:   Tue Dec 11 03:55:12 2018 +

  4.4.1-2 (patches unapplied)

  Imported using git-ubuntu import.

  These changes specifically:

  diff --git a/debian/dhclient-script.linux b/debian/dhclient-script.linux
  index 9b0d3f89..f9b734ab 100644
  --- a/debian/dhclient-script.linux
  +++ b/debian/dhclient-script.linux
  @@ -246,6 +246,8 @@ case "$reason" in
  

[Touch-packages] [Bug 1837227] Re: Random mount units sometimes fail, while file system is correctly mounted

[Nick Rosbrook]

The commits referenced in the upstream bug report are present in Lunar
and newer.

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

Title:
  Random mount units sometimes fail, while file system is correctly
  mounted

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

Bug description:
  In Ubuntu 18.04 at least, we sometimes get a random server in
  emergency mode with a failed mount unit (ext4 file system), while the
  corresponding file system is in fact correctly mounted. It happens
  roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Nick Rosbrook]

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

** Changed in: systemd (Ubuntu Lunar)
   Status: Incomplete => 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/1992979

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1830479] Re: testcases expect first kernel log line, but not always in logs

[Nick Rosbrook]

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  testcases expect first kernel log line, but not always in logs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  [impact]

  boot-and-services and cmdline-upstart-boot expect the first(ish)
  kernel log line to be in the system logs, but that is not guaranteed
  to be in the logs.

  [test case]

  run autopkgtest on arm64 with the current kernel, whose kernel log
  size is too small for journald or rsyslogd to capture the first kernel
  log messages.

  [regression potential]

  low; testcase fix only.

  [other info]

  the specific cause of this currently is too-small kernel log buffer
  size on arm64, which is being fixed in bug 1824864, but increasing
  amounts of boot time logging may cause a failure again, or custom
  kernel configs with small log buffers.

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


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

[Touch-packages] [Bug 1815045] Re: Failed unmounting /var when it is a separate filesystem

[Nick Rosbrook]

According to the upstream bug report, this is fixed by
https://github.com/systemd/systemd/commit/1e187d2dd52cbb4f0bb30e4d96acf7f72a145b91,
which is present in Focal and newer.

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

Title:
  Failed unmounting /var when it is a separate filesystem

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In a fresh install of Ubuntu Server 18.04.1 LTS with the /var-
  Filesystem on a separate partition (LVM), there are Errors on
  shutdown/reboot (Failed unmounting /var).

  1) The release
  Release: Ubuntu 18.04.1 LTS

  2) The version
  Version:apt-cache policy systemd
  systemd:  Installed: 237-3ubuntu10.12
Candidate: 237-3ubuntu10.12

  3) What you expected to happen
  Clean unmount of /var Filesystem without Failure

  4) What happened instead
  Console output on shutdown/reboot
  [...]
  [  OK  ] Stopped Flush Journal to Persistent Storage.
  [  OK  ] Stopped target Local File Systems.
   Unmounting /boot...
   Unmounting /var...
   Unmounting /run/user/1000...
  [FAILED] Failed unmounting /var.
  [  OK  ] Stopped File System Check on /dev/mapper/vg_system-lv_var.
  [  OK  ] Unmounted /run/user/1000
  [...]

  Extract from journalctl
  [...]
  Feb 07 13:13:31 x systemd[1]: Stopped Flush Journal to Persistent Storage.
  Feb 07 13:13:31 x systemd[1]: Stopped target Local File Systems.
  Feb 07 13:13:31 x systemd[1]: Unmounting /boot...
  Feb 07 13:13:31 x systemd[1]: Unmounting /var...
  Feb 07 13:13:31 x systemd[1]: Unmounting /run/user/1000...
  Feb 07 13:13:31 x umount[1775]: umount: /var: target is busy.
  Feb 07 13:13:31 x systemd[1]: var.mount: Mount process exited, 
code=exited status=32
  Feb 07 13:13:31 x systemd[1]: Failed unmounting /var.
  Feb 07 13:13:31 x systemd[1]: Stopped File System Check on 
/dev/mapper/vg_system-lv_var.
  Feb 07 13:13:31 x systemd[1]: Unmounted /run/user/1000.
  [...]

  Applying the changes described here:

  https://github.com/systemd/systemd/issues/867#issuecomment-250202183

  let the Error-Messages go away. But are there any side-effects?

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


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

[Touch-packages] [Bug 1838992] Re: udev doesn't pick up volumes properly

[Nick Rosbrook]

Is this issue still relevant?

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

Title:
  udev doesn't pick up volumes properly

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [Only happens on Ubuntu, not other OS's, like Debian]

  When we are attaching a volume to a running Ubuntu server (using
  kvm/libvirt), most of the time the udev rules are not properly
  triggered. In the end the volume will most of the time not be
  available in `/dev/disk/by-id/virtio-`. Sometimes it works
  though (10%/20%?).

  The reason for this is that udev somehow doesn't pick it up when the
  volume is attached. It looks like a timing issue. Just looking at
  `/sys/devices/pci:00/:00:05.0/virtio2/block/vdb/serial` makes
  it clear that it's there. However `udevadm info /dev/vdb` returns
  without the `ID_SERIAL` key. Only a `udevadm trigger` leads to a
  correct entry of `ID_SERIAL` and also fixes `/dev/disk/by-id`.

  We are a small cloud provider (cloudscale.ch). We have tested this on
  Ubuntu (16.04/18.04), Debian 9, CentOS, CoreOS. We haven't tested this
  extensively, but it sure looks like it's only happening on Ubuntu. .
  We never had any issues reported on other OS's about this.

  I tried looking at the differences of Debian and Ubuntu udev packages,
  but couldn't figure out what might be responsible for this behavior.

  If someone needs an account for our control panel to reproduce this,
  please contact me, I'm happy to give you the resources to debug this.

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


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

[Touch-packages] [Bug 1874144] Re: Suspends when lid closed despite "do nothing" option after using ext monitor

[Nick Rosbrook]

What settings have you actually tried to change in
/etc/systemd/logind.conf? The snippet above looks unchanged (or is at
least all commented out).

Some combination of HandleLidSwitch*=ignore should work.

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

Title:
  Suspends when lid closed despite "do nothing" option after using ext
  monitor

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I use "do nothing" (... I guess, "ne rien faire" in french) option on
  both battery and supply in power manager. It works until I plug an
  external monitor (DisplayPort), disconnect, then it suspends when
  closing lid.

  Changing options changes nothing in /etc/systemd/logind.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  #HandleLidSwitch=suspend
  #HandleLidSwitchDocked=ignore
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  Problem appeared after Mint 18 -> 19 upgrade with 'mintupgrade' tool.

  System:
  Toshiba Tecra A50-A-130

  Linux Mint 19 (= bionic)
  Cinnamon 3.8.9
  5.3.0-46-generic
  Intel© Core™ i7-4600M CPU @ 2.90GHz × 2

  apt-cache policy systemd
  systemd:
Installé : 237-3ubuntu10.39
Candidat : 237-3ubuntu10.39
   Table de version :
   *** 237-3ubuntu10.39 500
  500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10.38 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages

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


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

[Touch-packages] [Bug 1948593] Re: Hotkey to toggle Automatic Brightness does not work on ASUS UX410UQK

[Nick Rosbrook]

Ubuntu 21.10 is no longer supported. Is this still a problem in newer
releases?

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

Title:
  Hotkey to toggle Automatic Brightness does not work on ASUS UX410UQK

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On my laptop ASUS UX410UQK, the hotkey does not toggle automatic brightness 
as intended.
  Below is the result I got after two (Fn + A) strokes.

  $ sudo evtest
  [...]
  Select the device event number [0-19]: 5
  Input driver version is 1.0.1
  Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
  Input device name: "Asus WMI hotkeys"
  [...]
  Testing ... (interrupt to exit)
  Event: time 1635094270.706983, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7a
  Event: time 1635094270.706983, type 1 (EV_KEY), code 560 (KEY_ALS_TOGGLE), 
value 1
  Event: time 1635094270.706983, -- SYN_REPORT 
  Event: time 1635094270.707032, type 1 (EV_KEY), code 560 (KEY_ALS_TOGGLE), 
value 0
  Event: time 1635094270.707032, -- SYN_REPORT 
  Event: time 1635094276.299188, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7a
  Event: time 1635094276.299188, type 1 (EV_KEY), code 560 (KEY_ALS_TOGGLE), 
value 1
  Event: time 1635094276.299188, -- SYN_REPORT 
  Event: time 1635094276.299244, type 1 (EV_KEY), code 560 (KEY_ALS_TOGGLE), 
value 0
  Event: time 1635094276.299244, -- SYN_REPORT 

  
  Somehow monitor-sensor always reports the ambient light value as 400 lux, 
which seems incorrect.

  $ monitor-sensor
  Waiting for iio-sensor-proxy to appear
  +++ iio-sensor-proxy appeared
  === No accelerometer
  === Has ambient light sensor (value: 400,00, unit: lux)
  === No proximity sensor

  
  I have made some test with Windows 10 21H1, using this tool 
https://www.microsoft.com/p/sensorexplorer/9pgl3xpq1tpx
  When the ambient light senor is disable via the hotkey, it always report 
value as 400 lux to Windows.
  When the sensor is enable, the value changes as the ambient light condition 
changes.
  It seems that in Ubuntu, the sensor is acting as it is in disable state; as 
observed in Windows.

  So I am not sure if the key event is not registered, or if Ubuntu
  cannot enable the sensor.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udev 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CustomUdevRuleFiles: 70-snap.gnome-calculator.rules 70-snap.firefox.rules 
50-usb-ssd-trim.rules 70-snap.core.rules 70-snap.snap-store.rules 
70-snap.gnome-system-monitor.rules 70-snap.gnome-logs.rules 
70-snap.canonical-livepatch.rules 70-snap.gnome-characters.rules
  Date: Mon Oct 25 00:45:44 2021
  InstallationDate: Installed on 2018-02-15 (1347 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UQK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=130ff3d4-7338-4c7d-92ff-18caafab6bdc ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to impish on 2021-10-21 (3 days ago)
  dmi.bios.date: 04/17/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UQK.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UQK
  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.:bvrUX410UQK.311:bd04/17/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX410UQK:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX410UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UQK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 1943163] Re: systemd.mount constantly unmounts an in use drive!

[Nick Rosbrook]

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

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  systemd.mount constantly unmounts an in use drive!

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd.mount constantly unmounts an in use sshfs drive!

  Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded.
  ░░ Subject: Unit succeeded
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ The unit UNIT has successfully entered the 'dead' state.
  Sep 09 11:20:01 $HOSTNAME systemd[1]: pathtomount.mount: Succeeded.
  ░░ Subject: Unit succeeded
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ The unit pathtomount.mount has successfully entered the 'dead' state.

  Change my kernel and the issue *seems* to have subsided. Coincidence
  or swapping kernels reconfigured whatever was causing the issue. Did
  not change kernel expecting to fix this, just so happened after I did
  this stopped happening. Judging by the time stamps (that 01 seconds)
  something was misbehaving with cron.

  This only seemed to affect the fuse mounts which correlates with other
  reports elsewhere I found but no real fixes and me changing kernels
  and rebuilding some things were just happenstance. i.e. magically
  fixed yields no answers. I installed a snap app around the time it
  started misbehaving but again could be pointless coincidence. I just
  noticed in the logs snap was playing with mounts for sandboxing.

  Just occurred to me that I think I've seen this before. When 20.04
  came out I updated my roommates laptop with it. It's old, just plays
  movies off the network and the hard drive died so I just did an
  install to a little flash drive. She'd be watching something and it
  would do that little buffer stutter like you just yanked the drive out
  mid audio/video playback and crash. Eventually I just moved the
  machine back to 18.04 because there was no rhyme or reason to why it
  was doing that. I spent a month hunting thermal trip issues, power
  saving, you name it but not systemd. I never found anything in the
  logs but I was looking for power/thermal/shutdown stuff not something
  idiotic unmounting the rootfs!

  While I fear my angry bits are seen as trolling there is a distinct
  fall off from 18.04. Every release past 19 has been riddled with
  massive problems across several machines. Another friend I upgraded to
  20.04, couldn't print. Worked fine in 18.04. Found a solution after
  months of printing from an 18.04 vm.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3.4
  ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Thu Sep  9 10:05:11 2021
  EcryptfsInUse: Yes
  MachineType: Micro-Star International Co., Ltd MS-7C02
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=8e862394-d94b-4c1a-81be-8cef6143bedd ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.H5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450 TOMAHAWK (MS-7C02)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:skuTobefilledbyO.E.M.:rv

[Touch-packages] [Bug 1969248] Re: Systemd-oomd frequently kills applications on 8GB RAM machine

[Nick Rosbrook]

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

This was fixed in bug 1972159.

** This bug has been marked a duplicate of bug 1972159
   systemd-oomd frequently kills firefox and visual studio code

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

Title:
  Systemd-oomd frequently kills applications on 8GB RAM machine

Status in systemd package in Ubuntu:
  New

Bug description:
  On a machine with 8GB of RAM, systemd-oomd will frequently kill
  applications. This has been most apparent for me when using Firefox
  with quite a lot of tabs open. This could probably be avoided by being
  more disciplined with the number of tabs in use but shouldn't need to
  be an active consideration for the user. I think this is less of a bug
  with systemd-oomd as it is effectively doing its job when memory is
  low, but rather I think this is more a case of the default amount of
  swap (1GB) not being sufficient if only 8GB of RAM is present.

  Attached output of `journalctl -u systemd-oomd.service` to show the
  frequency of applications being killed

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  systemd-oomd:
Installed: 249.11-0ubuntu3
Candidate: 249.11-0ubuntu3
Version table:
   *** 249.11-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-oomd 249.11-0ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 21:32:59 2022
  InstallationDate: Installed on 2022-03-31 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV on bionic

[Tiago Pasqualini da Silva]

** Also affects: ubuntu-pro
   Importance: Undecided
   Status: New

** Also affects: ubuntu-pro/18.04
   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/2024864

Title:
  systemd-networkd crashes with SIGSEGV on bionic

Status in systemd:
  New
Status in Ubuntu Pro:
  New
Status in Ubuntu Pro 18.04 series:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158

  The following patch fixes the issue:
  
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8

  
  I was able simulate it to happen on gdb, by breaking once the manager is 
setup, getting the loopback device and running link_drop_foreign_config on the 
loopback device:

  
  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
  Starting program: /lib/systemd/systemd-networkd 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL

  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
  $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000", 
  n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
  storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
 
  type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
  $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772, 
state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0, 
flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state = 
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0, 
address_label_messages = 0, route_messages = 0, 
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0, 
enslaving = 0, 
addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0, 
routes_foreign = 0x55796180, addresses_configured = false, 
addresses_ready = false, dhcp_client = 0x0, dhcp_lease = 0x0, lease_file = 
0x5579c620 "/run/systemd/netif/leases/1", original_mtu = 0, 
dhcp4_messages = 0, dhcp4_configured = false, dhcp6_configured = false,

[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV on bionic

[Tiago Pasqualini da Silva]

** Description changed:

  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:
  
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158
  
  The following patch fixes the issue:
  
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8
  
- 
- I was able simulate it to happen on gdb, by breaking once the manager is 
setup, getting the loopback device and running link_drop_foreign_config on the 
loopback device:
- 
+ I was able simulate it to happen on gdb, by breaking once the manager is
+ setup, getting the loopback device and running link_drop_foreign_config
+ on the loopback device:
  
  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
- Starting program: /lib/systemd/systemd-networkd 
+ Starting program: /lib/systemd/systemd-networkd
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL
  
  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
- $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000", 
- n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
- storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
 
- type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
+ $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000",
+ n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
+ storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
+ type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
- $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772, 
-   state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
-   __u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0, 
-   flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state = 
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0, 
-   address_label_messages = 0, route_messages = 0, 
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0, 
enslaving = 0, 
-   addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0, 
routes_foreign = 0x55796180, addresses_configured = false, 
-   addresses_ready

[Touch-packages] [Bug 2004179] Re: neutron-linuxbridge-agent flat network incompatibility with systemd-networkd

[Nick Rosbrook]

> Since merging https://github.com/systemd/systemd/pull/17392, systemd-
network will remove the master flag > from the "public" interface, that
neutron-linuxbridge-agent assigned to the bridge for the network, e.g. >
brq88363244-5f, breaking all network on the flat network.

> The fix was revered in bug #1929560, but the behavior will not be
reverted in newer releases. Therefore, > every reload of systemd-
networkd will remove the physical network interface from neutrons
bridge.

It looks like the patch was backported to stable releases in that bug;
not reverted. Are you saying that that patch is wrong? Or that you want
that behavior still? Looking at the upstream code quickly, things have
changed quite a bit so I am not sure what the current behavior is.

> What would be the recommended why to configure networking on compute hosts 
> with Ubuntu OpenStack and flat > networks? Not using systemd-networkd or 
> netplan at all, but only /etc/network/interfaces?
> 
> Is there any modern alternative?

It sounds like a support site would be more appropriate:
https://discourse.ubuntu.com/t/community-support/709.

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

Title:
  neutron-linuxbridge-agent flat network incompatibility with systemd-
  networkd

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  We are running an OpenStack installation from Ubuntu's Cloud Archive,
  and our computer hosts have their network configured with systemd-
  networkd. For example, a bond and several VLANs on top, including two
  VLANs used for OpenStack flat networks. We are using neutron-
  linuxbridge-agent, i.e. no OVS or OVN.

  Network interface overview:

   ┌──┐ ┌──┐ ┌──┐
   │ eno2 │ │ eno3 │ │ eno4 │
   └───┬──┘ └───┬──┘ └───┬──┘
   │││
   ┌───┴┴┴──┐
   │ bond0  │
   └─┬───┬─┬┘
 │   │ │
 ┌───┴──┐ ┌──┴───┐ ┌───┴┐
 │ tnet │ │ stor │ │ public │
 └──┘ └──┘ └┘

  The "public" network is a flat provider network (VLAN) that shall be
  used by neutron-linuxbridge-agent and nova-compute to attach to
  virtual machines. "tnet" is used for VXLAN overlay networks, and
  "stor" for Ceph. The issue is with "public" only.

  The systemd-networkd configuration sets up all interfaces. We
  previously used netplan, but missing some needed options. It does use
  systemd-networkd too, so no relevant change to the problem.

  Since merging https://github.com/systemd/systemd/pull/17392, systemd-
  network will remove the master flag from the "public" interface, that
  neutron-linuxbridge-agent assigned to the bridge for the network, e.g.
  brq88363244-5f, breaking all network on the flat network.

  The fix was revered in bug #1929560, but the behavior will not be
  reverted in newer releases. Therefore, every reload of systemd-
  networkd will remove the physical network interface from neutrons
  bridge.

  Using "bridge_mappings" with nova-compute has never been finished,
  according to bug #1105488. nova-compute always requires the dynamic
  bridge, e.g. brq88363244-5f, to be present.

  @ddstreet asked for a new bug and the network configuration:

  # /etc/systemd/network/10-eno1.network:
  [..]

  # /etc/systemd/network/10-eno2.network:
  [Match]
  Name=eno2
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno3.network:
  [Match]
  Name=eno3
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno4.network:
  [Match]
  Name=eno4
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-bond0.netdev:
  [NetDev]
  Name=bond0
  Kind=bond
  MTUBytes=9000

  [Bond]
  Mode=802.3ad
  LACPTransmitRate=fast
  MIIMonitorSec=100ms
  TransmitHashPolicy=layer3+4

  # /etc/systemd/network/10-bond0.network:
  [Match]
  Name=bond0

  [Link]
  MTUBytes=9000

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes
  VLAN=tnet
  VLAN=stor
  VLAN=pulic

  # /etc/systemd/network/10-public.netdev:
  [NetDev]
  Name=public
  Kind=vlan
  MTUBytes=1500

  [VLAN]
  Id=82

  # /etc/systemd/network/10-public.network:
  [Match]
  Name=public

  [Link]
  MTUBytes=1500

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes

  # /etc/systemd/network/10-tnet.netdev:
  [..]

  # /etc/systemd/network/10-tnet.network:
  [..]

  # /etc/systemd/network/10-stor.netdev:
  [..]

  # /etc/systemd/network/10-stor.network:
  [..]

  
  neutron-linuxbridge-agent is configured to use "public" as a flat network, 

[Touch-packages] [Bug 2004179] Re: neutron-linuxbridge-agent flat network incompatibility with systemd-networkd

[Nick Rosbrook]

Also what release are you running?


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

Title:
  neutron-linuxbridge-agent flat network incompatibility with systemd-
  networkd

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  We are running an OpenStack installation from Ubuntu's Cloud Archive,
  and our computer hosts have their network configured with systemd-
  networkd. For example, a bond and several VLANs on top, including two
  VLANs used for OpenStack flat networks. We are using neutron-
  linuxbridge-agent, i.e. no OVS or OVN.

  Network interface overview:

   ┌──┐ ┌──┐ ┌──┐
   │ eno2 │ │ eno3 │ │ eno4 │
   └───┬──┘ └───┬──┘ └───┬──┘
   │││
   ┌───┴┴┴──┐
   │ bond0  │
   └─┬───┬─┬┘
 │   │ │
 ┌───┴──┐ ┌──┴───┐ ┌───┴┐
 │ tnet │ │ stor │ │ public │
 └──┘ └──┘ └┘

  The "public" network is a flat provider network (VLAN) that shall be
  used by neutron-linuxbridge-agent and nova-compute to attach to
  virtual machines. "tnet" is used for VXLAN overlay networks, and
  "stor" for Ceph. The issue is with "public" only.

  The systemd-networkd configuration sets up all interfaces. We
  previously used netplan, but missing some needed options. It does use
  systemd-networkd too, so no relevant change to the problem.

  Since merging https://github.com/systemd/systemd/pull/17392, systemd-
  network will remove the master flag from the "public" interface, that
  neutron-linuxbridge-agent assigned to the bridge for the network, e.g.
  brq88363244-5f, breaking all network on the flat network.

  The fix was revered in bug #1929560, but the behavior will not be
  reverted in newer releases. Therefore, every reload of systemd-
  networkd will remove the physical network interface from neutrons
  bridge.

  Using "bridge_mappings" with nova-compute has never been finished,
  according to bug #1105488. nova-compute always requires the dynamic
  bridge, e.g. brq88363244-5f, to be present.

  @ddstreet asked for a new bug and the network configuration:

  # /etc/systemd/network/10-eno1.network:
  [..]

  # /etc/systemd/network/10-eno2.network:
  [Match]
  Name=eno2
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno3.network:
  [Match]
  Name=eno3
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno4.network:
  [Match]
  Name=eno4
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-bond0.netdev:
  [NetDev]
  Name=bond0
  Kind=bond
  MTUBytes=9000

  [Bond]
  Mode=802.3ad
  LACPTransmitRate=fast
  MIIMonitorSec=100ms
  TransmitHashPolicy=layer3+4

  # /etc/systemd/network/10-bond0.network:
  [Match]
  Name=bond0

  [Link]
  MTUBytes=9000

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes
  VLAN=tnet
  VLAN=stor
  VLAN=pulic

  # /etc/systemd/network/10-public.netdev:
  [NetDev]
  Name=public
  Kind=vlan
  MTUBytes=1500

  [VLAN]
  Id=82

  # /etc/systemd/network/10-public.network:
  [Match]
  Name=public

  [Link]
  MTUBytes=1500

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes

  # /etc/systemd/network/10-tnet.netdev:
  [..]

  # /etc/systemd/network/10-tnet.network:
  [..]

  # /etc/systemd/network/10-stor.netdev:
  [..]

  # /etc/systemd/network/10-stor.network:
  [..]

  
  neutron-linuxbridge-agent is configured to use "public" as a flat network, 
e.g.:

  # /etc/neutron/plugins/ml2/linuxbridge_agent.ini
  [linux_bridge]
  physical_interface_mappings = public:public
  [..]
  
  When everything is started and a VM needs to be connected to the flat 
network, neutron-linuxbridge-agent creates a dynamic bridge for nova-compute, 
e.g. brq88363244-5f:

  14: public@bond0:  mtu 1500 master 
brqe240c66b-da state UP
  59: brqe240c66b-da:  mtu 1500 state UP

  When systemd-networkd is restarted, it will see that "public" is up
  but has a master assigned. It will be unassigned and break the flat
  network:

  14: public@bond0:  mtu 1500 state UP
  59: brqe240c66b-da:  mtu 1500 state UP

  What would be the recommended why to configure networking on compute
  hosts with Ubuntu OpenStack and flat networks? Not using systemd-
  networkd or netplan at all, but only /etc/network/interfaces?

  Is there any modern alternative?

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

[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV on bionic

[Heitor Alves de Siqueira]

** Tags added: se-sponsor-halves

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

Title:
  systemd-networkd crashes with SIGSEGV on bionic

Status in systemd:
  New
Status in Ubuntu Pro:
  New
Status in Ubuntu Pro 18.04 series:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158

  The following patch fixes the issue:
  
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8

  I was able simulate it to happen on gdb, by breaking once the manager
  is setup, getting the loopback device and running
  link_drop_foreign_config on the loopback device:

  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
  Starting program: /lib/systemd/systemd-networkd
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL

  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
  $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000",
  n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
  storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
  type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
  $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772,
    state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
    __u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0,
    flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state = 
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0,
    address_label_messages = 0, route_messages = 0, 
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0, 
enslaving = 0,
    addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0, 
routes_foreign = 0x55796180, addresses_configured = false,
    addresses_ready = false, dhcp_client = 0x0, dhcp_lease = 0x0, lease_file = 
0x5579c620 "/run/systemd/netif/leases/1", original_mtu = 0,
    dhcp4_messages = 0, dhcp4_configured = false, dhcp6_configured = false, 
ndisc_messages = 0, ndisc_configured = false, ipv4ll = 0x0,
    ipv4ll_address = false, ipv4ll_route = false, static_routes_config

[Touch-packages] [Bug 2004179] Re: neutron-linuxbridge-agent flat network incompatibility with systemd-networkd

[Jan Graichen]

> > The fix was revered in bug #1929560, but the behavior will not be reverted 
> > in newer releases. Therefore, every reload of systemd-networkd will remove 
> > the physical network interface from neutrons bridge.
> 
> It looks like the patch was backported to stable releases in that bug; not 
> reverted. Are you saying that that patch is wrong? Or that you want that 
> behavior still? Looking at the upstream code quickly, things have changed 
> quite a bit so I am not sure what the current behavior is.

Please see
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1929560/comments/15.

> It sounds like a support site would be more appropriate

Dan requested these details here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1929560/comments/13

> Also what release are you running?

Since the initial report, we upgraded from 18.04 to 20.04.

--

We continued to investigate for a solution, and systemd added a
KeepMaster= option in v250
(https://github.com/systemd/systemd/commit/57aef9d7373c97d04beb6c5fc268496c3fdcf0a4).
Unfortunately, Ubuntu 22.04 only includes systemd v249.

Would it be possible to have
https://github.com/systemd/systemd/commit/57aef9d7373c97d04beb6c5fc268496c3fdcf0a4
backported to Ubuntu 22.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/2004179

Title:
  neutron-linuxbridge-agent flat network incompatibility with systemd-
  networkd

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  We are running an OpenStack installation from Ubuntu's Cloud Archive,
  and our computer hosts have their network configured with systemd-
  networkd. For example, a bond and several VLANs on top, including two
  VLANs used for OpenStack flat networks. We are using neutron-
  linuxbridge-agent, i.e. no OVS or OVN.

  Network interface overview:

   ┌──┐ ┌──┐ ┌──┐
   │ eno2 │ │ eno3 │ │ eno4 │
   └───┬──┘ └───┬──┘ └───┬──┘
   │││
   ┌───┴┴┴──┐
   │ bond0  │
   └─┬───┬─┬┘
 │   │ │
 ┌───┴──┐ ┌──┴───┐ ┌───┴┐
 │ tnet │ │ stor │ │ public │
 └──┘ └──┘ └┘

  The "public" network is a flat provider network (VLAN) that shall be
  used by neutron-linuxbridge-agent and nova-compute to attach to
  virtual machines. "tnet" is used for VXLAN overlay networks, and
  "stor" for Ceph. The issue is with "public" only.

  The systemd-networkd configuration sets up all interfaces. We
  previously used netplan, but missing some needed options. It does use
  systemd-networkd too, so no relevant change to the problem.

  Since merging https://github.com/systemd/systemd/pull/17392, systemd-
  network will remove the master flag from the "public" interface, that
  neutron-linuxbridge-agent assigned to the bridge for the network, e.g.
  brq88363244-5f, breaking all network on the flat network.

  The fix was revered in bug #1929560, but the behavior will not be
  reverted in newer releases. Therefore, every reload of systemd-
  networkd will remove the physical network interface from neutrons
  bridge.

  Using "bridge_mappings" with nova-compute has never been finished,
  according to bug #1105488. nova-compute always requires the dynamic
  bridge, e.g. brq88363244-5f, to be present.

  @ddstreet asked for a new bug and the network configuration:

  # /etc/systemd/network/10-eno1.network:
  [..]

  # /etc/systemd/network/10-eno2.network:
  [Match]
  Name=eno2
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno3.network:
  [Match]
  Name=eno3
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-eno4.network:
  [Match]
  Name=eno4
  
  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  # /etc/systemd/network/10-bond0.netdev:
  [NetDev]
  Name=bond0
  Kind=bond
  MTUBytes=9000

  [Bond]
  Mode=802.3ad
  LACPTransmitRate=fast
  MIIMonitorSec=100ms
  TransmitHashPolicy=layer3+4

  # /etc/systemd/network/10-bond0.network:
  [Match]
  Name=bond0

  [Link]
  MTUBytes=9000

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes
  VLAN=tnet
  VLAN=stor
  VLAN=pulic

  # /etc/systemd/network/10-public.netdev:
  [NetDev]
  Name=public
  Kind=vlan
  MTUBytes=1500

  [VLAN]
  Id=82

  # /etc/systemd/network/10-public.network:
  [Match]
  Name=public

  [Link]
  MTUBytes=1500

  [Network]
  LinkLocalAddressing=no
  ConfigureWithoutCarrier=yes

  # /etc/systemd/network/10-tnet.netdev:
  [..]

  # /etc/systemd/network/10-tnet.network:
  [..]

  # /etc/systemd/network/10-stor.netdev:
  [..]

  # /etc/sys

[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV on bionic

[Heitor Alves de Siqueira]

Thank you for the bug report, Thiago! I did a little bit of housekeeping
so that this LP accurately reflects this targeting Ubuntu Pro 18.04.

Could you please fill in the description according to the SRU template?

https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

** Changed in: systemd
   Status: New => Fix Released

** Changed in: systemd
 Assignee: Tiago Pasqualini da Silva (tiago.pasqualini) => (unassigned)

** Changed in: ubuntu-pro/18.04
 Assignee: (unassigned) => Tiago Pasqualini da Silva (tiago.pasqualini)

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

** Changed in: ubuntu-pro/18.04
   Status: New => In Progress

** Changed in: ubuntu-pro/18.04
   Importance: Undecided => Medium

** Summary changed:

- systemd-networkd crashes with SIGSEGV on bionic
+ systemd-networkd crashes with SIGSEGV

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

Title:
  systemd-networkd crashes with SIGSEGV

Status in systemd:
  Fix Released
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158

  The following patch fixes the issue:
  
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8

  I was able simulate it to happen on gdb, by breaking once the manager
  is setup, getting the loopback device and running
  link_drop_foreign_config on the loopback device:

  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
  Starting program: /lib/systemd/systemd-networkd
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL

  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
  $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000",
  n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
  storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
  type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
  $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772,
    state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
    __u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0,

[Touch-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation

[Steve Langasek]

Currently nothing to be sponsored, so unsubscribing the team.  Tony, if
you want to provide a matching patch for SRU to the stable series,
please feel free to resubscribe ubuntu-sponsors once it's available.

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

Title:
  pcscd.socket is disabled after installation

Status in pcsc-lite package in Ubuntu:
  Fix Released
Status in pcsc-lite source package in Jammy:
  Triaged
Status in pcsc-lite source package in Kinetic:
  Triaged
Status in pcsc-lite source package in Lunar:
  Triaged
Status in pcsc-lite package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  The pscc-lite package provides an open source implementation of PC/SC,
  the de-facto standard to interface Personal Computers with Smart
  Cards/Readers.

  This bug is in the upstream debian packaging, and results in the
  pcscd.socket being disabled after installation. This prevents
  automatic startup of the associated pcscd.service, thus preventing
  automatic handling of Smart Cards/Readers w/out manual intervention to
  enable the socket (which doesn't persist across reboots).

  This is especially painful for users that require Smart Authentication
  for login.

  [ Test Plan ]

  Steps to reproduce:

  1. If installed, remove and do a fresh install of the package pcscd
  (the sole version released for jammy is 1.9.5-3).

  2. Verify that the pcscd.socket is disabled:

  $ systemctl status pcscd.socket
  ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket
   Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor 
preset: enabled)
   Active: inactive (dead)
     Triggers: ● pcscd.service
   Listen: /run/pcscd/pcscd.comm (Stream)

  3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or
  Nitrokey) that's known to work on Ubuntu and verify that it fails to
  work.

  Repeating the same steps with a package built with the patch attached
  to comment #27 should ensure that the socket is enabled, and that
  interaction with a Smart Card or Crypto Token should work w/out manual
  intervention.

  [ Where problems could occur ]

  This is a back-ported change from upstream and is a result of a bug in
  dh_installsystemd (see comment #26). As such the risk is minimal.

  The only potential risk of failure I can come up with is a snap that
  stages the old version of the client library, as it would be looking
  in the wrong place for the socket.

  [ Other Info ]

  This bug was originally reported against Ubuntu Mate 22.04, however it
  applies to all derivatives of Ubuntu Desktop 22.04 LTS.

  Note - while there's some disagreement as to whether this bug occurs
  100% of the time across all 22.04 installations, it's pretty clear
  from the upstream Debian bug and subsequent packaging fix that we
  should land this.

  As the upstream fix landed in 1.9.9-2 (which is already released in mantic) 
only the following releases are impacted by this bug:
   - jammy
   - kinetic
   - lunar

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


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

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Steve Langasek]

I have confirmed that the updated evince, without an updated apparmor,
fails in lunar with this error on stderr from evince:

internal error, please report: running "chromium" failed: open
/var/lib/snapd/inhibit/chromium.lock: permission denied

that looks sufficient to me to move forward with this SRU, with the
existing test case.

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Committed
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 1794064] Please test proposed package

[Steve Langasek]

Hello Olivier, or anyone else affected,

Accepted apparmor into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.8-1ubuntu2.1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Committed
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 2019970] Re: OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

[Seth Arnold]

That's awesome! I figure post-quantum cryptography will feel like
something for years in the future until the week when we all realize we
should have moved years earlier. Capture-and-store has to be going on
right now, on the assumptions that someone will bring a reliable quantum
machine to market. Thanks for working on it :)

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

Title:
  OpenSSL 3.0.2 crash in Ubuntu 22.04.2 LTS

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Full bug report at https://github.com/openssl/openssl/issues/20981

  No upstream impact: OpenSSL 3.0.9-dev does not contain the problem any
  more.

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


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

[Touch-packages] [Bug 2024540] Re: Vulnerability Can Gain Access even with Time OTP Enabled

[Seth Arnold]

What exactly is suspicious about remmina using shared memory?

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

Title:
  Vulnerability Can Gain Access even with Time OTP Enabled

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

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


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

[Touch-packages] [Bug 2024929] Re: dhclient does not reup valid_lft on service restart, kernel reaps IP

[Launchpad Bug Tracker]

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  dhclient does not reup valid_lft on service restart, kernel reaps IP

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Between Bionic and Focal, dhclient was patched to set the valid_lft on
  ipv4 addresses, which is a timer in the kernel that tells the kernel
  when to reap the IP. dhclient then is supposed to issue repeated `ip
  addr add` commands to reset this lft and prevent the kernel from
  releasing the IP. However, if you restart the dhclient service, it
  acquires a lease and then does *not* reup the lft. It only reups after
  a lease the currently running service knows about expires. So if you
  restart the dhclient service on a cadence that is faster than the DHCP
  leases in your network environment, you never see a lease expire
  during the lifetime of the service, which means the kernel will
  eventually rip the address out from under the server, causing a
  network outage. In some environments, the DCHP lease can be longer
  than a service restart cadence, and this bug can be very severe.

  I'm using the most up-to-date version of Focal's dhclient package.

  I'm not familiar with how the patch management for Ubuntu works, but
  the bug was introduced here:

  commit 41013cf19647ec323a7100fb61d50779d8c8a205 (tag: import/4.4.1-2)
  Author: Michael Gilbert 
  Date:   Tue Dec 11 03:55:12 2018 +

  4.4.1-2 (patches unapplied)

  Imported using git-ubuntu import.

  These changes specifically:

  diff --git a/debian/dhclient-script.linux b/debian/dhclient-script.linux
  index 9b0d3f89..f9b734ab 100644
  --- a/debian/dhclient-script.linux
  +++ b/debian/dhclient-script.linux
  @@ -246,6 +246,8 @@ case "$reason" in
   # new IP has been leased or leased IP changed => set it
   ip -4 addr add 
${new_ip_address}${new_subnet_mask:+/$new_subnet_mask} \
   ${new_broadcast_address:+broadcast $new_broadcast_address} \
  +${new_dhcp_lease_time:+valid_lft $new_dhcp_lease_time} \
  +${new_dhcp_lease_time:+preferred_lft $new_dhcp_lease_time} \
   dev ${interface} label ${interface}

   if [ -n "$new_interface_mtu" ]; then
  @@ -277,6 +279,12 @@ case "$reason" in
  fi
  done
  fi
  +else # RENEW||REBIND
  +ip -4 addr change 
${new_ip_address}${new_subnet_mask:+/$new_subnet_mask} \
  +${new_broadcast_address:+broadcast $new_broadcast_address} \
  +${new_dhcp_lease_time:+valid_lft $new_dhcp_lease_time} \
  +${new_dhcp_lease_time:+preferred_lft $new_dhcp_lease_time} \
  +dev ${interface} label ${interface}
   fi

   if [ -n "$alias_ip_address" ] &&
  @@ -323,6 +331,8 @@ case "$reason" in
   # set IP from recorded lease
   ip -4 addr add 
${new_ip_address}${new_subnet_mask:+/$new_subnet_mask} \
   ${new_broadcast_address:+broadcast $new_broadcast_address} \
  +${new_dhcp_lease_time:+valid_lft $new_dhcp_lease_time} \
  +${new_dhcp_lease_time:+preferred_lft $new_dhcp_lease_time} \
   dev ${interface} label ${interface}

   if [ -n "$new_interface_mtu" ]; then

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


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

[Touch-packages] [Bug 2023789] Re: IPv6 fails with busybox: ip: either "dev" is duplicate, or "permanent" is garbage

[Benjamin Drung]

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

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

Title:
  IPv6 fails with busybox: ip: either "dev" is duplicate, or "permanent"
  is garbage

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  This failure was detected while working on the amd64-net autopkgtest
  for initramfs-tools. Create a dummy root file system and launch qemu
  with user network and specify ip6=dhcp on the kernel command line:

  ```
  qemu-system-x86_64 -m 1G -drive 
"file=${ROOTDISK},if=${ROOTDISK_QEMU_IF},media=disk,format=raw" \
   ${USRDISK:+-drive 
"file=${USRDISK},if=${USRDISK_QEMU_IF},media=disk,format=raw"} \
   -nographic -no-reboot -kernel "/boot/vmlinuz-${KVER}" -initrd "${INITRAMFS}" 
\
   -device "virtio-net-pci,netdev=net0,bus=pci.0,addr=3,mac=52:54:00:65:43:21" \
   -netdev 
"user,id=net0,net=10.0.3.0/24,ipv6-net=fec7::/48,hostname=pizza,dnssearch=test,domainname=example.com,bootfile=/path/to/bootfile2"
 \
   -device "virtio-net-pci,netdev=net1,bus=pci.0,addr=5,mac=52:54:00:12:34:56" \
   -netdev 
"user,id=net1,hostname=goulash,dnssearch=example,dnssearch=example.net,domainname=test,bootfile=/path/to/bootfile"
 \
   -append "root=/dev/${ROOTDISK_LINUX_NAME} ro console=ttyS0,115200 ip6=dhcp"
  ```

  /sbin/dhclient-script fails. Running the script with "set -x" shows
  the culprit in PREINIT6:

  ```
  + ip -6 addr flush dev ens5 scope global permanent
  ip: either "dev" is duplicate, or "permanent" is garbage
  ```

  The busybox ip command does not support the FLAG "permanent".

  Distro: Ubuntu 23.10
  Packages:
   isc-dhcp-client 4.4.3-P1-2ubuntu2
   busybox-initramfs 1:1.35.0-4ubuntu1

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


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

[Touch-packages] [Bug 1997161] Re: libunwind-dev has wrong LTO data

[Ghislain Bourgeois]

I get the exact same error when building a rock on 22.04. The build is
using g++.

:: lto1: fatal error: bytecode stream in file 
‘/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libunwind.a’ 
generated with LTO version 11.2 instead of the expected 11.3
:: compilation terminated.
:: lto-wrapper: fatal error: g++ returned 1 exit status

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

** Changed in: llvm-toolchain-14 (Ubuntu)
   Status: Confirmed => New

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

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

Title:
  libunwind-dev has wrong LTO data

Status in libunwind package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
  New

Bug description:
  When linking libunwind into my program I get the following message:

  lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux-
  gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with
  LTO version 11.2 instead of the expected 11.3

  LTO stands for link time optimization.

  My guess is that libunwind-x86_64.a in Ubuntu repositories was
  compiled with earlier gcc 11.2, but the gcc version on this new
  installation of 22.04 is 11.3.

  I am not certain whether the right fix is to recompile with newer
  compiler version, or to make the library without turning on link time
  optimization options. libunwind is used for debugging, so there is no
  obvious benefit in enabling link time optimization for this library.

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


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