[Touch-packages] [Bug 2035220] Re: cve-2023-4863

[Nathan Teodosio]

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  Fix Released
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  Confirmed

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Touch-packages] [Bug 2035397] Re: I had a problem with HDMI

[Daniel van Vugt]

I'm guessing the HDMI port is connected to the Nvidia GPU, it usually is
on a hybrid laptop. And I'm seeing that you don't have a proper driver
for the Nvidia GPU installed. Please open the 'Additional Drivers' app
to install a supported Nvidia driver.

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

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

** Tags added: hybrid multigpu multimonitor nouveau

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

Title:
  I had a problem with HDMI

Status in Ubuntu:
  Incomplete

Bug description:
  I don't know a lot about Linux and Ubuntu, but recently, due to
  college, I did a duo boot so I could have both Windows and Linux. But,
  whenever im at Linux, for some reason, my screen doesn't share with
  another monitor through HDMI, but with Windows it does. So i searched
  for some instructions, and ive been told to try and run this code in
  my therminal ubuntu-bug xorg, and that's why im here.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 13:56:48 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] 
[1d05:1116]
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / 
Max-Q] [1d05:1116]
  InstallationDate: Installed on 2023-08-31 (13 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Avell High Performance A70 LIV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=c99dc4b0-1110-43e9-a231-5487f4e4ce0d ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07AVE00
  dmi.board.asset.tag: Standard
  dmi.board.name: Avell A70 LIV
  dmi.board.vendor: Avell High Performance
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07AVE00:bd02/22/2021:br5.17:efr1.14:svnAvellHighPerformance:pnA70LIV:pvrStandard:rvnAvellHighPerformance:rnAvellA70LIV:rvrStandard:cvnAvellHighPerformance:ct10:cvrStandard:skuA70LIV:
  dmi.product.family: A70 LIV
  dmi.product.name: A70 LIV
  dmi.product.sku: A70 LIV
  dmi.product.version: Standard
  dmi.sys.vendor: Avell High Performance
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  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/+bug/2035397/+subscriptions


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

[Touch-packages] [Bug 2035220] Re: cve-2023-4863

[Nishit Majithia]

Firefox has been released for focal(USN-6367-1) and other releases(as snap).
Thunderbird has been patched and released as well (USN-6368-1)
thanks

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

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

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  Fix Released
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  Confirmed

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Philip A Swiderski Jr]

everything was working before the updating and then I updated "
udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-
timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-
systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10) " and all of a sudden digikam
could no longer talk to my camera, gphoto2 could no longer talk to my
camera, entangle could no longer talk to my camera, again it all was
working right before the update, I took a nap came back had an update,
and did the update, went to live stream and gphoto2 could detect my
camera, I took a picture with the camera manually, tried to import with
digikam, digikam failed to connect, tried to use camera with entangle,
which reported no camera attached, lsusb saw my camera clearly lsusb Bus
003 Device 006: ID 04b0:043f Nikon Corp. D5600 the only thing that
changed was the above update/upgrade and now I am unable to do what I
normally do, and well this bug stinks.

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  Invalid
Status in systemd source package in Mantic:
  Invalid

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Philip A Swiderski Jr]

No I am using it for both still photography and for video streaming.

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  Invalid
Status in systemd source package in Mantic:
  Invalid

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Steve Langasek]

Ok that shows ACLs are present.  But I also just realized this was about
still photography, not video, so those aren't the relevant devices.
Less straightforward to find the right devices for a USB camera.

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  Invalid
Status in systemd source package in Mantic:
  Invalid

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Philip A Swiderski Jr]

Here is my output of ls -l /dev/video*

ls -l /dev/video*
crw-rw+ 1 root video 81, 0 Sep 13 18:45 /dev/video0
crw-rw+ 1 root video 81, 1 Sep 13 18:45 /dev/video1
crw-rw+ 1 root video 81, 2 Sep 13 18:45 /dev/video2

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  Invalid
Status in systemd source package in Mantic:
  Invalid

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Steve Langasek]

For understanding the nature of regression, it would be useful to see
the output of

ls -l /dev/video*

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  Invalid
Status in systemd source package in Mantic:
  Invalid

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2028180] Re: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

[Steve Langasek]

Marking verification-failed for jammy as this is the only patch touching
udev rules in this SRU and the likely source of the regression

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

