[Touch-packages] [Bug 1950961] Re: Sporadically Airplane mode option on setting page is not working on Ubuntu 21.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Sporadically Airplane mode option on setting page is not working on
  Ubuntu 21.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In network setting page airplane mode enable/disable is not working sometimes.
  More info: 
  1) root@ubuntu:/home/intel# uname -a
 Linux ubuntu 5.13.0-for-ubuntu #1 SMP Tue Oct 12 10:36:49 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  2) root@ubuntu:/home/intel# cat /etc/lsb-release 
 DISTRIB_ID=Ubuntu
 DISTRIB_RELEASE=21.04
 DISTRIB_CODENAME=hirsute
 DISTRIB_DESCRIPTION="Ubuntu 21.04"

  3) root@ubuntu:~$ ModemManager --version
 ModemManager 1.16.6
 Copyright (C) 2008-2021 The ModemManager authors
 License GPLv2+: GNU GPL version 2 or later 

 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.

  4) root@ubuntu:~$ nmcli -v
 nmcli tool, version 1.30.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1950961/+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 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts

[Bug Watch Updater]

** Changed in: isc-dhcp (Debian)
   Status: Unknown => New

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

Title:
  Apparmor Disallows Disabling Dhclient Scripts

Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp package in Debian:
  New

Bug description:
  In some cases, it may be desirable to disable dhclient scripts. By
  default /sbin/dhclient-script is used, and some others are allowed by
  the apparmor profile.

  Without Apparmor, disabling hook scripts can be accomplished with
  flags -sf /bin/true, but with apparmor enabled this gets blocked:

  execve (/bin/true, ...): Permission denied

  Unfortunately dhclient doesn't appear to provide any other mechanism
  for disabling hook scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 2003845] Re: updating CA certificates on 18.04

[Launchpad Bug Tracker]

