[Touch-packages] [Bug 1958019]

[soyer]

I don't know the reasons, but this code has been working in this way for
10+ years, so this type of collision can not be common.

I sent the ALC285_FIXUP_THINKPAD_HEADSET_JACK patch to the lists:
https://lore.kernel.org/all/7ffae10ebba58601d25fe2ff8381a6ae3a926e62.1708687813.git.so...@irl.hu/

And I sent a question about how to handle this collision:
https://lore.kernel.org/all/d5b42e483566a3815d229270abd668131a0d9f3a.ca...@irl.hu/

If you are interested in linux sound development, you can subscribe to the 
linux-sound list:
http://vger.kernel.org/vger-lists.html#linux-sound

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2054771] Re: Kernel panic boot error with kernel 6.5.0.21

[atactic]

Could restore a working Kernel 6.5.0.21 with 
$ sudo apt update
$ sudo apt upgrade

However, the system starts up directly without asking for the user
login, which is really weird.

There is also a security warning when updating:

$ sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease  
Hit:4 http://security.ubuntu.com/ubuntu mantic-security InRelease  
Ign:5 http://linux.dropbox.com/ubuntu mantic InRelease 
Hit:6 http://linux.dropbox.com/ubuntu mantic Release   
Get:7 http://linux.dropbox.com/ubuntu mantic Release.gpg [488 B]
Ign:7 http://linux.dropbox.com/ubuntu mantic Release.gpg 
Hit:8 https://dl.google.com/linux/chrome/deb stable InRelease
Reading package lists... Done
W: GPG error: http://linux.dropbox.com/ubuntu mantic Release: The following 
signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key 

E: The repository 'http://linux.dropbox.com/ubuntu mantic Release' is not 
signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
N: Skipping acquire of configured file 'main/binary-i386/Packages' as 
repository 'https://dl.google.com/linux/chrome/deb stable InRelease' doesn't 
support architecture 'i386'

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

Title:
  Kernel panic boot error with kernel 6.5.0.21

Status in network-manager package in Ubuntu:
  New

Bug description:
  Booting on kernel 6.5.0.21-generic returns error:

  'Unable to mount root fs on unknown-block(0.0)'

  The system starts up correctly with the previous kernel
  6.7.0.17-generic

  Trying fixing 6.5.0.21-generic does not work:

  
  $ update-initramfs -u -k 6.5.0.21-generic
  update-initramfs: Generating /boot/initrd.img-6.5.0.21-generic
  touch: cannot touch '/boot/initrd.img-6.5.0.21-generic.new': Permission denied
  W: Kernel configuration /boot/config-6.5.0.21-generic is missing, cannot 
check for zstd compression support (CONFIG_RD_ZSTD)
  W: missing /lib/modules/6.5.0.21-generic
  W: Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/6.5.0.21-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  cat: 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic/modules.builtin: No 
such file or directory
  W: Can't find modules.builtin.modinfo (for locating built-in drivers' 
firmware, supported in Linux >=5.2)
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (UUID=ae16e50c-6748-4c2f-877f-b084acd65a51)
  I: Set the RESUME variable to override this.
  cp: cannot access '/etc/lvm/backup': Permission denied
  depmod: WARNING: could not open modules.order at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  depmod: WARNING: could not open modules.builtin at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  depmod: WARNING: could not open modules.builtin.modinfo at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  /usr/sbin/mkinitramfs: 539: cannot create 
/boot/initrd.img-6.5.0.21-generic.new: Permission denied
  update-initramfs: failed for /boot/initrd.img-6.5.0.21-generic with 2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054771/+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 2054864] [NEW] Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

[David]

Public bug reported:

After I ran the updater last week, my computer could only have a Link
Local address for IPv6. I have now confirmed that IPv6 works normally
when I install a fresh copy of 22.04.3 LTS and has the bug even after a
fresh install of 22.04.4 LTS. Previous data and fault finding on this
fault can be found on 2 Ask Ubuntu Posts I made regarding this fault
during the last week (Note: Originally I thought that this was just an
mDNS6 fault, hence the inaccurate title on the first post):

First Ask Ubuntu Post: https://askubuntu.com/questions/1503895/cant-
ping-dynamic-ipv6-xubuntu-hostname-from-kubuntu-laptop

Second Ask Ubuntu Post: https://askubuntu.com/questions/1504030/only-
ipv6-link-local-address-after-ubuntu-update

The Ubuntu Release I am currently using is:
Description:Ubuntu 22.04.4 LTS
Release:22.04

network-manager version reports as:
  Installed: 1.36.6-0ubuntu2
  Candidate: 1.36.6-0ubuntu2
  Version table:
 *** 1.36.6-0ubuntu2 500

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager 1.36.6-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 16:02:45 2024
InstallationDate: Installed on 2024-02-24 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
IpRoute:
 default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.203 metric 600
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2054864

Title:
  Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

Status in network-manager package in Ubuntu:
  New

Bug description:
  After I ran the updater last week, my computer could only have a Link
  Local address for IPv6. I have now confirmed that IPv6 works normally
  when I install a fresh copy of 22.04.3 LTS and has the bug even after
  a fresh install of 22.04.4 LTS. Previous data and fault finding on
  this fault can be found on 2 Ask Ubuntu Posts I made regarding this
  fault during the last week (Note: Originally I thought that this was
  just an mDNS6 fault, hence the inaccurate title on the first post):

  First Ask Ubuntu Post: https://askubuntu.com/questions/1503895/cant-
  ping-dynamic-ipv6-xubuntu-hostname-from-kubuntu-laptop

  Second Ask Ubuntu Post: https://askubuntu.com/questions/1504030/only-
  ipv6-link-local-address-after-ubuntu-update

  The Ubuntu Release I am currently using is:
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  network-manager version reports as:
Installed: 1.36.6-0ubuntu2
Candidate: 1.36.6-0ubuntu2
Version table:
   *** 1.36.6-0ubuntu2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 24 16:02:45 2024
  InstallationDate: Installed on 2024-02-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.203 metric 
600
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Touch-packages] [Bug 2054861] [NEW] suspend-target and systemd-suspend.service hang on resume and blocks shutdown/reboot

[M. Kurt]

Public bug reported:

This happens only after I connect my Toshiba FireTV via HDMI. I don't need to 
be using the TV. If I have connected TV just once it is enough to trigger this 
bug. Laptop goes to sleep just fine but when it wakes up from sleep I see 5 
services when I execute
$ systemctl list-jobs

JOB  UNIT TYPE  STATE  
7348 nvidia-resume.servicestart waiting
7236 suspend.target   start waiting
7346 grub-common.service  start waiting
7237 systemd-suspend.service  start running
7241 grub-initrd-fallback.service start waiting

In this state, I have to cancel suspend-target which in turn cancels 
7346 grub-common.service  start waiting
7237 systemd-suspend.service  start running
7241 grub-initrd-fallback.service start waiting

Then, I have to cancel cancelling systemd-suspend.service which cancels
7348 nvidia-resume.servicestart waiting

I use the laptop without issues but then if I need to shut it down or
reboot, system gets stuck after logging out of X. I end up doing a
REISUB.

This only happens if I connect to TV via HDMI.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Fri Feb 23 19:32:08 2024
InstallationDate: Installed on 2023-11-04 (112 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash 
amd_pstate=passive vt.handoff=7
SourcePackage: systemd
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to mantic on 2023-12-10 (75 days ago)
dmi.bios.date: 12/28/2023
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN41WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.41
dmi.modalias: 
dmi:bvnLENOVO:bvrM3CN41WW:bd12/28/2023:br1.41:efr1.41:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug mantic

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

Title:
  suspend-target and systemd-suspend.service hang on resume and blocks
  shutdown/reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  This happens only after I connect my Toshiba FireTV via HDMI. I don't need to 
be using the TV. If I have connected TV just once it is enough to trigger this 
bug. Laptop goes to sleep just fine but when it wakes up from sleep I see 5 
services when I execute
  $ systemctl list-jobs

  JOB  UNIT TYPE  STATE  
  7348 nvidia-resume.servicestart waiting
  7236 suspend.target   start waiting
  7346 grub-common.service  start waiting
  7237 systemd-suspend.service  start running
  7241 grub-initrd-fallback.service start waiting

  In this state, I have to cancel suspend-target which in turn cancels 
7346 grub-common.service  start waiting
7237 systemd-suspend.service  start running
7241 grub-initrd-fallback.service start waiting

  Then, I have to cancel cancelling systemd-suspend.service which cancels
7348 nvidia-resume.servicestart waiting

  I use the laptop without issues but then if I need to shut it down or
  reboot, system gets stuck after logging out of X. I end up doing a
  REISUB.

  This only happens if I connect to TV via HDMI.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6.1
  ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Feb 23 19:32:08 2024
  InstallationDate: 

[Touch-packages] [Bug 1982336] Re: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)

[Launchpad Bug Tracker]

This bug was fixed in the package gdb - 15.0.50.20240219-0ubuntu1

---
gdb (15.0.50.20240219-0ubuntu1) noble; urgency=medium

  * New upstream snapshot.
  * Support for new IBM Z Hardware (IBM z16). LP: #1982336.

 -- Matthias Klose   Mon, 19 Feb 2024 21:49:40 +0100

** Changed in: gdb (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  GDB Support for new IBM Z Hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982336/+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 2054859] [NEW] VNC connection issues with 22.04

[Dan Towle]