Title:
  [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Fix Released
Status in systemd source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When working with NVMe/TCP host functionality, connecting to NVMe
  subsystem through multiple controllers can lead to an invalid device
  link created in /dev/disc/by-id/ being created.

  Steps to reproduce:
  Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
  Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
  Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

  This may cause users to choose the wrong link and would not be able to
  work with it.

  [Fix]

  udev-rules: fix nvme symlink creation on namespace changes
  
https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0

  [Test Plan]
  Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against 
a few Dell Storage systems.

  Steps to Reproduce:
  1. Use nvme connect-all to connect to an NVMe/TCP subsystems
  2. Check /dev/disk/by-id. The symlinks for NVMe devices should have the 
namespace id appended to them. E.g., if there is /dev/disk/by-id/nvme-$FOO, 
there should be a /dev/disk/by-id/name-$FOO_$ID.

  [ Where problems could occur ]
  This issue may be experienced by users who use NVMe/TCP solutions.
  Regression risk is low, because the existing symlink pattern is kept for 
backwards compatibility. This patch adds a new symlink pattern that includes 
the namespace ID, which will remain persistent throughout a boot.

  [ Other Info ]

  Expected Behavior:
  No duplicate entries of NVMe subsystems should exist.

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


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

[Touch-packages] [Bug 2028180] Re: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

** Tags removed: verification-done-jammy
** Tags added: verification-failed-jammy

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

Title:
  [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Fix Released
Status in systemd source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When working with NVMe/TCP host functionality, connecting to NVMe
  subsystem through multiple controllers can lead to an invalid device
  link created in /dev/disc/by-id/ being created.

  Steps to reproduce:
  Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
  Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
  Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

  This may cause users to choose the wrong link and would not be able to
  work with it.

  [Fix]

  udev-rules: fix nvme symlink creation on namespace changes
  
https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0

  [Test Plan]
  Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against 
a few Dell Storage systems.

  Steps to Reproduce:
  1. Use nvme connect-all to connect to an NVMe/TCP subsystems
  2. Check /dev/disk/by-id. The symlinks for NVMe devices should have the 
namespace id appended to them. E.g., if there is /dev/disk/by-id/nvme-$FOO, 
there should be a /dev/disk/by-id/name-$FOO_$ID.

  [ Where problems could occur ]
  This issue may be experienced by users who use NVMe/TCP solutions.
  Regression risk is low, because the existing symlink pattern is kept for 
backwards compatibility. This patch adds a new symlink pattern that includes 
the namespace ID, which will remain persistent throughout a boot.

  [ Other Info ]

  Expected Behavior:
  No duplicate entries of NVMe subsystems should exist.

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


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

[Touch-packages] [Bug 1982218] Re: wait-online does not correctly identify managed links

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  wait-online does not correctly identify managed links

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

Bug description:
  [Impact]

  systemd-networkd-wait-online will exit prematurely when the --any flag
  is passed, due to an incorrect patch in Ubuntu that is supposed to
  make systemd-networkd-wait-online exit when *no* links are managed.

  [Test Plan]

  This test uses a VM managed by libvirt. In this scenario we have the
  "default" network which provides DHCP to the VM, and the "no-dhcp"
  network which does not provide DHCP.

  To setup the VM (this assumes Jammy, but the same steps apply for
  Lunar using appropriate names and install media):

  1. Define the default and no-dhcp networks:

  $ cat > /tmp/net-default.xml << EOF
  
default
04260896-2701-422d-84e0-8e0df1122db3




  

  

  
  $ virsh net-create --file /tmp/net-default.xml
  $ cat > /tmp/net-default.xml << EOF
  
no-dhcp
2c047740-caab-4c90-8421-70da6732a759
  





  
  $ virsh net-create --file /tmp/net-no-dhcp.xml
  $ virsh net-start --network default
  $ virst net-start --network no-dhcp

  2. Create the VM using virt-install:

  virt-install \
  --connect=qemu:///system \
  --name=jammy \
  --arch=x86_64 \
  --cpu=host-passthrough \
  --ram=4096 \
  --vcpus=1 \
  
--disk=path=/var/lib/libvirt/images/jammy.qcow2,size=24,format=qcow2,sparse=true,bus=virtio
 \
  --virt-type=kvm \
  --accelerate \
  --hvm \
  --cdrom=/tmp/ubuntu-22.04.2-live-server-amd64.iso \
  --os-type=linux \
  --os-variant=generic \
  --graphics=spice \
  --input=tablet \
  --network=network=default,model=virtio \
  --video=qxl \
  --noreboot

  3. Complete the installation steps. Reboot the VM.

  Run the test:

  1. Detach the network interface so that the test starts with no
  interfaces attached:

  $ virsh detach-interface $VM network

  2. In the VM, write a network config for all en* links to use DHCP:

  $ cat > /etc/systemd/network/10-dhcp.network << EOF
  [Match]
  Name=en*

  [Network]
  DHCP=yes
  EOF

  3. Restart systemd-networkd:

  $ systemctl restart systemd-networkd

  4. On the host, attach an interface to the VM on the no-dhcp network,
  so that an IP is not assigned:

  $ virsh attach-interface $VM network no-dhcp

  5. Back in the VM, confirm that the device is in the
  degraded/configuring state:

  $ networkctl
  networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    8 ens3 etherdegradedconfiguring

  2 links listed.

  6. Run systemd-networkd-wait-online --any, and confirm that it does
  timeout instead of returning while the device is is still not
  configured:

  $ /lib/systemd/systemd-networkd-wait-online --any --timeout=10
  Timeout occurred while waiting for network connectivity.

  7. Confirm that the device is STILL in the degraded/configuring state:

  $ networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    8 ens3 etherdegradedconfiguring

  2 links listed.

  8. Now, leave systemd-network-wait-online --any running while we
  attach another interface:

  $ /lib/systemd/systemd-networkd-wait-online --any --timeout=0

  9. On the host, attach another interface to the VM on the default
  network, so that DHCP assigns the interface an IP:

  $ virsh attach-interface $VM network default

  10. Back in the VM, the systemd-networkd-wait-online process should
  have exited with success, and networkctl should show the new link as
  configured, while the old one is still configuring:

  $ /lib/systemd/systemd-networkd-wait-online --any --timeout=0
  $ echo $?
  0
  $ networkctl
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    8 ens3 etherdegradedconfiguring
    9 ens9 etherroutableconfigured

  3 links listed.

  [Where problems could occur]

  This patch we want to remove is totally confined to systemd-networkd-
  wait-online, so that's where we would see problems. From what I can
  tell, the patch is no longer doing what it was intended to do. E.g.
  running systemd-networkd-wait-online on a desktop install, where
  systemd-networkd does not manage links, results in a timeout. It only
  works with the --any flag, but the --any flag did not exist when the
  patch was written. If a user was relying on --any to make systemd-
  networkd-wait-online exit when no links are managed, they will see a
  c

[Touch-packages] [Bug 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  machinectl pull-tar/pull-raw Operation not permitted

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

Bug description:
  [impact]

  machinectl pull-tar does not work, ever

  [test case]

  see comment 2

  [regression potential]

  problems/failures during pull-tar operation

  [scope]

  needed only in j

  fixed (indirectly) by upstream commit referenced in original
  description, which is included in v250, so fixed already in k

  pull-tar does not fail on f; no fix needed there

  [original description]

  There is a bug in systemd 249, where one can't pull any images. This
  was fixed in version 250, and never got backported. (FIX:
  
https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851)

  Hopefully this can be addressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-container 249.11-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  4 04:51:42 2022
  InstallationDate: Installed on 2022-06-01 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  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/1977630/+subscriptions


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

[Touch-packages] [Bug 1991829] Re: machinectl read-only does not work

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  machinectl read-only does not work

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [impact]

  machinectl read-only does not work

  [test case]

  On a system where the systemd machines dir is *not* on a btrfs volume
  (e.g. it's on a normal ext4 fs), create an image 'test' and then:

  $ sudo machinectl image-status test
  test
  Type: directory
  Path: /var/lib/machines/test
  Hostname: ubuntu
OS: Ubuntu 20.04.5 LTS
RO: writable
   Created: Wed 2022-10-05 13:41:15 EDT; 34s ago

  $ sudo machinectl read-only test
  Could not mark image read-only: Access denied

  [regression potential]

  failure marking images ro or rw

  [scope]

  this is needed in all releases that include machinectl

  this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b

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


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

[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

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

Bug description:
  [Impact]

  Classless static routes served by DHCP are ignored by networkd in some
  cases. Specifically, the gateway is not being set for routes whenever
  the route destination is in the assigned network. This is a regression
  in behavior since Focal.

  [Test Plan]

  This is basically taken from systemd-networkd-tests.py. Using a veth
  pair, setup dnsmasq to serve the problematic routes:

  $ cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF
  [Match]
  Name=veth-peer

  [Network]
  IPv6AcceptRA=no
  Address=2600::1/0
  Address=192.168.5.1/24
  EOF

  $ cat > /etc/systemd/network/25-test.network << EOF
  [Match]
  Name=veth99

  [Network]
  DHCP=ipv4
  IPv6AcceptRA=false

  [DHCPv4]
  UseRoutes=yes
  EOF

  $ cat > /etc/systemd/network/25-veth.netdev << EOF
  [NetDev]
  Name=veth99
  Kind=veth
  MACAddress=12:34:56:78:9a:bc

  [Peer]
  Name=veth-peer
  MACAddress=12:34:56:78:9a:bd
  EOF

  $ mkdir -p /etc/systemd/system/systemd-networkd.service.d/
  $ cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  EOF

  $ systemctl daemon-reload
  $ systemctl restart systemd-networkd
  $ mkdir -p /run/networkd-ci
  $ dnsmasq --log-facility=/run/networkd-ci/test-dnsmasq.log 
--log-queries=extra --log-dhcp --pid-file=/run/networkd-ci/test-dnsmasq.pid 
--conf-file=/dev/null --bind-interfaces --interface=veth-peer 
--dhcp-leasefile=/run/networkd-ci/test-dnsmasq.lease --enable-ra 
--dhcp-range=2600::10,2600::20,2m --dhcp-range=192.168.5.10,192.168.5.200,2m 
--dhcp-option=option:mtu,1492 --dhcp-option=option:router,192.168.5.1 --port=0 
--no-resolv 
--dhcp-option=option:classless-static-route,0.0.0.0/0,192.168.5.4,8.0.0.0/8,192.168.5.5,192.168.5.64/26,192.168.5.5
 &

  $ systemctl restart systemd-networkd

  On an affected machine, the route to 192.168.5.64 on veth99 will be
  missing it's gateway address:

  $ ip r show dev veth99 192.168.5.64/26
  192.168.5.64/26 proto dhcp scope link src 192.168.5.181 metric 1024

  And, there will be a log message explaining that this was done
  intentionally:

  $ journalctl -u systemd-networkd --grep="veth99.*assigned network"
  Aug 03 16:58:49 mantic2 systemd-networkd[1418]: veth99: DHCP: requested route 
destination 192.168.5.64/26 is in the assigned network 192.168.5.0/24, ignoring 
gateway address 192.168.5.5

  On a fixed machine, the route for to 192.168.5.64 will correctly have
  its gateway configured:

  $ ip r show dev veth99 192.168.5.64/26
  192.168.5.64/26 via 192.168.5.5 proto dhcp src 192.168.5.181 metric 1024

  [Where problems could occur]

  The patch is in the DHCPv4 client code for handling routes from the
  DHCP server. It adds a flag, force_use_gw, to an internal function
  that essentially overrides the "ignore" behavior whenever classless
  static routes have been given. If we saw regressions, it would be
  related to creation of static routes handed down by DHCPv4 servers.

  [Original Description]

  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason t

[Touch-packages] [Bug 1999275] Re: systemd-binfmt.service fails in tests-in-lxd

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  systemd-binfmt.service fails in tests-in-lxd

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

Bug description:
  [Impact]

  systemd-binfmt.service fails in LXD because access
  /proc/sys/binfmt_misc is prevented by LXD apparmor config. This causes
  our autopkgtest to fail, and leaves systemd-binfmt.service in a failed
  state:

  root@jammy:~# systemctl status systemd-binfmt
  × systemd-binfmt.service - Set Up Additional Binary Formats
   Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static)
   Active: failed (Result: exit-code) since Thu 2023-08-17 18:54:18 UTC; 
1min 12s ago
 Docs: man:systemd-binfmt.service(8)
   man:binfmt.d(5)
   
https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
   https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
 Main PID: 118 (code=exited, status=1/FAILURE)
  CPU: 5ms

  Aug 17 18:54:18 jammy systemd[1]: Starting Set Up Additional Binary Formats...
  Aug 17 18:54:18 jammy systemd-binfmt[118]: Failed to add binary format: 
Permission denied
  Aug 17 18:54:18 jammy systemd[1]: systemd-binfmt.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 17 18:54:18 jammy systemd[1]: systemd-binfmt.service: Failed with result 
'exit-code'.
  Aug 17 18:54:18 jammy systemd[1]: Failed to start Set Up Additional Binary 
Formats.

  [Test Plan]

  1. test_no_failed from boot-and-services should pass.
  2. Manual test:

  * Start a Jammy LXD container:

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  * In the container, check systemd-binfmt.service:
  root@jammy:~# systemctl status systemd-binfmt
  ● systemd-binfmt.service - Set Up Additional Binary Formats
   Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static)
  Drop-In: /etc/systemd/system/systemd-binfmt.service.d
   └─override.conf
   Active: active (exited) since Thu 2023-08-17 19:01:00 UTC; 2min 27s ago
 Docs: man:systemd-binfmt.service(8)
   man:binfmt.d(5)
   
https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
   https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
 Main PID: 122 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Aug 17 19:01:00 jammy systemd[1]: Starting Set Up Additional Binary Formats...
  Aug 17 19:01:00 jammy systemd[1]: Finished Set Up Additional Binary Formats.
  root@jammy:~# journalctl -t systemd-binfmt -b
  Aug 17 19:01:00 jammy systemd-binfmt[122]: /proc/sys/fs/binfmt_misc is not 
mounted in read-write mode, skipping.

  [ Where problems could occur]

  The patches are contained to binfmt logic in systemd, and so any
  regressions would be within systemd-binfmt itself. The patches make it
  so that systemd-binfmt checks if /proc/sys/binfmt_misc is mounted as
  rw before trying to make any changes. If it is mounted, but read-only,
  then systemd-binfmt will exit cleanly and log a message indicating so.
  If the patch was incorrect, it could make it so that systemd-binfmt is
  not fully executed on systems where it should be.

  [Original Description]

  The systemd-binfmt.service requires read-write access to
  /proc/sys/fs/binfmt_misc, but this is not possible in unprivileged LXD
  containers without binfmt_misc namespace support in the kernel [1].
  When this service is triggered, we get the following failure from
  test_no_failed within tests-in-lxd:

  No failed units ...  journal for failed service 
systemd-binfmt.service ---
  Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: Starting Set Up Additional 
Binary Formats...
  Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd-binfmt[99]: Failed to flush 
binfmt_misc rules, ignoring: Permission denied
  Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd-binfmt[99]: 
/usr/lib/binfmt.d/python3.10.conf:1: Failed to delete rule 'python3.10', 
ignoring: Permission denied
  Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd-binfmt[99]: 
/usr/lib/binfmt.d/python3.10.conf:1: Failed to add binary format 'python3.10': 
Permission denied
  Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: systemd-binfmt.service: 
Main process exited, code=exited, status=1/FAILURE
  Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: systemd-binfmt.service: 
Failed with result 'exit-code'.
  Dec 08 10:43:37 autopkgtest-lxd-qicaxl systemd[1]: Failed to start Set Up 
Additional Binary Formats.
  FAIL
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cl

[Touch-packages] [Bug 2023229] Re: Autopkgtest failure for tests-in-lxd

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  Autopkgtest failure for tests-in-lxd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Fix Released
Status in systemd source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  systemd autopkgtests are failing in stable releases due to a change in LXD. 
We want the tests to be in good shape so that we can properly catch regressions 
etc. during SRUs.

  [Test Plan]

  The tests-in-lxd test should pass.

  [Where problems could occur]

  The patch adds a flag to lxc invocation in the debian/tests/tests-in-
  lxd script, so any problems would be contained to that test.

  [Original Description]

  Autopackagetests on multiple Jammy kernels show the same failure on
  the test-in-lxd test

  Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
  autopkgtest [16:33:58]: test tests-in-lxd: ---]
  autopkgtest [16:33:58]: test tests-in-lxd:  - - - - - - - - - - results - - - 
- - - - - - -
  tests-in-lxd FAIL non-zero exit status 1

  Where the error seems to be triggered by debian/tests/tests-in-lxd

  lxc publish systemd-lxc --alias $IMAGE

  To be determined if this a problem in the autopkgtest infrastructure
  or test bug.

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


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

[Touch-packages] [Bug 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  systemctl daemon-reexec forgets running services and starts everything
  new

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

Bug description:
  [Impact]

  Depending on the contents of /proc/cmdline, when systemd is re-
  executed with systemctl daemon-reexec, the --deserialize flag may be
  ignored because it was added after the other arguments. For example,
  if /proc/cmdline contains ---, then the re-exec cmdline might look
  like:

  $ cat /proc/1/cmdline | tr '\0' '\n' 
  /lib/systemd/systemd
  ---
  splash
  --system
  --deserialize
  54

  This causes systemd not to process the --deserialize 54 argument,
  causing it to start with a fresh state. This can cause all kinds of
  problems, and one easy symptom to see is many lines in the journal
  like:

  "$service.service: Found left-over process $pid ($service) in control
  group while starting unit. Ignoring."

  [Test Plan]

  1. (Only needed if your test system is not already affected) Edit the
  kernel command line to contain '---' at the end, which would trigger
  the bug. This can be done by appending '---' to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, running update-grub,
  and then rebooting.

  2. After enabling -proposed, install systemd:

  $ apt install systemd -y

  3. Check that the systemd.postinst script skipped the daemon-reexec
  call, and instead indicated a reboot is required:

  $ grep -Fsx systemd /run/reboot-required.pkgs
  systemd

  4. Reboot.

  5. Try to re-exec systemd, and check that there are not tons of "left-
  over process" log messages:

  $ systemctl daemon-reexec
  $ journalctl --grep "Found left-over process" -b 0

  6. Also confirm that the ordering of /proc/1/cmdline is correct, i.e.
  that --deserialize $fd comes before args from /proc/cmdline:

  $ cat /proc/1/cmdline | tr '\0' '\n'

  [Where problems could occur]

  There are two changes for this bug. First is the patch against systemd
  itself, which changes the ordering of arguments on the systemd
  commandline. This change simply makes it so that systemd's own
  arguments are always put first on it's re-exec commandline, and that
  anything from /proc/cmdline is appended after. Any regressions caused
  by this would also be seen in systemctl daemon-reexec invocations.

  The second change is in systemd.postinst, which skips the systemctl
  daemon-reexec call when upgrading from versions of systemd that could
  hit this bug. Regressions caused by this would be seen during package
  upgrades.

  
  [Original Description]

  # Our problem #

  During a regular update of our container environment, `systemd` (and
  the related packages libpam-systemd, libsystemd0, libudev1, systemd-
  sysv and udev) were updated from `249.11-0ubuntu3.6` to
  `249.11-0ubuntu3.7`. We're talking only about Ubuntu 22.04. Our Ubuntu
  20.04 is working fine with `systemctl daemon-reexec`.

  In my opinion, the update was not the problem because we've tried
  downgrading and tried these versions: (current) `249.11-0ubuntu3.7`,
  `249.11-0ubuntu3.6`, `249.11-0ubuntu3.4` and `249.11-0ubuntu3.3`. The
  symptoms were the same.

  # Symptoms #

  The `/var/lib/dpkg/info/systemd.postinst` executes a `systemctl
  daemon-reexec` and that ended in a disaster. It seems that `systemd`
  is forgetting all it started children and tries to start nearly every
  configured service again. Naturally, the old services are still
  running, and the ports can't be opened twice and `systemd` won't give
  up. Here are some(!) of the logfiles:

  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Create Volatile Files and 
Directories...
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 130 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 31475 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 31476 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED system

[Touch-packages] [Bug 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

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

Title:
  System can not shutdown if system has multiple VROC RAID arrays

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  The system can not shutdown if the system has multiple VROC RAID arrays.
  Intel has fixed it in systemd v251 [1].
  Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9.

  [1] The commit fixes the issue:
  commit 3a3b022d2cc112803ea7b9beea98bbcad110368a
  Author: Mariusz Tkaczyk 
  Date:   Tue Mar 29 12:49:54 2022 +0200

  shutdown: get only active md arrays.

  Current md_list_get() implementation filters all block devices, started 
from
  "md*". This is ambiguous because list could contain:
  - partitions created upon md device (mdXpY)
  - external metadata container- specific type of md array.

  For partitions there is no issue, because they aren't handle STOP_ARRAY
  ioctl sent later. It generates misleading errors only.

  Second case is more problematic because containers are not locked in 
kernel.
  They are stopped even if container member array is active. For that reason
  reboot or shutdown flow could be blocked because metadata manager cannot 
be
  restarted after switch root on shutdown.

  Add filters to remove partitions and containers from md_list. Partitions
  can be excluded by DEVTYPE. Containers are determined by MD_LEVEL
  property, we are excluding all with "container" value.

  Signed-off-by: Mariusz Tkaczyk 

  In the journal, we can see systemd-shutdown looping repeatedly as it
  tries and fails to detach all md devices:

  ...
  [  513.416293] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:5).
  [  513.422953] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or 
resource busy
  [  513.431227] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:4).
  [  513.437952] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or 
resource busy
  [  513.449298] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
  [  513.456278] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or 
resource busy
  [  513.465323] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
  [  513.472564] systemd-shutdown[1]: Couldn't finalize remaining  MD devices, 
trying again.
  [  513.485302] systemd-shutdown[1]: Failed to open watchdog device 
/dev/watchdog: No such file or directory
  [  513.496195] systemd-shutdown[1]: Stopping MD devices.
  [  513.502176] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
  [  513.513382] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
  [  513.521436] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
  [  513.534810] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
  [  513.545384] systemd-shutdown[1]: Failed to sync MD block device 
/dev/md126, ignoring: Input/output error
  [  513.557265] md: md126 stopped.
  [  513.561451] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:5).
  [  513.576673] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or 
resource busy
  [  513.589274] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:4).
  [  513.597976] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or 