[Expired for ca-certificates (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: ca-certificates (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  updating CA certificates on 18.04

Status in ca-certificates package in Ubuntu:
  Expired

Bug description:
  Ubuntu 18.04 uses older version of NSS (version 3.35) by which the
  latest root certificates distributed by NSS are not trusted in Ubuntu
  18.04. Hence, please update it to latest version of NSS. For example,
  Mozilla Firefox uses version 3.86 of NSS in Ubuntu 18.04. This issue
  is impacting a set of users using their TLS certificates from latest
  root CAs, where website connections are failing due to untrusted
  certificate authorities.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2003845/+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 2012943] Re: Systemd-resolved is crashing

[Naveen chand]

Hi Nick,
The setup is having multiple devices with the same configuration connected to a 
network.
If you need more details about his please go through the below bug.
https://bugs.launchpad.net/shiner/+bug/2001620

Regards,
Naveen

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

Title:
  Systemd-resolved is crashing

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

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system.

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  [ Where problems could occur ]

  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
  This commit is resolving the issue which is observed.

  Please refer to the above commit to assess the risk involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2013143] Re: [GK mini, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [GK mini, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My external monitor is LG 29wk600-w.

  https://www.lg.com/th/consumer-monitors/lg-29WK600-W

  Since March 28, 2006, there was no sound from the built-in speaker on
  the monitor under either 5.19.0-38 or 5.19.0-35.

  Thank you in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  id31931 F pulseaudio
   /dev/snd/controlC1:  id31931 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 29 08:34:11 2023
  InstallationDate: Installed on 2022-10-22 (157 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  id31931 F pulseaudio
   /dev/snd/controlC1:  id31931 F pulseaudio
   /dev/snd/pcmC1D0c:   id31931 F...m pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [GK mini, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: Default string
  dmi.board.name: GK mini
  dmi.board.vendor: AZW
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd12/07/2021:br5.13:svnAZW:pnGKmini:pvrDefaultstring:rvnAZW:rnGKmini:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: GK mini
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: AZW

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2013143/+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 1782447] Re: If BROWSER isn't set, sensible-browser outputs: "usage: which [-as] program ..."

[Bug Watch Updater]

** Changed in: sensible-utils (Debian)
   Status: Unknown => Fix Released

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

Title:
  If BROWSER isn't set, sensible-browser outputs: "usage: which [-as]
  program ..."

Status in sensible-utils package in Ubuntu:
  Fix Released
Status in sensible-utils package in Debian:
  Fix Released

Bug description:
  If environment variable BROWSER isn't set, sensible-browser always
  shows this error message:

  usage: which [-as] program ...

  even though it goes on and opens the browser.

  It's easy to reproduce:

  $ unset BROWSER
  $ sensible-browser http://example.com

  The bug is right at the beginning:

  # Prevent recursive loops, where these values are set to this script
  p="$(which sensible-browser)"
  [ "$(which $BROWSER || true)" = "$p" ] && BROWSER=

  It could be fixed with:

  [ -n "$BROWSER" -a "$(which "$BROWSER")" = "$p" ] && BROWSER=

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sensible-utils 0.0.12
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul 18 20:21:36 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-04-28 (81 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: sensible-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1782447/+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 2013143] [NEW] [GK mini, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My external monitor is LG 29wk600-w.

https://www.lg.com/th/consumer-monitors/lg-29WK600-W

Since March 28, 2006, there was no sound from the built-in speaker on
the monitor under either 5.19.0-38 or 5.19.0-35.

Thank you in advance.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  id31931 F pulseaudio
 /dev/snd/controlC1:  id31931 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 29 08:34:11 2023
InstallationDate: Installed on 2022-10-22 (157 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  id31931 F pulseaudio
 /dev/snd/controlC1:  id31931 F pulseaudio
 /dev/snd/pcmC1D0c:   id31931 F...m pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [GK mini, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.13
dmi.board.asset.tag: Default string
dmi.board.name: GK mini
dmi.board.vendor: AZW
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd12/07/2021:br5.13:svnAZW:pnGKmini:pvrDefaultstring:rvnAZW:rnGKmini:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: GK mini
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: AZW

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


** Tags: amd64 apport-bug jammy wayland-session
-- 
[GK mini, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all
https://bugs.launchpad.net/bugs/2013143
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

-- 
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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio -
1:15.99.1+dfsg1-1ubuntu2.1

---
pulseaudio (1:15.99.1+dfsg1-1ubuntu2.1) jammy; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/0018-bluetooth-Amend-writeout-to-send-more-initial-frames.patch
(LP: #2007331)

 -- Kai-Heng Feng   Thu, 16 Feb 2023
10:19:55 +0800

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

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in pulseaudio source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubunt

[Bug Watch Updater]

** Changed in: fontconfig (Debian)
   Status: Unknown => Fix Released

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

Title:
  package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade:
  trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which
  is also in package kubuntu-settings-desktop 1:23.04.2

Status in fontconfig package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in fontconfig package in Debian:
  Fix Released

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: fontconfig-config 2.13.1-4.4ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Feb  4 05:59:53 2023
  DuplicateSignature:
   package:fontconfig-config:2.13.1-4.4ubuntu1
   Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb 
(--unpack):
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is 
also in package kubuntu-settings-desktop 1:23.04.2
  ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', 
which is also in package kubuntu-settings-desktop 1:23.04.2
  InstallationDate: Installed on 2023-01-31 (3 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 
3.11.1-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.19ubuntu3
   apt  2.5.5
  SourcePackage: fontconfig
  Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: 
trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in 
package kubuntu-settings-desktop 1:23.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+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 1981794] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for dnsmasq has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Released
Status in dnsmasq source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When a DNS query fails to complete and the system retries it,
  subsequent copies of the query will be refused by dnsmasq. The client
  will automatically receive the REFUSED return value without a retry
  attempt.

  Adding this fix will stop dnsmasq from unnecessarily breaking
  connections, especially for situations where an internet connection is
  flaky.

  This bug is fixed by patching in an upstream commit -
  https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be
  - which allows retried DNS requests through rather than refusing them.

  [Test Plan]

  The fix can be tested using 2 lxd containers, 1 for running the fix,
  and 1 for acting as a dns server.

  Start by setting up the dns server container:

  # lxc launch images:ubuntu/jammy dns-resolver
  # lxc exec dns-resolver bash

  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf
  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf
  # apt install net-tools dnsmasq -y
  # systemctl enable dnsmasq

  Get the container's ip on lxd's network, in this case ifconfig is
  used, showing 10.62.42.157:

  # ifconfig
  eth0: flags=4163  mtu 1500
  inet 10.62.42.157  netmask 255.255.255.0  broadcast 10.62.42.255
  ...

  Now set up the test container:

  # lxc launch images:ubuntu/jammy test-dnsmasq
  # lxc exec test-dnsmasq bash

  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf

  Use other container's ip here, along with an ip that does not resolve

  # echo "nameserver 10.62.42.157
  nameserver 192.0.2.1" | tee /etc/resolv.conf

  # apt install dnsmasq -y
  # systemctl enable dnsmasq

  On the dns server side, set the nameserver to 127.0.0.1 to cause
  denials on the test server:

  # echo nameserver 127.0.0.1 | tee /etc/resolv.conf; systemctl restart
  dnsmasq

  Now ping a known domain on the test container, and while it runs set
  the dns server side nameserver back to 8.8.8.8:

  # ping ubuntu.com

  > swap containers

  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf; systemctl restart
  dnsmasq

  Ping will continue to not pick up the domain and fails with:

  ping: ubuntu.com: Temporary failure in name resolution

  With the fix, ping should now pick up the new successful responses:

  PING ubuntu.com (185.125.190.29) 56(84) bytes of data.
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=1 ttl=48 time=165 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=2 ttl=48 time=162 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=3 ttl=48 time=166 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=4 ttl=48 time=164 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=5 ttl=48 time=163 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=6 ttl=48 time=163 ms
  ^C
  --- ubuntu.com ping statistics ---
  6 packets transmitted, 6 received, 0% packet loss, time 5005ms

  Note: ping is used here instead of another dns tester such as dig
  because it continues its dns resolution attempts with retry packets
  even after receiving a REFUSED error. Other programs fail immediately
  on REFUSED and are unable to send duplicate packets to reproduce the
  issue.

  [Where problems could occur]

  This change was added upstream in version 2.87, which means it has not
  been tested in many situations alongside 2.86. Allowing the retries
  could lead to a flood of requests to remote DNS servers if the replies
  are unable to make it back through dnsmasq to the user.

  [Other Info]

  This bug was fixed in Kinetic in version 2.86-1.1ubuntu2.

  [Original Description]

  Duplicate or retried DNS queries will return REFUSED for one of the
  queries causing intermittent failures in clients.

  This probably breaks lots of things, but 

[Touch-packages] [Bug 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

[Launchpad Bug Tracker]

This bug was fixed in the package dnsmasq - 2.86-1.1ubuntu0.2

---
dnsmasq (2.86-1.1ubuntu0.2) jammy; urgency=medium

  * src/forward.c: Do not refuse retries from client DNS queries. Behaviour to
stop infinite loops when all servers return REFUSED was wrongly activated
on client retries, resulting in incorrect REFUSED replies to client
retries. The code added here is a cherry pick released in upstream version
2.87, originating at
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be
(LP: #1981794)

 -- Lena Voytek   Fri, 14 Oct 2022 14:39:41
-0700

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

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

Title:
  Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Released
Status in dnsmasq source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When a DNS query fails to complete and the system retries it,
  subsequent copies of the query will be refused by dnsmasq. The client
  will automatically receive the REFUSED return value without a retry
  attempt.

  Adding this fix will stop dnsmasq from unnecessarily breaking
  connections, especially for situations where an internet connection is
  flaky.

  This bug is fixed by patching in an upstream commit -
  https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be
  - which allows retried DNS requests through rather than refusing them.

  [Test Plan]

  The fix can be tested using 2 lxd containers, 1 for running the fix,
  and 1 for acting as a dns server.

  Start by setting up the dns server container:

  # lxc launch images:ubuntu/jammy dns-resolver
  # lxc exec dns-resolver bash

  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf
  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf
  # apt install net-tools dnsmasq -y
  # systemctl enable dnsmasq

  Get the container's ip on lxd's network, in this case ifconfig is
  used, showing 10.62.42.157:

  # ifconfig
  eth0: flags=4163  mtu 1500
  inet 10.62.42.157  netmask 255.255.255.0  broadcast 10.62.42.255
  ...

  Now set up the test container:

  # lxc launch images:ubuntu/jammy test-dnsmasq
  # lxc exec test-dnsmasq bash

  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf

  Use other container's ip here, along with an ip that does not resolve

  # echo "nameserver 10.62.42.157
  nameserver 192.0.2.1" | tee /etc/resolv.conf

  # apt install dnsmasq -y
  # systemctl enable dnsmasq

  On the dns server side, set the nameserver to 127.0.0.1 to cause
  denials on the test server:

  # echo nameserver 127.0.0.1 | tee /etc/resolv.conf; systemctl restart
  dnsmasq

  Now ping a known domain on the test container, and while it runs set
  the dns server side nameserver back to 8.8.8.8:

  # ping ubuntu.com

  > swap containers

  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf; systemctl restart
  dnsmasq

  Ping will continue to not pick up the domain and fails with:

  ping: ubuntu.com: Temporary failure in name resolution

  With the fix, ping should now pick up the new successful responses:

  PING ubuntu.com (185.125.190.29) 56(84) bytes of data.
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=1 ttl=48 time=165 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=2 ttl=48 time=162 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=3 ttl=48 time=166 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=4 ttl=48 time=164 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=5 ttl=48 time=163 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=6 ttl=48 time=163 ms
  ^C
  --- ubuntu.com ping statistics ---
  6 packets transmitted, 6 received, 0% packet loss, time 5005ms

  Note: ping is used here instead of another dns tester such as dig
  because it continues its dns resolution attempts with retry packets
  even after receiving a REFUSED error. Other programs fail immediately
  on REFUSED and are unable to send duplicate packets to reproduce the
  issue.

  [Where problems could occur]

  This change was added upstream in version 2.87, which means it has not
  been tested in many situations alongside 2.86. Allowing the retries
  could lead to a flood of requests to remote DNS servers if the replies
  are unable to make it back through dnsmasq to the user.

  [Other Info]

  This bug was 

[Touch-packages] [Bug 1899218] Re: Incorrect warning from apparmor_parser on force complained profiles

[Alex Murray]

This bug is fixed and the behaviour you are seeing is expected - ie. it
is expected that AppArmor prints a warning about forcing complain mode
for the usr.sbin.sssd profile and that it then also prints a warning
about caching being disabled for that due to it being in force complain
mode. This is expected and normal behaviour.

However, if you feel this expected behaviour is a bug, please file a
separate bug report for that and describe what you think is incorrect
about this behaviour and how instead you feel it should behave.

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

Title:
  Incorrect warning from apparmor_parser on force complained profiles

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  apparmor_parser on a force complained profile produces an incorrect
  warning message:

  $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
  Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
  Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd 
line 54): Warning failed to create cache: usr.sbin.sssd

  Even though not generating the cache at all is expected, the warning
  should describe caching is disabled for force complained profiles
  instead of failure to create it.

  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  $ apt-cache policy apparmor
  apparmor:
    Installed: 3.0.0~beta1-0ubuntu6
    Candidate: 3.0.0~beta1-0ubuntu6
    Version table:
   *** 3.0.0~beta1-0ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1899218/+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 1983794] Re: Evolution not deleting autosave files

[Chris Halse Rogers]

Can anyone do the verification for kinetic? Releasing this for 22.04 is
blocked waiting on successful testing for 22.10.

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Fix Released
Status in libcanberra source package in Jammy:
  Fix Committed
Status in evolution source package in Kinetic:
  Confirmed
Status in libcanberra source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  Autosave files are not removed from evolution local state directories
  (and windows leaked)

  
  [ Test case ]

  1. Open evolution, and start to compose a new email
  2. Write enough text and wait few minutes so that this command returns a file
 ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
  3. Close the email composer window, hitting "Do not save"
  4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list 
no files
  5. Opening and closing again evolution should not ask to restore the previous 
email

  
  [ Regression potential ]

  No sounds could be performed during some UI actions

  ---

  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

Looks like Sean was right - removing libva-wayland2 and then rebooting
resolved the issue.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 1728130] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for apparmor has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Policy needs improved feature versioning to ensure it is correctly
  being applied

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Currently allows pinning a single feature abi or running in a
  developer mode where the full abi available of the current kernel is
  enforced.

  However this can result in breaking applications in undesirable ways.

  If an application is shipped with its own policy, that policy might be
  different than the pinned feature abi, which can either result in
  denials because features the policy was not developed for are being
  enforced.

  If the feature version is not pinned then the most recent kernel abi
  is taken and applied to policy, which has not been updated. This can
  result in denials for userspace effectively breaking userspace. This
  is less than ideal for most users as it leads to a bad experience than
  they have not opted into and can lead to them disabling security
  protections.

  [ Test Plan ]

  The test can be done with several features. Here we are using mqueue as an 
example.
  Verify that the kernel that has mqueue mediation support:
  root@ubuntu:~# [ -e /sys/kernel/security/apparmor/features/ipc/posix_mqueue ] 
&& echo "supports mqueue"
  supports mqueue

  cd /tmp
  pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal
  cd apparmor-2.13.3/tests/regression/apparmor/
  USE_SYSTEM=1 make

  Using the parser from the mqueue-sru PPA, load the profile.
  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test, which should fail.
  ./posix_mq_rcv -c ./posix_mq_snd
  FAIL - could not open mq: Permission denied

  Now use an abi that does not have mqueue. This simulates a scenario
  where a policy was developed before mqueue support was added, so posix
  message queues should be allowed by default.

  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test again, it should pass.
  ./posix_mq_rcv -c ./posix_mq_snd
  PASS

  [ Where problems could occur ]

  ABI pinning forces policies that don't have abi specified in their
  profile to use the ABI pinned in parser.conf. When the ABI is pinned
  and the user is trying to use mediation that is not in the pinned ABI,
  they might be confused why it is always being allowed. This can be
  circumvented by specifying the correct abi in the profile.

  [ Other Info ]

  The patches for focal (apparmor-2.13) can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
  apparmor-3.0 already has this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1728130/+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 1728130] Re: Policy needs improved feature versioning to ensure it is correctly being applied

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.13.3-7ubuntu5.2

---
apparmor (2.13.3-7ubuntu5.2) focal; urgency=medium

  * Add capability upstream patches to fix LP: #1964636
- u/cap1-Generate-CAPABILITIES-in-a-script-due-to-make-4.3.patch: move
code that generates a list of capabilities to a script in common/
- u/cap2-parser-Move-to-a-pre-generated-cap_names.h.patch: use a
pre-generated list of capabilities so that all capabilities are
supported even when building against older kernels.
- u/cap3-parser-cleanup-capability_table-generation-by-droppi.patch: drop
sys_log static declaration because it's already in the generated list.
- u/cap4-parser-unify-capability-name-handling.patch: drop internal
hardcoded capability table.
- u/cap5-parser-Makefile-use-LC_ALL-C-when-invoking-sed.patch: use
LC_ALL=C when invoking sed.
- u/cap6-parser-Add-warning-to-capability_table-about-the-nee.patch: add
warning to capability_table about the need to update the Makefile.
- u/cap7-Add-CAP_BPF-and-CAP_PERFMON-to-severity.db.patch: add
support for cap_bpf and cap_perfmon
- u/cap8-parser-Makefile-fix-generated-cap-comparison-against.patch: fix
generated cap comparison against known list
  * Add upstream patches for abi support. LP: #1728130
- u/abi1-parser-feature-abi-setup-parser-to-intersect-policy-.patch: add
the ability to intersect parser and kernel features in the parser.
- u/abi2-parser-add-basic-support-for-feature-abis.patch: add support
to specify a feature abi.
- u/abi3-pin-abi-2.13.patch: add and pin a policy abi for 2.13
- u/abi4-parser-fix-abi-rule-and-pinned-feature-file-interact.patch: fix
abi rule and pinned feature file interaction
- apparmor.install: add 2.13 abi file to be installed in 
/etc/apparmor.d/abi/
  * Add mqueue patches. LP: #1993353
- u/mqueue1-parser-add-parser-support-for-message-queue-mediatio.patch:
add parser support for mqueue mediation
- u/mqueue2-tests-add-posix-message-queue-regression-tests.patch: add
posix mqueue regression tests
- u/mqueue3-utils-add-message-queue-rules-parsing-in-python-tool.patch:
add support in python tools to parse mqueue rules
- u/mqueue4-parser-add-parser-simple-tests-for-mqueue-rules.patch: add
parser simple tests for mqueue
- u/mqueue5-parser-place-perm-on-name-as-well-as-name-label-comb.patch:
add permissions on name and also on name + label
- u/mqueue6-libapparmor-add-support-for-requested-and-denied-on-.patch:
add parsing support for "denied" and "requested" from audit logs
- u/mqueue7-libapparmor-add-support-for-class-in-logparsing.patch: add
parsing support for "class" from audit logs
- u/mqueue8-utils-add-logparser-support-for-mqueue.patch: add logparser
support for mqueue rules
- u/mqueue9-tests-add-sysv-message-queue-regression-tests.patch: add
sysv mqueue regression tests
- u/mqueue10-parser-enable-mqueue-rules-when-abi-is-not-set.patch:
override pinned features for mqueue rules when abi is not set in policy.
- debian/rules: create mqueue testcase empty files for libapparmor tests.
  * Closes LP: #1994146

 -- Georgia Garcia   Mon, 10 Oct 2022
17:52:45 -0300

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

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

Title:
  Policy needs improved feature versioning to ensure it is correctly
  being applied

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Currently allows pinning a single feature abi or running in a
  developer mode where the full abi available of the current kernel is
  enforced.

  However this can result in breaking applications in undesirable ways.

  If an application is shipped with its own policy, that policy might be
  different than the pinned feature abi, which can either result in
  denials because features the policy was not developed for are being
  enforced.

  If the feature version is not pinned then the most recent kernel abi
  is taken and applied to policy, which has not been updated. This can
  result in denials for userspace effectively breaking userspace. This
  is less than ideal for most users as it leads to a bad experience than
  they have not opted into and can lead to them disabling security
  protections.

  [ Test Plan ]

  The test can be done with several features. Here we are using mqueue as an 
example.
  Verify that the kernel that has mqueue mediation support:
  root@ubuntu:~# [ -e /sys/kernel/security/apparmor/features/ipc/posix_mqueue ] 
&& echo "supports mqueue"
  supports mqueue

  cd /tmp
  pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal
  cd apparmor-2.13.3/tests/regression/apparmor/
  

[Touch-packages] [Bug 1964636] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for apparmor has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Incorrect handling of apparmor `bpf` capability

Status in apparmor package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  Incomplete
Status in apparmor source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  The apparmor_parser before the 3.0 release would build its capability list 
from the installed kernel headers. The apparmor_parser was built against a 
kernel without support for cap 'bpf'
  This was fixed in 3.0 by having a static caps list (with full mapping info) 
and the dynamic auto-generated list (against the kernel headers) that is used 
to check that the static list has not become stale. In addition the parser can 
pull kernel supported caps straight from the apparmor kernel module (it will 
however be missing the mapping info).
  Backporting the patches from 3.0 fixes the issue.

  [ Test Plan ]

  Before the fix, the following profile fails loading:

  # echo "profile foo { capability bpf, }" | apparmor_parser -Q
  AppArmor parser error, in stdin line 1: Invalid capability bpf.
  # echo $?
  1

  After the fix, it works as expected:

  # echo "profile foo { capability bpf, }" | apparmor_parser -Q
  # echo $?
  0

  [ Where problems could occur ]

  With these changes, the parser can change its behavior based on a few things.
  1. the kernel its built against. This would not change behavior when run in a 
container vs at system level.

  2. If a feature-file is specified, via --features-file, --policy-
  features, or --kernel-features. This allows overriding the normal
  policy and kernel examination that the parser does when compiling
  policy.

  3. If /sys/kernel/security/apparmor/features is not available. The
  parser will fallback to an old set of features available in a kernel
  before the kernel module started exporting what the kernel module
  supports on the running kernel.

  [ Other Info ]

  The patches for focal (apparmor-2.13) can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
  As mentioned before, these patches are already running on apparmor-3.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1964636/+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 1964636] Re: Incorrect handling of apparmor `bpf` capability

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.13.3-7ubuntu5.2

---
apparmor (2.13.3-7ubuntu5.2) focal; urgency=medium

  * Add capability upstream patches to fix LP: #1964636
- u/cap1-Generate-CAPABILITIES-in-a-script-due-to-make-4.3.patch: move
code that generates a list of capabilities to a script in common/
- u/cap2-parser-Move-to-a-pre-generated-cap_names.h.patch: use a
pre-generated list of capabilities so that all capabilities are
supported even when building against older kernels.
- u/cap3-parser-cleanup-capability_table-generation-by-droppi.patch: drop
sys_log static declaration because it's already in the generated list.
- u/cap4-parser-unify-capability-name-handling.patch: drop internal
hardcoded capability table.
- u/cap5-parser-Makefile-use-LC_ALL-C-when-invoking-sed.patch: use
LC_ALL=C when invoking sed.
- u/cap6-parser-Add-warning-to-capability_table-about-the-nee.patch: add
warning to capability_table about the need to update the Makefile.
- u/cap7-Add-CAP_BPF-and-CAP_PERFMON-to-severity.db.patch: add
support for cap_bpf and cap_perfmon
- u/cap8-parser-Makefile-fix-generated-cap-comparison-against.patch: fix
generated cap comparison against known list
  * Add upstream patches for abi support. LP: #1728130
- u/abi1-parser-feature-abi-setup-parser-to-intersect-policy-.patch: add
the ability to intersect parser and kernel features in the parser.
- u/abi2-parser-add-basic-support-for-feature-abis.patch: add support
to specify a feature abi.
- u/abi3-pin-abi-2.13.patch: add and pin a policy abi for 2.13
- u/abi4-parser-fix-abi-rule-and-pinned-feature-file-interact.patch: fix
abi rule and pinned feature file interaction
- apparmor.install: add 2.13 abi file to be installed in 
/etc/apparmor.d/abi/
  * Add mqueue patches. LP: #1993353
- u/mqueue1-parser-add-parser-support-for-message-queue-mediatio.patch:
add parser support for mqueue mediation
- u/mqueue2-tests-add-posix-message-queue-regression-tests.patch: add
posix mqueue regression tests
- u/mqueue3-utils-add-message-queue-rules-parsing-in-python-tool.patch:
add support in python tools to parse mqueue rules
- u/mqueue4-parser-add-parser-simple-tests-for-mqueue-rules.patch: add
parser simple tests for mqueue
- u/mqueue5-parser-place-perm-on-name-as-well-as-name-label-comb.patch:
add permissions on name and also on name + label
- u/mqueue6-libapparmor-add-support-for-requested-and-denied-on-.patch:
add parsing support for "denied" and "requested" from audit logs
- u/mqueue7-libapparmor-add-support-for-class-in-logparsing.patch: add
parsing support for "class" from audit logs
- u/mqueue8-utils-add-logparser-support-for-mqueue.patch: add logparser
support for mqueue rules
- u/mqueue9-tests-add-sysv-message-queue-regression-tests.patch: add
sysv mqueue regression tests
- u/mqueue10-parser-enable-mqueue-rules-when-abi-is-not-set.patch:
override pinned features for mqueue rules when abi is not set in policy.
- debian/rules: create mqueue testcase empty files for libapparmor tests.
  * Closes LP: #1994146

 -- Georgia Garcia   Mon, 10 Oct 2022
17:52:45 -0300

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

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

Title:
  Incorrect handling of apparmor `bpf` capability

Status in apparmor package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  Incomplete
Status in apparmor source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  The apparmor_parser before the 3.0 release would build its capability list 
from the installed kernel headers. The apparmor_parser was built against a 
kernel without support for cap 'bpf'
  This was fixed in 3.0 by having a static caps list (with full mapping info) 
and the dynamic auto-generated list (against the kernel headers) that is used 
to check that the static list has not become stale. In addition the parser can 
pull kernel supported caps straight from the apparmor kernel module (it will 
however be missing the mapping info).
  Backporting the patches from 3.0 fixes the issue.

  [ Test Plan ]

  Before the fix, the following profile fails loading:

  # echo "profile foo { capability bpf, }" | apparmor_parser -Q
  AppArmor parser error, in stdin line 1: Invalid capability bpf.
  # echo $?
  1

  After the fix, it works as expected:

  # echo "profile foo { capability bpf, }" | apparmor_parser -Q
  # echo $?
  0

  [ Where problems could occur ]

  With these changes, the parser can change its behavior based on a few things.
  1. the kernel its built against. This would not change behavior when run in a 
container vs at system level.

  2. If a feature-file is specified, via 

[Touch-packages] [Bug 1993353] Re: Add posix message queue IPC mediation

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.13.3-7ubuntu5.2

---
apparmor (2.13.3-7ubuntu5.2) focal; urgency=medium

  * Add capability upstream patches to fix LP: #1964636
- u/cap1-Generate-CAPABILITIES-in-a-script-due-to-make-4.3.patch: move
code that generates a list of capabilities to a script in common/
- u/cap2-parser-Move-to-a-pre-generated-cap_names.h.patch: use a
pre-generated list of capabilities so that all capabilities are
supported even when building against older kernels.
- u/cap3-parser-cleanup-capability_table-generation-by-droppi.patch: drop
sys_log static declaration because it's already in the generated list.
- u/cap4-parser-unify-capability-name-handling.patch: drop internal
hardcoded capability table.
- u/cap5-parser-Makefile-use-LC_ALL-C-when-invoking-sed.patch: use
LC_ALL=C when invoking sed.
- u/cap6-parser-Add-warning-to-capability_table-about-the-nee.patch: add
warning to capability_table about the need to update the Makefile.
- u/cap7-Add-CAP_BPF-and-CAP_PERFMON-to-severity.db.patch: add
support for cap_bpf and cap_perfmon
- u/cap8-parser-Makefile-fix-generated-cap-comparison-against.patch: fix
generated cap comparison against known list
  * Add upstream patches for abi support. LP: #1728130
- u/abi1-parser-feature-abi-setup-parser-to-intersect-policy-.patch: add
the ability to intersect parser and kernel features in the parser.
- u/abi2-parser-add-basic-support-for-feature-abis.patch: add support
to specify a feature abi.
- u/abi3-pin-abi-2.13.patch: add and pin a policy abi for 2.13
- u/abi4-parser-fix-abi-rule-and-pinned-feature-file-interact.patch: fix
abi rule and pinned feature file interaction
- apparmor.install: add 2.13 abi file to be installed in 
/etc/apparmor.d/abi/
  * Add mqueue patches. LP: #1993353
- u/mqueue1-parser-add-parser-support-for-message-queue-mediatio.patch:
add parser support for mqueue mediation
- u/mqueue2-tests-add-posix-message-queue-regression-tests.patch: add
posix mqueue regression tests
- u/mqueue3-utils-add-message-queue-rules-parsing-in-python-tool.patch:
add support in python tools to parse mqueue rules
- u/mqueue4-parser-add-parser-simple-tests-for-mqueue-rules.patch: add
parser simple tests for mqueue
- u/mqueue5-parser-place-perm-on-name-as-well-as-name-label-comb.patch:
add permissions on name and also on name + label
- u/mqueue6-libapparmor-add-support-for-requested-and-denied-on-.patch:
add parsing support for "denied" and "requested" from audit logs
- u/mqueue7-libapparmor-add-support-for-class-in-logparsing.patch: add
parsing support for "class" from audit logs
- u/mqueue8-utils-add-logparser-support-for-mqueue.patch: add logparser
support for mqueue rules
- u/mqueue9-tests-add-sysv-message-queue-regression-tests.patch: add
sysv mqueue regression tests
- u/mqueue10-parser-enable-mqueue-rules-when-abi-is-not-set.patch:
override pinned features for mqueue rules when abi is not set in policy.
- debian/rules: create mqueue testcase empty files for libapparmor tests.
  * Closes LP: #1994146

 -- Georgia Garcia   Mon, 10 Oct 2022
17:52:45 -0300

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

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

Title:
  Add posix message queue IPC mediation

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Focal:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  We need to add IPC mediation support in the userspace tools, starting with 
posix message queue.
  This would improve security and lower the attack surface for applications
  There is already a proposal upstream:
  https://gitlab.com/apparmor/apparmor/-/merge_requests/858

  [ Test Plan ]

  In the merge request in the description there are several tests added.
  There are parser tests that can be run with "make -C parser check" in the 
project source tree.
  There are also tests for the python tools that can be run ith "make -C utils 
check" in the project source tree.
  There are also regression tests in tests/regression/apparmor. They run with 
the whole test suite when you run with "sudo make tests", but they can also be 
run individually with "sudo ./posix_mq.sh"

  [ Where problems could occur ]

  There could be problems related to Bug 1728130, where a policy was developed 
for a set of rules supported by a specific kernel, and if new mediation is 
available on newer kernels, then there will be some denied rules. Therefore we 
need to also prevent that from happening. This is already available in 
apparmor-3.+, but for older versions could be done by backporting the abi 
patches from
  

[Touch-packages] [Bug 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

I can't reproduce this on Ubuntu MATE (though I can make other things
crash sadly).

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 1899218] Re: Incorrect warning from apparmor_parser on force complained profiles

[Andrew Lentvorski]

Also confirm.  I'm seeing the same error on an "apt upgrade":


Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
Warning from /etc/apparmor.d (/etc/apparmor.d/usr.sbin.sssd line 60): Caching 
disabled for: 'usr.sbin.sssd' due to force complain
Setting up docker-buildx-plugin (0.10.4-1~ubuntu.22.04~jammy) ...
Setting up libsnmp40:amd64 (5.9.1+dfsg-1ubuntu2.6) ...

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

Title:
  Incorrect warning from apparmor_parser on force complained profiles

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  apparmor_parser on a force complained profile produces an incorrect
  warning message:

  $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
  Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
  Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd 
line 54): Warning failed to create cache: usr.sbin.sssd

  Even though not generating the cache at all is expected, the warning
  should describe caching is disabled for force complained profiles
  instead of failure to create it.

  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  $ apt-cache policy apparmor
  apparmor:
    Installed: 3.0.0~beta1-0ubuntu6
    Candidate: 3.0.0~beta1-0ubuntu6
    Version table:
   *** 3.0.0~beta1-0ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1899218/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Bug Watch Updater]

** Changed in: firefox
   Status: New => Invalid

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340]

[Heather Ellsworth]

Hi Alexandre, I just tried on a fresh 20.04.6 vm and the issue is no
longer present.

To test this, I had to `apt purge firefox && snap install firefox` which
installed 111.0-2. xdg-desktop-portals is at version 1.6.0-1ubuntu2.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340]

[Lissyx+mozillians]

Heather, is this still happening ? This UI is the XDG Desktop Portal, so
if there is still a bug there it needs to be fixed upstream. THere is
https://launchpad.net/bugs/1949340 which was fixed in december. Can you
confirm if it is fixed on an uptodate system ?

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

cals.
#21 DRI2Authenticate (client=client@entry=0x558077415b80, 
pScreen=, magic=1)
at ../../../../../../hw/xfree86/dri2/dri2.c:1365
ds = 
dri2_client = 
primescreen = 
#22 0x558075c3eaab in ProcDRI2Authenticate (client=0x558077415b80)
at ../../../../../../hw/xfree86/dri2/dri2ext.c:156
stuff = 0x5580774347b0
rep = {type = 0 '\000', pad1 = 0 '\000', sequenceNumber = 0, 
  length = 0, authenticated = 2000771968, pad2 = 21888, 
  pad3 = 1976678512, pad4 = 21888, pad5 = 1976679392, pad6 = 21888}