Public bug reported:

I have several computers running 20.04 and a couple running 22.04. VNC
was great on 20.04. I could connect using remina or real vnc no problem.
on the 22.04 machines though, I cannot connect reliably at all. If the
server montitor is in sleep, the server rejects the connection. On some
machines I can connect once, but then not again until I restart the vnc
server.

The issue is the same using rdp or vnc.

I have searched on this, but couldn't find any information that was
helpful.

Thanks. Loving Ubuntu (35 year mac user)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 18:33:28 2024
DistUpgraded: 2022-09-04 14:22:00,091 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated 
Graphics Controller [106b:00e6]
InstallationDate: Installed on 2021-12-13 (803 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Apple Inc. Macmini5,1
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=3c9a744c-c73a-44bc-95a9-149b6bbc399a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-09-04 (537 days ago)
dmi.bios.date: 04/09/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM51.88Z.0080.B00.1804091930
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-8ED6AF5B48C039E1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini5,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-8ED6AF5B48C039E1
dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0080.B00.1804091930:bd04/09/2018:br0.1:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:skuSystemSKU#:
dmi.product.family: Macmini
dmi.product.name: Macmini5,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
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

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

Title:
  VNC connection issues with 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I have several computers running 20.04 and a couple running 22.04. VNC
  was great on 20.04. I could connect using remina or real vnc no
  problem. on the 22.04 machines though, I cannot connect reliably at
  all. If the server montitor is in sleep, the server rejects the
  connection. On some machines I can connect once, but then not again
  until I restart the vnc server.

  The issue is the same using rdp or vnc.

  I have searched on this, but couldn't find any information that was
  helpful.

  Thanks. Loving Ubuntu (35 year mac user)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 18:33:28 2024
  DistUpgraded: 2022-09-04 14:22:00,091 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 

[Touch-packages] [Bug 2049628] Re: Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS

[aminesaka]

** Description changed:

- Since the last three weeks' updates, I have encountered several
- challenges with the audio functionality on my system. Primarily, upon
- starting my laptop, the audio often fails to work, displaying "Dummy
- Output." To resolve this, I find myself needing to restart the laptop
- two or three times before the audio becomes functional.
- 
- Even when the audio is working, I've noticed a recurring issue where,
- after playing video or audio for approximately 2-3 minutes, the sound
- starts crackling and buzzing. The intensity of these distortions
- gradually increases, resembling the static interference on a radio
- station with a weak signal. This issue persists even when using 3.5mm
- headphones, requiring the use of a USB headset or Bluetooth headphones
- to enjoy distortion-free audio.
- 
- Furthermore, I have observed that, regardless of the Ubuntu version
- (ranging from 22.04 to 22.04.3), I face difficulties changing the
- microphone output settings when an external audio peripheral, such as a
- USB headset, 3.5mm headphones, or Bluetooth headphones, is connected.
- The OS appears to exclusively utilize the microphone from the connected
- peripheral, making it impossible to switch to the laptop's built-in
- microphone.
- 
- For your reference, here are the specifications of my laptop and the
- Ubuntu version I am currently using:
- 
- Laptop: Dell Vostro 3400
- CPU: 11th Gen Intel i5-1135G7
- GPU: Intel TigerLake-LP GT2 Iris Xe
- Memory: 2490MiB / 19720MiB
- Resolution: 1920x1080
- OS: Ubuntu 22.04.3 LTS x86_64
- Kernel: 6.5.0-14-generic
- DE: GNOME 42.9
- Shell: bash 5.1.16
- Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42
- 
- I want to emphasize that I receive updates from the Tunisia Ubuntu
- server.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 22.04
- Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
- ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
- Uname: Linux 6.5.0-14-generic x86_64
- ApportVersion: 2.20.11-0ubuntu82.5
- Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  galxy-a10   1404 F pulseaudio
- CasperMD5CheckResult: pass
- CurrentDesktop: ubuntu:GNOME
- Date: Wed Jan 17 14:56:16 2024
- InstallationDate: Installed on 2024-01-16 (1 days ago)
- InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
- SourcePackage: pulseaudio
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 10/03/2023
- dmi.bios.release: 1.27
- dmi.bios.vendor: Dell Inc.
- dmi.bios.version: 1.27.1
- dmi.board.name: 0GGCMJ
- dmi.board.vendor: Dell Inc.
- dmi.board.version: A02
- dmi.chassis.type: 10
- dmi.chassis.vendor: Dell Inc.
- dmi.modalias: 
dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23:
- dmi.product.family: Vostro
- dmi.product.name: Vostro 3400
- dmi.product.sku: 0A23
- dmi.sys.vendor: Dell Inc.
+ https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570

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

Title:
  Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2049628/+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 1823171] Re: systemd-resolve hides DS records in explicit queries

[Dominic]

DNSSEC isn't required to query a DS record. The reason your query
succeeded after you enabled DNSSEC is because systemd-resolved caches it
internally as a result of the DNSSEC lookup.

Once the DS query is cached, the bug will not manifest. Another way to
cache it is:

ubuntu@server:~$ dig ripe.net ds @127.0.0.53 +short

ubuntu@server:~$ dig ripe.net ds @127.0.0.54 +short
10186 13 2 BC15C85E16FE7C651EAAFCEE3B1F1C956217A5B70A536BFEF38C24A9 AB7B9A3F

ubuntu@server:~$ dig ripe.net ds @127.0.0.53 +short
10186 13 2 BC15C85E16FE7C651EAAFCEE3B1F1C956217A5B70A536BFEF38C24A9 AB7B9A3F

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

Title:
  systemd-resolve hides DS records in explicit queries

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When querying for DS resource records on a DNSSEC signed domain using
  dig, the DS records are not shown when the system is using systemd-
  resolve.

  Run: dig +short DS ripe.net

  Expected: something like
  40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6

  Actual result: no output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.15
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  4 14:14:06 2019
  MachineType: MSI MS-7A70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/system-slash ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.80
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M PRO-VDH (MS-7A70)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A70
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+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

Re: [Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

[Steve Langasek]

Belated response, but just for the record, Paride's recounting of upstream's
position in the context of the Debian decision was definitive for me:

On Wed, Jan 10, 2024 at 11:47:56AM -, Paride Legovini wrote:
> Back in the day I asked upstream their take on irqbalance usefulness
> with newer kernels, here is their reply:

In effect what this says is that: irqbalance is still useful, but unless
the admin configures it, the policy it provides is not a discernable
improvement over the in-kernel default policy.

Therefore I think it is the right path forward to unseed this and let users
install it in situations where they want to configure it.

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  In Progress
Status in Ubuntu on IBM z Systems:
  Opinion
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 1949723] Re: systemd-resolved segfault in hashmap_iterate_entry

[Nick Rosbrook]

The mentioned fix in the upstream report has been in systemd since 2021.

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

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

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

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

Title:
  systemd-resolved segfault in hashmap_iterate_entry

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

Bug description:
  installed libnss-resolve that put "resolve" in nsswitch.conf.

  $ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  $ dpkg -l systemd | grep systemd
  ii  systemd245.4-4ubuntu3.13 amd64system and service manager
  $ grep ^hosts /etc/nsswitch.conf 
  hosts:  files libvirt mdns4_minimal resolve [NOTFOUND=return] dns 
mymachines

  systemd-resolved crashed once with segmentation fault.


  (gdb) bt
  #0  0x7f119c67693a in hashmap_iterate_entry 
(h=h@entry=0x706f746b73656465, i=i@entry=0x7ffc4ef515d0) at 
../src/basic/hashmap.c:705
  #1  0x7f119c6789d6 in internal_hashmap_iterate (h=0x706f746b73656465, 
i=i@entry=0x7ffc4ef515d0, value=value@entry=0x7ffc4ef515c8, key=key@entry=0x0)
  at ../src/basic/hashmap.c:714
  #2  0x7f119c678a8b in set_iterate (s=, 
i=i@entry=0x7ffc4ef515d0, value=value@entry=0x7ffc4ef515c8) at 
../src/basic/hashmap.c:735
  #3  0x55ba5e0ea917 in dns_query_candidate_go (c=c@entry=0x55ba5f353180) 
at ../src/resolve/resolved-dns-query.c:152
  #4  0x55ba5e0e9f0c in dns_query_candidate_notify 
(c=c@entry=0x55ba5f353180) at ../src/resolve/resolved-dns-query.c:312
  #5  0x55ba5e0ea178 in dns_transaction_complete (t=0x55ba5f37a9d0, 
state=) at ../src/resolve/resolved-dns-transaction.c:351
  #6  0x55ba5e0e27cd in dns_transaction_process_dnssec 
(t=t@entry=0x55ba5f37a9d0) at ../src/resolve/resolved-dns-transaction.c:838
  #7  0x55ba5e0e3649 in dns_transaction_process_reply 
(t=t@entry=0x55ba5f37a9d0, p=p@entry=0x55ba5f39dce0)
  at ../src/resolve/resolved-dns-transaction.c:1210
  #8  0x55ba5e0e40ab in on_dns_packet (s=, fd=, revents=, userdata=0x55ba5f37a9d0)
  at ../src/resolve/resolved-dns-transaction.c:1264
  #9  0x7f119c5e6c77 in source_dispatch (s=s@entry=0x55ba5f346780) at 
../src/libsystemd/sd-event/sd-event.c:3193
  #10 0x7f119c5e6f11 in sd_event_dispatch (e=e@entry=0x55ba5f320430) at 