resource busy
  [  513.607263] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
  [  513.615067] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or 
resource busy
  [  513.625157] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
  [  513.632209] systemd-shutdown[1]: Couldn't finalize remaining  MD devices, 
trying again.
  [  513.641474] systemd-shutdown[1]: Failed to open watchdog device 
/dev/watchdog: No such file or directory
  [  513.653660] systemd-shutdown[1]: Stopping MD devices.
  [  513.661257] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
  [  513.668833] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
  [  513.677347] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
  [  513.687047] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
  [  513.697206] systemd-shutdown[1]: Failed to sync MD block device 
/dev/md126, ignoring: Input/output error
  [  513.707193] md: md126 stopped.
  ...

  [ Test Plan ]

  1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for 
Data volume.
  2. Install system on System volume.
  3. Update systemd.
  4. Reboot the system.
  5. Verify if the system can reboot.

  [ Wh

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

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  [Impact]

  Kernel modules that provide pstore backends are unnecessarily loaded
  by systemd-pstore.service. While this is pretty benign behavior, it
  was introduced by an earlier SRU (bug 1978079) and is not consistent
  with newer releases in which systemd-pstore.service only tries to load
  efi_pstore.

  [Test Plan]

  Check which modules systemd-pstore.service depends on:

  $ systemctl list-dependencies systemd-pstore.service
  systemd-pstore.service
  * |--.mount
  * |-modprobe@chromeos_pstore.service
  * |-modprobe@efi_pstore.service
  * |-modprobe@pstore_blk.service
  * |-modprobe@pstore_zone.service
  * |-modprobe@ramoops.service
  * `-system.slice

  On an affected machine, we see several pstore providers in addition to
  efi_pstore. On a patched system, we should only see efi_pstore.

  [Where problems could occur]

  If somehow a user was running a configuration where one of the other
  modules was needed for pstore on their system, and that module was not
  loaded when systemd-pstore.service ran, they might not get correct
  output. However, the original bug (bug 1978079) was only about
  efi_pstore, and that will still be loaded by systemd-pstore.service.
  On all releases newer than Jammy, only efi_pstore is loaded by
  systemd-pstore.service, and there have not been bug reports.

  [Original 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 2035220] Re: cve-2023-4863

[Bug Watch Updater]

** Changed in: libwebp (Debian)
   Status: New => Confirmed

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  New
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  Confirmed

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Erich Eickmeyer]

I believe this is a regression of an SRU so I'm assigning this to "High"
and assigning to the last uploader.

** Tags added: regression-update

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  Invalid
Status in systemd source package in Mantic:
  Invalid

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Erich Eickmeyer]

Set to "invalid" for Lunar and Mantic since they have different systemd
versions.

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

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

** Changed in: systemd (Ubuntu Jammy)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

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

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  Invalid
Status in systemd source package in Mantic:
  Invalid

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Erich Eickmeyer]

Setting as "confirmed" as I have multiple anecdotal instances via
#ubuntu IRC channel as well as twitter confirming this issue.

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

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

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

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

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Lunar:
  New
Status in systemd source package in Mantic:
  New

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
  dmi.product.family: 00
  dmi.product.name: Alienware 18
  dmi.product.sku: Alienware 18
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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


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

[Touch-packages] [Bug 2035406] [NEW] udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

[Philip A Swiderski Jr]

Public bug reported:

udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: udev 249.11-0ubuntu3.10
ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
Uname: Linux 6.2.0-1009-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Sep 13 18:16:14 2023
InstallationDate: Installed on 2023-08-23 (21 days ago)
InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807)
MachineType: Alienware Alienware 18
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2019
dmi.bios.vendor: Alienware
dmi.bios.version: A15
dmi.board.name: 0FT9KT
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A15
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18:
dmi.product.family: 00
dmi.product.name: Alienware 18
dmi.product.sku: Alienware 18
dmi.product.version: A15
dmi.sys.vendor: Alienware

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


** Tags: amd64 apport-bug jammy

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

Title:
  udev update has broken ubuntu's ability to import photos in digikam,
  gphoto2 can no longer see usb camera, entangle can no longer see
  camera

Status in systemd package in Ubuntu:
  New

Bug description:
  udev update has broken ubuntu's ability to import photos in digikam, gphoto2 
can no longer see usb camera, entangle can no longer see camera 
  after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) 
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the 
camera fine, but the upgrade broke the usage, and cant roll back shows it will 
break system to roll back please fix ASAP.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udev 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 13 18:16:14 2023
  InstallationDate: Installed on 2023-08-23 (21 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  MachineType: Alienware Alienware 18
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency 
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 0FT9KT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chass

[Touch-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

[Heitor Alves de Siqueira]

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

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

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: linux (Ubuntu Focal)
   Importance: Medium => High

** Changed in: systemd (Ubuntu Focal)
   Status: Fix Committed => In Progress

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

** Changed in: linux (Ubuntu Jammy)
   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:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original 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 2029019] Re: PulseAudio doesn't start by logging in after a standby

[Luca Pavan]

https://forum.zorin.com/t/no-audio-after-relogging-in/26234

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

Title:
  PulseAudio doesn't start by logging in after a standby

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Often when I log in after a standby PulseAudio doesn't play any audio, the 
service is working but no audio is heard. I noticed that when this happens, if 
I adjust volume the system shows Dummy Output instead of the usual speaker 
small window. Also, one day when I was having right this issue I simply took a 
screenshot to a game that I was playing and audio was played 🤨.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luca   1456 F pulseaudio
   /dev/snd/pcmC0D0p:   luca   1456 F...m pulseaudio
   /dev/snd/controlC1:  luca   1456 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: zorin:GNOME
  DistroRelease: Zorin OS 16
  InstallationDate: Installed on 2022-10-01 (325 days ago)
  InstallationMedia: Zorin-OS 16.1 Core 64bit
  Package: pulseaudio 1:13.99.1-1ubuntu3.13 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99
  Tags: focal third-party-packages
  Uname: Linux 5.15.0-78-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Zorin. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/28/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K52N.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K52N
  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.:bvrK52N.218:bd01/28/2011:br4.6:svnASUSTeKComputerInc.:pnK52N:pvr1.0:rvnASUSTeKComputerInc.:rnK52N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
  dmi.product.name: K52N
  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/pulseaudio/+bug/2029019/+subscriptions


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

[Touch-packages] [Bug 2035397] [NEW] I had a problem with HDMI

[Enzo Reis de Oliveira]

Public bug reported:

I don't know a lot about Linux and Ubuntu, but recently, due to college,
I did a duo boot so I could have both Windows and Linux. But, whenever
im at Linux, for some reason, my screen doesn't share with another
monitor through HDMI, but with Windows it does. So i searched for some
instructions, and ive been told to try and run this code in my therminal
ubuntu-bug xorg, and that's why im here.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 13:56:48 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] 
[1d05:1116]
 NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / 
Max-Q] [1d05:1116]
InstallationDate: Installed on 2023-08-31 (13 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: Avell High Performance A70 LIV
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=c99dc4b0-1110-43e9-a231-5487f4e4ce0d ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/22/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N.1.07AVE00
dmi.board.asset.tag: Standard
dmi.board.name: Avell A70 LIV
dmi.board.vendor: Avell High Performance
dmi.board.version: Standard
dmi.chassis.asset.tag: Standard
dmi.chassis.type: 10
dmi.chassis.vendor: Avell High Performance
dmi.chassis.version: Standard
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07AVE00:bd02/22/2021:br5.17:efr1.14:svnAvellHighPerformance:pnA70LIV:pvrStandard:rvnAvellHighPerformance:rnAvellA70LIV:rvrStandard:cvnAvellHighPerformance:ct10:cvrStandard:skuA70LIV:
dmi.product.family: A70 LIV
dmi.product.name: A70 LIV
dmi.product.sku: A70 LIV
dmi.product.version: Standard
dmi.sys.vendor: Avell High Performance
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
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

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  I had a problem with HDMI

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know a lot about Linux and Ubuntu, but recently, due to
  college, I did a duo boot so I could have both Windows and Linux. But,
  whenever im at Linux, for some reason, my screen doesn't share with
  another monitor through HDMI, but with Windows it does. So i searched
  for some instructions, and ive been told to try and run this code in
  my therminal ubuntu-bug xorg, and that's why im here.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 13:56:48 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] 
[1d05:1116]
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / 
Max-Q] [1d05:1116]
  InstallationDate: Installed on 2023-08-31 (13 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  M

[Touch-packages] [Bug 2035063] Re: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 12

[Steve Langasek]

The error in the logs is:

Use of uninitialized value in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 227,  line 19.
Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 237,  line 19.
Use of uninitialized value $_[1] in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 111,  line 19.
Use of uninitialized value $val in substitution (s///) at 
/usr/share/perl5/Debconf/Format/822.pm line 83,  line 14.
Use of uninitialized value $val in concatenation (.) or string at 
/usr/share/perl5/Debconf/Format/822.pm line 84,  line 14.
dpkg: error processing package libpam0g:amd64 (--configure):
 installed libpam0g:amd64 package post-installation script subprocess returned 
error exit status 128

This suggests a crash in the debconf frontend that the pam maintainer
script was talking to.

Without a reproducible case for this, it is probably not actionable.

** Package changed: pam (Ubuntu) => debconf (Ubuntu)

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

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

Title:
  package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade:
  installed libpam0g:amd64 package post-installation script subprocess
  returned error exit status 128

Status in debconf package in Ubuntu:
  Incomplete

Bug description:
  running Ubuntu off a USB drive on my hp pavilion windows 10 laptop.
  This issue came up after upgrade from Bionic Beaver.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam0g:amd64 1.3.1-5ubuntu4.6
  ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246
  Uname: Linux 5.4.0-162-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Sep 10 16:48:50 2023
  ErrorMessage: installed libpam0g:amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2023-09-06 (4 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.4
   apt  2.0.9
  SourcePackage: pam
  Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: 
installed libpam0g:amd64 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/debconf/+bug/2035063/+subscriptions


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

[Touch-packages] [Bug 2035337] Re: dh-python: Cannot exclude deliberately embedded .egg-info from the clean step

[Launchpad Bug Tracker]

This bug was fixed in the package pastescript - 3.2.1-1ubuntu1

---
pastescript (3.2.1-1ubuntu1) mantic; urgency=medium

  * d/rules: work around the (wrong) removal of FakePlugin.egg-info by
dh-python in the clean step (LP: #2035337)

 -- Simon Chopin   Wed, 13 Sep 2023 12:18:46 +0200

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

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

Title:
  dh-python: Cannot exclude deliberately embedded .egg-info from the
  clean step

Status in dh-python package in Ubuntu:
  New
Status in pastescript package in Ubuntu:
  Fix Released
Status in dh-python package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1051837:

  Source: dh-python
  Version: 6.20230825
  Severity: normal
  X-Debbugs-Cc: scho...@ubuntu.com

  We have a FTBFS on src:pastescript because its test suite embeds a
  FakePlugin Python package, including its .egg-info, and the recent
  change to the dh-python clean: target breaks that package.

  While we can work around it by temporarily renaming the problematic
  directory before the dh_clean call, it would be nicer to have an
  explicit mechanism to exclude some paths from the clean analysis.

  -- System Information:
  Debian Release: bookworm/sid
APT prefers lunar-updates
APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 
'lunar'), (100, 'lunar-proposed'), (100, 'lunar-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
  Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  -- no debconf information

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


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

[Touch-packages] [Bug 2035220] Re: cve-2023-4863

[Nathan Teodosio]

For your information, Chromium is now in 116.0.5845.187 in x86, and
should be in ARM too tomorrow.

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  New
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  New

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Touch-packages] [Bug 2035220] Re: cve-2023-4863

[themusicgod1]

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

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

** Also affects: firefox-esr (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  New
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  New

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Touch-packages] [Bug 2035385] [NEW] package initram is not updated

[Aleksey Volkov]

Public bug reported:

The system is not fully updated and gives the following error
Setting up initramfs-tools (0.136ubuntu6.7) ... 
 
update-initramfs: deferring update (trigger activated)  
 
Processing triggers for initramfs-tools (0.136ubuntu6.7) ...
 
update-initramfs: Generating /boot/initrd.img-5.4.0-162-generic 
 

 
E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.  
 
update-initramfs: failed for /boot/initrd.img-5.4.0-162-generic with 1. 
 
dpkg: error processing package initramfs-tools (--configure):   
 
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1  
Errors were encountered while processing:   
 
 initramfs-tools

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246
Uname: Linux 5.4.0-162-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 13 19:39:18 2023
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2023-09-13 (0 days ago)

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


** Tags: amd64 apport-package focal third-party-packages

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

Title:
  package initram is not updated

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The system is not fully updated and gives the following error
  Setting up initramfs-tools (0.136ubuntu6.7) ...   
   
  update-initramfs: deferring update (trigger activated)
   
  Processing triggers for initramfs-tools (0.136ubuntu6.7) ...  
   
  update-initramfs: Generating /boot/initrd.img-5.4.0-162-generic   
   

   
  E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
   
  update-initramfs: failed for /boot/initrd.img-5.4.0-162-generic with 1.   
   
  dpkg: error processing package initramfs-tools (--configure): 
   
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1  
  Errors were encountered while processing: 
   
   initramfs-tools

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246
  Uname: Linux 5.4.0-162-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 13 19:39:18 2023
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  T

[Touch-packages] [Bug 2035385] Re: package initram is not updated

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initram is not updated

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The system is not fully updated and gives the following error
  Setting up initramfs-tools (0.136ubuntu6.7) ...   
   
  update-initramfs: deferring update (trigger activated)
   
  Processing triggers for initramfs-tools (0.136ubuntu6.7) ...  
   
  update-initramfs: Generating /boot/initrd.img-5.4.0-162-generic   
   

   
  E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
   
  update-initramfs: failed for /boot/initrd.img-5.4.0-162-generic with 1.   
   
  dpkg: error processing package initramfs-tools (--configure): 
   
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1  
  Errors were encountered while processing: 
   
   initramfs-tools

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246
  Uname: Linux 5.4.0-162-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 13 19:39:18 2023
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-09-13 (0 days ago)

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


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

[Touch-packages] [Bug 1791691] Re: PATH broken in systemd units

[Benjamin Drung]

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

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

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

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

Title:
  PATH broken in systemd units

Status in cloud-images:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in snapd source package in Bionic:
  In Progress
Status in initramfs-tools source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Fix Released

Bug description:
  systemd units have broken PATH in recent cloud images.
  The PATH set for them is
    PATH=:/snap/bin.
  Previously value is
    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  # cat /etc/cloud/build.info
  build_name: server
  serial: 20180906

  Booted in lxc that fails like:
  # lxc launch ubuntu-daily:cosmic c3
  # lxc exec c3 cat /run/cloud-init/result.json
  {
   "v1": {
    "datasource": null,
    "errors": [
     "Unexpected error while running command.\nCommand: ['netplan', 
'generate']\nExit code: -\nReason: [Errno 2] No such file or directory: 
b'netplan': b'netplan'\nStdout: -\nStderr: -",
     "Unexpected error while running command.\nCommand: ['netplan', 
'generate']\nExit code: -\nReason: [Errno 2] No such file or directory: 
b'netplan': b'netplan'\nStdout: -\nStderr: -",
     "('ssh-authkey-fingerprints', KeyError('getpwnam(): name not found: 
ubuntu',))"
    ]
   }
  }

  
  Related bugs:
   * bug 1771382: ds-identify: does not have expected PATH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1791691/+subscriptions


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

[Touch-packages] [Bug 1513272] Re: Root lvm lv mounted with wrong name

[Benjamin Drung]

This bug has been fixeb in initramfs-tools 0.121~rc1 and therefore in
Ubuntu 16.04 LTS "Xenial Xerus".

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

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

Title:
  Root lvm lv mounted with wrong name

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  In 15.04 and before, my root showed up in mound/findmnt/etc as
  /dev/vg/root, but now it shows up as /dev/dm-11.  This appears to be
  due to the following new code in scripts/local:

  ROOT=$(resolve_device "$ROOT")

  This resolves the symbolic link /dev/vg/lv to /dev/dm-xx and mounts
  that instead.  It should not be doing this.

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


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

[Touch-packages] [Bug 1793060] Re: configure_networking uses features not available in initramfs.

[Benjamin Drung]

This bug has been "fixed" by initramfs-tools 0.142ubuntu9 in Ubuntu
23.10 (mantic) by replacing dhclient by dhcpcd.

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

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

Title:
  configure_networking uses features not available in initramfs.

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  initramfs-tools 0.131ubuntu10 modified configure_networking to use
  run_dhclient instead of ipconfig. configure_networking now fails to
  configure networking in the initramfs because it now uses features not
  available in the initramfs.

  https://git.launchpad.net/ubuntu/+source/initramfs-
  tools/commit/?id=a77729e9a69ff7af4911285c771d80e01b7addfe

  run_dhclient calls dhclient which calls /sbin/dhclient-script.

  /sbin/dhclient-script calls 'chown --reference=$resolv_conf
  $new_resolv_conf', but chown isn't available in initramfs
  /boot/initrd.img-4.18.0-7-generic.

  /sbin/dhclient-script also calls 'chmod --reference=$resolv_conf
  $new_resolv_conf' but busybox chmod in the initramfs does not support
  the option --reference.

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


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

[Touch-packages] [Bug 2035337] Re: dh-python: Cannot exclude deliberately embedded .egg-info from the clean step

[Bug Watch Updater]

** Changed in: dh-python (Debian)
   Importance: Undecided => Unknown

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

Title:
  dh-python: Cannot exclude deliberately embedded .egg-info from the
  clean step

Status in dh-python package in Ubuntu:
  New
Status in pastescript package in Ubuntu:
  New
Status in dh-python package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1051837:

  Source: dh-python
  Version: 6.20230825
  Severity: normal
  X-Debbugs-Cc: scho...@ubuntu.com

  We have a FTBFS on src:pastescript because its test suite embeds a
  FakePlugin Python package, including its .egg-info, and the recent
  change to the dh-python clean: target breaks that package.

  While we can work around it by temporarily renaming the problematic
  directory before the dh_clean call, it would be nicer to have an
  explicit mechanism to exclude some paths from the clean analysis.

  -- System Information:
  Debian Release: bookworm/sid
APT prefers lunar-updates
APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 
'lunar'), (100, 'lunar-proposed'), (100, 'lunar-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
  Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  -- no debconf information

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


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

[Touch-packages] [Bug 2035339] [NEW] libperl5.30 crash (segfault) at Perl__invlist_intersection_maybe_complement_2nd during nginx reload

[Walter]

Public bug reported:

On Focal, I got this in my kern.log:

  nginx[533]: segfault at 739 ip 7fadc806d5d9 sp 7ffc04f5cd50
error 4 in libperl.so.5.30.0[7fadc8005000+166000]

  Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76
10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83
39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d

Looking at IP ( 0x7fadc806d5d9 - 0x7fadc8005000 ) it appeared to
point at 0x685D9 in libperl.so.5.30.0.

  # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 685D9
  Perl_vload_module
  op.c:7752

But when looking at the code, it looks like it's at 0x685D9 + 0x48000 =
0xB05D9:

  # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 B05D9
  Perl__invlist_intersection_maybe_complement_2nd
  regcomp.c:9841

This makes more sense:

  # objdump -d /usr/lib/x86_64-linux-gnu/libperl.so.5.30
  ...
  000b0500 :
  ...
  b05cd:   4c 8d 0c c2 lea(%rdx,%rax,8),%r9
  b05d1:   84 c9   test   %cl,%cl
  b05d3:   0f 84 c7 02 00 00   je b08a0 


  b05d9:   49 83 39 00 cmpq   $0x0,(%r9)  <-- here

  b05dd:   0f 85 ad 03 00 00   jneb0990 

  b05e3:   49 83 c1 08 add$0x8,%r9
  b05e7:   49 83 ed 01 sub$0x1,%r13
 

There's a similar segfault:

  nginx[356456]: segfault at 10 ip 7f4f576785a3 sp 7ffd0be49220
error 4 in libperl.so.5.30.0[7f4f5761+166000]

  Code: 48 89 43 10 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f
40 00 0f b6 7f 30 48 c1 e8 03 48 29 f8 48 89 c3 74 89 48 8b 02 <4c> 8b
68 10 4d 85 ed 0f 84 28 01 00 00 0f b6 40 30 49 c1 ed 03 49

That is on 0xB05A3, also in
Perl__invlist_intersection_maybe_complement_2nd:

  b0598:   48 29 f8sub%rdi,%rax
  b059b:   48 89 c3mov%rax,%rbx
  b059e:   74 89   je b0529 

  b05a0:   48 8b 02mov(%rdx),%rax
  b05a3:   4c 8b 68 10 mov0x10(%rax),%r13  <-- here
  b05a7:   4d 85 edtest   %r13,%r13
  b05aa:   0f 84 28 01 00 00   je b06d8 



On GitHub I found a bug filed for perl 5.30 and this function:

  https://github.com/Perl/perl5/issues/17154

That issue is fixed in perl 5.32.0 and beyond (across multiple commits).

Apparently the bug triggers every now and then, but was not common
enough to be noticed. And looking at the timestamps, it is always during
an nginx reload.

Cheers,
Walter Doekes
OSSO B.V.

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

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

Title:
  libperl5.30 crash (segfault) at
  Perl__invlist_intersection_maybe_complement_2nd during nginx reload

Status in perl package in Ubuntu:
  New

Bug description:
  On Focal, I got this in my kern.log:

nginx[533]: segfault at 739 ip 7fadc806d5d9 sp 7ffc04f5cd50
  error 4 in libperl.so.5.30.0[7fadc8005000+166000]

Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76
  10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83
  39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d

  Looking at IP ( 0x7fadc806d5d9 - 0x7fadc8005000 ) it appeared to
  point at 0x685D9 in libperl.so.5.30.0.

# addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 685D9
Perl_vload_module
op.c:7752

  But when looking at the code, it looks like it's at 0x685D9 + 0x48000
  = 0xB05D9:

# addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 B05D9
Perl__invlist_intersection_maybe_complement_2nd
regcomp.c:9841

  This makes more sense:

# objdump -d /usr/lib/x86_64-linux-gnu/libperl.so.5.30
...
000b0500 :
...
b05cd:   4c 8d 0c c2 lea(%rdx,%rax,8),%r9
b05d1:   84 c9   test   %cl,%cl
b05d3:   0f 84 c7 02 00 00   je b08a0 


b05d9:   49 83 39 00 cmpq   $0x0,(%r9)  <-- here

b05dd:   0f 85 ad 03 00 00   jneb0990 

b05e3:   49 83 c1 08 add$0x8,%r9
b05e7:   49 83 ed 01 sub$0x1,%r13
   

  There's a similar segfault:

nginx[356456]: segfault at 10 ip 7f4f576785a3 sp
  7ffd0be49220 error 4 in libperl.so.5.30.0[7f4f5761+166000]

Code: 48 89 43 10 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f
  40 00 0f b6 7f 30 48 c1 e8 03 48 29 f8 48 89 c3 74 89 48 8b 02 <4c> 8b
  68 10 4d 85 ed 0f 84 28 01 00 00 0f b6 40 30 49 c1 ed 03 49

  That is on 0xB05A3, also in
  Perl__invlist_intersection_maybe_complement_2nd:

b0598:   48 29 f8sub%rdi,%rax
b059b:   48 89 c3mov%rax,%rbx
b059e:   74 89   je b0529 

b05a0:   48 8b 02 

[Touch-packages] [Bug 2035339] Re: libperl5.30 crash (segfault) at Perl__invlist_intersection_maybe_complement_2nd during nginx reload

[Walter]

Forgot to mention the versions:

- libperl5.30:amd64 5.30.0-9ubuntu0.4
- nginx-common 1.18.0-0ubuntu1.4

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

Title:
  libperl5.30 crash (segfault) at
  Perl__invlist_intersection_maybe_complement_2nd during nginx reload

Status in perl package in Ubuntu:
  New

Bug description:
  On Focal, I got this in my kern.log:

nginx[533]: segfault at 739 ip 7fadc806d5d9 sp 7ffc04f5cd50
  error 4 in libperl.so.5.30.0[7fadc8005000+166000]

Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76
  10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83
  39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d

  Looking at IP ( 0x7fadc806d5d9 - 0x7fadc8005000 ) it appeared to
  point at 0x685D9 in libperl.so.5.30.0.

# addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 685D9
Perl_vload_module
op.c:7752

  But when looking at the code, it looks like it's at 0x685D9 + 0x48000
  = 0xB05D9:

# addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 B05D9
Perl__invlist_intersection_maybe_complement_2nd
regcomp.c:9841

  This makes more sense:

# objdump -d /usr/lib/x86_64-linux-gnu/libperl.so.5.30
...
000b0500 :
...
b05cd:   4c 8d 0c c2 lea(%rdx,%rax,8),%r9
b05d1:   84 c9   test   %cl,%cl
b05d3:   0f 84 c7 02 00 00   je b08a0 


b05d9:   49 83 39 00 cmpq   $0x0,(%r9)  <-- here

b05dd:   0f 85 ad 03 00 00   jneb0990 

b05e3:   49 83 c1 08 add$0x8,%r9
b05e7:   49 83 ed 01 sub$0x1,%r13
   

  There's a similar segfault:

nginx[356456]: segfault at 10 ip 7f4f576785a3 sp
  7ffd0be49220 error 4 in libperl.so.5.30.0[7f4f5761+166000]

Code: 48 89 43 10 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f
  40 00 0f b6 7f 30 48 c1 e8 03 48 29 f8 48 89 c3 74 89 48 8b 02 <4c> 8b
  68 10 4d 85 ed 0f 84 28 01 00 00 0f b6 40 30 49 c1 ed 03 49

  That is on 0xB05A3, also in
  Perl__invlist_intersection_maybe_complement_2nd:

b0598:   48 29 f8sub%rdi,%rax
b059b:   48 89 c3mov%rax,%rbx
b059e:   74 89   je b0529 

b05a0:   48 8b 02mov(%rdx),%rax
b05a3:   4c 8b 68 10 mov0x10(%rax),%r13  <-- here
b05a7:   4d 85 edtest   %r13,%r13
b05aa:   0f 84 28 01 00 00   je b06d8 


  
  On GitHub I found a bug filed for perl 5.30 and this function:

https://github.com/Perl/perl5/issues/17154

  That issue is fixed in perl 5.32.0 and beyond (across multiple
  commits).

  Apparently the bug triggers every now and then, but was not common
  enough to be noticed. And looking at the timestamps, it is always
  during an nginx reload.

  Cheers,
  Walter Doekes
  OSSO B.V.

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


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

[Touch-packages] [Bug 2035337] [NEW] dh-python: Cannot exclude deliberately embedded .egg-info from the clean step

[Simon Chopin]

Public bug reported:

Imported from Debian bug http://bugs.debian.org/1051837:

Source: dh-python
Version: 6.20230825
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com

We have a FTBFS on src:pastescript because its test suite embeds a
FakePlugin Python package, including its .egg-info, and the recent
change to the dh-python clean: target breaks that package.

While we can work around it by temporarily renaming the problematic
directory before the dh_clean call, it would be nicer to have an
explicit mechanism to exclude some paths from the clean analysis.

-- System Information:
Debian Release: bookworm/sid
  APT prefers lunar-updates
  APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), 
(100, 'lunar-proposed'), (100, 'lunar-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

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

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

** Affects: dh-python (Debian)
 Importance: Undecided
 Status: New


** Tags: ftbfs

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

** Changed in: dh-python (Debian)
 Remote watch: None => Debian Bug tracker #1051837

** Tags added: ftbfs

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

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

Title:
  dh-python: Cannot exclude deliberately embedded .egg-info from the
  clean step

Status in dh-python package in Ubuntu:
  New
Status in pastescript package in Ubuntu:
  New
Status in dh-python package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1051837:

  Source: dh-python
  Version: 6.20230825
  Severity: normal
  X-Debbugs-Cc: scho...@ubuntu.com

  We have a FTBFS on src:pastescript because its test suite embeds a
  FakePlugin Python package, including its .egg-info, and the recent
  change to the dh-python clean: target breaks that package.

  While we can work around it by temporarily renaming the problematic
  directory before the dh_clean call, it would be nicer to have an
  explicit mechanism to exclude some paths from the clean analysis.

  -- System Information:
  Debian Release: bookworm/sid
APT prefers lunar-updates
APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 
'lunar'), (100, 'lunar-proposed'), (100, 'lunar-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
  Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  -- no debconf information

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


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

[Touch-packages] [Bug 1483975] Re: update-initramfs complains about missing /sbin/fsck.btrfs

[Benjamin Drung]

Commit 371221bf2f8ed19423aa2253a302c69a54c93b58 uses command to find the
path of the fsck.${type} binary. This commit is part of initramfs-tools
0.121 and therefore fixed in Ubuntu 20.04 LTS "Focal Fossa".

You can still see this error message in case btrfs-progs is not
installed. So please install btrfs-progs in that case. If you still
experience this failure, please open a new bug report.

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

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

Title:
  update-initramfs complains about missing /sbin/fsck.btrfs

Status in btrfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in btrfs-tools package in Debian:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  /sbin/fsck.btrfs moved to /bin/fsck.btrfs with btrfs-tools 4.0-2
  (http://bugs.debian.org/784234), which causes

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
  Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.

  I assume this means that fsck won’t run on a btrfs /, which seems bad.

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


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

[Touch-packages] [Bug 1829805] Re: update-initramfs -k all -c does not create initrd images anymore

[Benjamin Drung]

This bug has been fixed in initramfs-tools 0.136 and therefore in Ubuntu
20.04 LTS "Focal Fossa".

** Changed in: initramfs-tools (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  update-initramfs -k all -c does not create initrd images anymore

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  Context: The live environment appears to function properly and install
  proceeds as expected with no noticeable errors.

  Expected results: After a system reboot the virtual machine enters the
  graphical environment

  Actual Results: After rebooting the virtual machine a kernel panic
  error screen appears. I will attempt to attach the screenshot after
  submitting this bug report.

  The collected data is from the live environment as the installed
  environment will not boot.

  lubuntu@lubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10
  Codename:   eoan

  lubuntu@lubuntu:~$ apt-cache policy grub2
  grub2:
Installed: (none)
Candidate: 2.02+dfsg1-12ubuntu2
Version table:
   2.02+dfsg1-12ubuntu2 500
  500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) 
eoan/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.407
  CurrentDesktop: LXQt
  Date: Tue May 21 00:30:39 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

[Daniel van Vugt]

It's not surprising if 0908.2 doesn't have the workaround. It didn't
land for a day or so after that.

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

Title:
  gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Mantic 20230907 on Latitude 3320

  Crash on boot of the live session

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 08:02:08 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694028853
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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

[Touch-packages] [Bug 2035220] Re: cve-2023-4863

[Nathan Teodosio]

** Changed in: chromium-browser (Ubuntu)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Critical

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in libwebp package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  New

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Touch-packages] [Bug 2035315] [NEW] Unprivileged user namespace restrictions break various applications

[Alex Murray]

Public bug reported:

When the unprivileged user namespace restrictions are enabled, various
applications within and outside the Ubuntu archive fail to function, as
they use unprivileged user namespaces as part of their normal operation.

A search of the Ubuntu archive for the 23.10 release was performed
looking for all applications that make legitimate use of the
CLONE_NEWUSER argument, the details of which can be seen in
https://docs.google.com/spreadsheets/d/1MOPVoTW0BROF1TxYqoWeJ3c6w2xKElI4w-VjdCG0m9s/edit#gid=2102562502

For each package identified in that list, an investigation was made to
determine if the application actually used this as an unprivileged user,
and if so which of the binaries within the package were affected.

The full investigation can be seen in
https://warthogs.atlassian.net/browse/SEC-1898 (which is unfortunately
private) but is summarised to the following list of Ubuntu source
packages, with the affected binaries as noted. NOTE that due to time
constraints for some packages it was not possible to finish the complete
investigation and so for those *all* the binaries from the package are
listed below.

For each of these binaries, an apparmor profile is required so that the
binary can be granted use of unprivileged user namespaces - an example
profile for the ch-run binary within the charliecloud package is shown:

$ cat /etc/apparmor.d/usr.bin.ch-run 
abi ,

include 

/usr/bin/ch-run flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists 
}


However, in a few select cases, it has been decided not to ship an apparmor 
profile, since this would effectively allow this mitigation to be bypassed. In 
particular, the unshare and setns binaries within the util-linux package are 
installed on every Ubuntu system, and allow an unprivileged user the ability to 
launch an arbitrary application within a new user namespace. Any malicious 
application then that wished to exploit an unprivileged user namespace to 
conduct an attack on the kernel would simply need to spawn itself via `unshare 
-U` or similar to be granted this permission. Therefore, due to the ubiquitous 
nature of the unshare (and setns) binaries, profiles are not planned to be 
provided for these by default. Similarly, the bwrap binary within bubblewrap is 
also installed by default on Ubuntu Desktop 23.10 and can also be used to 
launch arbitrary binaries within a new user namespace and so no profile is 
planned to be provided for this either.

Those packages for which either a profile is not required or which a
profile is not planned are listed below, whilst the list of packages
that require a profile (and their associated binaries) is listed at the
end:

Packages that use user namespaces but for which a profile is not
required or not planned:

  - bubblewrap
- /usr/bin/bwrap (NOT PLANNED AS NOTED ABOVE)
  - cifs-utils
- /usr/sbin/cifs.upcall (NOT REQUIRED AS IS EXECUTED AS root)
  - consfigurator  # NOT REQUIRED, NO BINARIES OR reverse-depends
  - criu
- /usr/sbin/criu (NOT REQUIRED SINCE ONLY FUNCTIONS AS root)
  - docker.io-app
- /usr/bin/dockerd (NOT REQUIRED SINCE RUNS AS root)
  - firejail
- /usr/bin/firejail (NOT REQUIRED SINCE is suid root)
  - golang-github-containers-storage
- /usr/bin/containers-storage (NOT REQUIRED SINCE ONLY FUNCTIONS AS root)
  - golang-gvisor-gvisor
- /usr/bin/runsc (NOT REQUIRED SINCE ONLY FUNCTIONS AS root)
  - guix
- /usr/bin/guix-daemon (NOT REQURIED SINCE RUNS AS root)
  - libvdestack # NOT REQUIRED, NO BINARIES OR reverse-depends
  - libvirt # NOT REQUIRED SINCE USES lxc WHICH WILL HAVE A PROFILE
  - network-manager # NOT REQUIRED SINCE CODE IS UNUSED
  - nix # APPEARS UNNEEDED IN DEFAULT CONFIGURATION
  - ocaml-extunix # NO BINARIES OR reverse-depends
  - passt
- /usr/bin/passt # IS EXPECTED TO BE EXECUTED AS root
  - rust-rustix # NO BINARIES AND CODE IS UNUSED IN THE ARCHIVE
  - util-linux
- 
Packages that use unprivileged user namespaces which require a profile (or 
already have one as part of the previous apparmor update in 
4.0.0~alpha2-0ubuntu1 via LP: #2030353):

  - bazel-bootstrap
- /usr/libexec/@{multiarch}/bazel/linux-sandbox
  - busybox
- /usr/bin/busybox
  - charliecloud
- /usr/bin/ch-checkns (included in 4.0.0~alpha2-0ubuntu1 via LP: #2030353)
- /usr/bin/ch-run  (included in 4.0.0~alpha2-0ubuntu1 via LP: #2030353)
  - crun
- /usr/bin/crun (included in 4.0.0~alpha2-0ubuntu1 via LP: #2030353)
  - flatpak
- /usr/bin/flatpak
  - golang-github-containers-buildah
- /usr/bin/buildah
  - libcamera
- /usr/bin/cam
- /usr/bin/ipa_verify
- /usr/bin/lc-compliance
- /usr/bin/libcamerify
- /usr/bin/qcam
  - libpod
- /usr/bin/podman
  - lxc
- /usr/bin/lxc-attach
- /usr/bin/lxc-create
- /usr/bin/lxc-destroy
- /usr/bin/lxc-execute
- /usr/bin/lxc-start
- /usr/bin/lxc-stop
- /usr/bin/lxc-unshare
- /us