pDraw = 0x5580763743a0
status = 0
#23 ProcDRI2Dispatch (client=0x558077415b80)
at ../../../../../../hw/xfree86/dri2/dri2ext.c:609
stuff = 0x5580774347b0
#24 0x558075b0cef4 in Dispatch () at ../../../../dix/dispatch.c:550
result = 
client = 0x558077415b80
start_tick = 60
#25 0x558075b10f3c in dix_main (argc=11, argv=, 
envp=) at ../../../../dix/main.c:272
i = 
alwaysCheckForInput = {0, 1}
#26 0x7f39b1223a90 in __libc_start_call_main (
main=main@entry=0x558075afa020 , argc=argc@entry=11, 
argv=argv@entry=0x7ffd9edec698)
at ../sysdeps/nptl/libc_start_call_main.h:58
self = 
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140727268853400, 
-7547088934788218713, 0, 140727268853496, 94010220794264, 
139885770768384, 7545894580288012455, 7579620698683130023}, 
  mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7ffd9edec698, 
  0x7ffd9edec698}, data = {prev = 0x0, cleanup = 0x0, 
  canceltype = -1629567336}}}
not_first_call = 
#27 0x7f39b1223b49 in __libc_start_main_impl (main=0x558075afa020 , 
argc=11, argv=0x7ffd9edec698, init=, fini=, 
rtld_fini=, stack_end=0x7ffd9edec688)
at ../csu/libc-start.c:360
No locals.
#28 0x558075afa055 in _start ()
No symbol table info available.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1

[Touch-packages] [Bug 1261211]

[contact]

EDIT:
I owe you a beer/coffee, if we ever meet.

I thought you meant reboot and not actually turning off the computer
entirely. I have the exact same behavior as you on an official Creative
Sound Blaster Z. Actually power cycling the computer seem to "fix" it
somehow. Whatever is causing this, it must be a very rare race
condition.

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

Title:
  No multichannel support on Creative CA0132

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Multichannel sound is not working on my Creative CA0132 sound card.
  Stereo is working just fine but I cannot get 5.1 to work. when I run
  'speaker-test -c 6' sound only comes out of the front 2 speakers and
  if I add '-Dsurround51' it returns "Channels count (6) not available
  for playbacks: Invalid argument". My alsa info http://www.alsa-
  project.org/db/?f=3a5ca77035da6be08769128daa43dcbc59badb93

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  somedude   1605 F lxpanel
somedude   4927 F firefox
   /dev/snd/pcmC0D0p:   somedude   4927 F...m firefox
   /dev/snd/timer:  somedude   4927 f firefox
  Date: Sun Dec 15 15:58:33 2013
  InstallationDate: Installed on 2013-12-15 (0 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z87 Professional
  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.50:bd07/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Professional:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1261211/+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 1261211]

[contact]

(In reply to Adam Stylinski from comment #9)
> Several kernels later and it still seems that randomly the port
> configuration works on boot and other times not.  It seems like maybe a race
> condition after loading the DSP firmware?  Maybe there needs to be a waiting
> period before resetting the device after the firmware download?  There's
> code in there for other chipsets that seems to suggest that's happening
> elsewhere.

I've been using a Sound Blaster Z for 2 years (from kernel 5.14) and never
experienced the issue you mentioned, but since the last kernel update
(6.1.12 I think), I completely lost surround sound. The issue surfaces in a
similar way as you, L+R only, no matter the settings in alsamixer or
speaker-test.

This is what alsa-info.sh dmesg section looks like for me:

[6.256560] snd_hda_codec_ca0132 hdaudioC3D1: autoconfig for Sound Blaster 
Z: line_outs=3 (0xb/0x11/0x10/0x0/0x0) type:line
[6.256568] snd_hda_codec_ca0132 hdaudioC3D1:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[6.256571] snd_hda_codec_ca0132 hdaudioC3D1:hp_outs=1 
(0xf/0x0/0x0/0x0/0x0)
[6.256573] snd_hda_codec_ca0132 hdaudioC3D1:mono: mono_out=0x0
[6.256574] snd_hda_codec_ca0132 hdaudioC3D1:dig-out=0xc/0xd
[6.256576] snd_hda_codec_ca0132 hdaudioC3D1:inputs:
[6.256578] snd_hda_codec_ca0132 hdaudioC3D1:  Mic=0x12
[6.256580] snd_hda_codec_ca0132 hdaudioC3D1:  Line=0x13
[6.256581] snd_hda_codec_ca0132 hdaudioC3D1:dig-in=0xe
[6.795248] snd_hda_codec_ca0132 hdaudioC3D1: ca0132 DSP downloaded and 
running

[7.202572] input: HDA Creative Mic as 
/devices/pci:80/:80:00.0/:81:00.0/sound/card3/input32
[7.264138] input: HDA Creative Line Out Front as 
/devices/pci:80/:80:00.0/:81:00.0/sound/card3/input33
[7.277203] input: HDA Creative Line Out Surround as 
/devices/pci:80/:80:00.0/:81:00.0/sound/card3/input34
[7.277332] input: HDA Creative Line Out CLFE as 
/devices/pci:80/:80:00.0/:81:00.0/sound/card3/input35
[7.277536] input: HDA Creative Front Headphone as 
/devices/pci:80/:80:00.0/:81:00.0/sound/card3/input36

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

Title:
  No multichannel support on Creative CA0132

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Multichannel sound is not working on my Creative CA0132 sound card.
  Stereo is working just fine but I cannot get 5.1 to work. when I run
  'speaker-test -c 6' sound only comes out of the front 2 speakers and
  if I add '-Dsurround51' it returns "Channels count (6) not available
  for playbacks: Invalid argument". My alsa info http://www.alsa-
  project.org/db/?f=3a5ca77035da6be08769128daa43dcbc59badb93

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  somedude   1605 F lxpanel
somedude   4927 F firefox
   /dev/snd/pcmC0D0p:   somedude   4927 F...m firefox
   /dev/snd/timer:  somedude   4927 f firefox
  Date: Sun Dec 15 15:58:33 2013
  InstallationDate: Installed on 2013-12-15 (0 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z87 Professional
  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.50:bd07/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Professional:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1261211/+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 2007837] Re: Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix available in 3.2.4

[Bug Watch Updater]

** Changed in: rsync (Debian)
   Status: Unknown => New

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

Title:
  Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix
  available in 3.2.4

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Jammy:
  Fix Released
Status in rsync package in Debian:
  New

Bug description:
  rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling,
  leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04)
  to surface [1].

  It practically makes using BackupPC 3 impossible with clients using
  rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04
  can't be used to back up machines with 22.04 is rather surprising and
  has bitten other users [2].

  It's unclear whether the bug will be fixed in 18.04's and 20.04's
  libfile-rsyncp-perl package (for status, see [3]).

  Because of this, the rsync maintainer has included a patch in 3.2.4
  that fixes this regression [4] (even though not strictly an rsync
  bug). As a result, rsync 3.2.3 is the only affected version, which
  happens to be the one packaged in 22.04.

  This report is to request backporting that fix [4] to Ubuntu 22.04, so
  that things don't silently break in scenarios where the backup server
  is left at 20.04, and some backup clients happen to upgrade to 22.04.

  I'm not sure what the criteria for security releases are, but as the
  issue causes backup denial of service and has easy mitigation, I think
  it would make sense to put it through the security channel.

  [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358
  [2]: 
https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html
  [3]: 
https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833
  [4]: 
https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 2012146] Re: very high cpu usage, system unresponsive

