[Touch-packages] [Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus

[Jeremy Bícha]

This is mostly fixed in the next development release of Ubuntu. Ubuntu
23.04 is not a Long Term Support release but will be released in April.

I am leaving this issue open because although the thumbnails are larger
now, I don't see a way to change the thumbnail size.

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

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

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

** Changed in: gtk4 (Ubuntu)
   Status: Fix Committed => Triaged

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

Title:
  Thumbnails too small in 'open file' dialog nautilus

Status in Nautilus:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in gtk4 package in Ubuntu:
  Triaged

Bug description:
  When trying to upload image files to e.g. websites like marktplaats.nl
  (kind of ebay) I get  very, very small image thumbnails. There seems
  no way to enlarge these thumbnails. All options only work if Nautilus
  is used stand alone, but not with the open file dialog that is being
  used to upload files.

  I have attached a screen dump just to show what I mean.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1175608/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

[Rafael Filipe Ferreirinha Cardoso]

I'm running on Ubuntu 22.04, kernel 5.15.0-60-generic and this still
happens.

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

[cetver]

Same problem

Laptop
Product Name: Victus by HP Laptop 16-e17xxx
Serial Number: 5CD212MCYY

OS
DISTRIB_ID=Kubuntu
DISTRIB_RELEASE=22.10

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

[Dimitri John Ledkov]

we ought to sponosr
http://launchpadlibrarian.net/453184210/lxc_3.0.4-0ubuntu1_3.0.4-0ubuntu2.diff.gz
into bionic

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

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Triaged

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 2001568] Re: unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

[Dave Jones]

It looks like Debian independently fixed the running_escape_regexp line
in January (in 2.9.1+nmu3 [1]). The d/t/control fix isn't *strictly*
necessary to fix this and is more a matter of fixing semantics -- but
I'll try and forward that change if I can figure out where to submit a
PR (doesn't appear u-u is in salsa, and the GH Vcs-Git repo is way
behind where it's meant to be).

[1]: https://tracker.debian.org/news/1405664/accepted-unattended-
upgrades-291nmu3-source-into-unstable/

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+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 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss

[Nick Rosbrook]

I have confirmed that this bug affects Jammy and newer. The upstream
patch looks straight-forward, so I will test a build with that patch
included to see if it fixes the issue.

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

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

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

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

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

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

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

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

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

Title:
  networkctl reload with bond devices causes slaves to go DOWN and UP,
  causing couple of seconds of network loss

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Triaged

Bug description:
  We currently use Ubuntu 22.04.1 LTS including updates for our production 
cloud (switched from legacy Centos 7).
  Although we like the distribution we recently hit serious systemd buggy 
behavior described in [1] bugreport using packages [2].

  Unfortunatelly the clouds we are running consist of openstack on top
  of kubernetes and we need to have complex network configuration
  including linux bond devices.

  Our observation is that every time we apply our configuration via
  CI/CD infrastructure using ansible and netplan (regardless whether
  there is actual network configuration change) we see approximatelly
  8-16 seconds network interruptions and see bond interfaces going DOWN
  and then UP.

  We expect bond interfaces stay UP when there is no network
  configuration change.

  We went though couple of options how to solve the issue and the first
  one is to add such existing patch [3] into current
  systemd-249.11-0ubuntu3.6.

  Could you comment whether this kind of non-security patch is likely to land 
in 22.04.1 LTS soon.
  We are able to help to bring patch into systemd package community way if you 
suggest the steps.

  
  [1] https://github.com/systemd/systemd/issues/25067
  [2] Packages
  root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)'
  netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 
[installed,automatic]
  systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic]
  [3] https://github.com/systemd/systemd/pull/25162
  [4] # lsb_release -rd
  Description:Ubuntu 22.04.1 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+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 2007155] Re: grep: sometimes mistakenly matches lines when last of multiple patterns includes backref

[Ubuntu Foundations Team Bug Bot]

The attachment "1029235-grep-bug-backref-in-last-of-multiple-
patterns.patch" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  grep: sometimes mistakenly matches lines when last of multiple
  patterns includes backref

Status in grep package in Ubuntu:
  New

Bug description:
  This bug was introduced upstream with grep 3.4. Originally reported in
  Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029235#19

  On an ubuntu focal machine:
echo 'Total failed: 2 (1 ignored)' | grep -e '^Total failed: 0$' -e '^Total 
failed: \([0-9]*\) (\1 ignored)$'
Total failed: 2 (1 ignored)

  A fixed grep doesn't match the line.

  This has been fixed in debian unstable with 3.8-4, and in bullseye
  with 3.6-1+deb11u1.

  I've tested the attached patch in ubuntu focal (grep 3.4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/2007155/+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 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

[Amin Bandali]

Thanks for the upload and for your comments, Simon; noted.

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

Title:
  Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

Status in librsvg package in Ubuntu:
  New

Bug description:
  Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

  Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1:

  librsvg (2.54.5+dfsg-1) unstable; urgency=medium

* New upstream release
* debian/librsvg2-2.docs: NEWS.md -> NEWS

   -- Jeremy Bicha   Thu, 22 Sep 2022 17:00:54 -0400

  Remaining differences with librsvg from Debian unstable:

* Don't fail the build on tests error for i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+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 2007155] [NEW] grep: sometimes mistakenly matches lines when last of multiple patterns includes backref

[Santiago Ruano Rincon]

Public bug reported:

This bug was introduced upstream with grep 3.4. Originally reported in
Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029235#19

On an ubuntu focal machine:
  echo 'Total failed: 2 (1 ignored)' | grep -e '^Total failed: 0$' -e '^Total 
failed: \([0-9]*\) (\1 ignored)$'
  Total failed: 2 (1 ignored)

A fixed grep doesn't match the line.

This has been fixed in debian unstable with 3.8-4, and in bullseye with
3.6-1+deb11u1.

I've tested the attached patch in ubuntu focal (grep 3.4)

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

** Patch added: "1029235-grep-bug-backref-in-last-of-multiple-patterns.patch"
   
https://bugs.launchpad.net/bugs/2007155/+attachment/5646814/+files/1029235-grep-bug-backref-in-last-of-multiple-patterns.patch

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

Title:
  grep: sometimes mistakenly matches lines when last of multiple
  patterns includes backref

Status in grep package in Ubuntu:
  New

Bug description:
  This bug was introduced upstream with grep 3.4. Originally reported in
  Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029235#19

  On an ubuntu focal machine:
echo 'Total failed: 2 (1 ignored)' | grep -e '^Total failed: 0$' -e '^Total 
failed: \([0-9]*\) (\1 ignored)$'
Total failed: 2 (1 ignored)

  A fixed grep doesn't match the line.

  This has been fixed in debian unstable with 3.8-4, and in bullseye
  with 3.6-1+deb11u1.

  I've tested the attached patch in ubuntu focal (grep 3.4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/2007155/+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 2002445] Re: udev NIC renaming race with mlx5_core driver

[Lukas Märdian]

Fixed upstream in https://github.com/systemd/systemd/pull/25221

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  New
Status in systemd source package in Lunar:
  New

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Since this is a race condition, we need to boot many instances before we see 
the issue. The Ubuntu Server team will help coordinate the testing at scale to 
confirm the fix.

  [Where problems could occur]
  The patches effectively make it so that if a interface cannot be renamed from 
udev, then the new name is left as an alternative name as a fallback. If 
problems occur, it would be related to device renaming, and particularly 
related to the devices alternative names.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2002445/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist

[Jan-Jonas Sämann]

What @fargiolas wrote, solved this issue for me on 20.04.

Configure watchdog module in /etc/defaults/watchdog

The watchdog service loads the module itself on demand. You don't have
to load the module yourself then.

Seems that the issue can be closed now.

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

Title:
  systemd ignoring /etc/modules due to blacklist

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is 
blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is 
blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 228-4ubuntu1
Candidate: 228-4ubuntu1
Version table:
   *** 228-4ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

[Vladimir Djurovic]

I'm having the same problem with HP Elitebook 860 G9. I get sound
through headphones and HDMI output, but not through built-in speakers.

Upgrading to kernel 5.9.17 seems to fix the problem.

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

[Tobias Heider]

I have installed libunwind=1.6.2-0ubuntu1.1 on my 16K page arm machine
and verified that the xorg crash is indeed fixed with this version. To
make sure it also does not negatively affect other hardware
configurations I also tested on my amd64 desktop and found that
everything still works without regressions after the update.

To test the functionality of the library I installed 
libunwind-dev=1.6.2-0ubuntu1.1 and ran the libunwind examples from 
https://github.com/daniel-thompson/libunwind-examples
The results look good:

$USER:~/libunwind-examples$ ./unwind-local 
0x55d35d0d644c: (cmp+0xe)
0x7f927ac3d33c: (bsearch+0x5c)
0x55d35d0d61fc: (main+0x5c)
0x7f927ac23510: (__libc_init_first+0x90)
0x7f927ac235c9: (__libc_start_main+0x89)
0x55d35d0d6245: (_start+0x25)


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

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

Title:
  libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with
  bigger page sizes

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * On kernels with page size > 4K Xorg (and presumably other applications
     relying on libunwind) crashes on startup. This affects anyone
     running the official arm64 generic-64k kernel or custom non 4k kernels
     (as used by e.g. apple silicon).

 The exact error I am seeing in the logs is:

  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 0: 
/usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaab456ca998]
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 
unw_get_proc_info failed: no unwind info found [-10]
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Segmentation 
fault at address 0x0
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Fatal server error:
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Please consult the 
The X.Org Foundation support
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]:  at 
http://wiki.x.org
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]:  for help.
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)

I have not found a workaround other than using wayland (which has other
limitations). To reproduce use a kernel configured with a page size of
16K (CONFIG_ARM64_16K_PAGES=y or CONFIG_ARM64_64K_PAGES=y or) and try
to start "Ubuntu on Xorg" in gdm.

  [ Test Plan ]

   * Make sure Xorg doesn't crash on 4K, 16K and 64K kernels.

  [ Where problems could occur ]

   * We will have to make sure the fixed version still works with 4k
     kernels. The patch is already widely in use so the risk seems low if
     we test properly.

  [ Other Info ]

   * The lunar version ships the bug fix synced from debian

   * Debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1026217

   * Upstream fix:
  
https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf

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

[Benjamin Drung]

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

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

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
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 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:
  New
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 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 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 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:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
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:
  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 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

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


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

[Touch-packages] [Bug 2007124] [NEW] Move available config files from /etc to /usr

[Gunnar Hjalmarsson]

Public bug reported:

At the upgrade to fontconfig 2.10 a decade ago, the directory for
storing available config files was changed from /etc/fonts/conf.avail to
/usr/share/fontconfig/conf.avail. It was done upstream as well as in
Debian, but Ubuntu delayed the transition for some reason. I think we
should do that transition in Ubuntu too. That will get Ubuntu in sync
with the upstream documentation and the delta to Debian gets reduced a
little.

The changes needed are straightforward. I put a proposed upload in this
PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig

and I would appreciate someone's eyes on it.

So, what's the caveat? The only thing I can think of is that distros,
system admins and individual users may have tweaked the font
configuration by including symlinks which point to the moved files.
While I don't have the impression that such symlinks are very frequent —
custom conf files put directly in /etc/fonts/conf.d or equivalent places
in $HOME seem to be more common — to the extent they exist, they will be
silently disabled.

Bug #2005124 revealed an example of a symlink which pointed to a file
which will be moved if we do this. OTOH, in that case upstream added a
symlink with the very same name, so we had to deal with that conflict.
If the name of Kubuntu's link had been something else, we might not be
aware of it yet.

The changelog for this upload:

https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1

states that the transition will be done "later with another upload once
the details are sorted". Are there other details which I have missed? If
not, I suppose that the potential inconvenience is approximately as big
today as it was 2012. And since next LTS release is more than one year
ahead, this ought to be an appropriate time to make the change.

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

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

Title:
  Move available config files from /etc to /usr

Status in fontconfig package in Ubuntu:
  New

Bug description:
  At the upgrade to fontconfig 2.10 a decade ago, the directory for
  storing available config files was changed from /etc/fonts/conf.avail
  to /usr/share/fontconfig/conf.avail. It was done upstream as well as
  in Debian, but Ubuntu delayed the transition for some reason. I think
  we should do that transition in Ubuntu too. That will get Ubuntu in
  sync with the upstream documentation and the delta to Debian gets
  reduced a little.

  The changes needed are straightforward. I put a proposed upload in
  this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig

  and I would appreciate someone's eyes on it.

  So, what's the caveat? The only thing I can think of is that distros,
  system admins and individual users may have tweaked the font
  configuration by including symlinks which point to the moved files.
  While I don't have the impression that such symlinks are very frequent
  — custom conf files put directly in /etc/fonts/conf.d or equivalent
  places in $HOME seem to be more common — to the extent they exist,
  they will be silently disabled.

  Bug #2005124 revealed an example of a symlink which pointed to a file
  which will be moved if we do this. OTOH, in that case upstream added a
  symlink with the very same name, so we had to deal with that conflict.
  If the name of Kubuntu's link had been something else, we might not be
  aware of it yet.

  The changelog for this upload:

  https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1

  states that the transition will be done "later with another upload
  once the details are sorted". Are there other details which I have
  missed? If not, I suppose that the potential inconvenience is
  approximately as big today as it was 2012. And since next LTS release
  is more than one year ahead, this ought to be an appropriate time to
  make the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2007124/+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 2007107] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.9 failed to install/upgrade: »installiertes linux-firmware-Skript des Paketes post-installation«-Unterprozess

[Elisabeth Maubach]

Public bug reported:

can't update due to too little space on /boot
autoremove doesn't do the trick

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.9
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  isa4656 F pulseaudio
 /dev/snd/controlC0:  isa4656 F pulseaudio
CasperMD5CheckResult: unknown
Date: Mon Feb 13 09:03:25 2023
Dependencies: firmware-sof-signed 2.0-1ubuntu4
ErrorMessage: »installiertes linux-firmware-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2022-04-11 (307 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: LENOVO 20NKS01Y00
PackageArchitecture: all
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_davvyz@/vmlinuz-5.15.0-58-generic 
root=ZFS=rpool/ROOT/ubuntu_davvyz ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1
SourcePackage: initramfs-tools
Title: package linux-firmware 20220329.git681281e4-0ubuntu3.9 failed to 
install/upgrade: »installiertes linux-firmware-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2021
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: R12ET58W(1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NKS01Y00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET58W(1.28):bd06/11/2021:br1.28:efr1.28:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NK_BU_Think_FM_ThinkPadT495:
dmi.product.family: ThinkPad T495
dmi.product.name: 20NKS01Y00
dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
dmi.product.version: ThinkPad T495
dmi.sys.vendor: LENOVO

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.9 failed to
  install/upgrade: »installiertes linux-firmware-Skript des Paketes
  post-installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  can't update due to too little space on /boot
  autoremove doesn't do the trick

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.9
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  isa4656 F pulseaudio
   /dev/snd/controlC0:  isa4656 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Mon Feb 13 09:03:25 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4
  ErrorMessage: »installiertes linux-firmware-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2022-04-11 (307 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: LENOVO 20NKS01Y00
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_davvyz@/vmlinuz-5.15.0-58-generic 
root=ZFS=rpool/ROOT/ubuntu_davvyz ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.9 failed to 
install/upgrade: »installiertes linux-firmware-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2021
  

[Touch-packages] [Bug 2006955] Re: Screens not detected anymore

[Daniel van Vugt]

Thanks for the bug report.

Please try reinstalling this package:

  https://launchpad.net/ubuntu/+archive/primary/+files/linux-modules-
extra-5.15.0-60-generic_5.15.0-60.66_amd64.deb

and then reboot. If the problem persists after that then please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

** Tags added: amdgpu

** Summary changed:

- Screens not detected anymore
+ [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 
5.15.0-58-generic works)

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

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

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

Title:
  [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but
  5.15.0-58-generic works)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have 3 monitors, but since very recently (yesterday or so), only 1
  of them seems to be detected.

  In the Settings app, under "Screen Display", I used to have a place
  where I can move my monitors relatively to each other, and adjust each
  of their settings. Now, I no longer have the monitor drag-and-drop
  zone, I only have one detected "Unknown display", fixed at 1920x1080
  77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any
  setting except orientation, scaling, and fractional scaling.

  The bug started happening just when the kernel was auto-updated to
  5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux
  user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC
  2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with
  5.15.0-58-generic, all of my 3 displays are detected and working fine.

  I also noticed the same problem happened when I installed
  5.15.0-58-lowlatency.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 10 11:00:59 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 
5600 OEM/5600 XT / 5700/5700 XT] [1462:3816]
  InstallationDate: Installed on 2021-01-27 (743 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: B550 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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