../src/libsystemd/sd-event/sd-event.c:3634
  #11 0x7f119c5e8948 in sd_event_run (e=e@entry=0x55ba5f320430, 
timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:3692
  #12 0x7f119c5e8b6f in sd_event_loop (e=0x55ba5f320430) at 
../src/libsystemd/sd-event/sd-event.c:3714
  #13 0x55ba5e0c326a in run (argv=, argc=) at 
../src/resolve/resolved.c:84
  #14 main (argc=, argv=) at 
../src/resolve/resolved.c:91

  This seems to have been reported upstream
  https://github.com/systemd/systemd/issues/16168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949723/+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 1880839] Re: Clock skew on testbeds

[Nick Rosbrook]

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

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

Title:
  Clock skew on testbeds

Status in Auto Package Testing:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Clock stepped backward on a testbed:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  groovy/groovy/amd64/b/boost1.71/20200501_151103_1e387@/log.gz

  ...
  context  FAIL stderr: make[2]: Warning: File 
'/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future
  autopkgtest [13:55:37]: test context:  - - - - - - - - - - stderr - - - - - - 
- - - -
  make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification 
time 0.52 s in the future
  make[2]: warning:  Clock skew detected.  Your build may be incomplete.
  ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1880839/+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 1888391] Re: /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root network namespaces

[Nick Rosbrook]

I don't think that script is or was part of src:systemd?

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

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

Title:
  /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root
  network namespaces

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Running dhclient in a (non-root) network namespace on a system with
  systemd enabled fails because the hook installed by the systemd
  package updates the DNS configuration of the core/root namespace,
  instead of simply the /etc/resolv.conf file of that particular network
  namespace.

  ("ip netns add " nicely links /etc/resolv.conf in that namespace
  to /etc/netns//resolv.conf if it exists.)

  The following patch ensures that this script no longer misbehaves for
  this scenario:

  --- /etc/dhcp/dhclient-enter-hooks.d/resolved.bak 2020-07-21 
14:05:23.390989468 +0200
  +++ /etc/dhcp/dhclient-enter-hooks.d/resolved 2020-07-21 14:03:18.566046842 
+0200
  @@ -14,7 +14,7 @@
   #   (D) = master script downs interface
   #   (-) = master script does nothing with this

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && [ -z "$(ip netns identify)" ] ; 
then
   # For safety, first undefine the nasty default make_resolv_conf()
   make_resolv_conf() { : ; }
   case "$reason" in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1888391/+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 2045621] Re: Improve power consumption on Framework systems

[Nick Rosbrook]

** Changed in: systemd (Ubuntu Noble)
   Status: Fix Committed => 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/2045621

Title:
  Improve power consumption on Framework systems

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-hwe package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Won't Fix
Status in systemd-hwe source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd-hwe source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix
Status in systemd-hwe source package in Mantic:
  Fix Released
Status in systemd source package in Noble:
  Fix Released
Status in systemd-hwe source package in Noble:
  Invalid

Bug description:
  [ Impact ]

   * Framework systems that have DP or HDMI cards connected will have
  increased power consumption even when nothing is connected to DP or
  HDMI ports since the cards don't default to autosuspend.

   * Backporting upstream patch that adds rules in
  hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions.

  [ Test Plan ]

   * DUT: Framework with DP and HDMI:

  $ lsusb | grep Framework
  Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
  Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card

   1. Autosuspend is not enabled before patch. Set to "on" in
  power/control

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control
  on

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control
  on

   2. Install patch
   3. Autosuspend is enabled for both extensions. Set to "auto" in power/control

  $ cat power/control
  auto

  [ Where problems could occur ]

   * During testing verified that both DP+HDMI display show good output after 
hot-plug, system suspend, and reboot. There might be some differences when 
hibernate and hotplug.
   
  [ Other Info ]

   *
  
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2051765] Re: Plymouth FTBFS (even after apt-get build-dep plymouth)

[Nick Rosbrook]

The systemd version in question migrated.

** Changed in: systemd (Ubuntu)
   Status: Fix Committed => 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/2051765

Title:
  Plymouth FTBFS (even after apt-get build-dep plymouth)

Status in plymouth package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  dh_install
  dh_install: warning: Cannot find (any matches for) "lib/systemd/system" 
(tried in ., debian/tmp)

  dh_install: warning: plymouth missing files: lib/systemd/system
  dh_install: error: missing files, aborting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2051765/+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 1605941] Re: /usr/share/initramfs-tools/hooks/udev fails if /etc/udev/rules.d contains directories

[Nick Rosbrook]

Uh, isn't the real problem that in this case
/etc/udev/rules.d/10-network.rules is a *directory*, and not a *file*?

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

Title:
  /usr/share/initramfs-tools/hooks/udev fails if /etc/udev/rules.d
  contains directories

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  update-initramfs: Generating /boot/initrd.img-4.4.0-28-generic
  cp: omitting directory '/etc/udev/rules.d/10-network.rules'
  E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-28-generic with 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 23 15:50:43 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-27 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605941/+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 1605941] Re: /usr/share/initramfs-tools/hooks/udev fails if /etc/udev/rules.d contains directories

[Nick Rosbrook]

Given the age of this, I am going to mark won't fix, but please re-open
if you think I am wrong.

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

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

Title:
  /usr/share/initramfs-tools/hooks/udev fails if /etc/udev/rules.d
  contains directories

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  update-initramfs: Generating /boot/initrd.img-4.4.0-28-generic
  cp: omitting directory '/etc/udev/rules.d/10-network.rules'
  E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-28-generic with 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 23 15:50:43 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-27 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605941/+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 2025382] Re: 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

[Nick Rosbrook]

The mentioned fix is included in v255, which is now in Noble.

** Changed in: systemd (Ubuntu)
   Status: Triaged => 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/2025382

Title:
  22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

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

Bug description:
  Ubuntu 22.04.2 LTS
  kernel 5.15.0-1038-oracle
  systemd 249.11-0ubuntu3.9

  After an update a couple weeks ago, Ubuntu 22.04 can no longer get
  IPv6 via DHCPv6 systemd-networkd, at least on Oracle OCI, but there
  are also other similar reports, e.g.

  https://ubuntuforums.org/showthread.php?t=2487465=14146758

  Oracle seems to be aware of the issue but they claim it's a Ubuntu
  22.04 bug:

  https://community.oracle.com/customerconnect/discussion/687610/oci-
  ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

  The workaround to assign a static IPv6 is not great when managing
  multiple cloud instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2025382/+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 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd

[Nick Rosbrook]

I guess this only applied to Lunar? Which is EOL. So, marking this won't
fix, but correct me if I am wrong.

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

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

Title:
  conflict on syslog.service when moving between rsyslog and busybox-
  syslogd

Status in busybox package in Ubuntu:
  Won't Fix
Status in rsyslog package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Suppose a system with systemd 252 and rsyslog installed.  Install
  busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
  be removed (but not purged).  The install of busybox-syslogd will fail
  as follows:

  Failed to preset unit, file "/etc/systemd/system/syslog.service"
  already exists and is a symlink to
  "/lib/systemd/system/rsyslog.service".

  The failure can also be seen in the reverse direction - busybox-
  syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.

  With systemd 253, we instead see:
  Removed "/etc/systemd/system/syslog.service".

  Workarounds:
  * use systemd 253 when available
  * purge the existing system-log-daemon before installing the new one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+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 1965328] Re: transient scope could not be started error in bionic lxd container

[Nick Rosbrook]

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

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

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

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

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

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  New

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

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

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

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


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

[Touch-packages] [Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

[Nick Rosbrook]

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

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Confirmed
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+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 2017317] Re: Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

[Nick Rosbrook]

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

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

Title:
  Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ### Issue description
  When restarting my machine, cryptsetup waits forever. Waiting for the 
swapfile. Unable to start Ubuntu at all. Error message is:

  ```
  cryptsetup: Waiting for encrypted source device /swapfile...
  ```

  ### Steps for reproducing the issue
  1. Do a fresh installation of Ubuntu, unencrypted.
  2. Later, due to restrictions at work, encrypt Ubuntu POST installation 
accordingly to this article: 
https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation
  3. Reboot, all works fine, but ...
  4. Later, after a couple of months, install a new Linux kernel and then ...
  5. Upon boot cryptsetup gets stuck, waits forever. See attached photo.

  ### Additional info
  I've found a temporary, painful workaround by rebooting in recovery mode and 
running this command every time:

  ```
  sudo update-initramfs -u -k all
  ```

  Then I can boot again. But I have to do this every time. Why?

  ### Debug log

  Hard to say but here's the output of this command `journalctl | grep
  crypt`, not sure if you can find anything interesting about it:

  ```
  Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr" 
class="file" info="Failed name lookup - disconnected path" error=-13 
profile="/usr/bin/evince-thumbnailer" 
name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-"
 pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r" 
fsuid=1000 ouid=1000
  Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate: 
/home/michael-heuberger is already mounted
  Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing 
jobs: Transaction for plymouth-quit.service/start is destructive 
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' 
job queued, but 'start' is included in transaction).
  Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, 
ignoring: Transaction for plymouth-quit.service/start is destructive 
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' 
job queued, but 'start' is included in transaction).
  Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and 
passphrase cache...
  Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and 
passphrase cache.
  Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes.
  Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig 
[2bda85c181b04823]: Required key not available
  Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig 