[Bug Watch Updater]

** Changed in: ardour (Debian)
   Status: Unknown => New

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

Title:
  very high cpu usage, system unresponsive

Status in ibus:
  Unknown
Status in ardour package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in ardour package in Debian:
  New

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/2012146/+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 2013135] [NEW] Dissapearing Mouse Cursor

[Thomas G.]

Public bug reported:

Touching the touch screen display removes the mouse cursor. It comes back after 
blindly navigating to the menu bar. This also happends randomly without 
touching the touchscreen. There doesn't appear to be a trigger for the random 
disappearances that is user input.
Thanks,

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 28 18:19:00 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc]
   Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc]
InstallationDate: Installed on 2023-02-28 (28 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: Dell Inc. Inspiron 7737
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=1322e8b8-bc4a-464a-89b8-6bc305451ff5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2013
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0H9X60
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 0.4
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd10/09/2013:br0.4:efr0.4:svnDellInc.:pnInspiron7737:pvr:rvnDellInc.:rn0H9X60:rvrA00:cvnDellInc.:ct8:cvr0.1:skuInspiron7737:
dmi.product.family: Shark Bay ULT
dmi.product.name: Inspiron 7737
dmi.product.sku: Inspiron 7737
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

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

Title:
  Dissapearing Mouse Cursor

Status in xorg package in Ubuntu:
  New

Bug description:
  Touching the touch screen display removes the mouse cursor. It comes back 
after blindly navigating to the menu bar. This also happends randomly without 
touching the touchscreen. There doesn't appear to be a trigger for the random 
disappearances that is user input.
  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 28 18:19:00 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc]
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc]
  InstallationDate: Installed on 2023-02-28 (28 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  

[Touch-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Bug Watch Updater]

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

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[hyc]

One last note - playing a particular video clip (Star Trek Strange New
Worlds S01E10), the opening splash sequence, the maximum loudness in
Linux was only 65dB, and 78dB in Windows. Volume control set to 100% in
both cases, identical video file.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[cam]

Here's a thread where people are expressing their dissatisfaction with Lenovo's 
support of Linux on their Legion series laptops. Maybe if enough people chime 
in, they'll take us seriously and we'll get somewhere. I personally don't 
need/want formalized Linux support... I just want the hardware to work:
https://forums.lenovo.com/t5/Ubuntu/Ubuntu-and-legion-pro-7-16IRX8H-audio-issues/m-p/5210709

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[hyc]

Hey again, sorry I just now noticed this: on my 2021 Legion 7 16ACHg6,
the sound from the left speaker is much quieter than from the right
speaker. Is there anything I can tweak to adjust this?

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[cam]

Looking more closely at your alsa-info... You have: 
/sys/bus/acpi/devices/CLSA0102:00/status

I didn't even know the CLSA0102 existed! Just the CLSA0100 and the 
CLSA0101. I don't think that's supported at all at this point. You might 
try reaching out to Cirrus Logic. I think that's your best bet. There's 
certainly nothing I can do. Sounds like the CLSA0102 's are strictly for 
your the woofers?

CLSA0102 is almost certainly going to fall under cs35l41 and like the 
CLSA010/1, it would likely need a custom code path.

Really wish Lenovo would play more nice with us. Yes, they have Linux 
specific offerings, but like most of you, I'm not interested in those. 
And in case anyone from Lenovo is listening... I'm not personally 
interested in getting ANY Lenovo support for Linux. I just want my 
hardware to work.

On 3/4/23 03:39, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #751 from oppsig (toggiwo...@gmail.com) ---
> Hey Cameron, I did apply the patch against kernel 6.2.2 for the 14ACN6.
> There was sound from the 2 tweeters as before the patch was applied but still
> I
> don't know if the 2 woofers are actually active?
> Not sure what the best way to find out if woofers are working.
> Is there anything I can do with speaker-test?
> But I'll try to compare before and after patch.
>
> I was going to try to sniff the verbs for this laptop but the problem is that
> the audio controllers are on the same IOMMU groups as radeon gpu, pci, usb
> and
> psp.
> So I cannot not passthrough the audio devices without ACL override.
>
> Uname -a
> Linux 6.2.2-273-tkg-cfs #1 SMP PREEMPT_DYNAMIC TKG Sat, 04 Mar 2023 08:30:30
> + x86_64 GNU/Linux
>
> Alsa info:
> http://alsa-project.org/db/?f=f1d466ea0cfa556f461b73a529bba4a66d634725
>
> Dmesg:
> ❯ sudo dmesg | grep -E '(csc3551|cs35l41|reset_gpio|short|adev|speaker)'
> [0.654315] IPI shorthand broadcast: enabled
> [   19.026160] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC287:
> line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
> [   19.026199] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0
> (0x0/0x0/0x0/0x0/0x0)
> [   23.866865] wlan0: VHT capa missing/short, disabling VHT/HE/EHT
> [  200.121348] wlan0: VHT capa missing/short, disabling VHT/HE/EHT
> [  271.290659] wlan0: VHT capa missing/short, disabling VHT/HE/EHT
>
> bugid for this laptop:
> https://bugzilla.kernel.org/show_bug.cgi?id=215632
>

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

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

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

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

  uname -r
  5.11.0-44-generic

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

[Touch-packages] [Bug 1958019]

[toggiworks]

Hey Cameron, I did apply the patch against kernel 6.2.2 for the 14ACN6.
There was sound from the 2 tweeters as before the patch was applied but still I 
don't know if the 2 woofers are actually active?
Not sure what the best way to find out if woofers are working.
Is there anything I can do with speaker-test?
But I'll try to compare before and after patch.

I was going to try to sniff the verbs for this laptop but the problem is that 
the audio controllers are on the same IOMMU groups as radeon gpu, pci, usb and 
psp.
So I cannot not passthrough the audio devices without ACL override.

Uname -a
Linux 6.2.2-273-tkg-cfs #1 SMP PREEMPT_DYNAMIC TKG Sat, 04 Mar 2023 08:30:30 
+ x86_64 GNU/Linux

Alsa info:
http://alsa-project.org/db/?f=f1d466ea0cfa556f461b73a529bba4a66d634725

Dmesg:
❯ sudo dmesg | grep -E '(csc3551|cs35l41|reset_gpio|short|adev|speaker)'
[0.654315] IPI shorthand broadcast: enabled
[   19.026160] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC287: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   19.026199] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   23.866865] wlan0: VHT capa missing/short, disabling VHT/HE/EHT
[  200.121348] wlan0: VHT capa missing/short, disabling VHT/HE/EHT
[  271.290659] wlan0: VHT capa missing/short, disabling VHT/HE/EHT

bugid for this laptop:
https://bugzilla.kernel.org/show_bug.cgi?id=215632

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[pierrox]

(In reply to Cameron Berkenpas from comment #746)

> Please share the following outputs with me:
> uname -a

Linux shin 6.2.1-arch1-1-custom #1 SMP PREEMPT_DYNAMIC Tue, 28 Feb 2023
09:19:31 + x86_64 GNU/Linux

> And mostly I need this:
> dmesg | egrep -i '(csc3551|cs35l41|reset_gpio|short|adev|speaker)'

[8.047665] Serial bus multi instantiate pseudo device driver CSC3551:00: 
error -ENOENT: Error requesting irq at index 0
[8.052566] Serial bus multi instantiate pseudo device driver: probe of 
CSC3551:00 failed with error -2
[8.331024] input: PC Speaker as /devices/platform/pcspkr/input/input5
[   11.421129] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   11.421138] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)

I'll ask Cirrus developers about the issue.

Agreed, this thread is too long.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[cam]

See https://bugzilla.kernel.org/show_bug.cgi?id=216194 for a new patch.
Currently the latest is  lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b-002.patch

This latest patch theoretically has support for Blake Lee's machine.

A new revision of the 16IAX7.

oppsig's Yoga Slim 7 Carbon 14ACN6

Pierre Hébert,

I missed that you were getting this error previous: "Serial bus multi
instantiate pseudo device driver CSC3551:00: error -ENOENT: Error
requesting irq at index 0"

That is indeed occurring before any of my code. Some hopefully good news
is that this is a Cirrus Logic issue that they might fix if you can
report it to them. Once fixed, you'd probably still need a patch such as
mine to get you over the finish line.

PLEASE READ MY COMMENT HERE AS THIS PATCH IS USE AT-YOUR-OWN-RISK:
https://bugzilla.kernel.org/show_bug.cgi?id=216194#c66

From here on out, I will direct people to bug
https://bugzilla.kernel.org/show_bug.cgi?id=216194 as there's far too
many posts in this thread and it's made things difficult to keep track
of.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[jmaximusix]

