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

[bugproxy]

--- Comment From sthou...@in.ibm.com 2023-06-06 01:35 EDT---
(In reply to comment #6)
> Backtraces are on the upstream bug, eg:
>
> https://github.com/systemd/systemd/issues/25091#issuecomment-1401824195
> https://github.com/systemd/systemd/issues/25091#issuecomment-1402425787
>
> It would be better if the IBM developers could engage directly on the
> upstream ticket for the initial investigation, given the information is
> recorded there. Thanks!

Peter, Could you check this upstream bug and confirm if this needs to be
looked by tools chain team as claimed by Ubuntu distro team?

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

Title:
  autopkgtest: upstream tests that run in qemu hang on ppc64el

Status in systemd:
  Unknown
Status in The Ubuntu-power-systems project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New

Bug description:
  I believe this started early in the kinetic cycle, cf.
  https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs
  https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el.
  Timeouts in the upstream tests have been an issue for a while, but
  kinetic on ppc64el consistently times out with upstream tests that run
  in QEMU.

  Skipping individual tests does not help, because *which* tests time
  out appears to change with each build. For example, in 251.4-1ubuntu4
  the TEST-36-NUMAPOLICY test was consistently the culprit, but now in
  251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out.

  I have not been able to identify a root cause for this, but it seems
  that running tests in QEMU is very fragile on ppc64el, where as the
  tests that run in nspawn are more consistent.

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


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

[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately

[Doug Brown]

It appears that this bug no longer affects newer versions of Ubuntu.
It's unclear to me exactly how this change happened, but in 23.04,
running "setsid pkexec echo hello" for example no longer prints the
"Refusing to render service to dead parents." message, and instead works
correctly. The original reproduction steps with Firefox/Chrome also
don't cause the problem anymore.

The difference seems to be that when you run pkexec like that, it now
gets parented to "systemd --user" in modern Ubuntu versions instead of
init, so pkexec is no longer unhappy about it.

I can still spend some time tweaking the merge request as per Julian's
feedback if there is any chance that this would result in new builds of
gdebi for the older affected versions like 20.04 and 22.04.

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

Title:
  gdebi-gtk calls pkexec inappropriately

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Have Ubuntu with gdebi-gtk installed
  2. Open Firefox
  3. Visit some site with deb-package download link or use direct link like 
https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb
  4. Proceed with file downloading
  5. In Firefox select Library → Downloads, click on downloaded deb-file

  Expected results:
  * gdebi-gtk is opened, the package installs normally after users clicks 
Install button

  Actual results:
  * gdebi-gtk is opened, the package is not installed because of vanishing of 
gdebi-gtk window just after clicking Install button


  

  Before anyone says this bug already exists... it doesn't (at least as
  far as I can see).  It's just that a lot of similar bugs do/did exist
  where people have also experienced the same symptoms (of gdebi-gtk
  vanishing upon clicking 'Install').

  So yes this is the same symptoms, but it must be a different cause as
  the circumstances are different and doesn't have the same resolution.

  The meat of it...

  Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or 
with Chrome if you installed that) go to any site that offers a .deb package 
and either...
  a) choose to open it directly from the browser (rather than saving it to 
'Downloads' folder)
  b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that 
file from within the browser itself.

  You should find that gdebi-gtk appears but vanishes the moment you
  click 'Install' without a prompt for a password, an explanation or the
  package actually getting installed.

  This bug has existed since the beginning of Ubuntu 18.04 however it's
  been largely confused with other similar bugs.  I've had it on half a
  dozen machines and confirmed it exists with IRC users on #ubuntu-mate
  of freenode.

  However with *this* bug (compared to others) gdebi-gtk works perfectly
  fine if you run it from the terminal or just double click the .deb
  package from your file manager.

  It's the kind of bug which if you're a hardened desktop Linux user,
  you'd just work around it...

  But if you're a novice and you can't get a simple thing like
  Teamviewer installed (which is a .deb, and a thing I might ask someone
  to do over the phone to try to help them) you likely get fed up and
  re-install Windows :S

  Any input on this would be brilliant as I can't seem to get any
  logs/output.

  ~lantizia

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


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

[Touch-packages] [Bug 2021505] Re: Flaky DEP8 test: saslauthd

[Bug Watch Updater]

** Changed in: cyrus-sasl2 (Debian)
   Status: New => Fix Released

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

Title:
  Flaky DEP8 test: saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  It looks like the saslauthd test is a bit flaky, and more so in
  platforms like arm64[1]:

  autopkgtest [15:14:52]: test saslauthd: [---
  Setting up saslauthd with mecanism sasldb
  Authentication of user user1887 with correct password should succeed... FAIL
  exit status: 255
  output:
  connect() : No such file or directory
  0:
  autopkgtest [15:14:53]: test saslauthd: ---]
  autopkgtest [15:14:53]: test saslauthd:  - - - - - - - - - - results - - - - 
- - - - - -
  saslauthdFAIL non-zero exit status 1

  The "connect()" error looks like the saslauthd unix socket isn't ready
  yet. That test happens right after a saslauthd restart:

  echo "Setting up saslauthd with mecanism ${mech}"
  setup_saslauthd ${mech} <--- restart happens here

  # test correct credentials
  echo -n "Authentication of user ${sasluser} with correct password should 
succeed... "
  result=0
  output=$(testsaslauthd -u "${sasluser}" -p "${saslpass}" 2>&1) || 
result=$? <--- this is the authentication test

  Maybe we should loop for a few times in a check for the socket, and if
  it still fails, add extra logging to the output so it can be
  troubleshooted better.

  
  1. https://autopkgtest.ubuntu.com/packages/c/cyrus-sasl2/mantic/arm64

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


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

[Touch-packages] [Bug 2022981] Re: Frequent hard reboots on RaptorLake

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Frequent hard reboots on RaptorLake

Status in xorg package in Ubuntu:
  New

Bug description:
  I can repro in multiple ways:

  1. Unplug my HDMI monitor. This is pretty much a guaranteed reboot.
  2. Using hardware accelerated Chromium, switching between google profiles 
seems to trigger a crash and full reboot pretty often.

  These could be two separate bugs. I'm not sure I'd be unlucky enough
  to have two full reboot bugs at the same time though. Happy to help
  with more debugging

  Release: Jammy
  Chromium version: 115.0.5762.4-hwacc
  snap refresh --channel=latest/edge/hwacc chromium

  What you expected to happen
  1. HDMI monitor disconnects, and no reboots happen.
  2. I can switch Chromium profiles without a reboot

  What happened instead
  Both actions cause a reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  6 16:09:12 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-41-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-43-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   tp_smapi/0.43, 5.19.0-41-generic, x86_64: installed
   tp_smapi/0.43, 5.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5630]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:]
  InstallationDate: Installed on 2023-04-20 (46 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: System76 Gazelle
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_90m3zy@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_90m3zy ro drm.debug=0xe quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2023
  dmi.bios.release: 4.19
  dmi.bios.vendor: coreboot
  dmi.bios.version: 2023-03-22_799ed79
  dmi.board.name: Gazelle
  dmi.board.vendor: System76
  dmi.board.version: gaze18
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr2023-03-22_799ed79:bd03/22/2023:br4.19:efr0.0:svnSystem76:pnGazelle:pvrgaze18:rvnSystem76:rnGazelle:rvrgaze18:cvnSystem76:ct9:cvr:sku:
  dmi.product.name: Gazelle
  dmi.product.version: gaze18
  dmi.sys.vendor: System76
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

[Touch-packages] [Bug 1964763] Re: QtChooser doesn't support qt6

[tom stevens]

If you are using cmake you might get your builds to find the desired flavor by 
setting
CMAKE_PREFIX_PATH to something like /usr/lib/x86_64-linux-gnu/cmake/Qt6 or 
/usr/lib/x86_64-linux-gnu/cmake/Qt5 either on the command line or by exporting 
that variable.

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Won't Fix

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Mauricio Faria de Oliveira]

Uploaded to Lunar and Jammy, but not Kinetic (Won't Fix).

$ ubuntu-distro-info --series=kinetic --days=eol
45

Thanks!

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  In Progress
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

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


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

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Sam]

OK just a question about pinning since we would prefer to minimize
changes to user systems.  When we follow the instructions from Steve's
message on:

 https://wiki.ubuntu.com/Testing/EnableProposed

which sets the pin priority for proposed to 400, the page says to run a
simulated apt upgrade to verify that no packages are scheduled for
upgrade.  However when we try that we see 11 upgrade-able packages.

We can get that number to 0 if we set the pin priority to something less
than that of /var/lib/dpkg/status, i.e., to something less than 100.
But is that correct?

If we comment out all the pin restrictions we see 44 proposed packages
scheduled for upgrade.  Is that because some of the proposed packages
aren't controlled by /var/lib/dpkg/status?

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 1983359] Re: hwrng drivers missing in initrd.img

[Steve Langasek]

This needs the bug description completed according to
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ("Where
problems could occur") before it can be sponsored.

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

Title:
  hwrng drivers missing in initrd.img

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  Incomplete
Status in initramfs-tools source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  The initialization of the entropy buffer of the urandom device is critical 
for security.

  [Test case]
  When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings:

  [   14.654546] random: lvm: uninitialized urandom read (4 bytes read)
  [   15.247995] random: lvm: uninitialized urandom read (2 bytes read)
  [   22.484719] random: lvm: uninitialized urandom read (4 bytes read)
  [   43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read)
  [   48.862281] random: lvm: uninitialized urandom read (4 bytes read)

  Module virtio-rng.ko is missing in initrd.img.
  Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings.

  Hardware RNG drivers should generally be included in the initrd to
  provide early entropy.

  Best regards

  Heinrich

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


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

[Touch-packages] [Bug 1983359] Re: hwrng drivers missing in initrd.img

[Steve Langasek]

This needs the bug description completed according to
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ("Where
problems could occur") before it can be sponsored.

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

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

Title:
  hwrng drivers missing in initrd.img

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  Incomplete
Status in initramfs-tools source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  The initialization of the entropy buffer of the urandom device is critical 
for security.

  [Test case]
  When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings:

  [   14.654546] random: lvm: uninitialized urandom read (4 bytes read)
  [   15.247995] random: lvm: uninitialized urandom read (2 bytes read)
  [   22.484719] random: lvm: uninitialized urandom read (4 bytes read)
  [   43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read)
  [   48.862281] random: lvm: uninitialized urandom read (4 bytes read)

  Module virtio-rng.ko is missing in initrd.img.
  Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings.

  Hardware RNG drivers should generally be included in the initrd to
  provide early entropy.

  Best regards

  Heinrich

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


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

[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

[Bug Watch Updater]

** Changed in: wpa (Debian)
   Status: New => Fix Released

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Fix Released
Status in wpa package in Debian:
  Fix Released

Bug description:
  * Impact
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  * Test case
  try to connect to a TLS <= 1.1 access point

  * Regression potential
  the patch lowers the security level in some situation for compatibility, it 
shouldn't prevent connecting to newer hardware, still try to connect to 
different type of wifi with different security levels

  ---

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1967014] Re: Lenovo Ideapad 3 screen brightness F keys not working...

[Launchpad Bug Tracker]

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

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

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

Title:
  Lenovo Ideapad 3 screen brightness F keys not working...

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  As the title says, the F keys the control screen brightness (F11/F12
  on the Lenovo Ideapad 3 15ITL05 laptop I have) don't work on Ubuntu
  21.10. All other special function keys (volume up/down, lock screen,
  airplane mode, etc...) and the screen brightness slider in the top
  right-hand corner work; it's just the brightness keys that are not
  working.

  I know I can just use the slider, but it's more convenient to use the
  F keys. I hope you are working on this for a future 21.10 update.

  Also, I originally installed 20.04 and upgraded to 21.10, but even on
  20.04, those keys weren't working, either.

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


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

[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore

[Marian Rainer-Harbach]

I tested the package from proposed after deleting the manually created
plugins directory first. The new package correctly creates the directory
and HEIF files can be opened. Thanks!

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

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

Title:
  Cannot open HEIF/HEIC images in 23.04/lunar anymore

Status in eog package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in libheif package in Ubuntu:
  Fix Released
Status in eog source package in Lunar:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Invalid
Status in libheif source package in Lunar:
  Fix Committed

Bug description:
  * Impact

  The libheif loader is bailing out due to a missing plugin directory
  which leads to image viewer as eog not being able to open pictures in
  that format anymore

  * Testcase

  Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in
  eog

  * Where problems could occur

  The package build is using the option to not split the codec in
  separate plugins but the version of Lunar doesn't handle the missing
  plugins directory and bails out. The code of the version in mantic has
  been refactored in a way which fixes this problem. For lunar it's
  easier to just create the directory. The directory is included in the
  libheif1 binary but that should not create any conflict, it's a
  temporary situation for lunar only and even if the soname changed dpkg
  allows for several deb packages to provide the same directory.

  --


  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.

  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC

  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  eog then shows "Could not load image “IMG_9996.HEIC”. Image loading
  failed."

  gpicview even crashes immediately:
  $ gpicview IMG_9996.HEIC
  Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module"

  ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin
  directory.

  ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory.
  Segmentation fault (core dumped)

  The problem concerns all HEIF/HEIC images I tested.

  The installed versions of the (possibly) relevant packages are:
  libheif1: 1.14.2-1
  heif-gdk-pixbuf: 1.14.2-1
  libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1
  eog: 44.0-1
  gpicview: 0.2.5-3build1

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


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

[Touch-packages] [Bug 1977645] Re: python3-gpg 1.16.0-unknown version is incomparable, dependencies always fail

[Steve Langasek]

Well, as it turns out I'm not marking it as a duplicate because bug
#1731268 in Launchpad prevents it.  Closing this bug instead as wontfix,
then.

** Changed in: gpgme1.0 (Ubuntu Jammy)
   Status: Triaged => Won't Fix

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

Title:
  python3-gpg 1.16.0-unknown version is incomparable, dependencies
  always fail

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Jammy:
  Won't Fix
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in gpgme1.0 source package in Lunar:
  Fix Released
Status in gpgme1.0 package in Debian:
  Fix Released

Bug description:
  The python version of the gpgme version contains "unknown" and is
  therefore not PEP440 order compatible.

  See this example:

# pip3 freeze | grep gpg
gpg===1.16.0-unknown

# pip3 install pstore
...
Successfully installed gpg-1.10.0
Successfully installed pstore-2.0.0

# pip3 freeze | grep gpg
gpg==1.10.0

  
  Key takeways from that example:

  - pstore depends on gpg>=1.10

  - 1.16 SHOULD be higher than 1.10

  - pip installs 1.10 even though 1.16 exists

  - the triple-= (gpg===1.16.0-unknown) means that the version exists,
  but cannot be version compared:
  https://peps.python.org/pep-0440/#arbitrary-equality


  Suggested fix:

  - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with
  a '+'; that will compare as expected;

  - fix so "-unknown" isn't appended.

  
  Apparently, this is caused by insufficient fixes in 
0001-avoid-identifying-as-beta.patch

  I've attached a FIXED version, which should fix things.

  Before:

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown.

  After:

$ quilt push 
Applying patch 0001-avoid-identifying-as-beta-FIXED.patch

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0.

  
  Versions:

  $ lsb_release -a 2>/dev/null| grep Codename
  Codename: jammy

  $ apt-cache policy python3-gpg  | grep Installed
Installed: 1.16.0-1.2ubuntu4

  
  Cheers,
  Walter Doekes
  OSSO B.V.

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


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

[Touch-packages] [Bug 2002511]

[tstaudt]

Thanks, Lukas

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

Title:
  zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Jammy:
  New
Status in zlib source package in Kinetic:
  New
Status in zlib source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
 the patch from LP#1990379, break libxml2 and lxml on s390x.

   * The problem appears during loading a gzipped XML file.

   * Disabling hw compression with 'export DFLTCC=0' solves this,
 hence it's a problem with the hardware acceleration patches DFLTCC.

   * For more info see:
  https://bugzilla.redhat.com/show_bug.cgi?id=2155328

  [ Test Plan ]

   * Steps to Reproduce:
 1. echo "" > file.xml
 2. gzip file.xml
 3. python3
 >>> import libxml2
 >>> libxml2.parseFile("file.xml.gz")

   * Actual results:
 file.xml.gz:1: parser error : Document is empty
 ^
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python3.11/site-packages/libxml2.py",
   line 1362, in parseFile
 if ret is None:raise parserError('xmlParseFile() failed')
^^
 libxml2.parserError: xmlParseFile() failed

   * Expected results:
 Loaded file.

  [ Where problems could occur ]

   * Since this is limited to s390x and DFLTCC / hw acceleration active,
 any possible problems are limited to such environments.

   * Fix can be broken if the state handling (state->wrap),
 or the states mixed.

   * The translation from stream to parameter block could be broken
 (again due to wrong states) and the inflate as well.

  [ Other Info ]

   * The official upstream fix is here:
 https://github.com/zlib-ng/zlib-ng/pull/1390
 but it's for zlib-ng.

   * For zlib this needs to be adjusted and was done by the author here:
 https://launchpadlibrarian.net/641454325/patch-1.2.11

   * And again slightly adjusted by me (renamed, some white-space fixes
 and conversion into a quilt patch with proper dep3 header):
 https://launchpadlibrarian.net/645435847/1390.patch

   * The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
  __

  It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks 
libxml2 (and libxml) on s390x:
  (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch 
should fix the issue.

  The upstream author proposed a fix and a new test for zlib-ng
  (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
  breakages in the future.

  ___

  This was initially reported as part of LP#1990379,
  especially: 
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
  but needs a separate LP bug (number) - this one.
  ___

  The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
  needed some tweaks regarding white-spaces, but then applied fine on focal, 
jammy, kinetic and also  1.2.13, which is what we currently have in 
lunar-proposed.

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


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

[Touch-packages] [Bug 2002511]

[ljavorsk]

Hi Thomas,

This has been already fixed in RHEL-9.2 (BZ#2166501) which has been
shipped already.

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

Title:
  zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Jammy:
  New
Status in zlib source package in Kinetic:
  New
Status in zlib source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
 the patch from LP#1990379, break libxml2 and lxml on s390x.

   * The problem appears during loading a gzipped XML file.

   * Disabling hw compression with 'export DFLTCC=0' solves this,
 hence it's a problem with the hardware acceleration patches DFLTCC.

   * For more info see:
  https://bugzilla.redhat.com/show_bug.cgi?id=2155328

  [ Test Plan ]

   * Steps to Reproduce:
 1. echo "" > file.xml
 2. gzip file.xml
 3. python3
 >>> import libxml2
 >>> libxml2.parseFile("file.xml.gz")

   * Actual results:
 file.xml.gz:1: parser error : Document is empty
 ^
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python3.11/site-packages/libxml2.py",
   line 1362, in parseFile
 if ret is None:raise parserError('xmlParseFile() failed')
^^
 libxml2.parserError: xmlParseFile() failed

   * Expected results:
 Loaded file.

  [ Where problems could occur ]

   * Since this is limited to s390x and DFLTCC / hw acceleration active,
 any possible problems are limited to such environments.

   * Fix can be broken if the state handling (state->wrap),
 or the states mixed.

   * The translation from stream to parameter block could be broken
 (again due to wrong states) and the inflate as well.

  [ Other Info ]

   * The official upstream fix is here:
 https://github.com/zlib-ng/zlib-ng/pull/1390
 but it's for zlib-ng.

   * For zlib this needs to be adjusted and was done by the author here:
 https://launchpadlibrarian.net/641454325/patch-1.2.11

   * And again slightly adjusted by me (renamed, some white-space fixes
 and conversion into a quilt patch with proper dep3 header):
 https://launchpadlibrarian.net/645435847/1390.patch

   * The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
  __

  It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks 
libxml2 (and libxml) on s390x:
  (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch 
should fix the issue.

  The upstream author proposed a fix and a new test for zlib-ng
  (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
  breakages in the future.

  ___

  This was initially reported as part of LP#1990379,
  especially: 
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
  but needs a separate LP bug (number) - this one.
  ___

  The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
  needed some tweaks regarding white-spaces, but then applied fine on focal, 
jammy, kinetic and also  1.2.13, which is what we currently have in 
lunar-proposed.

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


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

[Touch-packages] [Bug 2002511]

[tstaudt]

Hello Lukas,

do we need to open a bug to get this into RHEL 9.3 or will this be propagated 
somehow?
Thanks.

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

Title:
  zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Jammy:
  New
Status in zlib source package in Kinetic:
  New
Status in zlib source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
 the patch from LP#1990379, break libxml2 and lxml on s390x.

   * The problem appears during loading a gzipped XML file.

   * Disabling hw compression with 'export DFLTCC=0' solves this,
 hence it's a problem with the hardware acceleration patches DFLTCC.

   * For more info see:
  https://bugzilla.redhat.com/show_bug.cgi?id=2155328

  [ Test Plan ]

   * Steps to Reproduce:
 1. echo "" > file.xml
 2. gzip file.xml
 3. python3
 >>> import libxml2
 >>> libxml2.parseFile("file.xml.gz")

   * Actual results:
 file.xml.gz:1: parser error : Document is empty
 ^
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python3.11/site-packages/libxml2.py",
   line 1362, in parseFile
 if ret is None:raise parserError('xmlParseFile() failed')
^^
 libxml2.parserError: xmlParseFile() failed

   * Expected results:
 Loaded file.

  [ Where problems could occur ]

   * Since this is limited to s390x and DFLTCC / hw acceleration active,
 any possible problems are limited to such environments.

   * Fix can be broken if the state handling (state->wrap),
 or the states mixed.

   * The translation from stream to parameter block could be broken
 (again due to wrong states) and the inflate as well.

  [ Other Info ]

   * The official upstream fix is here:
 https://github.com/zlib-ng/zlib-ng/pull/1390
 but it's for zlib-ng.

   * For zlib this needs to be adjusted and was done by the author here:
 https://launchpadlibrarian.net/641454325/patch-1.2.11

   * And again slightly adjusted by me (renamed, some white-space fixes
 and conversion into a quilt patch with proper dep3 header):
 https://launchpadlibrarian.net/645435847/1390.patch

   * The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
  __

  It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks 
libxml2 (and libxml) on s390x:
  (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch 
should fix the issue.

  The upstream author proposed a fix and a new test for zlib-ng
  (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
  breakages in the future.

  ___

  This was initially reported as part of LP#1990379,
  especially: 
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
  but needs a separate LP bug (number) - this one.
  ___

  The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
  needed some tweaks regarding white-spaces, but then applied fine on focal, 
jammy, kinetic and also  1.2.13, which is what we currently have in 
lunar-proposed.

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


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

[Touch-packages] [Bug 2002511]

[iii]

Created attachment 1941938
patch for zlib 1.2.11

You can also find this patch at
https://github.com/iii-i/zlib/commits/crc32vx-v5-1.2.11.

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

Title:
  zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Jammy:
  New
Status in zlib source package in Kinetic:
  New
Status in zlib source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
 the patch from LP#1990379, break libxml2 and lxml on s390x.

   * The problem appears during loading a gzipped XML file.

   * Disabling hw compression with 'export DFLTCC=0' solves this,
 hence it's a problem with the hardware acceleration patches DFLTCC.

   * For more info see:
  https://bugzilla.redhat.com/show_bug.cgi?id=2155328

  [ Test Plan ]

   * Steps to Reproduce:
 1. echo "" > file.xml
 2. gzip file.xml
 3. python3
 >>> import libxml2
 >>> libxml2.parseFile("file.xml.gz")

   * Actual results:
 file.xml.gz:1: parser error : Document is empty
 ^
 Traceback (most recent call last):
   File "", line 1, in 
   File "/usr/lib/python3.11/site-packages/libxml2.py",
   line 1362, in parseFile
 if ret is None:raise parserError('xmlParseFile() failed')
^^
 libxml2.parserError: xmlParseFile() failed

   * Expected results:
 Loaded file.

  [ Where problems could occur ]

   * Since this is limited to s390x and DFLTCC / hw acceleration active,
 any possible problems are limited to such environments.

   * Fix can be broken if the state handling (state->wrap),
 or the states mixed.

   * The translation from stream to parameter block could be broken
 (again due to wrong states) and the inflate as well.

  [ Other Info ]

   * The official upstream fix is here:
 https://github.com/zlib-ng/zlib-ng/pull/1390
 but it's for zlib-ng.

   * For zlib this needs to be adjusted and was done by the author here:
 https://launchpadlibrarian.net/641454325/patch-1.2.11

   * And again slightly adjusted by me (renamed, some white-space fixes
 and conversion into a quilt patch with proper dep3 header):
 https://launchpadlibrarian.net/645435847/1390.patch

   * The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
  __

  It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks 
libxml2 (and libxml) on s390x:
  (https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch 
should fix the issue.

  The upstream author proposed a fix and a new test for zlib-ng
  (https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
  breakages in the future.

  ___

  This was initially reported as part of LP#1990379,
  especially: 
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
  but needs a separate LP bug (number) - this one.
  ___

  The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
  needed some tweaks regarding white-spaces, but then applied fine on focal, 
jammy, kinetic and also  1.2.13, which is what we currently have in 
lunar-proposed.

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


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

[Touch-packages] [Bug 1977645] Re: python3-gpg 1.16.0-unknown version is incomparable, dependencies always fail

[Steve Langasek]

Thank you for this report.  Yes, this is the same issue as bug #1991606.
It is a valid bug report; however, as discussed in that bug it's not
clear that addressing this in Ubuntu 22.04 fits our stable release
update policy.  The impact of downloading a second copy of python3-gpg
is pretty minimal - certainly less than the impact of setuptools failing
to work out of the box. This bug has been marked as Importance: Medium,
which seems accurate to me, and would therefore not fit our normal SRU
policy.

I am marking this bug as a duplicate of LP: #1991606.

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

Title:
  python3-gpg 1.16.0-unknown version is incomparable, dependencies
  always fail

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Jammy:
  Triaged
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in gpgme1.0 source package in Lunar:
  Fix Released
Status in gpgme1.0 package in Debian:
  Fix Released

Bug description:
  The python version of the gpgme version contains "unknown" and is
  therefore not PEP440 order compatible.

  See this example:

# pip3 freeze | grep gpg
gpg===1.16.0-unknown

# pip3 install pstore
...
Successfully installed gpg-1.10.0
Successfully installed pstore-2.0.0

# pip3 freeze | grep gpg
gpg==1.10.0

  
  Key takeways from that example:

  - pstore depends on gpg>=1.10

  - 1.16 SHOULD be higher than 1.10

  - pip installs 1.10 even though 1.16 exists

  - the triple-= (gpg===1.16.0-unknown) means that the version exists,
  but cannot be version compared:
  https://peps.python.org/pep-0440/#arbitrary-equality


  Suggested fix:

  - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with
  a '+'; that will compare as expected;

  - fix so "-unknown" isn't appended.

  
  Apparently, this is caused by insufficient fixes in 
0001-avoid-identifying-as-beta.patch

  I've attached a FIXED version, which should fix things.

  Before:

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown.

  After:

$ quilt push 
Applying patch 0001-avoid-identifying-as-beta-FIXED.patch

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0.

  
  Versions:

  $ lsb_release -a 2>/dev/null| grep Codename
  Codename: jammy

  $ apt-cache policy python3-gpg  | grep Installed
Installed: 1.16.0-1.2ubuntu4

  
  Cheers,
  Walter Doekes
  OSSO B.V.

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


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

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Steve Langasek]

Verified (as a consequence of LP: #1977645) that python3-gpg has a
PEP440-compliant version in kinetic and later.

** Changed in: gpgme1.0 (Ubuntu Kinetic)
   Status: New => Fix Released

** Changed in: gpgme1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Incomplete
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 

[Touch-packages] [Bug 1977645] Re: python3-gpg 1.16.0-unknown version is incomparable, dependencies always fail

[Steve Langasek]

** Also affects: gpgme1.0 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: gpgme1.0 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: gpgme1.0 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: gpgme1.0 (Ubuntu Kinetic)
   Status: New => Fix Released

** Changed in: gpgme1.0 (Ubuntu Lunar)
   Status: New => Fix Released

** Changed in: gpgme1.0 (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: gpgme1.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  python3-gpg 1.16.0-unknown version is incomparable, dependencies
  always fail

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Jammy:
  Triaged
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in gpgme1.0 source package in Lunar:
  Fix Released
Status in gpgme1.0 package in Debian:
  Fix Released

Bug description:
  The python version of the gpgme version contains "unknown" and is
  therefore not PEP440 order compatible.

  See this example:

# pip3 freeze | grep gpg
gpg===1.16.0-unknown

# pip3 install pstore
...
Successfully installed gpg-1.10.0
Successfully installed pstore-2.0.0

# pip3 freeze | grep gpg
gpg==1.10.0

  
  Key takeways from that example:

  - pstore depends on gpg>=1.10

  - 1.16 SHOULD be higher than 1.10

  - pip installs 1.10 even though 1.16 exists

  - the triple-= (gpg===1.16.0-unknown) means that the version exists,
  but cannot be version compared:
  https://peps.python.org/pep-0440/#arbitrary-equality


  Suggested fix:

  - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with
  a '+'; that will compare as expected;

  - fix so "-unknown" isn't appended.

  
  Apparently, this is caused by insufficient fixes in 
0001-avoid-identifying-as-beta.patch

  I've attached a FIXED version, which should fix things.

  Before:

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown.

  After:

$ quilt push 
Applying patch 0001-avoid-identifying-as-beta-FIXED.patch

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0.

  
  Versions:

  $ lsb_release -a 2>/dev/null| grep Codename
  Codename: jammy

  $ apt-cache policy python3-gpg  | grep Installed
Installed: 1.16.0-1.2ubuntu4

  
  Cheers,
  Walter Doekes
  OSSO B.V.

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


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

[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets

[Bug Watch Updater]

** Bug watch added: Linux Kernel Bug Tracker #217526
   https://bugzilla.kernel.org/show_bug.cgi?id=217526

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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


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

[Touch-packages] [Bug 1801540]

[haro41]

Done: https://bugzilla.kernel.org/show_bug.cgi?id=217526

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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


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

[Touch-packages] [Bug 1801540]

[tiwai]

For ASUS-specific codec issues, could you open another bug instead of
hanging this old issue?  The AMD controller problem was basically fixed,
and the Realtek codec quirk is a different story.

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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


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

[Touch-packages] [Bug 2022927] Re: Busybox mount fails to mount Snaps

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  Busybox mount fails to mount Snaps

Status in busybox package in Ubuntu:
  New

Bug description:
  Snapd tries to mount squashfs Snaps with non-standard mount flags like
  "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to
  userspace programs that a given mount should not be shown in a list of
  mounted partitions/filesystems. Busybox does not support these flags,
  and so fails with "Invalid argument".

  $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test
  mount: mounting test on /tmp/test failed: Invalid argument

  These flags can likely be be safely ignored, as they don't actually
  affect the functionality of the mount. This goes for all mount options
  starting with "x-", as these generally denote non-standard mount
  option "extensions".

  I've created a patch against Busybox which adds an optional
  configuration item to ignore all mount options beginning with "x-". An
  additional verbose option has also been added to enable the ability to
  report that the mount flags have been ignored, rather than silently
  ignoring them.

  This is a requirement for a customer project, where we are limited to
  using Busybox (due to coreutils' GPL-3.0 licence) but would also
  require using Snaps like checkbox for testing and verification. This
  was posted on the Busybox mailing list a few months ago
  (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html)
  but patch acceptance there seems to take quite a long time, and we
  need this for the customer.

  A PPA containing the patched Busybox version is available on the
  project's Launchpad team: https://launchpad.net/~nemos-
  team/+archive/ubuntu/ppa

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


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

[Touch-packages] [Bug 2022954] [NEW] RDP and VNC fail when headless with no monitor (but work otherwise!)

[TheKorn]

Public bug reported:

Steps to reproduce:

*  Install fresh Ubuntu 22.04.2 LTS
*  Enable RDP and VNC via sharing control panel
*  Test RDP and VNC, verify working
*  Unplug monitor
*  Try RDP.  Authenticate, then connection closed with no display
*  Try VNC.  Authenticate, then connection closed with no display
*  Plug monitor back in
*  Try RDP.  Works!
*  Try VNC.  Works!
*  Unplug monitor
*  Try RDP.  AUthenticate, then connection closed with no display
*  Try VNC.  Authenticate, then connection closed with no display
*  GOTO 10

Symptoms are present with both wayland and X11.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  5 11:02:41 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
   Subsystem: ZOTAC International (MCO) Ltd. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [19da:b301]
InstallationDate: Installed on 2023-06-01 (4 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: ZOTAC ZBOX-CI323NANO
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_j45abz@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_j45abz ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2019
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B301P027
dmi.board.asset.tag: N/A
dmi.board.name: ZBOX-CI323NANO
dmi.board.vendor: ZOTAC
dmi.board.version: XX
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB301P027:bd09/11/2019:br5.11:svnZOTAC:pnZBOX-CI323NANO:pvrXX:rvnZOTAC:rnZBOX-CI323NANO:rvrXX:cvnDefaultstring:ct3:cvrDefaultstring:skuN/A:
dmi.product.family: N/A
dmi.product.name: ZBOX-CI323NANO
dmi.product.sku: N/A
dmi.product.version: XX
dmi.sys.vendor: ZOTAC
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  RDP and VNC fail when headless with no monitor (but work otherwise!)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  *  Install fresh Ubuntu 22.04.2 LTS
  *  Enable RDP and VNC via sharing control panel
  *  Test RDP and VNC, verify working
  *  Unplug monitor
  *  Try RDP.  Authenticate, then connection closed with no display
  *  Try VNC.  Authenticate, then connection closed with no display
  *  Plug monitor back in
  *  Try RDP.  Works!
  *  Try VNC.  Works!
  *  Unplug monitor
  *  Try RDP.  AUthenticate, then connection closed with no display
  *  Try VNC.  Authenticate, then connection closed with no display
  *  GOTO 10

  Symptoms are present with both wayland and X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  5 11:02:41 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) 

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

[Valentijn Sessink]

Here is one made for the very purpose of (not) being clickable.

** Attachment added: "evince-test.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5677900/+files/evince-test.pdf

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Incomplete
Status in evince package in Debian:
  New

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

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

[Steve Langasek]

Georgia, as noted in comment #31, it's better to use '#include if
exists' than to add a versioned dependency on apparmor.  Can you update
the patches to do this and verify that it works as expected?  Once this
is done please resubscribe ~ubuntu-sponsors and we can get this done.

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

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Incomplete
Status in evince package in Debian:
  New

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

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

[Steve Langasek]

Found one locally that doesn't contain any confidential information, so
attaching

** Attachment added: "invoice.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5677898/+files/invoice.pdf

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Confirmed
Status in evince package in Debian:
  New

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately

[Steve Langasek]

Please address Julian's feedback in
https://code.launchpad.net/~macg3/ubuntu/+source/gdebi/+git/gdebi/+merge/414211
and then subscribe ~ubuntu-sponsors again.

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

Title:
  gdebi-gtk calls pkexec inappropriately

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Have Ubuntu with gdebi-gtk installed
  2. Open Firefox
  3. Visit some site with deb-package download link or use direct link like 
https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb
  4. Proceed with file downloading
  5. In Firefox select Library → Downloads, click on downloaded deb-file

  Expected results:
  * gdebi-gtk is opened, the package installs normally after users clicks 
Install button

  Actual results:
  * gdebi-gtk is opened, the package is not installed because of vanishing of 
gdebi-gtk window just after clicking Install button


  

  Before anyone says this bug already exists... it doesn't (at least as
  far as I can see).  It's just that a lot of similar bugs do/did exist
  where people have also experienced the same symptoms (of gdebi-gtk
  vanishing upon clicking 'Install').

  So yes this is the same symptoms, but it must be a different cause as
  the circumstances are different and doesn't have the same resolution.

  The meat of it...

  Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or 
with Chrome if you installed that) go to any site that offers a .deb package 
and either...
  a) choose to open it directly from the browser (rather than saving it to 
'Downloads' folder)
  b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that 
file from within the browser itself.

  You should find that gdebi-gtk appears but vanishes the moment you
  click 'Install' without a prompt for a password, an explanation or the
  package actually getting installed.

  This bug has existed since the beginning of Ubuntu 18.04 however it's
  been largely confused with other similar bugs.  I've had it on half a
  dozen machines and confirmed it exists with IRC users on #ubuntu-mate
  of freenode.

  However with *this* bug (compared to others) gdebi-gtk works perfectly
  fine if you run it from the terminal or just double click the .deb
  package from your file manager.

  It's the kind of bug which if you're a hardened desktop Linux user,
  you'd just work around it...

  But if you're a novice and you can't get a simple thing like
  Teamviewer installed (which is a .deb, and a thing I might ask someone
  to do over the phone to try to help them) you likely get fed up and
  re-install Windows :S

  Any input on this would be brilliant as I can't seem to get any
  logs/output.

  ~lantizia

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


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

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

[Steve Langasek]

Can someone provide a reference PDF showing this issue, to use in the
SRU verification?  (They are common, but we shouldn't have to hunt for
one for the verification)

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Confirmed
Status in evince package in Debian:
  New

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Touch-packages] [Bug 2022836] Re: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de erro

[Benjamin Drung]

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

The issue is that /var/cache/debconf/config.dat is locked by another
process. Can you retry the package update? In case it is still locked,
can you retry after a reboot?

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

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

Title:
  package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el
  subproceso instalado paquete tzdata script post-installation devolvió
  el código de salida de error 1

Status in tzdata package in Ubuntu:
  Incomplete

Bug description:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: tzdata 2023c-0ubuntu0.22.04.2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jun  3 13:13:18 2023
  ErrorMessage: el subproceso instalado paquete tzdata script post-installation 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2022-09-28 (247 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: tzdata
  Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el 
subproceso instalado paquete tzdata script post-installation devolvió el código 
de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface

[Benjamin Drung]

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

** This bug has been marked a duplicate of bug 1993541
   initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' 
sysfs interface

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

Title:
  initramfs need to mount efivarfs because kernel 6.0 deprecated
  'efivars' sysfs interface

Status in OEM Priority Project:
  Invalid
Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC
  RAID, mdadm needs initramfs to mount efivarfs instead.

  [1] The commit:
  commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741
  Author: Ard Biesheuvel 
  Date: Mon Jun 20 13:34:03 2022 +0200

  efi: vars: Remove deprecated 'efivars' sysfs interface

  [ Test Plan ]

  1. Install initramfs-tools
  2. update-initramfs -u
  3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs
  4. Check if boot script 00_mount_efivarfs exists in directory 
/tmp/extract-initramfs/main/scripts/init-top/
  5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot 
script 00_mount_efivarfs will be execute before udev.

  [ Where problems could occur ]

  Not sure if there any other tools/utilities also need to mount efivarfs as 
early as mdadm but the probability of file conflict should be very low.
  Also, there are no impact mounting efivarfs multiple times.
  mount: /sys/firmware/efi/efivars: efivarfs already mounted on 
/sys/firmware/efi/efivars.

  [ Scope ]

  Jammy, Kinetic

  [ Other Info ]

  The private bug link
  https://bugs.launchpad.net/somerville/+bug/1990231

  debian MR:
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994936/+subscriptions


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

[Touch-packages] [Bug 1489979] Re: initiramfs-tools: configure_network retry indefinitely option

[Benjamin Drung]

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

Please submit the change to Debian so that we do not need to carry
another change in Ubuntu only. One way to submit it is to open a merge
request on https://salsa.debian.org/kernel-team/initramfs-
tools/-/merge_requests

To make the patch more flexible, the command line option could allow
setting the timeout duration or retry count.

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

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

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

Title:
  initiramfs-tools: configure_network retry indefinitely option

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  initramfs network booting by default fails after a fixed number of
  attempts/timeout to configure the network. For example, in an
  automation environment with heavy DHCP usage, a system will give up
  trying to get a DHCP lease after 265 seconds. This will require manual
  intervention or a hardware watchdog to power-cycle the system in order
  to retry getting a DHCP lease.

  This patch for Ubuntu 12.04 LTS adds a notimeout kernel command line
  for casper that tells configure_network to instead retry indefinitely
  with an increasing retry interval.

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


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

[Touch-packages] [Bug 2008763] Re: mkinitramfs reproducible fonts uuid

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. I can the /var/cache/fontconfig files in the initrd on
Ubuntu 23.04 as well:

```
$ lsinitramfs /boot/initrd.img | grep -i font
etc/fonts
etc/fonts/conf.d
etc/fonts/conf.d/60-latin.conf
etc/fonts/fonts.conf
usr/bin/setfont
usr/bin/loadfont
usr/lib/x86_64-linux-gnu/libfontconfig.so.1
usr/lib/x86_64-linux-gnu/libfontconfig.so.1.12.0
usr/local/share/fonts
usr/share/fonts
usr/share/fonts/truetype
usr/share/fonts/truetype/ubuntu
usr/share/fonts/truetype/ubuntu/UbuntuMono-Italic[wght].ttf
usr/share/fonts/truetype/ubuntu/UbuntuMono[wght].ttf
usr/share/fonts/truetype/ubuntu/Ubuntu[wdth,wght].ttf
var/cache/fontconfig
var/cache/fontconfig/2300eef321c393bfd76478a5c0e95b23-le64.cache-8
var/cache/fontconfig/3830d5c3ddfd5cd38a049b759396e72e-le64.cache-8
var/cache/fontconfig/4c599c202bc5c08e2d34565a40eac3b2-le64.cache-8
var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-8
var/cache/fontconfig/CACHEDIR.TAG
```

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

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

Title:
  mkinitramfs reproducible fonts uuid

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Dear all,

  I am trying to do some reproducible builds of the daily isos and
  noticed that in chroot with a daily xubuntu Jammy iso mkinitramfs
  fails to create a reproducible initrd by setting random uuid's and
  filenames in the initrd:

  main/usr/share/fonts/.uuid
  main/usr/share/fonts/truetype/.uuid
  main/usr/share/fonts/truetype/ubuntu/.uuid

  main/usr/local/share/fonts/.uuid

  main/var/cache/fontconfig/***random-file-names***

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


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

[Touch-packages] [Bug 1999881] Re: unmkinitramfs fails with symlinked zstd compressed initrds

[Benjamin Drung]

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

I tried to reproduce this behavior in a Ubuntu 22.04 VM (initramfs-tools
0.140ubuntu13.1, zstd 1.4.8+dfsg-3build1), but `lsinitramfs
/boot/initrd.img` worked. Can you still reproduce the failure?

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

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

Title:
  unmkinitramfs fails with symlinked zstd compressed initrds

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * Cannot unpack zstd compressed initrds when accessed through a
  symbolic link

  [Test Case]

  $ grep COMPRESS= /etc/initramfs-tools/initramfs.conf
  COMPRESS=zstd
  # This is the default

  $ stat -c '%F %N' /boot/initrd.img*
  symbolic link '/boot/initrd.img' -> 'initrd.img-5.15.0-53-generic'
  regular file '/boot/initrd.img-5.15.0-53-generic'

  $ lsinitramfs /boot/initrd.img-5.15.0-53-generic
  ... works as expected ...

  $ lsinitramfs /boot/initrd.img
  cpio: premature end of archive

  [Regression Potential]

   * Ubuntu Jammy changes the default compression scheme for the initrd
  from lz4 to zstd. Unpacking lz4 initrds had already been fixed by
  https://bugs.launchpad.net/ubuntu/cosmic/+source/initramfs-
  tools/+bug/1832108 but unpacking zstd initrds works as expected when
  directly accessing the file. However, it fails when accessing it
  through a symbolic link.

  [Other Info]

  A fix proposal is attached.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  $ dpkg-query -W initramfs-tools
  initramfs-tools   0.140ubuntu13

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


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

[Touch-packages] [Bug 2022928] [NEW] package libdca0:amd64 0.0.7-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Mohit Kumar Rohatgi]

Public bug reported:

i cant install any package from store

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libdca0:amd64 0.0.7-2
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg
CasperMD5CheckResult: fail
Date: Mon Jun  5 18:23:05 2023
DpkgTerminalLog:
 dpkg: error processing package libdca0:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2023-06-01 (3 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.9
SourcePackage: libdca
Title: package libdca0:amd64 0.0.7-2 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package libdca0:amd64 0.0.7-2 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libdca package in Ubuntu:
  New

Bug description:
  i cant install any package from store

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libdca0:amd64 0.0.7-2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg
  CasperMD5CheckResult: fail
  Date: Mon Jun  5 18:23:05 2023
  DpkgTerminalLog:
   dpkg: error processing package libdca0:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2023-06-01 (3 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: libdca
  Title: package libdca0:amd64 0.0.7-2 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1899019] Re: Typo in UDisks action

[Launchpad Bug Tracker]

This bug was fixed in the package policykit-desktop-privileges - 0.22

---
policykit-desktop-privileges (0.22) mantic; urgency=medium

  * Include a .rules in the new javascript format for newer polkitd
  * Remove old legacy udisks1 actions (lp: #1899019)
  * Remove the network manager system connection override
there is a similar entry included in the network-manager package
  * Update copyright, debhelper and standards version
  * Remove old breaks, update for the new polkitd binary naming

 -- Sebastien Bacher   Mon, 05 Jun 2023 11:58:29
+0200

** Changed in: policykit-desktop-privileges (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  Typo in UDisks action

Status in policykit-desktop-privileges package in Ubuntu:
  Fix Released

Bug description:
  It appears that com.ubuntu.desktop.pkla contains a typo in the UDisks
  section:

  [Mounting, checking, etc. of internal drives]
  Identity=unix-group:admin;unix-group:sudo
  
Action=org.freedesktop.udisks.filesystem-*;org.freedesktop.udisks.drive-ata-smart*;org.freedesktop.udisks2.filesystem-mount-system;org.freedesktop.udisks2.encrypted-unlock-system;org.freedesktop.udisks2.filesystem-fstab;
  ResultActive=yes

  Notice that the first two actions contain the string "udisks", rather
  than "udisks2", which appears to be a typo.

  However, the typo is actually a lucky accident because it is
  preventing a vulnerability in UDisks from being exploited. The
  vulnerable code in UDisks is protected by the
  `org.freedesktop.udisks2.filesystem-take-ownership` polkit action, so
  it will become accessible if the typo is fixed. I have separately
  reported the UDisks vulnerability to the maintainers of UDisks. I have
  attached a copy of that report for your information.

  I would recommend removing the first two actions from this file. Since
  they don't currently work, presumably nobody will miss them if they
  are removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1899019/+subscriptions


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

[Touch-packages] [Bug 2022927] [NEW] Busybox mount fails to mount Snaps

[Isaac True]

Public bug reported:

Snapd tries to mount squashfs Snaps with non-standard mount flags like
"x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to
userspace programs that a given mount should not be shown in a list of
mounted partitions/filesystems. Busybox does not support these flags,
and so fails with "Invalid argument".

$ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test
mount: mounting test on /tmp/test failed: Invalid argument

These flags can likely be be safely ignored, as they don't actually
affect the functionality of the mount. This goes for all mount options
starting with "x-", as these generally denote non-standard mount option
"extensions".

I've created a patch against Busybox which adds an optional
configuration item to ignore all mount options beginning with "x-". An
additional verbose option has also been added to enable the ability to
report that the mount flags have been ignored, rather than silently
ignoring them.

This is a requirement for a customer project, where we are limited to
using Busybox (due to coreutils' GPL-3.0 licence) but would also require
using Snaps like checkbox for testing and verification. This was posted
on the Busybox mailing list a few months ago
(http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but
patch acceptance there seems to take quite a long time, and we need this
for the customer.

A PPA containing the patched Busybox version is available on the
project's Launchpad team: https://launchpad.net/~nemos-
team/+archive/ubuntu/ppa

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

** Patch added: "busybox-1.35.0-4ubuntu1ppa5.debdiff"
   
https://bugs.launchpad.net/bugs/2022927/+attachment/5677880/+files/busybox-1.35.0-4ubuntu1ppa5.debdiff

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

Title:
  Busybox mount fails to mount Snaps

Status in busybox package in Ubuntu:
  New

Bug description:
  Snapd tries to mount squashfs Snaps with non-standard mount flags like
  "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to
  userspace programs that a given mount should not be shown in a list of
  mounted partitions/filesystems. Busybox does not support these flags,
  and so fails with "Invalid argument".

  $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test
  mount: mounting test on /tmp/test failed: Invalid argument

  These flags can likely be be safely ignored, as they don't actually
  affect the functionality of the mount. This goes for all mount options
  starting with "x-", as these generally denote non-standard mount
  option "extensions".

  I've created a patch against Busybox which adds an optional
  configuration item to ignore all mount options beginning with "x-". An
  additional verbose option has also been added to enable the ability to
  report that the mount flags have been ignored, rather than silently
  ignoring them.

  This is a requirement for a customer project, where we are limited to
  using Busybox (due to coreutils' GPL-3.0 licence) but would also
  require using Snaps like checkbox for testing and verification. This
  was posted on the Busybox mailing list a few months ago
  (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html)
  but patch acceptance there seems to take quite a long time, and we
  need this for the customer.

  A PPA containing the patched Busybox version is available on the
  project's Launchpad team: https://launchpad.net/~nemos-
  team/+archive/ubuntu/ppa

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


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

[Touch-packages] [Bug 2022899] Re: apport-gtk does not offer to show details of crash

[Benjamin Drung]

You can run `ubuntu-bug` on the command line and specify a .crash from
from `/var/crash` (e.g. `ubuntu-bug
/var/crash/_usr_lib_xorg_Xorg.0.crash`).

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

Title:
  apport-gtk does not offer to show details of crash

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  "Show Details" option missing in apport-gtk

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 
+0200:2023-06-05 09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun  5 09:51:17 2023
  InstallationDate: Installed on 2023-06-03 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.38.1-5ubuntu2

---
util-linux (2.38.1-5ubuntu2) mantic; urgency=medium

  * d/p/ubuntu/lp-2019856-add-missing-arm-cores.patch:
Add missing ARM cores for NVIDIA Grace (LP: #2019856)

 -- Mauricio Faria de Oliveira   Tue, 23 May 2023
15:55:47 -0300

** Changed in: util-linux (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  In Progress
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

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


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

[Touch-packages] [Bug 1968857] Re: Upgrading to jammy leaves obsolete conffiles

[Sebastien Bacher]

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

Title:
  Upgrading to jammy leaves obsolete conffiles

Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  Hi,

  after upgrading my system from impish to jammy, it is left with the
  following obsolete conffiles:

  $ dpkg-query -W -f='${Conffiles}\n' | grep obsolete
   /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf 
c4dbd2117c52f367f1e8b8c229686b10 obsolete
   /etc/polkit-1/localauthority.conf.d/50-localauthority.conf 
2adb9d174807b0a3521fabf03792fbc8 obsolete
   /etc/pam.d/polkit-1 7c794427f656539b0d4659b030904fe0 obsolete

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: polkitd 0.105-33
  Uname: Linux 5.17.2-051702-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Apr 13 10:58:03 2022
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago)
  modified.conffile..etc.pam.d.polkit-1: [deleted]
  modified.conffile..etc.polkit-1.localauthority.conf.d.50-localauthority.conf: 
[deleted]
  modified.conffile..etc.polkit-1.localauthority.conf.d.51-ubuntu-admin.conf: 
[deleted]

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


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

[Touch-packages] [Bug 2022916] Re: gdbusconnection: Explicitly destroy an idle source on cleanup

[Bug Watch Updater]

** Changed in: glib
   Status: Unknown => New

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

Title:
  gdbusconnection: Explicitly destroy an idle source on cleanup

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu Touch we run into regular unit test freezes of lomiri-app-
  launch (formerly known as ubuntu-app-launch) based on some race time
  conditions (number of CPUs to build/test on, CPU speed, etc.).

  As it turned out, the game changer is a commit in glib2.0 upstream:
  
https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17

  It would be super-cool to see this commit applied on top of glib2.0 in
  Ubuntu focal and Ubuntu jammy.

  Thanks+Greets,
  Mike (aka sunweaver @ Debian, working for the UBports core dev team these 
days)

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


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

[Touch-packages] [Bug 2022899] Re: apport-gtk does not offer to show details of crash

[jonas]

Some more info;

The LightDM install I use with slick-greeter & customize with the 
lightdm-settings package works now.
It did throw a lot of apport issues before I got it working, so that would be a 
potential source of my recent troubles.

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

Title:
  apport-gtk does not offer to show details of crash

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  "Show Details" option missing in apport-gtk

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 
+0200:2023-06-05 09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun  5 09:51:17 2023
  InstallationDate: Installed on 2023-06-03 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2022899] Re: apport-gtk does not offer to show details of crash

[jonas]

Thanks Benjamin,

I'll let you know as soon as another apport-gtk window without the "show
details" button surfaces.

Not sure if it's relevant, but I'm using the ubunut-budgie flavor of
22.04 on an Asus Vivobook;

description: Computer
width: 64 bits
capabilities: smp vsyscall32
  *-core
   description: Motherboard
   physical id: 0
 *-memory
  description: System memory
  physical id: 0
  size: 7680MiB
 *-cpu
  product: AMD Ryzen 5 4600H with Radeon Graphics
  vendor: Advanced Micro Devices [AMD]
  physical id: 1
  bus info: cpu@0
  version: 23.96.1
  size: 1773MHz
  capacity: 4004MHz
  width: 64 bits
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx 
mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc 
cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 
sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic 
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext 
perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate 
ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed 
adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc 
cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru 
wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid 
decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl 
umip rdpid overflow_recov succor smca cpufreq
  configuration: microcode=140509446

Cheers,
jonas

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

Title:
  apport-gtk does not offer to show details of crash

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  "Show Details" option missing in apport-gtk

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 
+0200:2023-06-05 09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun  5 09:51:17 2023
  InstallationDate: Installed on 2023-06-03 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1990824] Re: initramfs-tools: out-of-memory failures during autopkgtest

[Benjamin Drung]

I checked all failing autopkgtests on mantic and the most recent ones on
lunar. I only saw the `net` autopkgtest fail (which use 512 MB). So only
512 MB was too small, but 1 GB was enough recently.

0.142ubuntu3 ported the net autopkgtest to the common test framework and
uses 1 GB now. I am marking it as fixed released due to the 0.142ubuntu3
upload. Please reopen this bug in case this version starts to have
failing autopkgtest or in case you disagree that 1 GB is enough.

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

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

Title:
  initramfs-tools: out-of-memory failures during autopkgtest

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Some autopkgtest tests are failing due to out-of-memory conditions,
  especially amd64-ata-only and net.

  It seems that we are creating a VM with 1GB only to run the amd64-ata-
  only test and even just 512MB for the net test.

  It probably makes sense to create larger VMs (at least 2GB) to run
  these tests with a more recent kernels (that will likely require a
  little more RAM).

  [Test case]

  sudo autopkgtest . -- null

  [Fix]

  Increase memory size of instances used to run the autopkgtests to 2GB.

  [Regression potential]

  We may experience regressions in small cloud instances, or systems
  with less than 2GB or RAM that are using a recent kernel (but this is
  more a generic potential regression, not strictly related to
  initramfs-tools).

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


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

[Touch-packages] [Bug 2022916] Re: gdbusconnection: Explicitly destroy an idle source on cleanup

[Sebastien Bacher]

Hey Mike. While I understand that the issue is annoying there is always
risk in doing change to a library of the base system as libglib and
difficult to verify that there are not side effect of any of the
software using it. If there is no real user visible impact the benefit
is probably not worth the risk and effort for Ubuntu. Perhaps you could
set up a ppa or local env for your CI including the fix instead?

I'm closing the bug since the issue is fixed in the current version, it
doesn't prevent us to target older series if we decide to go the SRU way

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2925
   https://gitlab.gnome.org/GNOME/glib/-/issues/2925

** Also affects: glib via
   https://gitlab.gnome.org/GNOME/glib/-/issues/2925
   Importance: Unknown
   Status: Unknown

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

Title:
  gdbusconnection: Explicitly destroy an idle source on cleanup

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu Touch we run into regular unit test freezes of lomiri-app-
  launch (formerly known as ubuntu-app-launch) based on some race time
  conditions (number of CPUs to build/test on, CPU speed, etc.).

  As it turned out, the game changer is a commit in glib2.0 upstream:
  
https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17

  It would be super-cool to see this commit applied on top of glib2.0 in
  Ubuntu focal and Ubuntu jammy.

  Thanks+Greets,
  Mike (aka sunweaver @ Debian, working for the UBports core dev team these 
days)

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


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

[Touch-packages] [Bug 1969901] Re: network-manager fails to renew ipv6 address

[Julian Andres Klode]

Ubuntu 18.04 has reached it's end of standard support, hence marking
won't fix.

** Changed in: network-manager (Ubuntu Bionic)
   Status: Triaged => Won't Fix

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

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

   * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.

   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.

   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on 1.10.6):
     
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f

   * Upstream bug:
     https://bugzilla.gnome.org/show_bug.cgi?id=783391

  [Test Plan]

  The test requires three computers
  * one computer runing isc dhcpd server (with network configured static)
  * one computer running patched network manager
  * one computer running vanilla ubuntu

  The idea is to execute on an isolated network and trigger the error by 
changing
  ip range handed out by the dhcp-server to force a nack response back to the
  clients.

  Expected result
  * patched network keeps dhclient6 alive
  * vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted

  ON THE SERVER
  # Disable app-armor, as it has rules restricting dhcpd
  aa-teardown

  # install isc dhcpserver
  isc-dhcp-server

  # configure network static
  sudo nmcli connection modify "${CONNECTION_NAME}" \
   ipv4.method "manual" \
   ipv4.addresses "192.168.1.1/24" \
   ipv4.gateway "192.168.1.254" \
   ipv4.dns "192.168.1.1" \
   ipv6.method "manual" \
   ipv6.addresses "2001:db8:0:1::1/64" \
   ipv6.gateway "2001:db8:0:1::ffbb" \
   ipv6.dns "2001:db8:0:1::1/64"

  mkdir -p tmp
  touch tmp/dhcpd4_a.leases
  touch tmp/dhcpd4_b.leases
  touch tmp/dhcpd6_a.leases
  touch tmp/dhcpd6_b.leases

  Then it is time to execute dhcpd
  -f - run in foreground
  -d - print errors to stderr instead of syslog

  # Start in separate terminals
  dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6

  Press ctrl-C to kill servers, then restart with the b configurations

  dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6

  Then leases to expire (check for clients that kills dhclient)
  Press ctrl-C to kill servers, then restart with the a configurations

  ON THE CLIENTS
  Setup:
  Configure ipv6 network in settings to use dhcp (using the gui)

  Test:
  check that dhcp clients are still running:
  ps aux|grep dhclient

  Expected in output
  one client for dhcpv4
  one client for dhcpv6

  Also check network manager status :
  journalctl -u NetworkManager.service
  journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
  journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4

  if dhclient is not running:
  stop network in gui
  remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the 
lease for the client not running.
  start network in gui

  if dhclients are running:
  wait additional ten minutes, repeat from beginning of test

  [Where problems could occur]

   * The change is in the dchp lease expiration handling so verify that
  there is no regression in dhcp renewals on different type of
  configuration include IPv6

  [Other Info]
   * We have tested this patch on a couple of clients where we have seen this
     this problem. If this patch is feasible to include in Ubuntu 18.04 we
     could request more users to test.

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


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

[Touch-packages] [Bug 1964763] Re: QtChooser doesn't support qt6

[Julian Andres Klode]

The reasoning for rejection on the Debian side seems valid, and since
that's a universe package maintained by the community it's best left
that way.

** Changed in: qtchooser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Won't Fix

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

[Touch-packages] [Bug 2022899] Re: apport-gtk does not offer to show details of crash

[Benjamin Drung]

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

I failed to reproduce the missing "Show Details" option in a Ubuntu
22.04 VM with your installed apport packages. I checked the code to see
if this button is conditionally hidden but I found nothing relevant in
this regard.

Can you state how to reproduce it? What command did you use? What did
you click? Can you reproduce it? Maybe add a screenshot.

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

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

Title:
  apport-gtk does not offer to show details of crash

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  "Show Details" option missing in apport-gtk

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 
+0200:2023-06-05 09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun  5 09:51:17 2023
  InstallationDate: Installed on 2023-06-03 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2022916] [NEW] gdbusconnection: Explicitly destroy an idle source on cleanup

[Mike Gabriel]

Public bug reported:

In Ubuntu Touch we run into regular unit test freezes of lomiri-app-
launch (formerly known as ubuntu-app-launch) based on some race time
conditions (number of CPUs to build/test on, CPU speed, etc.).

As it turned out, the game changer is a commit in glib2.0 upstream:
https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17

It would be super-cool to see this commit applied on top of glib2.0 in
Ubuntu focal and Ubuntu jammy.

Thanks+Greets,
Mike (aka sunweaver @ Debian, working for the UBports core dev team these days)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch-accepted-upstream

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

Title:
  gdbusconnection: Explicitly destroy an idle source on cleanup

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  In Ubuntu Touch we run into regular unit test freezes of lomiri-app-
  launch (formerly known as ubuntu-app-launch) based on some race time
  conditions (number of CPUs to build/test on, CPU speed, etc.).

  As it turned out, the game changer is a commit in glib2.0 upstream:
  
https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17

  It would be super-cool to see this commit applied on top of glib2.0 in
  Ubuntu focal and Ubuntu jammy.

  Thanks+Greets,
  Mike (aka sunweaver @ Debian, working for the UBports core dev team these 
days)

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


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

[Touch-packages] [Bug 2022916] Re: gdbusconnection: Explicitly destroy an idle source on cleanup

[Mike Gabriel]

See UT issue discussion here:
https://gitlab.com/ubports/development/core/lomiri-app-
launch/-/merge_requests/49

** Tags added: patch-accepted-upstream

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

Title:
  gdbusconnection: Explicitly destroy an idle source on cleanup

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  In Ubuntu Touch we run into regular unit test freezes of lomiri-app-
  launch (formerly known as ubuntu-app-launch) based on some race time
  conditions (number of CPUs to build/test on, CPU speed, etc.).

  As it turned out, the game changer is a commit in glib2.0 upstream:
  
https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17

  It would be super-cool to see this commit applied on top of glib2.0 in
  Ubuntu focal and Ubuntu jammy.

  Thanks+Greets,
  Mike (aka sunweaver @ Debian, working for the UBports core dev team these 
days)

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


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

[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore

[Łukasz Zemczak]

Hello Marian, or anyone else affected,

Accepted libheif into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libheif/1.14.2-1ubuntu1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libheif (Ubuntu Lunar)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  Cannot open HEIF/HEIC images in 23.04/lunar anymore

Status in eog package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in libheif package in Ubuntu:
  Fix Released
Status in eog source package in Lunar:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Invalid
Status in libheif source package in Lunar:
  Fix Committed

Bug description:
  * Impact

  The libheif loader is bailing out due to a missing plugin directory
  which leads to image viewer as eog not being able to open pictures in
  that format anymore

  * Testcase

  Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in
  eog

  * Where problems could occur

  The package build is using the option to not split the codec in
  separate plugins but the version of Lunar doesn't handle the missing
  plugins directory and bails out. The code of the version in mantic has
  been refactored in a way which fixes this problem. For lunar it's
  easier to just create the directory. The directory is included in the
  libheif1 binary but that should not create any conflict, it's a
  temporary situation for lunar only and even if the soname changed dpkg
  allows for several deb packages to provide the same directory.

  --


  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.

  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC

  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  eog then shows "Could not load image “IMG_9996.HEIC”. Image loading
  failed."

  gpicview even crashes immediately:
  $ gpicview IMG_9996.HEIC
  Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module"

  ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin
  directory.

  ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory.
  Segmentation fault (core dumped)

  The problem concerns all HEIF/HEIC images I tested.

  The installed versions of the (possibly) relevant packages are:
  libheif1: 1.14.2-1
  heif-gdk-pixbuf: 1.14.2-1
  libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1
  eog: 44.0-1
  gpicview: 0.2.5-3build1

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


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

[Touch-packages] [Bug 2022899] [NEW] apport-gtk does not offer to show details of crash

[jonas]

Public bug reported:

"Show Details" option missing in apport-gtk

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport-gtk 2.20.11-0ubuntu82.5
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 +0200:2023-06-05 
09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
CurrentDesktop: Budgie:GNOME
Date: Mon Jun  5 09:51:17 2023
InstallationDate: Installed on 2023-06-03 (1 days ago)
InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  apport-gtk does not offer to show details of crash

Status in apport package in Ubuntu:
  New

Bug description:
  "Show Details" option missing in apport-gtk

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:125:4075240:2023-06-05 09:45:58.006581182 
+0200:2023-06-05 09:45:58.010581202 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun  5 09:51:17 2023
  InstallationDate: Installed on 2023-06-03 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2022880] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023

[Chris Guiver]

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

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

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

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

I'm marking this as duplicate of
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2022879 as it
appears to be the same report just filed against a different package
(If this impacts both when pipewire & alsa are being used; both packages
are possibly not involved but it's a common package like linux kernel)


** This bug has been marked a duplicate of bug 2022879
   No sound from Woofer speaker of Asus Zephyrus G14 2023

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

Title:
   No sound from Woofer speaker of Asus Zephyrus G14 2023

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter
  speaker. The woofer speaker does not produce any sound at all on
  either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  Uname: Linux 6.3.5-060305-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  surfer12877 F wireplumber
   /dev/snd/controlC1:  surfer12877 F wireplumber
   /dev/snd/controlC0:  surfer12877 F wireplumber
   /dev/snd/seq:surfer12875 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Jun  5 12:47:29 2023
  InstallationDate: Installed on 2023-05-31 (4 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 5.29
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: GA402XV.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA402XV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.39
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: "ROG Zephyrus G14"
  dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2022881] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023

[Chris Guiver]

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

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

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


I'm marking this bug invalid, as it appears a duplicate of 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022880


** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
   No sound from Woofer speaker of Asus Zephyrus G14 2023

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter
  speaker. The woofer speaker does not produce any sound at all on
  either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations

  1)
  ┌─[surfer@M5-RGV]-[~]
  └──╼ $lsb_release -rd
  No LSB modules are available.
  Description: Ubuntu 23.04
  Release: 23.04
  )
  2)
  ┌─[surfer@M5-RGV]-[~]
  └──╼ $apt-cache policy pipewire
  pipewire:
Installed: 0.3.65-3
Candidate: 0.3.65-3
Version table:
   *** 0.3.65-3 500
  500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  3) The Woofer/rear speaker should produce sound

  4) Sound only comes from the pair of tweeter speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  Uname: Linux 6.3.5-060305-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  surfer12877 F wireplumber
   /dev/snd/controlC1:  surfer12877 F wireplumber
   /dev/snd/controlC0:  surfer12877 F wireplumber
   /dev/snd/seq:surfer12875 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Jun  5 12:47:29 2023
  InstallationDate: Installed on 2023-05-31 (4 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 5.29
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: GA402XV.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA402XV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.39
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: "ROG Zephyrus G14"
  dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Timo Aaltonen]

forget about those test failures, they're flaky by nature

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 2022881] [NEW] No sound from Woofer speaker of Asus Zephyrus G14 2023

[Mohammad Ikhsan]

Public bug reported:

On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter
speaker. The woofer speaker does not produce any sound at all on either
on Analog Stereo, Analog Surround 4.0, or 2.1 configurations

1)
┌─[surfer@M5-RGV]-[~]
└──╼ $lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.04
Release: 23.04
)
2)
┌─[surfer@M5-RGV]-[~]
└──╼ $apt-cache policy pipewire
pipewire:
  Installed: 0.3.65-3
  Candidate: 0.3.65-3
  Version table:
 *** 0.3.65-3 500
500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
100 /var/lib/dpkg/status

3) The Woofer/rear speaker should produce sound

4) Sound only comes from the pair of tweeter speaker

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
Uname: Linux 6.3.5-060305-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  surfer12877 F wireplumber
 /dev/snd/controlC1:  surfer12877 F wireplumber
 /dev/snd/controlC0:  surfer12877 F wireplumber
 /dev/snd/seq:surfer12875 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Mon Jun  5 12:47:29 2023
InstallationDate: Installed on 2023-05-31 (4 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2023
dmi.bios.release: 5.29
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: GA402XV.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GA402XV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.39
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: "ROG Zephyrus G14"
dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar wayland-session

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

Title:
   No sound from Woofer speaker of Asus Zephyrus G14 2023

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter
  speaker. The woofer speaker does not produce any sound at all on
  either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations

  1)
  ┌─[surfer@M5-RGV]-[~]
  └──╼ $lsb_release -rd
  No LSB modules are available.
  Description: Ubuntu 23.04
  Release: 23.04
  )
  2)
  ┌─[surfer@M5-RGV]-[~]
  └──╼ $apt-cache policy pipewire
  pipewire:
Installed: 0.3.65-3
Candidate: 0.3.65-3
Version table:
   *** 0.3.65-3 500
  500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  3) The Woofer/rear speaker should produce sound

  4) Sound only comes from the pair of tweeter speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  Uname: Linux 6.3.5-060305-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  surfer12877 F wireplumber
   /dev/snd/controlC1:  surfer12877 F wireplumber
   /dev/snd/controlC0:  surfer12877 F wireplumber
   /dev/snd/seq:surfer12875 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Jun  5 12:47:29 2023
  InstallationDate: Installed on 2023-05-31 (4 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 5.29
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: GA402XV.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA402XV