[96c111e5680ecc45]: Required key not available
  Apr 21 17:27:09 M1 systemd[1]: Deactivating swap 
/dev/disk/by-id/dm-name-cryptswap1...
  Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap: 
Deactivated successfully.
  Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1.
  ```

  Do you have any tips, advice please, how to fix this, how can I reboot
  my machine without running `update-initramfs` every time? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017317/+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 2017846] Re: System kept waking up after pressing power button

[Nick Rosbrook]

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

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

Title:
  System kept waking up after pressing power button

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

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F wireplumber
   /dev/snd/seq:yamiyuki  42972 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  Package: systemd 252.5-2ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Touch-packages] [Bug 2031898] Re: Enable / include ukify

[Nick Rosbrook]

systemd-ukify is in noble now:
https://launchpad.net/ubuntu/noble/+package/systemd-ukify

** Changed in: systemd (Ubuntu)
   Status: Triaged => 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/2031898

Title:
  Enable / include ukify

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Systemd 253 has ukify as a tool available but this has not been
  enabled.

  See also the changelog from debian systemd 254 where they have enabled ukify.
  
https://metadata.ftp-master.debian.org/changelogs//main/s/systemd/systemd_254.1-2_changelog

  It would be great if systemd could be updated to 254 for mantic or to
  enable ukify in version 253.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2031898/+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 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents

[Simon Déziel]

@enr0n, the proposal to add:

bridges:
  br0:
interfaces: [vlan1]

To the network config defeats the purpose. The goal is to not have to do
double configuration. The bridge is define in LXD, the vlan1 only in
netplan.

The other proposed fix of `KeepMaster=true` snippet in
/etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf didn't
work for me. I also tried putting it in 99-netplan-vlan1.network.d to
match the name of my netplan .yaml but still didn't work.


root@networkd-bug:~# cat /etc/netplan/99-vlan1.yaml 
network:
  version: 2
  vlans:
vlan1:
  id: 1
  link: eth0

root@networkd-bug:~# cat 
/etc/systemd/network/99-netplan-vlan1.network.d/keep_master.conf 
[Network]
KeepMaster=true

root@networkd-bug:~# grep -n . /run/systemd/network/*vlan1*
/run/systemd/network/10-netplan-vlan1.netdev:1:[NetDev]
/run/systemd/network/10-netplan-vlan1.netdev:2:Name=vlan1
/run/systemd/network/10-netplan-vlan1.netdev:3:Kind=vlan
/run/systemd/network/10-netplan-vlan1.netdev:5:[VLAN]
/run/systemd/network/10-netplan-vlan1.netdev:6:Id=1
/run/systemd/network/10-netplan-vlan1.network:1:[Match]
/run/systemd/network/10-netplan-vlan1.network:2:Name=vlan1
/run/systemd/network/10-netplan-vlan1.network:4:[Network]
/run/systemd/network/10-netplan-vlan1.network:5:LinkLocalAddressing=ipv6
/run/systemd/network/10-netplan-vlan1.network:6:ConfigureWithoutCarrier=yes

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

Title:
  Restarting `systemd-networkd` looses unmanaged bridged parents

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  My home network comprises many VLANs managed by `systemd-
  networkd`/`netplan`. Those VLANs are then used as parent interfaces
  for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post-
  update), my whole network breaks because all the unmanaged bridges
  lose their parent devices. Another way to see it is that `systemd-
  networkd` undoes the `master` setting of those VLAN devices.

  
  Here is a simplified reproducer:

  1. Create a `vlan1` device

  $ lxc launch ubuntu:22.04 networkd-bug
  Creating networkd-bug
  Starting networkd-bug

  $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF
  network:
version: 2
vlans:
  vlan1:
id: 1
link: eth0
  EOF

  $ lxc exec networkd-bug -- netplan apply

  2. Manually create a bridge and join `vlan1` to it

  $ lxc exec networkd-bug -- ip link add br0 type bridge
  $ lxc exec networkd-bug -- ip link set vlan1 master br0
  $ lxc exec networkd-bug -- ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: vlan1@eth0:  mtu 1500 qdisc noqueue 
master br0 state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff
  3: br0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff
  164: eth0@if165:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0

  3. Restart `systemd-networkd`

  $ lxc exec networkd-bug -- systemctl restart systemd-networkd

  4. Notice `vlan1` lost it's master config

  $ lxc exec networkd-bug -- ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: vlan1@eth0:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff
  3: br0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff
  164: eth0@if165:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0

  
  Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose 
connectivity :)


  Additional information:

  # apt-cache policy systemd netplan.io iproute2
  systemd:
Installed: 249.11-0ubuntu3.9
Candidate: 249.11-0ubuntu3.9
Version table:
   *** 249.11-0ubuntu3.9 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3.7 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   249.11-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  netplan.io:
Installed: 0.105-0ubuntu2~22.04.3
Candidate: 0.105-0ubuntu2~22.04.3
Version table:
   *** 0.105-0ubuntu2~22.04.3 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.104-0ubuntu2 500
  500 

[Touch-packages] [Bug 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances

[Nick Rosbrook]

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

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

Title:
  "optional: true" flag introduces problem it's meant to fix in certain
  circumstances

Status in netplan:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello!

  This bug is in relation to the situation where the "systemd-networkd-
  wait-online.service" hangs for several minutes on boot before
  eventually failing. I guess I don't know if this flag was introduced
  specifically for this situation, but I do know that one of the fixes
  for this issue is to add "optional: true" to any non-critical
  interfaces (as per the docs[1]). While this may be the case, it just
  so happens that adding this flag to an interface when it's the only
  configured interface in netplan can actually INTRODUCE the issue as
  well. Example:

  ---
  :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  enp5s0:
  dhcp4: true
  optional: true
  ---

  The above config will cause the service hang/failure, and the removal
  of the flag will resolve the issue. I primarily opened this bug report
  with the idea that we might update aforementioned documentation to
  include a caveat that you want to avoid adding this flag to the only
  configured interface. However, it was also discussed that we might
  consider having the netplan config parser complain about such a setup
  and consider it invalid, which it kinda is. I believe in a situation
  where you may have a server that should have NO network connectivity,
  you would simply leave netplan unconfigured and/or stop any relevant
  services, rather than try to configure all interfaces as optional.

  My original test was on Jammy, though I tested this also on Focal and
  Bionic, and neither of those appear to be affected by this - setting
  the only interface as optional in either of those does not cause the
  "systemd-networkd-wait-online" service to hang and the system boots
  normally.

  Let me know if you'd like/need any more info from me! Thank you!

  [1] https://netplan.io/faq#prevent-waiting-for-interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2039083/+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 2049392] Re: Symlink for resolv.conf not working with F5 vpn

[Nick Rosbrook]

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

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

Title:
   Symlink for resolv.conf not working with F5 vpn

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I create this bug issue following an advice from Nick Rosbrook in this
  bug : https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234

  
  May be it's a F5 VPN. I haven't found such a bug anywhere. 

  I have an issue when connection to a F5 VPN when  /etc/resolv.conf is
  the symbolic link of ../run/systemd/resolve/stub-resolv.conf

  ➜ ~ sudo ls -la /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 juin 23 12:37 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  When F5 is launched, /etc/resolv.conf is not changed. I have to
  manually set resolv.conf to change the nameserver(s).


  
  When I change the symbolic link /etc/resolv.conf to 
/run/systemd/resolve/resolv.conf

  sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

  When F5 is launched, /etc/resolv.conf is  updated whith vpn
  nameserver(s).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049392/+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 2020177] Re: Leaking sessions in pam_systemd

[Nick Rosbrook]

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

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

Title:
  Leaking sessions in pam_systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session):
  Failed to create session: Maximum number of sessions (8192) reached,
  refusing further sessions.

  # loginctl list-sessions|wc -l
  8195

  
   # loginctl session-status 302548700
  302548700 - topaz (450)
 Since: Tue 2022-10-18 09:29:02; 7 months 0 days ago
Leader: 2637625
Remote: 92.42.15.122
   Service: sshd; type tty; class user
 State: closing
  Unit: session-302548700.scope

  # ps axf|wc -l
  72

  
  The only way I could figure to fix this is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.21
  Uname: Linux 4.15.0 x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   
  Date: Fri May 19 12:58:47 2023
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.utf8
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts'
  ProcKernelCmdLine: quiet
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2022-01-26 (478 days ago)
  acpidump:
   
  mtime.conffile..etc.systemd.journald.conf: 2022-08-19T16:13:27.570934

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2020177/+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 1811295] Re: systemctl daemon-reexec does not update group membership

[Nick Rosbrook]

This sounds like a question better suited for upstream. Please open a
bug there instead: https://github.com/systemd/systemd/issues

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

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

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

Title:
  systemctl daemon-reexec does not update group membership

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On  Ubuntu 16.04.4 LTS  
  using 
  Package: systemd
  Architecture: amd64
  Version: 229-4ubuntu21.10

  Changes the group membership are not picked up by the systemd process
  for a logged-in user or for a user with enable-linger set regardless
  of login status.  Evidently the

systemctl --user daemon-reexec

  command preserves group membership across the daemon restart. This is
  bad. It means that only a reboot or

sudo loginctl terminate-user 

  will update the group membership to the proper set. Both of those
  things are extreme disruptions for a system/user that runs servers.

  Can systemctl daemon-reexec be made to update group membership for the
  user in the systemd process?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811295/+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 2019026] Re: systemd /tmp cleaning is suboptimal

[Nick Rosbrook]

** Tags added: rls-nn-incoming

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

Title:
  systemd /tmp cleaning is suboptimal

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Historically on Debian and Ubuntu, before systemd, the default
  handling of /tmp was to periodically, and at boot, remove all
  files/directories older than 30 days; and leave other contents alone.

  With the move to systemd, the "default" (really, hard-coded in
  /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but
  at boot to remove all contents.

  This is suboptimal for two reasons.

  By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp
  and has lots of inodes under it, possibly due to failures of some
  process to clean up after itself, at boot the system will be
  unavailable for an unnecessarily long time while these files are
  removed.

  By cleaning *all* files under /tmp, this makes a reboot an Event where
  in-progress files may be unnecessarily lost.

  While the FHS does not *guarantee* that files under /tmp will persist
  across boot (because /tmp may be a tmpfs), it also does not *require*
  that /tmp be cleared on boot.

 Although data stored in /tmp may be deleted in a site-specific
 manner, it is recommended that files and directories located in
 /tmp be deleted whenever the system is booted.

 FHS added this recommendation on the basis of historical
 precedent and common practice, but did not make it a
 requirement because system administration is not within the
 scope of this standard.

  I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf
  to restore past behavior is 'd /tmp 1777 root root 30d'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+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 2038994] Re: systemd-networkd: Unable to acquire IPv6 DNS server address

[Nick Rosbrook]

The fixes you mentioned should be included in noble already. The patches
you mention do not apply to v249, which is the systemd version in jammy.
So, when 24.04 is released, the fix will be available there, but
unfortunately I don't think we will fix this in 22.04.

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

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

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

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

Title:
  systemd-networkd: Unable to acquire IPv6 DNS server address

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

Bug description:
  I found that starting from Ubuntu 22, when using systemd-networkd as
  the netplan backend, the IPV6 DNS server cannot be obtained through
  DHCPv6. I reported the issue to the systemd team and they located and
  fixed the issue. How can I get these updates in ubuntu packages?

  issue details: https://github.com/systemd/systemd/issues/28566

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Oct 11 03:58:58 2023
  InstallationDate: Installed on 2023-10-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Launchpad Bug Tracker]

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later

[Nick Rosbrook]

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

This sounds like a duplicate of 2037667, which is planned to be fixed
sometime soon-ish.

** This bug has been marked a duplicate of bug 2037667
   Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

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

Title:
  non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or
  later

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

Bug description:
  jammy kernel 5.15.0-81.90 includes the following backport:

  
https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43
  https://bugs.launchpad.net/bugs/2029401

  This causes creation of ip6tnl tunnel interface to fail through
  systemd-networkd. The following systemd commit also has to be applied
  to jammy:

  
https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb

  (Other commits might be required along with above)

  Since the systemd commit is missing on jammy, Kind=ip6tnl netdev
  configuration fails as follows:

  > eno1: Could not create stacked netdev: Invalid argument

  I believe this is a regression; We encountered this linux-
  image-5.15.0-91-generic installed via unattended-upgrade -- Also
  EINVAL during creating tunnel interfaces let AcceptIPv6RA function not
  to start, so we lose connection to our server due to missing IP
  address.

  ```
  # eno1.network
  [Match]
  Name=eno1

  [Network]
  Tunnel=test_tun
  ```

  ```
  # test_tun.netdev
  [NetDev]
  Name=test_tun
  Kind=ip6tnl

  [Tunnel]
  Local=2001:db8::a
  Remote=2001:db8::b
  Mode=any
  ```

  ```
  # test_tun.network
  [Match]
  Name=test_tun

  [Network]
  Address=10.0.0.1/24
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+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 1823171] Re: systemd-resolve hides DS records in explicit queries

[Nick Rosbrook]

It sounds like you don't have DNSSEC=yes anywwhere. I can do the following.
root@mantic:~# resolvectl dnssec
Global: no
Link 41 (eth0): no
root@mantic:~# dig +short DS ripe.net
root@mantic:~# resolvectl dnssec eth0 yes
root@mantic:~# resolvectl dnssec
Global: no
Link 41 (eth0): yes
root@mantic:~# dig +short DS ripe.net
10186 13 2 BC15C85E16FE7C651EAAFCEE3B1F1C956217A5B70A536BFEF38C24A9 AB7B9A3F


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

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

Title:
  systemd-resolve hides DS records in explicit queries

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When querying for DS resource records on a DNSSEC signed domain using
  dig, the DS records are not shown when the system is using systemd-
  resolve.

  Run: dig +short DS ripe.net

  Expected: something like
  40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6

  Actual result: no output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.15
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  4 14:14:06 2019
  MachineType: MSI MS-7A70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/system-slash ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.80
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M PRO-VDH (MS-7A70)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A70
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+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 1950906] Re: etc/rc.local should Want or Require network-online.target

[Nick Rosbrook]

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

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

Title:
  etc/rc.local should Want or Require network-online.target

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  The fix for bug #1451797 introduced /lib/systemd/system/rc-
  local.service.d/debian.conf with the intent that rc.local would always
  run after the network was fully online. However, it only has an After=
  line, without actually pulling in network-online.target. Systemd docs
  say:

  "Units that strictly require a configured network connection should pull in 
network-online.target (via a Wants= type dependency) and order themselves after 
it. ... Note the distinction between this unit and network.target. This unit is 
an active unit (i.e. pulled in by the consumer rather than the
  provider of this functionality) ... Usually, network.target is part of the 
boot of most systems, while network-online.target is not ..."

  TL;DR - need to add "Wants=network-online.target" to
  /lib/systemd/system/rc-local.service.d/debian.conf :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.13
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Xpra
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Nov 14 17:22:54 2021
  InstallationDate: Installed on 2017-01-08 (1771 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
   |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
  MachineType: Dell Inc. OptiPlex 3040
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-90-generic 
root=/dev/mapper/lvg2-host ro rootflags=subvol=rootfs rw 
drm.edid_firmware=edid/toguard2.bin video=HDMI-A-1:1024x768@60D
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-09-02 (73 days ago)
  acpidump:
   
  dmi.bios.date: 06/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.6
  dmi.board.name: 0TTDMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.6:bd06/30/2016:svnDellInc.:pnOptiPlex3040:pvr:rvnDellInc.:rn0TTDMJ:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 3040
  dmi.product.sku: 06BB
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.logind.conf: 2019-03-03T09:57:30.814201

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950906/+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 2052137] Re: bonded link goes down on reconfigure

[Nick Rosbrook]

The upstream bug is tagged for a stable backport, so we *should* get
this soon-ish in noble.

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

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

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

** Tags added: foundations-todo

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

Title:
  bonded link goes down on reconfigure

Status in systemd:
  Fix Released
Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  systemd-networkd brings down member interfaces of a bond when they get
  reconfigured

  Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link
  down

  This has a result that a server has complete downtime for a few
  seconds, this has also been reported upstream
  https://github.com/systemd/systemd/issues/31165.

  A pull request has been opened to fix this
  https://github.com/systemd/systemd/pull/31172

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2052137/+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 2046606] Re: Harden default systemd services with sandboxing

[Nick Rosbrook]

This would take a larger coordination, and is not really a "bug" to be
assigned to systemd per se. We will likely inherit lots of this from
Debian over time.

Marking as invalid just because this is not really the place for this
(probably a thread on ubuntu-devel would be better?).

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

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

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

Title:
  Harden default systemd services with sandboxing

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  
https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#Sandboxing

  https://wiki.debian.org/ServiceSandboxing

  Fedora is probably going forward with this.

  
  https://fedoraproject.org/wiki/Changes/SystemdSecurityHardening

  
  ~$ systemd-analyze security

  The security verb was released five years ago.
  https://lists.freedesktop.org/archives/systemd-devel/2018-December/041852.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046606/+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 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents

[Nick Rosbrook]

The drop-in would apply to vlan1, e.g.:

$ mkdir -p /etc/systemd/network/10-netplan-vlan1.network.d
$ cat > /etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf << EOF
[Network]
KeepMaster=true
EOF

Again, if netplan has a setting equivalent to KeepMaster=, that would be
simpler. I just don't know netplan well enough.

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

Title:
  Restarting `systemd-networkd` looses unmanaged bridged parents

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  My home network comprises many VLANs managed by `systemd-
  networkd`/`netplan`. Those VLANs are then used as parent interfaces
  for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post-
  update), my whole network breaks because all the unmanaged bridges
  lose their parent devices. Another way to see it is that `systemd-
  networkd` undoes the `master` setting of those VLAN devices.

  
  Here is a simplified reproducer:

  1. Create a `vlan1` device

  $ lxc launch ubuntu:22.04 networkd-bug
  Creating networkd-bug
  Starting networkd-bug

  $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF
  network:
version: 2
vlans:
  vlan1:
id: 1
link: eth0
  EOF

  $ lxc exec networkd-bug -- netplan apply

  2. Manually create a bridge and join `vlan1` to it

  $ lxc exec networkd-bug -- ip link add br0 type bridge
  $ lxc exec networkd-bug -- ip link set vlan1 master br0
  $ lxc exec networkd-bug -- ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: vlan1@eth0:  mtu 1500 qdisc noqueue 
master br0 state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff
  3: br0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff
  164: eth0@if165:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0

  3. Restart `systemd-networkd`

  $ lxc exec networkd-bug -- systemctl restart systemd-networkd

  4. Notice `vlan1` lost it's master config

  $ lxc exec networkd-bug -- ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: vlan1@eth0:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff
  3: br0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff
  164: eth0@if165:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0

  
  Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose 
connectivity :)


  Additional information:

  # apt-cache policy systemd netplan.io iproute2
  systemd:
Installed: 249.11-0ubuntu3.9
Candidate: 249.11-0ubuntu3.9
Version table:
   *** 249.11-0ubuntu3.9 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3.7 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   249.11-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  netplan.io:
Installed: 0.105-0ubuntu2~22.04.3
Candidate: 0.105-0ubuntu2~22.04.3
Version table:
   *** 0.105-0ubuntu2~22.04.3 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.104-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  iproute2:
Installed: 5.15.0-1ubuntu2
Candidate: 5.15.0-1ubuntu2
Version table:
   *** 5.15.0-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  # lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  # uname -a
  Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+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 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents

[Nick Rosbrook]

You have a couple options here. I think simplest would be to just add:

bridges:
  br0:
interfaces: [vlan1]

to your netplan config. This will generate
/run/systemd/network/10-netplan-vlan1.network with:

[Match]
Name=vlan1

[Network]
LinkLocalAddressing=no
ConfigureWithoutCarrier=yes
Bridge=br0

so the master will be configured correctly. Otherwise, you could add a
drop-in configuration for vlan1 to set KeepMaster=true (I don't know if
netplan has something for this)[1].

Either way, I do not think this is a bug.

[1]
https://www.freedesktop.org/software/systemd/man/latest/systemd.network.html#KeepMaster=


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

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

Title:
  Restarting `systemd-networkd` looses unmanaged bridged parents

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  My home network comprises many VLANs managed by `systemd-
  networkd`/`netplan`. Those VLANs are then used as parent interfaces
  for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post-
  update), my whole network breaks because all the unmanaged bridges
  lose their parent devices. Another way to see it is that `systemd-
  networkd` undoes the `master` setting of those VLAN devices.

  
  Here is a simplified reproducer:

  1. Create a `vlan1` device

  $ lxc launch ubuntu:22.04 networkd-bug
  Creating networkd-bug
  Starting networkd-bug

  $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF
  network:
version: 2
vlans:
  vlan1:
id: 1
link: eth0
  EOF

  $ lxc exec networkd-bug -- netplan apply

  2. Manually create a bridge and join `vlan1` to it

  $ lxc exec networkd-bug -- ip link add br0 type bridge
  $ lxc exec networkd-bug -- ip link set vlan1 master br0
  $ lxc exec networkd-bug -- ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: vlan1@eth0:  mtu 1500 qdisc noqueue 
master br0 state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff
  3: br0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff
  164: eth0@if165:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0

  3. Restart `systemd-networkd`

  $ lxc exec networkd-bug -- systemctl restart systemd-networkd

  4. Notice `vlan1` lost it's master config

  $ lxc exec networkd-bug -- ip link
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: vlan1@eth0:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff
  3: br0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff
  164: eth0@if165:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0

  
  Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose 
connectivity :)


  Additional information:

  # apt-cache policy systemd netplan.io iproute2
  systemd:
Installed: 249.11-0ubuntu3.9
Candidate: 249.11-0ubuntu3.9
Version table:
   *** 249.11-0ubuntu3.9 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3.7 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   249.11-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  netplan.io:
Installed: 0.105-0ubuntu2~22.04.3
Candidate: 0.105-0ubuntu2~22.04.3
Version table:
   *** 0.105-0ubuntu2~22.04.3 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.104-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  iproute2:
Installed: 5.15.0-1ubuntu2
Candidate: 5.15.0-1ubuntu2
Version table:
   *** 5.15.0-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  # lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  # uname -a
  Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login

[ravi mano]

Stragely though, when I reboot my ubuntu and mosue-click some times out of my 
ubuntu and inside my VmWare player randomly some times, it allowed me in. and 
also on reboot, it works with an Enter
( i.e  removing password effected ).

Also i tried to change password with passwd command giving the same
string I had used earlier, as new password. Strangely, this fails saying
"please enter a longer password". Then why was I allowed to be using a
"shorter" password all these days ?

My config:
--
anon@ubuntu:~$ 
anon@ubuntu:~$ uname -as
Linux ubuntu 4.15.0-142-generic #146~16.04.1-Ubuntu SMP Tue Apr 13 09:27:15 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux
anon@ubuntu:~$ 
anon@ubuntu:~$ 

anon@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.7 LTS
Release:16.04
Codename:   xenial
anon@ubuntu:~$


VmWare player version: ( not related though )
VMware® Workstation 16 Pro
16.1.2 build-17966106

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

Title:
  No administrative actions possible (password refused) after enabling
  passwordless login

Status in accountsservice package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-system-tools package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543

  Release: 11.10

  Cause: The password is cleared to be empty, and this prevents
  authentification for many admin tasks for security reasons. However,
  the user only needs to be added to the "nopasswdlogin" group, to
  enable passwordless login with gdm (and any other DM that ships with a
  corresponding "auth sufficient pam_succeed_if.so user ingroup
  nopasswdlogin" configuration).

  Fix:
   * lightdm to add pam rule
   * account managing tools not clearing password but only adding user to
 "nopasswdlogin" group

  
  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of the 
dialog. Enter your user password when prompted.
  5. Click on the four dots next to the "Password" label to change your 
password.
  6. Select "Log in without a password" from the dropdown box. Close the window.
  7. Try to perform an action requiring administrative privileges. For example, 
try running "sudo apt-get update" from a terminal.

  Expected behavior:
  sudo should require the user's password and accept it, or proceed without 
requiring any password altogether.

  Actual behavior:
  sudo requires the user's password and does not accept it (since it is set to 
an empty string in /etc/shadow).

  Further notes:
  After disabling the password request at login, the /etc/shadow file related 
to the test user account I created looked like this:
  test::15283:0:9:7:::
  This shows that the password hash is made completely empty; that conflicts 
with the policies listed in /etc/sudoers, which require a password to be given 
in order to perform
  administrative actions.

  Workaround:
  -If you can not perform administrative actions but can still login without a 
password, open a terminal and type "passwd". This command should prompt you for 
a new password and change it without any problems.
  -If you can not login, you can reset your password by booting into recovery 
mode and changing it there. Follow the instructions at 
.

  You may also choose to use a password for your account and to enable
  autologin at the same time. This choice will enable you to benefit the
  advantage of not entering a password at boot time with the security of
  Ubuntu requiring your password when attempting to perform privileged
  actions. Of course, this helps when you are the only desktop user or
  the primary one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/882255/+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 2039571] Re: systemd-modules-load fails on Azure 23.10 images on arm64

[Nick Rosbrook]

Is this still an issue on 24.04?

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

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

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

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

Title:
  systemd-modules-load fails on Azure 23.10 images on arm64

Status in cloud-images:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Mantic:
  New

Bug description:
  On some arm64 instances systemd-modules-load.service fails with the
  following error:

  $ sudo journalctl -u systemd-modules-load
  Oct 04 08:03:30 ubuntu systemd[1]: systemd-modules-load.service: start 
operation timed out. Terminating.
  Oct 04 08:03:30 ubuntu systemd[1]: systemd-modules-load.service: Main process 
exited, code=killed, status=15/TERM
  Oct 04 08:03:30 ubuntu systemd[1]: systemd-modules-load.service: Failed with 
result 'timeout'.
  Oct 04 08:03:30 ubuntu systemd[1]: Failed to start 
systemd-modules-load.service - Load Kernel Modules.

  It only fails on boot, when restarted manually the service runs fine.
  I can't find which module fails to load. The only kernel module that
  this service is supposed to load is multipathd and it appears to be
  loaded even when the service has failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2039571/+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 2054719] Re: base-files, glibc lockstep migration blocking bug

[Julian Andres Klode]

apt and bzip2 have migrated, so we are ready to land them in the next
britney run.

** Tags removed: block-proposed

** Changed in: base-files (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  base-files, glibc lockstep migration blocking bug

Status in base-files package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released

Bug description:
  With the new changes I'm uploading, taken from Helmut's patches on
  Debian bug tracker, base-files will own the /lib64 symlink, and /lib64
  in libc6 will move to /usr/lib64.

  Special care has been taken to not break upgrades: You can upgrade the
  two in any order.

  However, debootstrap requires both packages to be at a matching
  version:

  1. If base-files migrates first, the old libc6 would fail to unpack
  2. If glibc migrates first, and is bootstrapped before base-files, we do not 
end up with the /lib64 symlink at all because debootstrap only *moves* an 
existing /lib64 (which now is no longer present).

  Since upgrades are fine due to having the symlink already, we do not
  want to solve this by introducing dependencies: We could have added
  mutual Depends or Breaks, but they would have required temporarily
  deconfiguring one of the packages to unpack the other on upgrades.

  Hence we'll mark this bug as block-proposed and remove the tag once
  both are ready to land.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054719/+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 2054823] Re: Sync klibc 2.0.13-4 (main) from Debian unstable (main)

[Paride Legovini]

klibc (2.0.13-4) unstable; urgency=medium

  [ Sven Joachim ]
  * debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
(Closes: #1055694).

  [ Salvatore Bonaccorso ]
  * debian/control: Add myself to Uploaders

Date: 2024-02-21 22:32:43.744541+00:00
Signed-By: Paride Legovini 
https://launchpad.net/ubuntu/+source/klibc/2.0.13-4

==

 OK: klibc_2.0.13-4.dsc
 -> Component: main Section: libs
 OK: klibc_2.0.13.orig.tar.xz
 OK: klibc_2.0.13-4.debian.tar.xz

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

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

Title:
  Sync klibc 2.0.13-4 (main) from Debian unstable (main)

Status in klibc package in Ubuntu:
  Fix Released

Bug description:
  Please sync klibc 2.0.13-4 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
[ Klaus Frank ]
* d/i/h/klibc-utils: Fix compatibility issue with busybox and improve 
verbose debug output.
  (Closes: #1055694) (LP: #2046336)

  This patch provided one way to fix the `cp -n` incompatibility. The changelog
  below mentions another change with the same purpose. I've also checked the 
code,
  and that new version from Debian correctly doesn't use `cp -n`, which means
  it will be safe to use with any version of coreutils, older or newer than the
  change of semantic in `cp -n`.

  
  Changelog entries since current noble version 2.0.13-2ubuntu1:

  klibc (2.0.13-4) unstable; urgency=medium

[ Sven Joachim ]
* debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
  (Closes: #1055694).

[ Salvatore Bonaccorso ]
* debian/control: Add myself to Uploaders

   -- Salvatore Bonaccorso   Wed, 21 Feb 2024
  13:08:58 +0100

  klibc (2.0.13-3) experimental; urgency=medium

* Install klibc shared library in /usr/lib

   -- Ben Hutchings   Sat, 25 Nov 2023 00:49:35 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2054823/+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 2054823] Re: Sync klibc 2.0.13-4 (main) from Debian unstable (main)

[Paride Legovini]

** Changed in: klibc (Ubuntu)
 Assignee: (unassigned) => Paride Legovini (paride)

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

Title:
  Sync klibc 2.0.13-4 (main) from Debian unstable (main)

Status in klibc package in Ubuntu:
  New

Bug description:
  Please sync klibc 2.0.13-4 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
[ Klaus Frank ]
* d/i/h/klibc-utils: Fix compatibility issue with busybox and improve 
verbose debug output.
  (Closes: #1055694) (LP: #2046336)

  This patch provided one way to fix the `cp -n` incompatibility. The changelog
  below mentions another change with the same purpose. I've also checked the 
code,
  and that new version from Debian correctly doesn't use `cp -n`, which means
  it will be safe to use with any version of coreutils, older or newer than the
  change of semantic in `cp -n`.

  
  Changelog entries since current noble version 2.0.13-2ubuntu1:

  klibc (2.0.13-4) unstable; urgency=medium

[ Sven Joachim ]
* debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
  (Closes: #1055694).

[ Salvatore Bonaccorso ]
* debian/control: Add myself to Uploaders

   -- Salvatore Bonaccorso   Wed, 21 Feb 2024
  13:08:58 +0100

  klibc (2.0.13-3) experimental; urgency=medium

* Install klibc shared library in /usr/lib

   -- Ben Hutchings   Sat, 25 Nov 2023 00:49:35 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2054823/+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 2054827] Re: [regression] GUI crashed after installed proposed package after mesa updates

[drouineau]

and here is the syslog

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054827/+attachment/5748736/+files/syslog

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

Title:
  [regression] GUI crashed after installed proposed package after mesa
  updates

Status in mesa package in Ubuntu:
  New

Bug description:
  Dear all, after the upgrade of various mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong) than those reported there 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. 
  I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the 
issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The 
issue occurs if I use either the nouveau driver or the proprietary nvidia 
driver (535 from ubuntu repo) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).
  I enclose the syslog before the crash which mentions an issue with mesa 
drivers.
  I will enclose also the apt log describing the operations that have cause the 
bug

  I suspect that this bug is related to this one
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068


  
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04


  
  libegl-mesa0:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  
  libgl1-mesa-dri:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  [Summary]
  After upgrade of packages last monday, reboot system when using nouveau 
driver, nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. 
It works if using nvidia-driver with profile nvidia.


  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2
  ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73
  Uname: Linux 6.1.0-1034-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 16:21:34 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed
   nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0c40]
 Subsystem: Dell Device [1028:0c40]
  InstallationDate: Installed on 2024-01-12 (42 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Precision 5480
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0VCJYY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 

[Touch-packages] [Bug 2054827] [NEW] [regression] GUI crashed after installed proposed package after mesa updates

[drouineau]

Public bug reported:

Dear all, after the upgrade of various mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong) than those reported there 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. 
I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the 
issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The 
issue occurs if I use either the nouveau driver or the proprietary nvidia 
driver (535 from ubuntu repo) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).
I enclose the syslog before the crash which mentions an issue with mesa drivers.
I will enclose also the apt log describing the operations that have cause the 
bug

I suspect that this bug is related to this one
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068


Description:Ubuntu 22.04.4 LTS
Release:22.04


libegl-mesa0:
  Installé : 23.2.1-1ubuntu3.1~22.04.2
  Candidat : 23.2.1-1ubuntu3.1~22.04.2
 Table de version :
 *** 23.2.1-1ubuntu3.1~22.04.2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 22.0.1-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


libgl1-mesa-dri:
  Installé : 23.2.1-1ubuntu3.1~22.04.2
  Candidat : 23.2.1-1ubuntu3.1~22.04.2
 Table de version :
 *** 23.2.1-1ubuntu3.1~22.04.2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 22.0.1-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


[Summary]
After upgrade of packages last monday, reboot system when using nouveau driver, 
nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. It works 
if using nvidia-driver with profile nvidia.


[Steps to reproduce]
1. Boot into OS
2. sudo apt update
3. sudo apt upgrade
4. After upgrade process finished, reboot system.
5. GUI crashed.

[Expected result]
GUI displayed normally

[Actual result]
GUI crashed

[Failure rate]
100%

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2
ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73
Uname: Linux 6.1.0-1034-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 16:21:34 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed
 nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0c40]
   Subsystem: Dell Device [1028:0c40]
InstallationDate: Installed on 2024-01-12 (42 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Dell Inc. Precision 5480
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2023
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 0VCJYY
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd12/18/2023:br1.8:efr1.16:svnDellInc.:pnPrecision5480:pvr:rvnDellInc.:rn0VCJYY:rvrA01:cvnDellInc.:ct10:cvr:sku0C40:
dmi.product.family: Precision
dmi.product.name: Precision 5480
dmi.product.sku: 0C40
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
version.xserver-xorg-input-evdev: 

[Touch-packages] [Bug 2054827] Re: [regression] GUI crashed after installed proposed package after mesa updates

[drouineau]

here is the apt.log of the upgrade that have raised the issue

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054827/+attachment/5748735/+files/apt.log

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

Title:
  [regression] GUI crashed after installed proposed package after mesa
  updates

Status in mesa package in Ubuntu:
  New

Bug description:
  Dear all, after the upgrade of various mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong) than those reported there 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. 
  I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the 
issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The 
issue occurs if I use either the nouveau driver or the proprietary nvidia 
driver (535 from ubuntu repo) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).
  I enclose the syslog before the crash which mentions an issue with mesa 
drivers.
  I will enclose also the apt log describing the operations that have cause the 
bug

  I suspect that this bug is related to this one
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068


  
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04


  
  libegl-mesa0:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  
  libgl1-mesa-dri:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  [Summary]
  After upgrade of packages last monday, reboot system when using nouveau 
driver, nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. 
It works if using nvidia-driver with profile nvidia.


  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2
  ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73
  Uname: Linux 6.1.0-1034-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 16:21:34 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed
   nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0c40]
 Subsystem: Dell Device [1028:0c40]
  InstallationDate: Installed on 2024-01-12 (42 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Precision 5480
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0VCJYY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  

[Touch-packages] [Bug 2054823] [NEW] Sync klibc 2.0.13-4 (main) from Debian unstable (main)

[Skia]

Public bug reported:

Please sync klibc 2.0.13-4 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  [ Klaus Frank ]
  * d/i/h/klibc-utils: Fix compatibility issue with busybox and improve verbose 
debug output.
(Closes: #1055694) (LP: #2046336)

This patch provided one way to fix the `cp -n` incompatibility. The changelog
below mentions another change with the same purpose. I've also checked the code,
and that new version from Debian correctly doesn't use `cp -n`, which means
it will be safe to use with any version of coreutils, older or newer than the
change of semantic in `cp -n`.


Changelog entries since current noble version 2.0.13-2ubuntu1:

klibc (2.0.13-4) unstable; urgency=medium

  [ Sven Joachim ]
  * debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
(Closes: #1055694).

  [ Salvatore Bonaccorso ]
  * debian/control: Add myself to Uploaders

 -- Salvatore Bonaccorso   Wed, 21 Feb 2024 13:08:58
+0100

klibc (2.0.13-3) experimental; urgency=medium

  * Install klibc shared library in /usr/lib

 -- Ben Hutchings   Sat, 25 Nov 2023 00:49:35 +

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

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

Title:
  Sync klibc 2.0.13-4 (main) from Debian unstable (main)

Status in klibc package in Ubuntu:
  New

Bug description:
  Please sync klibc 2.0.13-4 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
[ Klaus Frank ]
* d/i/h/klibc-utils: Fix compatibility issue with busybox and improve 
verbose debug output.
  (Closes: #1055694) (LP: #2046336)

  This patch provided one way to fix the `cp -n` incompatibility. The changelog
  below mentions another change with the same purpose. I've also checked the 
code,
  and that new version from Debian correctly doesn't use `cp -n`, which means
  it will be safe to use with any version of coreutils, older or newer than the
  change of semantic in `cp -n`.

  
  Changelog entries since current noble version 2.0.13-2ubuntu1:

  klibc (2.0.13-4) unstable; urgency=medium

[ Sven Joachim ]
* debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
  (Closes: #1055694).

[ Salvatore Bonaccorso ]
* debian/control: Add myself to Uploaders

   -- Salvatore Bonaccorso   Wed, 21 Feb 2024
  13:08:58 +0100

  klibc (2.0.13-3) experimental; urgency=medium

* Install klibc shared library in /usr/lib

   -- Ben Hutchings   Sat, 25 Nov 2023 00:49:35 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2054823/+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 2053165] Re: [noble] Version 2.7.5 causes software-properties to crash

[RedLeaves]

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

I deleted the files in the /etc/apt/sources.list.d and it worked
normally.

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

Title:
  [noble] Version 2.7.5 causes software-properties to crash

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Only since recent 2.7.5 update along with 0.99.42 for software-properties.
  Crash on start-up.

  $ software-properties-gtk 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2053165/+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 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found

[Luca Boccassi]

Note that currently in noble lvm2 fails to build due to
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683 which is
unrelated to the MR linked here

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

Title:
  libdm returns wrong error code when dm-verity key cannot be found

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Noble:
  Confirmed

Bug description:
  When libcryptsetup tries to activate a signed dm-verity volume, and
  the key is not in the kernel keyring, libdevicemapper does not return
  the appropriate ENOKEY, so the failure cannot be distinguished from
  other generic issues.

  This is fixed in the lvm2 version 2.03.23 upstream release.

  Please consider backporting this patch for Noble.

  Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3
  Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+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 2052925] Re: lpoptions -d as root

[Timo Aaltonen]

Hello Rudra, or anyone else affected,

Accepted cups into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cups/2.4.1op1-1ubuntu4.8 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-jammy

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

Title:
  lpoptions -d as root

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Jammy:
  Fix Committed

Bug description:
  Copied from https://github.com/OpenPrinting/cups/issues/454

  Yair Yarom submitted Debian bug 1008053 and observed that running
  lpoptions as root does not update /etc/cups/lpoptions but
  /root/.cups/lpoptions.

  Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should
  update /etc/cups/lpoptions to be the defaults for all users. But
  instead it tries to update /root/.cups/lpoptions.

  This has been fixed upstream in cups, in debian sid, and mantic.
  Proposing to add this change in jammy and older (still supported)
  series as well.

  The fix is a one line change in
  https://github.com/OpenPrinting/cups/pull/456

  Thanks.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  ubuntu@jammy-vm:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  ubuntu@jammy-vm:~$ apt-cache policy cups
  cups:
    Installed: 2.4.1op1-1ubuntu4.7
    Candidate: 2.4.1op1-1ubuntu4.7
    Version table:
   *** 2.4.1op1-1ubuntu4.7 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.1op1-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  3) What you expected to happen:

  root@jammy-vm:~# lpstat -p
  printer HP-Officejet-Pro-8710 is idle.  enabled since Thu 01 Feb 2024 
03:17:49 PM UTC
  root@jammy-vm:~#
  root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710
  copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 
job-cancel-after=10800 job-hold-until=no-hold job-priority=50 
job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color 
printer-commands=none printer-info=HP-Officejet-Pro-8710 
printer-is-accepting-jobs=true printer-is-shared=true 
printer-is-temporary=false printer-location printer-make-and-model='HP 
Officejet Pro 8710, hpcups 3.21.12' printer-state=3 
printer-state-change-time=1706800669 printer-state-reasons=none 
printer-type=4124 
printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710
  root@jammy-vm:~#
  root@jammy-vm:~# cat /etc/cups/lpoptions
  Default HP-Officejet-Pro-8710
  root@jammy-vm:~#
  root@jammy-vm:~# cat /root/.cups/lpoptions
  cat: /etc/cups/lpoptions: No such file or directory
  root@jammy-vm:~#

  4) What happened instead:

  root@jammy-vm:~# lpstat -p
  printer HP-Officejet-Pro-8710 is idle.  enabled since Thu 01 Feb 2024 
03:17:49 PM UTC
  root@jammy-vm:~#
  root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710
  copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 
job-cancel-after=10800 job-hold-until=no-hold job-priority=50 
job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color 
printer-commands=none printer-info=HP-Officejet-Pro-8710 
printer-is-accepting-jobs=true printer-is-shared=true 
printer-is-temporary=false printer-location printer-make-and-model='HP 
Officejet Pro 8710, hpcups 3.21.12' printer-state=3 
printer-state-change-time=1706800669 printer-state-reasons=none 
printer-type=4124 
printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710
  root@jammy-vm:~#
  root@jammy-vm:~# 

[Touch-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[drouineau]

I also enclose the apt log describing the dist-upgrade that causes the
issue

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+attachment/5748703/+files/apt.log

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[drouineau]

Dear all, after the upgrade of mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong). I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 
6.1.0-1034-oem but the issue remains with kernel 6.2.0-26-generic). I have a 
Dell precision 5480. The issue occurs if I use the nouveau driver or the 
proprietary nvidia driver (535) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).  
I enclose the syslog around the crash which mentions an issue with mesa drivers.

Is this the same issue or should I open a new issue?


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+attachment/5748702/+files/syslog

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 1677827] Re: Missing dep8 tests

[Miriam España Acebal]

Fixed on Debian, and as the package is in sync, we already have the tests.
Marking FixReleased and removing myself as assignee.

** Changed in: dnsmasq (Ubuntu)
 Assignee: Miriam España Acebal (mirespace) => (unassigned)

** Changed in: dnsmasq (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 dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1677827

Title:
  Missing dep8 tests

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source dnsmasq zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/dnsmasq
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XcdAAoJEIP8BxPaZgwlCPUQAIeBwdnTYjMB0QFt7FZSUOqx
  9N4PMHdxodMVmtEW2FytBuuq0S1jTyu06GNsLwKBmzfyuICScCoGPt8KS14omp/R
  g0QAA4Fk2T6YMtVdsZIflUpMzlNTiFw2Ndgf7LOs3xX2lkB36xqbWlr+86fCTe+2
  O8pzYZoQeveHc7XQxlT0eDFCiZx83ZFwjF8OjgGfWY3iQsvcb2T00hKlkpQ2qCdT
  uiBTN6xnw9v50OGGlphObRy4YdE8x4u3/jWFOzwKUk5X1Qi31wK9hQYLSBAgX7Ph
  kkL681OBi5RIlUO5QsD3qJPvi3OIGMx2zhMvQfcK8Otn5DMwDoEETOAafMvPmhd/
  NUK/OaNcB2TR6Sl5Jt/NUp3E0LRTYgbMuEONkEeBm5YdABb7hUcYRPomnpzCcNBL
  iSdcEH2khGbiCK3oYcT5UgtBe4MFlpHHkkQzmew/nLNZ/BrgULFs0HWLXu8gWN8g
  Wn0iAF/Ft2kcWgRNXJ3JCd2nc04U0hqiUmMtVXku4r0f3fxfTudtvPACcZC7ctKb
  0rqChEm0r/ewtHvLcuOFIIJBaTQxoQmm8zBPv/y/S+YdkwmVYS9LlWKqG54KLlPy
  iAt7+/GvQ0fqqzmk88yQ5F4L19Dg+X5fLZVM1wBvvQ4nTsJRfUhf3+I2orcKDy6C
  zNZGvitiod7eMrypmXIA
  =k1Nj
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1677827/+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 2023322] Re: GTK internal browser does not render with Nvidia drivers

[Bug Watch Updater]

** Bug watch added: bugs.webkit.org/ #210100
   https://bugs.webkit.org/show_bug.cgi?id=210100

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is 

[Touch-packages] [Bug 2023322]

[Zlatko-webkit]

Hi Michael,

I already hopped over to bug #261874, as the description in #c32 over
there matches my setup exactly. The errors I get are:

> [zlatko@disclosure:~]$ liferea
> src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): 
> DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
> 
> Failed to create GBM buffer of size 469x191: Invalid argument
> src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): 
> DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
> 
>Failed to create GBM buffer of size 469x191: Invalid argument
> src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): 
> DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
> 
> Failed to create GBM buffer of size 469x191: Invalid argument
> Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1

Yes, I'm on X11 without modsetting (with NVidia this only works when
booting UEFI, which I don't), and "liferea" is a GTK3 application (ie.
using libwebkit2gtk-4.0.so), where the current state still seems to be
...

> "There's no workaround for GTK3, we need to figure out why gbm_bo_map
is failing and fix it."

... so this bug seems to be the perfect fit. :-)

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 

[Touch-packages] [Bug 2023322]

[Georges Basile Stavracas Neto]

This bug is for GTK4, Liferea is GTK3. That's a separate issue that
should not be marked as a blocker for
https://bugs.webkit.org/show_bug.cgi?id=210100

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR 

[Touch-packages] [Bug 2023322]

[Mcatanzaro-c]

Hi Craig and Thomas (and Emil if you're still around): if you're still
encountering problems with NVIDIA graphics, please report new a bug and
leave a comment here linking to the new bug.

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window