(In reply to Pierre Hébert from comment #741)
> I'm not too sure that this worked for the slim variant of the legion 7 gen
> 7, or at least jmaximusix, who uses a slim 7 too, doesn't seem to have it
> working neither (https://bugzilla.kernel.org/show_bug.cgi?id=216194#c49).
> Also I get the very same error message regarding CSC3551 (where the serial
> multi-instanciate driver fails to get an irq in smi_i2c_probe).
> 
> I applied lenovo-7i-gen7-sound-6.2.0-rc3-0.0.4.patch and I have no doubt
> that the path is active in the currently running kernel. Unfortunately this
> is the only thing I know for sure, I'm sorry to be quite ignorant in most
> other areas regarding sound and amplifiers in Linux :-/

Yes exactly, I have the same laptop and the same issue. If you find any 
solution, be sure to let me know, and so will I! :D
I think I might be able to clear up some confusion around a patch existing or 
not. Cameron Berkenpas did try to add support for the Slim 7i using some logs I 
provided, but that didn't turn out fixing the csc3551 error. So thats why, I 
think, in his patch, the Slim 7i model (16IAH7) is listed, but it's not 
working, at least I am unaware of any success anybody had with it.

I have more or less given up on this for now, because at least with my
(nonexistent) knowledge of this stuff, I don't see anything in my power
I can do. But if anybody has ideas what to try or where to look, I'll
happily try it out.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[toggiworks]

Hello Cameron.
Do you think this patch for Slim 7 AMD versions be viable for Yoga Slim 7 
Carbon 14ACN6 as well?

Subsystem Id: 0x17aa3856
http://alsa-project.org/db/?f=256bbaf062611cf8f537a377104273142f99d2f1
https://psref.lenovo.com/Detail/Yoga/Yoga_Slim_7_Carbon_14ACN6?M=82L0005RMX

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[cam]

The name doesn't matter, just the numeric ID. If I had a patch worth 
submitting, I would fix the names but otherwise they don't matter.

Please share the following outputs with me:
uname -a

And mostly I need this:
dmesg | egrep -i '(csc3551|cs35l41|reset_gpio|short|adev|speaker)'

On 2/28/23 23:47, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #745 from Pierre Hébert (pier...@pierrox.net) ---
> Yes, I confirm that the patch includes the slim 7 in the list of fixups, with
> the right "16IAH7" model number and right numeric id: 0x17aa:0x3803 (same as
> my
> alsa-info), so I thought there was some success for this computer. But
> rewinding the discussion to the top in this thread and the other one
> (https://bugzilla.kernel.org/show_bug.cgi?id=216194) doesn't show any
> evidence
> of success for the "slim" variant. Or maybe I missed it?
> I noticed that the clear text name for the entry in the patch is named
> "Legion
> 7" not "Legion S7". Maybe there's some mismatch here? I mean: could the slim
> references have been used in place of another model, maybe another 7 variant?
> Lenovo's naming scheme is confusing: there's the 7, the 7i, the 7 Pro and the
> S7 which is either named S7 (without "i" no matter Intel or AMD) or Slim 7
> (only AMD) or Slim 7i (only Intel).
>
> I understand the issue with DSD and why it's frustrating. This isn't by far
> the
> first frustration I get with this kind of issue... But fortunately these
> little
> issues are more than balanced by the benefits of running Linux :-)
>
> Using 6.2.1 on my slim 7i (16IAH7), the cs35l41 driver fails to load. If my
> understanding is correct, this will prevent code in the patch to be executed,
> even if some code paths in cs35l41 are bypassed by the patch, right? Please
> correct me if I'm wrong, as really I'm a newbie in this area.
>
> I'm 100% sure that the patch is applied though, but I don't see the related
> printk in the kernel log (in particular there is no "CSC3551: probing"). What
> I
> am trying to understand is whether this is because of the cs35l41 error, and
> in
> which case I should look into this issue first, or whether this is due to
> another problem.
>
> While unloading and reloading cs35l41 modules (snd_hda_scodec_cs35l41_i2c
> snd_hda_scodec_cs35l41_spi snd_hda_scodec_cs35l41 snd_soc_cs35l41_lib
> snd_hda_cs_dsp_ctls cs_dsp), there's no indication of the driver being
> initialized again in kernel logs, so my guess is that this is triggered by
> another sound module. Would you have any hint on a what should be done to
> unload/reload the sound subsystem and avoid reboot between each code
> modification/build?
>
> Thank you so far for the help and the patches. Even if I cannot ever hear
> sound
> from the speakers (and I can perfectly live with this), your work is really
> appreciated!
>
>
> (In reply to Cameron Berkenpas from comment #742)
>> You have the slim? I don't think I added slim support to the patch. I think
>> someone else did and it worked.
>>
>> It's not that hard to do. The numeric ID you need can be found in your
>> alsa-info.

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

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

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

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

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   

[Touch-packages] [Bug 1958019]

[pierrox]

Yes, I confirm that the patch includes the slim 7 in the list of fixups, with 
the right "16IAH7" model number and right numeric id: 0x17aa:0x3803 (same as my 
alsa-info), so I thought there was some success for this computer. But 
rewinding the discussion to the top in this thread and the other one 
(https://bugzilla.kernel.org/show_bug.cgi?id=216194) doesn't show any evidence 
of success for the "slim" variant. Or maybe I missed it?
I noticed that the clear text name for the entry in the patch is named "Legion 
7" not "Legion S7". Maybe there's some mismatch here? I mean: could the slim 
references have been used in place of another model, maybe another 7 variant? 
Lenovo's naming scheme is confusing: there's the 7, the 7i, the 7 Pro and the 
S7 which is either named S7 (without "i" no matter Intel or AMD) or Slim 7 
(only AMD) or Slim 7i (only Intel).

I understand the issue with DSD and why it's frustrating. This isn't by
far the first frustration I get with this kind of issue... But
fortunately these little issues are more than balanced by the benefits
of running Linux :-)

Using 6.2.1 on my slim 7i (16IAH7), the cs35l41 driver fails to load. If
my understanding is correct, this will prevent code in the patch to be
executed, even if some code paths in cs35l41 are bypassed by the patch,
right? Please correct me if I'm wrong, as really I'm a newbie in this
area.

I'm 100% sure that the patch is applied though, but I don't see the
related printk in the kernel log (in particular there is no "CSC3551:
probing"). What I am trying to understand is whether this is because of
the cs35l41 error, and in which case I should look into this issue
first, or whether this is due to another problem.

While unloading and reloading cs35l41 modules
(snd_hda_scodec_cs35l41_i2c snd_hda_scodec_cs35l41_spi
snd_hda_scodec_cs35l41 snd_soc_cs35l41_lib snd_hda_cs_dsp_ctls cs_dsp),
there's no indication of the driver being initialized again in kernel
logs, so my guess is that this is triggered by another sound module.
Would you have any hint on a what should be done to unload/reload the
sound subsystem and avoid reboot between each code modification/build?

Thank you so far for the help and the patches. Even if I cannot ever
hear sound from the speakers (and I can perfectly live with this), your
work is really appreciated!


(In reply to Cameron Berkenpas from comment #742)
> You have the slim? I don't think I added slim support to the patch. I think
> someone else did and it worked.
> 
> It's not that hard to do. The numeric ID you need can be found in your
> alsa-info.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

[Touch-packages] [Bug 1958019]

[cam]

Created attachment 303815
attachment-24448-0.html

Uploaded lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b.patch to 
https://bugzilla.kernel.org/show_bug.cgi?id=216194

Although I forgot to update it in the patch name... This patch is 
against 6.2.1

I put a disclaimer that this is a use-at-your-own-risk as the missing 
settings were guessed for the full-sized Legion 7i, and it appears the 
the Legion 7i has been working without issue since August or so without 
any serious issues developing.

The previous patch includes 7i Slim support and it seems this has been 
working for some people... If you've been using my patches for the 7i 
Slim, I would like to hear if things are still working for you without 
issue. With that feedback other 7i Slim users will be able to make an 
informed decision on the use of these patches.

This updated patch adds support for the Slim 7 (AMD version). Same thing 
stands. If there are serious issues such as perhaps loudness, distorted 
sound, "amp short" messages in dmesg (when this happens the affected 
speaker will no longer output sound), etc, I suggest to stop using the 
patch to avoid the possibility of permanent damage (as well as following 
up with your issues).

Since the 1-2 reports I saw that it seemed to work okay for the Slim 7i, 
I suspect it will for the AMD based Slim 7 as well, but I can't make any 
guarantees.

And finally... I did work on overriding the ACPI DSD table to get sound 
working months back... While I did have some initial success, I was 
running into "AMP short" issues. My patch was originally based on an 
older version of the cs35l41 support and so it actually ends up 
bypassing some of the code paths used in the current CS35l41 driver. If 
I change the driver to go through that newer path, it has approximately 
the same problems that using a DSD override does. So it seems my patch 
works because it's "cheating" somehow due to historical reasons...

Probably the info I use in the DSD override is very slightly off from 
what's needed, but if the issues could be ironed out... We'd have a 
solution that didn't require patching the kernel. However, we'd still be 
left with the problem of determining safe values and the values are 
(more or less) going to be specific to your model of laptop.

This is why it's so frustrating that Lenovo won't add this info in a 
BIOS update where as my understanding is that Asus has, in at least a 
few cases, added these DSD entires in BIOS updates to get sound working 
under Linux. As I no longer require my laptop to specifically have a 
more professional Lenovo look, my next laptop will likely be Asus.

Like many of you, Linux is my daily driver (and has been since the late 
90's in my case). But being able to boot to Windows to play games with 
advanced optimus, some mild HDR support, etc... has been really great.

Anyway, looking forward to the feedback.

On 2/28/23 11:56, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #743 from Blake Lee (blake99...@gmail.com) ---
> (In reply to Cameron Berkenpas from comment #742)
>> You have the slim? I don't think I added slim support to the patch. I think
>> someone else did and it worked.
>>
>> It's not that hard to do. The numeric ID you need can be found in your
>> alsa-info.
> Hi Cameron, I'm trying to get my Legion Slim 7 Gen 7 AMD version working...
> How
> do I modify the patch, or are you planning to? My alsa-info is below..
>
> http://alsa-project.org/db/?f=3c10f6ee9607eabbc8f783505b7b29c87b7d0cca
>
> Thank you for being so helpful to everyone, this is a great computer I'm just
> sick of using headphones lol
>

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

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

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

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

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: 

[Touch-packages] [Bug 1958019]

[blake99lee]

(In reply to Cameron Berkenpas from comment #742)
> You have the slim? I don't think I added slim support to the patch. I think
> someone else did and it worked.
> 
> It's not that hard to do. The numeric ID you need can be found in your
> alsa-info.

Hi Cameron, I'm trying to get my Legion Slim 7 Gen 7 AMD version
working... How do I modify the patch, or are you planning to? My alsa-
info is below..

http://alsa-project.org/db/?f=3c10f6ee9607eabbc8f783505b7b29c87b7d0cca

Thank you for being so helpful to everyone, this is a great computer I'm
just sick of using headphones lol

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[pierrox]

I'm not too sure that this worked for the slim variant of the legion 7 gen 7, 
or at least jmaximusix, who uses a slim 7 too, doesn't seem to have it working 
neither (https://bugzilla.kernel.org/show_bug.cgi?id=216194#c49).
Also I get the very same error message regarding CSC3551 (where the serial 
multi-instanciate driver fails to get an irq in smi_i2c_probe).

I applied lenovo-7i-gen7-sound-6.2.0-rc3-0.0.4.patch and I have no doubt
that the path is active in the currently running kernel. Unfortunately
this is the only thing I know for sure, I'm sorry to be quite ignorant
in most other areas regarding sound and amplifiers in Linux :-/

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[cam]

You have the slim? I don't think I added slim support to the patch. I
think someone else did and it worked.

It's not that hard to do. The numeric ID you need can be found in your
alsa-info.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[cam]

As the 6.1.x kernel worked, likely something else isn't quite right.

Are you sure you're running your patched kernel? Which patch did you
apply?

On 2/28/23 06:00, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #739 from Pierre Hébert (pier...@pierrox.net) ---
> (In reply to Cameron Berkenpas from comment #737)
>
> With Linux 6.2.1, I get the same error "Serial bus multi instantiate pseudo
> device driver CSC3551:00: error -ENOENT: Error requesting irq at index 0". I
> guess your patch is not reached at all then.
>
> If I understand correctly, this is somewhat unrelated to this original bug,
> maybe I should look further around CS35L41 and/or serial multi-instantiate
> driver?
>

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[pierrox]

(In reply to Cameron Berkenpas from comment #737)

With Linux 6.2.1, I get the same error "Serial bus multi instantiate
pseudo device driver CSC3551:00: error -ENOENT: Error requesting irq at
index 0". I guess your patch is not reached at all then.

If I understand correctly, this is somewhat unrelated to this original
bug, maybe I should look further around CS35L41 and/or serial multi-
instantiate driver?

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[pierrox]

Thank you very much for the link! I missed this other discussion.
It doesn't work yet with my current 6.1.12 kernel (although the patch applies 
quite nicely) but I'll give it a try soon.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[cam]

For details around why this doesn't work as well as a use at your own 
risk patch (which SO FAR has proven safe), look here:
https://bugzilla.kernel.org/show_bug.cgi?id=216194

The short short version is that Lenovo has zero interest in adding 
entries in a BIOS update that would allow sound to work out of the box.

On 2/27/23 07:12, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> Pierre Hébert (pier...@pierrox.net) changed:
>
> What|Removed |Added
> 
>   CC||pier...@pierrox.net
>
> --- Comment #736 from Pierre Hébert (pier...@pierrox.net) ---
> I own a Lenovo Legion Slim 7 Intel 16IAH7 with the same issue (no speaker
> sound
> but headphones ok).
>
> Alsa-info for this particular machine can be found here:
> http://www.alsa-project.org/db/?f=9f1deb511b2604f1b52a7905889deb4463ca9211.
>
> Would these alsa-info be enough for someone to create a patch for this model?
> If not, I'm ok to spend some time on the issue. I have no particular
> knowledge
> on how fixups are implemented but patching and compiling the kernel is not an
> issue. Probably I can take example on existing fixups to implement a new one.
> If so, some pointer on documentation or resource on where to start would be
> much appreciated.
>

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1958019]

[pierrox]

I own a Lenovo Legion Slim 7 Intel 16IAH7 with the same issue (no
speaker sound but headphones ok).

Alsa-info for this particular machine can be found here:
http://www.alsa-
project.org/db/?f=9f1deb511b2604f1b52a7905889deb4463ca9211.

Would these alsa-info be enough for someone to create a patch for this
model? If not, I'm ok to spend some time on the issue. I have no
particular knowledge on how fixups are implemented but patching and
compiling the kernel is not an issue. Probably I can take example on
existing fixups to implement a new one. If so, some pointer on
documentation or resource on where to start would be much appreciated.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE

[Bug Watch Updater]

** Changed in: python3.7 (Debian)
   Status: New => Fix Released

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

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

Title:
  Python interpreter binary is not compiled as PIE

Status in Python:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.10 package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.6 package in Ubuntu:
  Won't Fix
Status in python3.7 package in Ubuntu:
  Won't Fix
Status in python3.8 package in Ubuntu:
  Won't Fix
Status in python3.9 package in Ubuntu:
  Won't Fix
Status in python3.7 package in Debian:
  Fix Released
Status in python3.8 package in Debian:
  New

Bug description:
  The python2.7 binary (installed at /usr/bin/python2.7; package version
  2.7.6-8) is not compiled as a position independent executable (PIE).
  It appears that the python compilation process is somewhat arcane and
  the hardening wrapper probably doesn't do the trick for it.

  This is incredibly dangerous as it means that any vulnerability within
  a native module (e.g. ctypes-based), or within python itself will
  expose an incredibly large amount of known memory contents at known
  addresses (including a large number of dangerous instruction
  groupings). This enables ROP-based
  (https://en.wikipedia.org/wiki/Return-oriented_programming) to abuse
  the interpreter itself to bypass non-executable page protections.

  I have put together an example vulnerable C shared object (with a buffer 
overflow) accessed via python through the ctypes interface as an example. This 
uses a single ROP "gadget" on top of using the known PLT location for system(3) 
(https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example 
code is accessible at:
  - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367

  I'm not exactly familiar enough with the python build process to say
  where exactly an -fPIE needs to be injected into a script/makefile,
  but I feel that given the perceived general preference for ctypes-
  based modules over python written ones, as the native code
  implementations tend to be more performant, this feels like a large
  security hole within the system. Given the nature of this "issue," I'm
  not 100% sure of where it is best reported, but from what I can tell,
  this conflicts with the Ubuntu hardening features and is definitely
  exploitable should a native module contain a sufficiently exploitable
  vulnerability that allows for control of the instruction register.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1452115/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

And there's more random crashes. (xiccd being the next one to go kaput)
All of this in a pure QEMU VM.

My guess is xfce4-power-manager crashes thanks to GLib and that takes
down other stuff at random. Not sure how that would be triggered by the
third-party software option, but that's what I'm seeing here.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

Hmm, and now xfce4-power-manager.

Looking at the stacktrace when xfce4-power-manager goes awry, it's
GLib's fault. Which means we probably have another slice allocator
removal causing problems.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Islam]

It is different issue than the one reported in #44.

So if the fix is released for Kinetic, when it should be available in
the repository for upgrade?

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

I notice a blueman-applet crash when I reproduce this.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 2013071] Re: Session crash after initial login

[Launchpad Bug Tracker]

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

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

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]

[Bug Watch Updater]

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

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

Title:
  Periodic black frames and stutter [Failed to post KMS update:
  drmModeAddFB does not support format 'AR24' (0x34325241)]

Status in Mesa:
  Fix Released
Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Every so often, the desktop will go black and then re appear on Ubuntu
  22.10 Wayland Session which should not be occurring (this does not
  happen on 22.04.) Note that only the cursor can be seen.

  Reporting this before release so that it can be patched for (at least)
  the RasPi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
  Uname: Linux 5.19.0-1001-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 16:10:37 2022
  DisplayManager: gdm3
  ImageMediaBuild: 20220826
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1988859/+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 2012788] Re: Entering Unicode characters with code points broken

[Bug Watch Updater]

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

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

Title:
  Entering Unicode characters with code points broken

Status in ibus:
  New
Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/2012788/+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 2004264] Re: FTBFS against glibc 2.37

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=30065.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-01-31T15:55:16+00:00 Simon Chopin wrote:

I did some tests on master (2f39e44a84) for the upcoming 2.37 release,
and I found a regression in libunistring test suite on amd64 with AVX-2
instructions, more specifically on gnulib's test-strncat. It can be
reproduced using these instructions:

https://sourceware.org/glibc/wiki/Testing/Gnulib


I bisected the issue to
commit 642933158e7cf072d873231b1a9bb03291f2b989
Author: Noah Goldstein 
Date:   Tue Nov 8 17:38:39 2022 -0800

x86: Optimize and shrink st{r|p}{n}{cat|cpy}-avx2 functions

Optimizations are:
1. Use more overlapping stores to avoid branches.
2. Reduce how unrolled the aligning copies are (this is more of a
   code-size save, its a negative for some sizes in terms of
   perf).
3. For st{r|p}n{cat|cpy} re-order the branches to minimize the
   number that are taken.

I get the following backtrace:

#0  __strncat_avx2 () at ../sysdeps/x86_64/multiarch/strncat-avx2.S:76
#1  0x55d7 in strncat (__len=0, __src=0x77de4000 "", 
__dest=0xc2a1 "") at /tmp/glibc-dev/include/bits/string_fortified.h:138
#2  check_single (input=input@entry=0x77de4000 "", n=n@entry=0, length=90) 
at unistr/test-strncat.h:41
#3  0x5352 in check (input=0x9100  "Grüß Gott. 
Здравствуйте! x=(-b±sqrt(b²-4ac))/(2a)  日本語,中文,한글", input_length=91)
at unistr/test-strncat.h:86
#4  main () at test-strncat.c:58

I'm out of my depth in the assembler code.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/2004264/comments/1


On 2023-01-31T19:41:55+00:00 Goldstein-w-n wrote:

(In reply to Simon Chopin from comment #0)
> I did some tests on master (2f39e44a84) for the upcoming 2.37 release, and I
> found a regression in libunistring test suite on amd64 with AVX-2
> instructions, more specifically on gnulib's test-strncat. It can be
> reproduced using these instructions:
> 
> https://sourceware.org/glibc/wiki/Testing/Gnulib

Those directions seem a bit outdated, any chance you can share your
build steps?

> 
> 
> I bisected the issue to
> commit 642933158e7cf072d873231b1a9bb03291f2b989
> Author: Noah Goldstein 
> Date:   Tue Nov 8 17:38:39 2022 -0800
> 
> x86: Optimize and shrink st{r|p}{n}{cat|cpy}-avx2 functions
> 
> Optimizations are:
> 1. Use more overlapping stores to avoid branches.
> 2. Reduce how unrolled the aligning copies are (this is more of a
>code-size save, its a negative for some sizes in terms of
>perf).
> 3. For st{r|p}n{cat|cpy} re-order the branches to minimize the
>number that are taken.
> 
> I get the following backtrace:
> 
> #0  __strncat_avx2 () at ../sysdeps/x86_64/multiarch/strncat-avx2.S:76
> #1  0x55d7 in strncat (__len=0, __src=0x77de4000 "",
> __dest=0xc2a1 "") at
> /tmp/glibc-dev/include/bits/string_fortified.h:138
> #2  check_single (input=input@entry=0x77de4000 "", n=n@entry=0,
> length=90) at unistr/test-strncat.h:41
> #3  0x5352 in check (input=0x9100  "Grüß Gott.
> Здравствуйте! x=(-b±sqrt(b²-4ac))/(2a)  日本語,中文,한글", input_length=91)
> at unistr/test-strncat.h:86
> #4  main () at test-strncat.c:58
> 
> I'm out of my depth in the assembler code.

So far unable to reproduce, haven't been able to build gnulib against
installed GLIBC, but pulled out the u8/u32 strncat and tested them both.

As well have done exhaustive strncat/wcsncpy at the end of page
(exhaustive for len {0..128} with all alignments {4096-128...4095} for
s1/s2. So far unable to reproduce. Maybe the issue is uninitialized
register.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/2004264/comments/3


On 2023-01-31T20:09:11+00:00 Goldstein-w-n wrote:

(In reply to Simon Chopin from comment #0)
> I did some tests on master (2f39e44a84) for the upcoming 2.37 release, and I
> found a regression in libunistring test suite on amd64 with AVX-2
> instructions, more specifically on gnulib's test-strncat. It can be
> reproduced using these instructions:
> 
> https://sourceware.org/glibc/wiki/Testing/Gnulib
> 
> 
> I bisected the issue to
> commit 642933158e7cf072d873231b1a9bb03291f2b989
> Author: Noah Goldstein 
> Date:   Tue Nov 8 17:38:39 2022 -0800
> 
> x86: Optimize and shrink st{r|p}{n}{cat|cpy}-avx2 functions
> 
> Optimizations are:
> 1. Use more overlapping 

[Touch-packages] [Bug 1960736] Re: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 )

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1820348.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-03-04T16:42:51+00:00 Bartłomiej Żogała wrote:

Steps to reproduce:

I've faced an issue with all browsers relying in libnss refusing ever X.509 
certificate. I've hard time to debug it through months due to not enough 
information returned from libnss. It was in detail described here:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1960736


Actual results:

Root issue is that libnss returned 
[23391:23426:0213/133531.202486:ERROR:nss_util.cc(286)] After loading Root 
Certs, loaded==false: NSS error code: -8018
In my case the root cause was poor quality code written by local government 
agency known for infringing LGPG licence. The configuration change was deployed 
when installing their PKCS#11 related software and lack of proper debug from 
Libnss cause I was not able to connect cause and the effect.


Expected results:

Instead of displaying code which couldn't be googled NSS should return
full human readable error name ' SEC_ERROR_UNKNOWN_PKCS11_ERROR' - in
way it does for other errors of same kind.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1960736/comments/8


On 2023-03-07T20:01:34+00:00 Dkeeler wrote:

This is a bug in Chromium, not NSS. You can file a bug here:
https://bugs.chromium.org/p/chromium/issues/list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1960736/comments/10


** Changed in: nss
   Status: Unknown => Invalid

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

Title:
  Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly  ( NSS
  error code: -8018 )

Status in NSS:
  Invalid
Status in nss package in Ubuntu:
  New

Bug description:
  I've got the issue with Google Chrome not recognizing any of SSL/TSL 
certificates as trusted. When I look into certificate checksums it's renders 
all bytes of it as NULL bytes. I'm aware Google Chrome is proprietary but it 
depends on ubuntu provided libnss3-package. And libnss provides very nigmatic 
error code -8018:
  `/opt/google/chrome$ google-chrome
  [23391:23426:0213/133531.202486:ERROR:nss_util.cc(286)] After loading Root 
Certs, loaded==false: NSS error code: -8018
  [23434:23434:0213/133531.266711:ERROR:sandbox_linux.cc(377)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [23391:23427:0213/133531.313065:ERROR:cert_verify_proc_builtin.cc(681)] 
CertVerifyProcBuiltin for accounts.google.com failed:
  - Certificate i=3 (CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign 
nv-sa,C=BE) -
  ERROR: No matching issuer found

  '
  When trying to enter this particular error code into search engine nothing is 
found. So my suggestion with this bug is to make it more transparent by 
providing information to what happened - it seems other bug codes has better 
error messages. To get SEC_ERROR_UNKNOWN_PKCS11_ERROR string I was force to 
download source code and manually calculate offsets. Another issue is if 
failing to initialize PKCS11 token should make whole SSL/TLS crypto invalid ? 
I'm not sure if this is libnss or Google Chrome issue but it behaves 
differently in Chromium browser with same libnss so I assume either of two is 
doing better - it's worth to review this from security perspective.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libnss3 2:3.35-2ubuntu2.13
  Uname: Linux 5.10.0-051000rc6-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 13 13:33:51 2022
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1.5 [origin: LP-PPA-ubuntu-security-proposed]
   libgcc1 1:8.4.0-1ubuntu1~18.04
   libnspr4 2:4.18-1ubuntu1
   libsqlite3-0 3.22.0-1ubuntu0.4
  InstallationDate: Installed on 2015-05-08 (2473 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nss
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (1266 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nss/+bug/1960736/+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 344814] Re: Synthetic emboldening/italic/italic-bold fails for single-styled fonts

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => Invalid

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Invalid
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/344814/+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 344814]

[Daniel Holbert]

Given that this bug was from over a decade ago, and we've done
substantial printing improvements & re-investigations over the past few
years which could conceivably have fixed this, and this hasn't come up
recently, I think we can consider this "worksforme" at this point.

(It sounds like comment 24 had a strong suspicion that there was a
particular cairo change that would've fixed this over 5 years ago, too;
and this has been mostly silent since then.)

If anyone can still reproduce a version of this bug (bold text missing
on Linux), it's probably best to track that in a new bug at this point,
since there's a good likelihood it'd be a new/different issue from what
was originally going on here.

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Invalid
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/344814/+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 1933775]

[Redi]

N.B. you can use -DTBB_SUPPRESS_DEPRECATED_MESSAGES=1 to suppress the
warning.

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

Title:
  libgcc-s1 and libstdc++6 depend on broken libtbb2 package

Status in gcc:
  In Progress
Status in tbb package in Ubuntu:
  New

Bug description:
  The gcc-11 source package produces libgcc-s1 and (I think?)
  libstdc++6. Both of these binary packages on Hirsute depend on libtbb2
  version 2020.3-1. The latter contains deprecated APIs that create
  #pragma generated warnings whenever  is included.

  See upstream for discussion:

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1933775/+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 2013128] [NEW] [feature request] Upgrade libglx-mesa0

[David Vereb]

Public bug reported:

Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

I was directed to report this bug via my question at
answers.launchpad.net/ubuntu:
https://answers.launchpad.net/ubuntu/+question/705988

Please let me know if you need further information.  Thanks!


 > lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04

 > apt-cache policy libglx-mesa0
libglx-mesa0:
  Installed: 22.2.5-0ubuntu0.1~22.04.1
  Candidate: 22.2.5-0ubuntu0.1~22.04.1
  Version table:
 *** 22.2.5-0ubuntu0.1~22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 22.0.1-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: i3
Date: Tue Mar 28 15:30:59 2023
InstallationDate: Installed on 2022-04-28 (334 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

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


** Tags: amd64 apport-bug jammy

** Summary changed:

- Upgrade libglx-mesa0
+ [feature request] Upgrade libglx-mesa0

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

Title:
  [feature request] Upgrade libglx-mesa0

Status in mesa package in Ubuntu:
  New

Bug description:
  Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
  bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

  I was directed to report this bug via my question at
  answers.launchpad.net/ubuntu:
  https://answers.launchpad.net/ubuntu/+question/705988

  Please let me know if you need further information.  Thanks!

  
   > lsb_release -rd
  Description: Ubuntu 22.04.2 LTS
  Release: 22.04

   > apt-cache policy libglx-mesa0
  libglx-mesa0:
Installed: 22.2.5-0ubuntu0.1~22.04.1
Candidate: 22.2.5-0ubuntu0.1~22.04.1
Version table:
   *** 22.2.5-0ubuntu0.1~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Tue Mar 28 15:30:59 2023
  InstallationDate: Installed on 2022-04-28 (334 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2013128/+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 977526] Re: Manpage makes erroneous claim about BROWSER documentation

[Bug Watch Updater]

** Changed in: sensible-utils (Debian)
   Status: Unknown => Fix Released

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

Title:
  Manpage makes erroneous claim about BROWSER documentation

Status in sensible-utils package in Ubuntu:
  Fix Released
Status in sensible-utils package in Debian:
  Fix Released

Bug description:
  sensible-editor(1) (and other programs in sensible-utils) in the ‘SEE
  ALSO’ section of the manpagesays:

    Documentation  of  the  EDITOR, VISUAL, PAGER, and BROWSER variables
  in environ(7)

  But environ(7) doesn't actually make any mention at all of BROWSER, so
  looking there is of little help in determining how to set the
  preferred browser, so that mention should be removed.

  What would be useful is to document that sensible-browser by default
  tries gnome-www-browser, x-www-browser, or www-browser (depending on
  whether it's running under Gnome, X, or neither), and so the browser
  choice can be set with update-alternatives(8).

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/977526/+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 2000817] Re: Wrong SHA256-value computed on kinetic

[Bug Watch Updater]

** Changed in: openldap (Debian)
   Status: Unknown => Fix Released

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

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Jammy:
  In Progress
Status in openldap source package in Kinetic:
  Fix Committed
Status in openldap source package in Lunar:
  Fix Released
Status in openldap package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  OpenLDAP deployments using the contrib pw-sha2 module are not able to
  authenticate their users because the SHA2 calculation is done
  incorrectly.

  Even though this is a contrib module, from an upstream PoV, it is
  shipped in the Ubuntu (and Debian) OpenLDAP packages, and available
  for use.

  Some fix possibilities were discussed in comment #5, and we selected
  the one with the least impact to OpenLDAP users at large, which is to
  recompile that module only without the strict-aliasing optimization.

  This update makes that change, and also includes a DEP8 change to
  verify it.

  We didn't use a patch for the pw-sha2 Makefile because d/rules
  overrides the OPT variable in the make command line
  
(https://git.launchpad.net/~ahasenack/ubuntu/+source/openldap/tree/debian/rules?h=lunar-
  slapd-sha2-2000817#n44)

  [ Test Plan ]

  # Install slapd and openssl
  $ sudo apt install slapd openssl

  # Run the following script

  #!/bin/bash

  reference_hash="{SHA256}$(echo -n secret | openssl dgst -sha256 -binary | 
openssl enc -base64)"
  test_hash=$(slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2)

  echo "Reference hash of \"secret\" (openssl): ${reference_hash}"
  echo "slapd's pw-sha2 hash: ${test_hash}"

  if [ "${reference_hash}" != "${test_hash}" ]; then
  echo "ERROR: hashes differ"
  exit 1
  else
  echo "PASS: hashes are identical"
  fi

  With the affected openldap package installed, the script should print
  an error. With the packages from proposed, the hashes should be
  identical.

  [ Where problems could occur ]

  The fix is a change of a compiler option strictly when building only
  the pw-sha2 module, so it's very localized. It could affect the
  performance of this module (for the worse), but it's already not
  working correctly.

  [ Other Info ]
  Not at this time.

  [Original Description]

  The OpenLDAP-contrib module sha2 (located in contrib/slapd-
  modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
  kinetic. This breaks our current password-authentication in ldap.

  The problematic computation:

  $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
  {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=

  The (correct) reference-value on the same system (or older ubuntu
  Versions):

  $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
  K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  We nailed the problem down to a bug in the gcc-optimizer for strict-
  aliasing. so most probably the gcc-version on kinetic (v12.2.0) is the
  reason. The workaround is to compile the sha2-Module with the flag
  "-fno-strict-aliasing". Then the correct value is computed. An example
  taken from a git-compiled version of OpenLDAP 2.5.13:

  $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o 
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
  {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Bug Watch Updater]

** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)

[Bug Watch Updater]

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

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

Title:
  Gtk-WARNING ... drawing failure for widget ... invalid value
  (typically too big)

Status in GTK+:
  New
Status in cairo package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

[Bug Watch Updater]

** Changed in: evolution-data-server
   Status: New => Fix Released

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  I use google calendar.  Events are created and updated via the
  browser. The calendar feed is configured through settings/online
  accounts. I can see upcoming events in the calendar drop down. The
  calendar and desktop are configured for the same timezone, and alerts
  normally appear simultaneously on my phone and desktop.

  I know sometimes stale calendar entries can be a factor, but I don't
  *think* that's an issue at this time (the change was made almost 24
  hours ago, I don't see the API limit errors I used to see in logs).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 15:02:11 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (666 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.8.0-49-generic
   linux-base
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1923893/+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 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [accountsservice]

Status in accountsservice:
  Fix Released
Status in gnome-control-center:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is now the #1 gnome-shell crasher in Ubuntu 23.04.

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  

[Touch-packages] [Bug 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]

[Bug Watch Updater]

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

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

Title:
  Periodic black frames and stutter [Failed to post KMS update:
  drmModeAddFB does not support format 'AR24' (0x34325241)]

Status in Mesa:
  Fix Released
Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Every so often, the desktop will go black and then re appear on Ubuntu
  22.10 Wayland Session which should not be occurring (this does not
  happen on 22.04.) Note that only the cursor can be seen.

  Reporting this before release so that it can be patched for (at least)
  the RasPi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
  Uname: Linux 5.19.0-1001-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 16:10:37 2022
  DisplayManager: gdm3
  ImageMediaBuild: 20220826
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1988859/+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 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => Fix Released

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

Title:
  Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page
  fault)

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  My desktop unexpectedly freezes or crashes every now and then (once or
  week or less). Typically the machine is not usable but this time I
  managed to log back in via the text console and grab the following
  text from dmesg:

  [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed
  [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245291] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a01000 from client 0x1b (UTCL2)
  [11689.245294] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245296] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245298] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245299] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245301] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245302] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245304] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245311] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0c000 from client 0x1b (UTCL2)
  [11689.245313] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245315] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245316] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245318] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245319] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245320] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245322] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245329] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0b000 from client 0x1b (UTCL2)
  [11689.245331] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245333] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245334] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245336] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245337] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245339] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245340] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245347] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a06000 from client 0x1b (UTCL2)
  [11689.245349] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245350] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245351] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245352] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245354] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245355] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245356] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245362] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0a000 from client 0x1b (UTCL2)
  [11689.245363] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245364] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245366] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245367] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245368] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245369] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245370] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245374] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245376] amdgpu :09:00.0: amdgpu:   in page starting at address 

[Touch-packages] [Bug 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

[Bug Watch Updater]

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

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [accountsservice]

Status in accountsservice:
  Fix Released
Status in gnome-control-center:
  Unknown
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is now the #1 gnome-shell crasher in Ubuntu 23.04.

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

[Gunnar Hjalmarsson]

** Bug watch added: github.com/ibus/ibus/issues #2496
   https://github.com/ibus/ibus/issues/2496

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2496
   Importance: Unknown
   Status: Unknown

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

Title:
  Entering Unicode characters with code points broken

Status in ibus:
  Unknown
Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/2012788/+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 2013095] Re: sphinx autopkgtest needs to be updated for webkit 2.40

[Jeremy Bícha]

** Changed in: sphinx (Ubuntu)
 Assignee: Jeremy Bícha (jbicha) => (unassigned)

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

Title:
  sphinx autopkgtest needs to be updated for webkit 2.40

Status in pygobject package in Ubuntu:
  New
Status in sphinx package in Ubuntu:
  Triaged
Status in texlive-extra package in Ubuntu:
  New

Bug description:
  The sphinx autopkgtest needs to be updated for webkitgtk 2.40 which
  made breaking changes to the gtk4 library (webkit2-5.0 -> webkit-6.0).

  Our usual auto-transition tools didn't detect the autopkgtest-only
  dependency.

  https://github.com/WebKit/WebKit/blob/main/Source/WebKit/gtk/migrating-
  to-webkitgtk-6.0.md

  I am adding some other affected packages for our excuses tracker page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2013095/+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 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

I'm going to set this to Won't Fix because that seems to be an important
part of the solver logic, and the workarounds - running upgrade first,
or using ubuntu-drivers - are easy to do and the potential for
regression significantly outweighs them.

This will get solved eventually by a nicer solver (a proper optimization
solver) sure, if we make it there. Lots of caveats because I'm not that
clever that I want to write a competitive partial weighted maxsat or
linear programming solver, so end up reusing libraries, and neither z3
nor clasp are exactly optimal (also figuring out how to get them to
explain uninstallability is hard).

On the other hand, I am also exploring preventing the solver (both old
and new) from removing packages due to Conflicts, so removals can only
happen as part of a dist-upgrade or an explicit removal request, to
further reduce issues with people breaking their systems by accidentally
removing half of it (caveats as to the scope with manually vs
automatically installed packages, and whether packages are not needed
anymore are to be).

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+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 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

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

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+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 2009543] Re: network-manager nm.py autopkgtest needs to be updated for 1.42

[Jeremy Bícha]

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  network-manager nm.py autopkgtest needs to be updated for 1.42

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu's network-manager package includes several autopkgtest.
  (Debian's network-manager package does not have any autopkgtests.)

  One of those, nm.py needs to be updated for changes in the new
  network-manager 1.42 series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2009543/+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 1972159] Re: systemd-oomd frequently kills firefox and visual studio code

[Mantas Kriaučiūnas]

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

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

Title:
  systemd-oomd frequently kills firefox and visual studio code

Status in Default settings and artwork for Baltix OS:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Kinetic:
  Fix Released
Status in systemd package in Fedora:
  Fix Released

Bug description:
  [Impact]

  The "swap kill" side of systemd-oomd has caused unexpected behavior
  for desktop users. A user's browser, desktop session, or some other
  desktop application may be killed by systemd-oomd when SwapUsedLimit
  is reached, but system performance otherwise appears unaffected. This
  leaves users confused as to why their application was killed, and has
  a negative impact on their desktop experience.

  For now, let's disable the swap kill functionality by default.

  [Test Plan]

  On Jammy desktop, check the ManagedOOMSwap property on -.slice:

  $ systemctl show -- "-.slice" | grep "^ManagedOOMSwap"
  ManagedOOMSwap=kill # After the fix, this should print ManagedOOMSwap=auto

  [Where problems could occur]

  Disabling swap kill by default means that users may experience
  degraded system performance due to high swap usage, because systemd-
  oomd will no longer act on cgroups with high swap usage.

  [Other Info]

  If a user wishes to restore the original systemd-oomd behavior, they
  can do so by creating the following overrides file:

   $ cat /etc/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
   [Slice]
   ManagedOOMSwap=kill

  [Original Description]

  Since I installed Ubuntu 22.04, firefox and visual studio code are
  frequently killed by systemd-oomd (every 2hours).

  I have 8 GB memory and never experienced this before the upgrade to
  Ubuntu 22.04. I thus assume that the claim that there is not enough
  memory is abusive. Did 64GB of memory become the minimum requirement
  to run Ubuntu ?

  The second problem is that it gives a very bad user experience which
  is critical for new Ubuntu users.

  There should be a warning prior killing apps to give the opportunity
  to save the app data. There should at least be an apologize and an
  explanation after killing the app.

  The current behavior gives the impression that Ubuntu 22.04 is
  unreliable and unsafe to use which is a problem for an LTS release
  that many people might want to use for critical production context.

  There might be a configuration problem with systemd-oomd or simply a
  bogus behavior. I would recommend to disable it or remove it
  completely until this problem is resolved. This is what I will do for
  myself because I have work to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1972159/+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 2012148] Re: package libgstreamer-plugins-bad1.0-0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', whi

[Eduardo Barretto]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libgstreamer-plugins-bad1.0-0 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-
  gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in package
  libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  i have added kali linus repositories to ubuntu sources list these
  problems started to happen

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer-plugins-bad1.0-0 (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Mar 18 23:23:38 2023
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in 
package libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1
  InstallationDate: Installed on 2023-03-18 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.1-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: gst-plugins-bad1.0
  Title: package libgstreamer-plugins-bad1.0-0 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in 
package libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2012148/+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 2013095] Re: sphinx autopkgtest needs to be updated for webkit 2.40

[Dmitry Shachnev]

I will fix it via Debian.

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

Title:
  sphinx autopkgtest needs to be updated for webkit 2.40

Status in pygobject package in Ubuntu:
  New
Status in sphinx package in Ubuntu:
  Triaged
Status in texlive-extra package in Ubuntu:
  New

Bug description:
  The sphinx autopkgtest needs to be updated for webkitgtk 2.40 which
  made breaking changes to the gtk4 library (webkit2-5.0 -> webkit-6.0).

  Our usual auto-transition tools didn't detect the autopkgtest-only
  dependency.

  https://github.com/WebKit/WebKit/blob/main/Source/WebKit/gtk/migrating-
  to-webkitgtk-6.0.md

  I am adding some other affected packages for our excuses tracker page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2013095/+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 1933090] Autopkgtest regression report (systemd/245.4-4ubuntu3.21)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.21) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.0.9 (armhf)
bilibop/unknown (s390x)
freeipa/unknown (s390x)
fwupd/1.7.9-1~20.04.1 (armhf)
libsoup2.4/2.70.0-1 (s390x)
libusb-1.0/unknown (s390x)
libvirt/unknown (s390x)
linux-aws-5.11/blacklisted (amd64, arm64)
linux-aws-5.13/blacklisted (amd64, arm64)
linux-aws-5.15/5.15.0-1033.37~20.04.1 (arm64)
linux-aws-5.15/unknown (amd64)
linux-aws-5.8/blacklisted (amd64)
linux-azure-5.11/blacklisted (amd64, arm64)
linux-azure-5.13/blacklisted (arm64)
linux-azure-5.8/blacklisted (amd64)
linux-azure-cvm/5.4.0-1105.111+cvm1 (amd64)
linux-gcp-5.11/blacklisted (amd64)
linux-gcp-5.13/blacklisted (amd64)
linux-gcp-5.15/5.15.0-1030.37~20.04.1 (amd64)
linux-gcp-5.15/5.15.0-1031.38~20.04.1 (arm64)
linux-gcp-5.8/blacklisted (amd64)
linux-gke-5.15/5.15.0-1029.34~20.04.1 (amd64, arm64)
linux-gkeop-5.15/5.15.0-1016.21~20.04.1 (amd64)
linux-hwe-5.11/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-hwe-5.13/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-hwe-5.15/5.15.0-69.76~20.04.1 (amd64, armhf)
linux-hwe-5.8/blacklisted (amd64, arm64, ppc64el, s390x)
linux-ibm/5.4.0-1046.51 (amd64)
linux-intel-5.13/blacklisted (amd64)
linux-intel-iotg-5.15/5.15.0-1027.32~20.04.1 (amd64)
linux-oem-5.10/blacklisted (amd64)
linux-oem-5.13/blacklisted (amd64)
linux-oem-5.14/5.14.0-1059.67 (amd64)
linux-oem-5.6/blacklisted (amd64)
linux-oracle-5.11/blacklisted (amd64)
linux-oracle-5.13/blacklisted (amd64, arm64)
munin/2.0.56-1ubuntu1 (arm64, ppc64el)
pdns-recursor/unknown (s390x)
php7.4/unknown (s390x)
polkit-qt-1/unknown (s390x)
puppet/5.5.10-4ubuntu3 (s390x)
tinyssh/unknown (s390x)
udisks2/2.8.4-1ubuntu2 (amd64)
upower/0.99.11-1build2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [SRU Impact]

  Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, 
test_protect_syscall
  sysctl is called with the expectation the error result is EFAULT and not 
ENOSYS.
  This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, 
oem, gke, oracle).

  [Fix]
  Assertion checks if either EFAULT or ENOSYS is returned. This way it will 
work for focal-5.4 kernels and focal-5.15 kernels.

  [Test to reproduce the issue]
  1. Create a vm and install one of the focal-5.15 kernels (i.e 
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
  2. Run the autotests for upstream and/or root-unittests:
  autopkgtest --test-name=upstream systemd -- qemu 

  [Test to verify the fix]
  1. Same as above
  2. Apply the fix in your local repo and run the tests using your local repo
  autopkgtest --test-name=upstream  -- qemu 

  [Where problems could occur]
  This is not gonna affect end users since it is a change in the test only.
  It may impact autotests, but it's a very low probability.

  [Original Description]

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

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  

[Touch-packages] [Bug 1991285] Autopkgtest regression report (systemd/245.4-4ubuntu3.21)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.21) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.0.9 (armhf)
bilibop/unknown (s390x)
freeipa/unknown (s390x)
fwupd/1.7.9-1~20.04.1 (armhf)
libsoup2.4/2.70.0-1 (s390x)
libusb-1.0/unknown (s390x)
libvirt/unknown (s390x)
linux-aws-5.11/blacklisted (amd64, arm64)
linux-aws-5.13/blacklisted (amd64, arm64)
linux-aws-5.15/5.15.0-1033.37~20.04.1 (arm64)
linux-aws-5.15/unknown (amd64)
linux-aws-5.8/blacklisted (amd64)
linux-azure-5.11/blacklisted (amd64, arm64)
linux-azure-5.13/blacklisted (arm64)
linux-azure-5.8/blacklisted (amd64)
linux-azure-cvm/5.4.0-1105.111+cvm1 (amd64)
linux-gcp-5.11/blacklisted (amd64)
linux-gcp-5.13/blacklisted (amd64)
linux-gcp-5.15/5.15.0-1030.37~20.04.1 (amd64)
linux-gcp-5.15/5.15.0-1031.38~20.04.1 (arm64)
linux-gcp-5.8/blacklisted (amd64)
linux-gke-5.15/5.15.0-1029.34~20.04.1 (amd64, arm64)
linux-gkeop-5.15/5.15.0-1016.21~20.04.1 (amd64)
linux-hwe-5.11/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-hwe-5.13/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-hwe-5.15/5.15.0-69.76~20.04.1 (amd64, armhf)
linux-hwe-5.8/blacklisted (amd64, arm64, ppc64el, s390x)
linux-ibm/5.4.0-1046.51 (amd64)
linux-intel-5.13/blacklisted (amd64)
linux-intel-iotg-5.15/5.15.0-1027.32~20.04.1 (amd64)
linux-oem-5.10/blacklisted (amd64)
linux-oem-5.13/blacklisted (amd64)
linux-oem-5.14/5.14.0-1059.67 (amd64)
linux-oem-5.6/blacklisted (amd64)
linux-oracle-5.11/blacklisted (amd64)
linux-oracle-5.13/blacklisted (amd64, arm64)
munin/2.0.56-1ubuntu1 (arm64, ppc64el)
pdns-recursor/unknown (s390x)
php7.4/unknown (s390x)
polkit-qt-1/unknown (s390x)
puppet/5.5.10-4ubuntu3 (s390x)
tinyssh/unknown (s390x)
udisks2/2.8.4-1ubuntu2 (amd64)
upower/0.99.11-1build2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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] Autopkgtest regression report (systemd/245.4-4ubuntu3.21)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.21) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.0.9 (armhf)
bilibop/unknown (s390x)
freeipa/unknown (s390x)
fwupd/1.7.9-1~20.04.1 (armhf)
libsoup2.4/2.70.0-1 (s390x)
libusb-1.0/unknown (s390x)
libvirt/unknown (s390x)
linux-aws-5.11/blacklisted (amd64, arm64)
linux-aws-5.13/blacklisted (amd64, arm64)
linux-aws-5.15/5.15.0-1033.37~20.04.1 (arm64)
linux-aws-5.15/unknown (amd64)
linux-aws-5.8/blacklisted (amd64)
linux-azure-5.11/blacklisted (amd64, arm64)
linux-azure-5.13/blacklisted (arm64)
linux-azure-5.8/blacklisted (amd64)
linux-azure-cvm/5.4.0-1105.111+cvm1 (amd64)
linux-gcp-5.11/blacklisted (amd64)
linux-gcp-5.13/blacklisted (amd64)
linux-gcp-5.15/5.15.0-1030.37~20.04.1 (amd64)
linux-gcp-5.15/5.15.0-1031.38~20.04.1 (arm64)
linux-gcp-5.8/blacklisted (amd64)
linux-gke-5.15/5.15.0-1029.34~20.04.1 (amd64, arm64)
linux-gkeop-5.15/5.15.0-1016.21~20.04.1 (amd64)
linux-hwe-5.11/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-hwe-5.13/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-hwe-5.15/5.15.0-69.76~20.04.1 (amd64, armhf)
linux-hwe-5.8/blacklisted (amd64, arm64, ppc64el, s390x)
linux-ibm/5.4.0-1046.51 (amd64)
linux-intel-5.13/blacklisted (amd64)
linux-intel-iotg-5.15/5.15.0-1027.32~20.04.1 (amd64)
linux-oem-5.10/blacklisted (amd64)
linux-oem-5.13/blacklisted (amd64)
linux-oem-5.14/5.14.0-1059.67 (amd64)
linux-oem-5.6/blacklisted (amd64)
linux-oracle-5.11/blacklisted (amd64)
linux-oracle-5.13/blacklisted (amd64, arm64)
munin/2.0.56-1ubuntu1 (arm64, ppc64el)
pdns-recursor/unknown (s390x)
php7.4/unknown (s390x)
polkit-qt-1/unknown (s390x)
puppet/5.5.10-4ubuntu3 (s390x)
tinyssh/unknown (s390x)
udisks2/2.8.4-1ubuntu2 (amd64)
upower/0.99.11-1build2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Released

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]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit).

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import json
  import logging
  import os
  import sys
  from enum import Enum

  import pycloudlib

  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba]
  """

  #source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # - apt install systemd udev -y --allow-unauthenticated

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: {source}
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}

[Touch-packages] [Bug 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS

[Dave Jones]

This should only be merged once LP: #2004430 as it builds upon those
commits.

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/439835

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/439842

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+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 2013095] [NEW] sphinx autopkgtest needs to be updated for webkit 2.40

[Jeremy Bícha]

Public bug reported:

The sphinx autopkgtest needs to be updated for webkitgtk 2.40 which made
breaking changes to the gtk4 library (webkit2-5.0 -> webkit-6.0).

Our usual auto-transition tools didn't detect the autopkgtest-only
dependency.

https://github.com/WebKit/WebKit/blob/main/Source/WebKit/gtk/migrating-
to-webkitgtk-6.0.md

I am adding some other affected packages for our excuses tracker page.

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

** Affects: sphinx (Ubuntu)
 Importance: High
 Assignee: Jeremy Bícha (jbicha)
 Status: Triaged

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lunar update-excuse

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

** Also affects: texlive-extra (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  sphinx autopkgtest needs to be updated for webkit 2.40

Status in pygobject package in Ubuntu:
  New
Status in sphinx package in Ubuntu:
  Triaged
Status in texlive-extra package in Ubuntu:
  New

Bug description:
  The sphinx autopkgtest needs to be updated for webkitgtk 2.40 which
  made breaking changes to the gtk4 library (webkit2-5.0 -> webkit-6.0).

  Our usual auto-transition tools didn't detect the autopkgtest-only
  dependency.

  https://github.com/WebKit/WebKit/blob/main/Source/WebKit/gtk/migrating-
  to-webkitgtk-6.0.md

  I am adding some other affected packages for our excuses tracker page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2013095/+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 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 22.08.8-1ubuntu5

---
accountsservice (22.08.8-1ubuntu5) lunar; urgency=medium

  * src/libaccountsservice/act-user-manager.c:
- cherry pick a fix invalid users requests (lp: #1966905)

 -- Sebastien Bacher   Mon, 27 Mar 2023 22:02:47
+0200

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [accountsservice]

Status in accountsservice:
  New
Status in gnome-control-center:
  Unknown
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is now the #1 gnome-shell crasher in Ubuntu 23.04.

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: 

[Touch-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

I think we debugged this recently but I'm not sure where the end result
of this is that we do not mark packages for removal that have an upgrade
available, hence we end up without a removal request after the first
stage solver, and the Conflicts solver that runs after can't solve that.

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+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 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

Reproduced issue and dumped test case into https://salsa.debian.org/apt-
team/apt-tests/-/blob/main/edsp/fail-ubuntu-1992513.edsp.log for future
analysis when doing solver work.

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+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 2012943] Re: Systemd-resolved is crashing

[Naveen chand]

The system is hung due to system-resolved crash

```
Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service.
Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main 
process exited, code=killed, status=11/SEGV
```

also the system-resolved service is aborted.

```
Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting.
Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main 
process exited, code=killed, status=6/ABRT
```

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

Title:
  Systemd-resolved is crashing

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

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system.

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  [ Where problems could occur ]

  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
  This commit is resolving the issue which is observed.

  Please refer to the above commit to assess the risk involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2009543] Re: network-manager nm.py autopkgtest needs to be updated for 1.42

[Jeremy Bícha]

** Changed in: network-manager (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  network-manager nm.py autopkgtest needs to be updated for 1.42

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Ubuntu's network-manager package includes several autopkgtest.
  (Debian's network-manager package does not have any autopkgtests.)

  One of those, nm.py needs to be updated for changes in the new
  network-manager 1.42 series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2009543/+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 2009543] Re: network-manager nm.py autopkgtest needs to be updated for 1.42

[Lukas Märdian]

The issue seems to be related to
https://networkmanager.dev/blog/networkmanager-1-42/#managing-the-
loopback-interface

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

Title:
  network-manager nm.py autopkgtest needs to be updated for 1.42

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Ubuntu's network-manager package includes several autopkgtest.
  (Debian's network-manager package does not have any autopkgtests.)

  One of those, nm.py needs to be updated for changes in the new
  network-manager 1.42 series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2009543/+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 2013083] [NEW] libwebp-dev doesn't install CMake configs

[Dmitry]

Public bug reported:

Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu
package doesn't install them. This prevents client applications from
using the recommended find_package(WebP) functionality.

Please install the CMake configs along with the pkg-config files.

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

** Summary changed:

- libwebp-dev doesn't install CMake rules
+ libwebp-dev doesn't install CMake configs

** Description changed:

  Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu
  package doesn't install them. This prevents client applications from
  using the recommended find_package(WebP) functionality.
  
- Please install CMake configs along with pkg-config files.
+ Please install the CMake configs along with the pkg-config files.

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

Title:
  libwebp-dev doesn't install CMake configs

Status in libwebp package in Ubuntu:
  New

Bug description:
  Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu
  package doesn't install them. This prevents client applications from
  using the recommended find_package(WebP) functionality.

  Please install the CMake configs along with the pkg-config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2013083/+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 2009543] Re: network-manager nm.py autopkgtest needs to be updated for 1.42

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~slyon/network-manager/+git/network-manager/+merge/439829

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

Title:
  network-manager nm.py autopkgtest needs to be updated for 1.42

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Ubuntu's network-manager package includes several autopkgtest.
  (Debian's network-manager package does not have any autopkgtests.)

  One of those, nm.py needs to be updated for changes in the new
  network-manager 1.42 series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2009543/+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 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts

[Robie Basak]

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

** Also affects: isc-dhcp (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033597
   Importance: Unknown
   Status: Unknown

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

Title:
  Apparmor Disallows Disabling Dhclient Scripts

Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp package in Debian:
  Unknown

Bug description:
  In some cases, it may be desirable to disable dhclient scripts. By
  default /sbin/dhclient-script is used, and some others are allowed by
  the apparmor profile.

  Without Apparmor, disabling hook scripts can be accomplished with
  flags -sf /bin/true, but with apparmor enabled this gets blocked:

  execve (/bin/true, ...): Permission denied

  Unfortunately dhclient doesn't appear to provide any other mechanism
  for disabling hook scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 2009498] Re: autopkg test failure

[Jeremy Bícha]

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

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

Title:
  autopkg test failure

Status in ganeti package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  Fix Released
Status in ganeti package in Debian:
  Unknown

Bug description:
  pgrep -u '-1'; echo $?

  used to yield 1 but with procps 4.0.3 it yields 2.

  Negative uids don't exist in the Linux kernel.

  
  Function testRequestUnusedUid() is wrong in assuming that -1 will be 
considered an unused uid.

  See Debian bug#1031765: ganeti-testsuite: autopkgtest failure with
  procps 2:4.0.3-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ganeti/+bug/2009498/+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 2013080] [NEW] On rpi desktop images, grow root leaving slack for LUKS

[Dave Jones]

Public bug reported:

To aid in user-implemented FDE we wish to leave 16MB of the file-system
unexpanded during first boot. The growth of the partition is unaffected,
but rather than relying on systemd's growfs facility in fstab, we should
use a service that runs a simple script to handle calculating the resize
in early boot.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-23.04

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+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 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway

[geole0]

Hello
I work with UBUNTU 22.04.2 LTS and when i want to report  a bug with ubuntu-bug
the connection  is not possible.

NETWORK PROBLEM
Cannot connect to crash database, please check your Internet connection.
HTTP error 502: Bad Gateway


But i can connect me to bugs.launchpad.net  and post to this message.

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

Title:
  apport-gtk crashed with urllib.error.HTTPError in
  http_error_default(): HTTP Error 502: Bad Gateway

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Had a Nautlius crash prior to this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apport-gtk 2.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 
12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash
   640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 
10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 
17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded
   640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 
10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash
   664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 
10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 10:18:26 2023
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2023-02-13 (12 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors:
   Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: 
Failed with result 'exit-code'.
   Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification 
regarding a crash report.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonArgs: ['/usr/share/apport/apport-gtk']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport-gtk crashed with urllib.error.HTTPError in 
http_error_default(): HTTP Error 502: Bad Gateway
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2008638/+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 2013071] Re: Session crash after initial login

[Sean Davis]

** Description changed:

  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.
  
  When logging in for the first time, the session immediately crashes and
  returns to the login screen.
  
  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.
+ 
+ The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
+ - chromium-codecs-ffmpeg-extra
+ - gimp-help-common
+ - gimp-help-en
+ - gstreamer1.0-plugins-ugly
+ - gstreamer1.0-vaapi
+ - hyphen-en-us
+ - liba52-0.7.4
+ - libmpeg2-4
+ - libopencore-amrnb0
+ - libopencore-amrwb0
+ - libreoffice-help-common
+ - libreoffice-help-en-us
+ - libsidplay1v5
+ - libva-wayland2
+ - mythes-en-us
+ - thunderbird-locale-en
+ - thunderbird-locale-en-us
+ - ubuntu-restricted-addons
+ - wbritish
+ 
+ Since it seems unlikely that the language pack packages are
+ interfering... maybe libva-wayland2 is to blame?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  New

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpe