[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Thanks Nick for pointing me to this bug; I was working on the same issue, as reported in a duplicate bug. As far as the classic desktop is concerned, this bug occurs not because of the failed mount, but because of "unshare" failing (see the discussion in bug 1971955); in any case, the analysis by Jiwei Sun is correct: it's happening because of the added SystemCallFilter entry to the udev unit file. ** Changed in: snapd Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: snapd Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1975561] [NEW] package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: it automatically cme up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 24 06:39:36 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-05-13 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1975561 Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: it automatically cme up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 24 06:39:36 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-05-13 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1975561/+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 1975554] [NEW] Apply default TTL to records obtained from getaddrinfo(): Focal and beyond
Public bug reported: The issue was fixed for bionic in: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453 However, was missed for Focal, Impish and Jammy. Since I'm not getting responses for that bug, I'm opening this one. ** Affects: keyutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1975554 Title: Apply default TTL to records obtained from getaddrinfo(): Focal and beyond Status in keyutils package in Ubuntu: New Bug description: The issue was fixed for bionic in: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453 However, was missed for Focal, Impish and Jammy. Since I'm not getting responses for that bug, I'm opening this one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1975554/+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 1871148] Re: services start before apparmor profiles are loaded
@mardy I thought we had snapd.apparmor specifically to avoid this scenario but I can't see that service mentioned at all in systemd- analyze plot... -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1975549] [NEW] NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
Public bug reported:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".
The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manag
[Touch-packages] [Bug 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch added: "Patch to resolve Divert issue for Jammy ucf 3.0043" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5592489/+files/ucf-3.0043-divert.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch added: "Patch for Focal UCF 3.0038" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5592488/+files/ucf-3.0038-divert.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch removed: "ucf-3.0038-divertfix.patch" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5581412/+files/ucf-3.0038-divertfix.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1974230] [NEW] Negative cache results from dnsmasq do not include SOA as required in RFC2308
Acknowledge that RFC non-compliance. Fixing this is actually a fairly big ask, since the problem is not that dnsmasq omits the SOA when answering from cache, but that dnsmasq doesn't cache SOA records. The design philosophy was (and is) to cache only a few RR types to make the code and data structures simple and small (remember that dnsmasq's niche is "lightweight", for low capability hardware). There's been a implied assumption that clients using dnsmasq would typically be stub-resolvers, and not full-service DNS servers. That said, the set of cached RR types has increased over the years, notably with the introduction of DNSSEC and the RR types needed to suuport that. Adding caching of SOA records is possible, but I'm not sure it's worth the effort. A reasonable workaround might be to disable negative caching in dnsmasq and rely on systemd-resolved to do that for itself. Simon. On 19/05/2022 20:51, Eric Blevins wrote: > Public bug reported: > > RFC2308 states: > 6 - Negative answers from the cache > > When a server, in answering a query, encounters a cached negative > response it MUST add the cached SOA record to the authority section > of the response with the TTL decremented by the amount of time it was > stored in the cache. This allows the NXDOMAIN / NODATA response to > time out correctly. > > The effect is that the negative cache results returned by dnsmasq cannot > be cached by other resolvers such as systemd-resolved. > > A good example of why this is a problem: > Two clients with systemd-resolved send DNS queries to dnsmasq for the same > record > The first one makes a query and gets NXDOMAIN with SOA. > This results in systemd-resolved caching the negative result. > > The second client makes a query and gets NODATA without the SOA. > This results in systemd-resolved not caching the negative result. > > Consider a domain name that only has an A record published. > When connecting to that domain a lookup happens for the and A record. > One can end up in a situation where systemd-resolved has the A record cached > locally, but it still goes out to the network to perform the lookup only > to get the same negative cache result that is missing the SOA > > I see this behavior in 18.04 and 22.04 > > > First query to dnsmasq can be cached: > dig @10.0.1.21 a.google.com > > ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com > ; (1 server found) > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3107 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 512 > ;; QUESTION SECTION: > ;a.google.com. IN A > > ;; AUTHORITY SECTION: > google.com. 60 IN SOA ns1.google.com. > dns-admin.google.com. 449437361 900 900 1800 60 > > ;; Query time: 15 msec > ;; SERVER: 10.0.1.21#53(10.0.1.21) > ;; WHEN: Thu May 19 15:00:12 EDT 2022 > ;; MSG SIZE rcvd: 91 > > > Cached response from dnsmasq cannot be cached: > dig @10.0.1.21 a.google.com > > ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com > ; (1 server found) > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61408 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: > ;a.google.com. IN A > > ;; Query time: 0 msec > ;; SERVER: 10.0.1.21#53(10.0.1.21) > ;; WHEN: Thu May 19 15:00:13 EDT 2022 > ;; MSG SIZE rcvd: 41 > > ** Affects: dnsmasq (Ubuntu) > Importance: Undecided > Status: New > -- 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/1974230 Title: Negative cache results from dnsmasq do not include SOA as required in RFC2308 Status in dnsmasq package in Ubuntu: New Bug description: RFC2308 states: 6 - Negative answers from the cache When a server, in answering a query, encounters a cached negative response it MUST add the cached SOA record to the authority section of the response with the TTL decremented by the amount of time it was stored in the cache. This allows the NXDOMAIN / NODATA response to time out correctly. The effect is that the negative cache results returned by dnsmasq cannot be cached by other resolvers such as systemd-resolved. A good example of why this is a problem: Two clients with systemd-resolved send DNS queries to dnsmasq for the same record The first one makes a query and gets NXDOMAIN with SOA. This results in systemd-resolved caching the negative result. The second client makes a query and gets NODATA without the SOA. This results in systemd-resolved not caching the negative result. Consider a domain name that only has an A r
[Touch-packages] [Bug 1958019]
The first two modprobe commands returned ` modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory /lib/modules/5.13.0-051300-generic ` The third one returns nothing. I tried reinstalling my nvidia driver too but even after purging all it doesn't seem to work :\ I tried following these instructions: https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it- couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest- nvidia-driver-is-installed-and-running/197141/6 (In reply to Cameron Berkenpas from comment #612) > I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't > even have any point releases so chances are reasonably high you'll run into > bugs. > > Additionally, I don't have the ACHg6. It's possible you'll need to specify > which modules to load. In the likely event that 5.17 doesn't work, perhaps > someone can provide information on what's needed there. > > Possibly these steps will work: > sudo modprobe snd-hda-codec-cs35l41-i2c > sudo modeprobe snd_soc_cs35l41_i2c > sudo modeprobe i2c-multi-instantiate > > (In reply to she...@liang.at from comment #609) > > Thanks for the quick responses. I followed the instructions to install the > > latest version. Is it supposed to work if I installed 5.18 too? It's not > > working and it stopped recognising my external monitors too. > > -- 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]
I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't even have any point releases so chances are reasonably high you'll run into bugs. Additionally, I don't have the ACHg6. It's possible you'll need to specify which modules to load. In the likely event that 5.17 doesn't work, perhaps someone can provide information on what's needed there. Possibly these steps will work: sudo modprobe snd-hda-codec-cs35l41-i2c sudo modeprobe snd_soc_cs35l41_i2c sudo modeprobe i2c-multi-instantiate (In reply to she...@liang.at from comment #609) > Thanks for the quick responses. I followed the instructions to install the > latest version. Is it supposed to work if I installed 5.18 too? It's not > working and it stopped recognising my external monitors too. > -- 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]
Your error message shows you're 5.13, which definitely doesn't have support. On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #614 from she...@liang.at (she...@liang.at) --- > The first two modprobe commands returned > ` > modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory > /lib/modules/5.13.0-051300-generic > ` > The third one returns nothing. > > I tried reinstalling my nvidia driver too but even after purging all it > doesn't > seem to work :\ > > I tried following these instructions: > > https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-nvidia-driver-is-installed-and-running/197141/6 > > (In reply to Cameron Berkenpas from comment #612) >> I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't >> even have any point releases so chances are reasonably high you'll run into >> bugs. >> >> Additionally, I don't have the ACHg6. It's possible you'll need to specify >> which modules to load. In the likely event that 5.17 doesn't work, perhaps >> someone can provide information on what's needed there. >> >> Possibly these steps will work: >> sudo modprobe snd-hda-codec-cs35l41-i2c >> sudo modeprobe snd_soc_cs35l41_i2c >> sudo modeprobe i2c-multi-instantiate >> >> (In reply to she...@liang.at from comment #609) >>> Thanks for the quick responses. I followed the instructions to install the >>> latest version. Is it supposed to work if I installed 5.18 too? It's not >>> working and it stopped recognising my external monitors too. >>> -- 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]
There's no patch for your laptop yet. Assuming your sound bar is initialized through verbs (I suspect it is), you'll need to find the verb sequence yourself: https://github.com/thiagotei/linux-realtek-alc287/tree/cameron Once there's a working verb sequence, a patch can be created. On 5/23/22 04:50, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #611 from singo (hnsinan...@gmail.com) --- > Hello everyone, > > I really appreciate this thread and all of the solutions that have been > produced for this issue. Thanks to everyone contributing, especially Cameron > Berkenpas who has been very helpful to a number of users and the main driving > force for fixes:) > > Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287. > Currently > it runs Ubuntu 22.04. LTS with the included 5.15 Kernel. Before I have run > Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially > but > never fully. The experience is the same as many other users here, where there > would only be sound coming out the from the downward firing speakers, but not > from the soundbar above the keyboard, which are the bass speakers judging by > the tinny sound I get now. The sound works beautifully in Windows, since the > lower end frequencies can be replayed. > > Quite honestly, I've lost the overview over this thread and am not so sure > which patch I should apply. I've tried manually update my Ubuntu 22.04. to > the > mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope > was > that the sound patches have been included in that Kernel, but it seems > they're > only working for the Legion 7. > > Could someone point me to the right patch or verbs that have to be applied > for > my Lenovo model in order for the bass speakers to work? Maybe someone has > figured it out for this particular case? > > Much thanks in advance. > > Here's my alsa-info: > > http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302 > -- 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 t
[Touch-packages] [Bug 1958019]
Hello everyone, I really appreciate this thread and all of the solutions that have been produced for this issue. Thanks to everyone contributing, especially Cameron Berkenpas who has been very helpful to a number of users and the main driving force for fixes:) Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287. Currently it runs Ubuntu 22.04. LTS with the included 5.15 Kernel. Before I have run Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially but never fully. The experience is the same as many other users here, where there would only be sound coming out the from the downward firing speakers, but not from the soundbar above the keyboard, which are the bass speakers judging by the tinny sound I get now. The sound works beautifully in Windows, since the lower end frequencies can be replayed. Quite honestly, I've lost the overview over this thread and am not so sure which patch I should apply. I've tried manually update my Ubuntu 22.04. to the mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope was that the sound patches have been included in that Kernel, but it seems they're only working for the Legion 7. Could someone point me to the right patch or verbs that have to be applied for my Lenovo model in order for the bass speakers to work? Maybe someone has figured it out for this particular case? Much thanks in advance. Here's my alsa-info: http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302 -- 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]
Hello everyone, I really appreciate this thread and all of the solutions that have been produced for this issue. Thanks to everyone contributing, especially Cameron Berkenpas who has been very helpful to a number of users and the main driving force for fixes:) Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287. Currently it runs Ubuntu 22.04. LTS with the included 5.15 Kernel. Before I have run Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially but never fully. The experience is the same as many other users here, where there would only be sound coming out the from the downward firing speakers, but not from the soundbar above the keyboard, which are the bass speakers judging by the tinny sound I get now. The sound works beautifully in Windows, since the lower end frequencies can be replayed. Quite honestly, I've lost the overview over this thread and am not so sure which patch I should apply. I've tried manually update my Ubuntu 22.04. to the mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope was that the sound patches have been included in that Kernel, but it seems they're only working for the Legion 7. Could someone point me to the right patch or verbs that have to be applied for my Lenovo model in order for the bass speakers to work? Maybe someone has figured it out for this particular case? Much thanks in advance. Here's my alsa-info: http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302 -- 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]
Thanks for the quick responses. I followed the instructions to install the latest version. Is it supposed to work if I installed 5.18 too? It's not working and it stopped recognising my external monitors too. (In reply to Cameron Berkenpas from comment #608) > Seems like this is the best way to do it (but if someone knows of a better > way for Ubuntu, let us know): > https://sleeplessbeastie.eu/2021/11/01/how-to-install-mainline-linux-kernel- > on-ubuntu-based-distribution/ > > Seems this gets you a tool that allows you to manage and install mainline > kernels. You'll need a 5.17 (which is the latest stable mainline release) to > get your sound working. > > Keep us posted. > > > (In reply to Cameron Berkenpas from comment #607) > > > There should be a repo you can add on your system to be able to pull the > > latest mainline kernels. I don't have it handy at the moment as I've > > been building/installing kernels myself since the 90's, but I'll try > > find it and post it in a little bit. -- 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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-33.34~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in urfkill package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Status in urfkill source package in Jammy: New Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. 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-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
I read https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18 and identified the 4 files that must be adapted but . there is not directory /src/core or supplicant on my disk and so no files that i can adapt. I don't identify what i have to do, sorry! -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1871148] Re: services start before apparmor profiles are loaded
Inside the attached journal for the 'apparmor.service' unit, I do NOT understand at all which "DENIED" messages are normal and which are abnormal. For independent reasons, I would like to keep my machine running for several days (or weeks). But after I reboot, and before running the apparmor_parser command, I will attach the output of following commands : $ SNAPD_DEBUG=1 firefox $ journalctl -b ** Attachment added: "journalctl-apparmor.service-sirius-2022-05-23.log" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5592394/+files/journalctl-apparmor.service-sirius-2022-05-23.log -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1974456] Re: regression: apt.postint fails if never previously configured
It might, I just might miss the right setting, I don't really know. -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured
P.S. I have worked around this in my build system (by creating an empty executable script at the location that apt.postinst is expecting before I call dpkg --configure) so I'm not worried. When I reported this I didn't realise it wouldn't affect debootstrap. -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1871148] Re: services start before apparmor profiles are loaded
Yes, on the slower machine (where I am seeing this issue), I will NOT be able to start firefox until I have run that apparmor_parser command. Not even if I try starting firefox well after the login. $ ls -l /etc/apparmor.d/disable total 0 lrwxrwxrwx. 1 root root 31 août 27 2019 usr.bin.firefox -> /etc/apparmor.d/usr.bin.firefox lrwxrwxrwx. 1 root root 33 août 27 2019 usr.sbin.rsyslogd -> /etc/apparmor.d/usr.sbin.rsyslogd $ ls -l /etc/apparmor.d/usr.bin.firefox -rw-r--r-- 1 root root 9186 déc. 1 10:22 /etc/apparmor.d/usr.bin.firefox I do NOT know at all if '/etc/apparmor.d/disable/usr.bin.firefox' is useful or harmful. ** Attachment added: "systemctl-status-apparmor-sirius-2022-05-17.log" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5592390/+files/systemctl-status-apparmor-sirius-2022-05-17.log -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1974456] Re: regression: apt.postint fails if never previously configured
> Which tool were you using to bootstrap your system? My own build system (which I wrote about for LWN: https://lwn.net/Articles/821367/ ). -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974230] Re: Negative cache results from dnsmasq do not include SOA as required in RFC2308
Hello Eric, Thank you for providing this bug report. When testing in Jammy I see the same behavior. We will look into the issue this week. ** Tags added: server-triage-discuss -- 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/1974230 Title: Negative cache results from dnsmasq do not include SOA as required in RFC2308 Status in dnsmasq package in Ubuntu: New Bug description: RFC2308 states: 6 - Negative answers from the cache When a server, in answering a query, encounters a cached negative response it MUST add the cached SOA record to the authority section of the response with the TTL decremented by the amount of time it was stored in the cache. This allows the NXDOMAIN / NODATA response to time out correctly. The effect is that the negative cache results returned by dnsmasq cannot be cached by other resolvers such as systemd-resolved. A good example of why this is a problem: Two clients with systemd-resolved send DNS queries to dnsmasq for the same record The first one makes a query and gets NXDOMAIN with SOA. This results in systemd-resolved caching the negative result. The second client makes a query and gets NODATA without the SOA. This results in systemd-resolved not caching the negative result. Consider a domain name that only has an A record published. When connecting to that domain a lookup happens for the and A record. One can end up in a situation where systemd-resolved has the A record cached locally, but it still goes out to the network to perform the lookup only to get the same negative cache result that is missing the SOA I see this behavior in 18.04 and 22.04 First query to dnsmasq can be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3107 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;a.google.com. IN A ;; AUTHORITY SECTION: google.com. 60 IN SOA ns1.google.com. dns-admin.google.com. 449437361 900 900 1800 60 ;; Query time: 15 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:12 EDT 2022 ;; MSG SIZE rcvd: 91 Cached response from dnsmasq cannot be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61408 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;a.google.com. IN A ;; Query time: 0 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:13 EDT 2022 ;; MSG SIZE rcvd: 41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1974230/+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 1975430] Re: I can select the Xorg Nouveau server, but not click on "apply"
Thanks for the debugging details, retitling and changing the component according ** Package changed: software-properties (Ubuntu) => ubuntu-drivers- common (Ubuntu) ** Summary changed: - I can select the Xorg Nouveau server, but not click on "apply" + kerneldetection except when custom kernel installed ** Summary changed: - kerneldetection except when custom kernel installed + kerneldetection exception when a custom kernel installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1975430 Title: kerneldetection exception when a custom kernel installed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I want to switch back from the nvidia driver to nouveau. In the dialog the last row lets me select the Nouveau driver, but the "apply" button is inactive and doesnt let me apply the change. There is also no message or anything that would allow me to understand, why this is the case, and what i could do about it. heres also the outout of ubuntu-drivers debug that I learned in anothe bug can be important: === log messages from detection === DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on video abi DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on video abi DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video abi DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821
[Touch-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
The update on bug #1974428 fixed an issue where only WPA3 compatible devices would be able to connect to the hotspot, https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18, could you try if the update is improving things for you? bug #1972790 is another similar report -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1972790] Re: Can't connect to hotspot created on ubuntu
** Changed in: wpa (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1013012] Re: regression with sendmail and Android clients
No current issues with modern android and modern ubuntu ** Changed in: openssl (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1013012 Title: regression with sendmail and Android clients Status in openssl package in Ubuntu: Fix Released Bug description: Something appear to be broken between the Android SSL library used by K-9 Mail (and the native Android "E-mail" client), and the 1.0.0 openssl in 12.04 as used by sendmail. I am seeing this error with K-9 Mail clients trying to talk to sendmail: http://code.google.com/p/k9mail/issues/detail?id=3022 If I downgrade the sendmail-bin package to the version from Natty (which uses openssl 0.9.8), everything is fine again. Oddly, the logs in K-9 Mail show successful post-SSL-handshake communication. It is extremely unclear what is going on here. Since nothing changed in the sendmail package between natty and precise, I'm opening this against openssl. The problem could probably be anywhere in openssl, sendmail, K-9 Mail, or the Android SSL libraries, but there is at least a visible regression seen when changing from 0.9.8 to 1.0.0 on Ubuntu. :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1013012/+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 1948346] Re: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has m
I've been trying to resolve this for a while now. Everything I have tried so far has not worked, including this. I keep getting the same messages: Do you want to continue? [Y/n] y dpkg: error processing archive /var/cache/apt/archives/libnih-dbus1_1.0.3-12_amd 64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-ins tallable with libnih-dbus1 which has multiple installed instances dpkg: error processing archive /var/cache/apt/archives/libnih1_1.0.3-12_amd64.de b (--unpack): package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Errors were encountered while processing: /var/cache/apt/archives/libnih-dbus1_1.0.3-12_amd64.deb /var/cache/apt/archives/libnih1_1.0.3-12_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies. libnih-dbus-dev : Depends: libnih-dbus1 (= 1.0.3-12) but 1.0.3-6ubuntu2 is to be installed libnih-dev : Depends: libnih1 (= 1.0.3-12) but 1.0.3-6ubuntu2 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). Any more ideas? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances Status in libnih package in Ubuntu: Confirmed Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+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 1971650] Re: wrong check for "server" in libssl3.postinst
Certainly if Debian is dropping the per-package code in favor of needrestart we should head in the same direction, but we need to sort out getting needrestart included in the desktop-common seed first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971650 Title: wrong check for "server" in libssl3.postinst Status in openssl package in Ubuntu: New Bug description: A security update has just been applied to my system for openssl, and the 'reboot required' message just popped on my desktop. I looked to see why this was, and found the following code in the libssl3 postinst: # Here we issue the reboot notification for upgrades and # security updates. We do want services to be restarted when we # update for a security issue, but planned by the sysadmin, not # automatically. # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/lib/xorg/Xorg > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi Now, AFAIK this is the only package that interfaces with notify- reboot-required but omits the notification on desktops, so that seems to be an inconsistent policy; but even if we thought that was the correct policy to apply, the above check for a desktop is not because it doesn't match in the case the user is running Xwayland, which most users not using the nvidia driver will be doing now by default. Also, this is now inside a block that checks for the presence of needrestart, which is part of the server seed; so in effect this notification now *never* fires on servers, it *only* fires on desktops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 5 05:39:06 2022 InstallationDate: Installed on 2019-12-23 (863 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-15 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971650/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
Fixed in https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Triaged Status in cyrus-sasl2 source package in Jammy: In Progress Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1971272] Re: Merge cyrus-sasl2 from Debian unstable for kinetic
It's back to being a sync: https://launchpad.net/ubuntu/+source/cyrus- sasl2/2.1.28+dfsg-6 ** Changed in: cyrus-sasl2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1971272 Title: Merge cyrus-sasl2 from Debian unstable for kinetic Status in cyrus-sasl2 package in Ubuntu: Fix Released Bug description: Upstream: tbd Debian: 2.1.28+dfsg-4 Ubuntu: 2.1.27+dfsg2-3ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### cyrus-sasl2 (2.1.28+dfsg-4) unstable; urgency=medium * d/copyright: java/* files were removed upstream * d/copyright: Reformat the default license's margin * d/copyright: Add project's license to include/makemd5.c * Move SCRAM to libsasl2-modules (Closes: #977360) * Install additional GS2 module for Heimdal * Remove Roberto from the Uploaders * Drop 0005-Fixes-in-library-mutexes.patch * Drop 0021-Fix-keytab-option-for-MIT-Kerberos.patch * Remove former logcheck conffile (Closes: #1009851) * lintian: Fix excessive-priority-for-library-package * lintian: Fix package-contains-empty-directory -- Bastian Germann Wed, 20 Apr 2022 01:01:01 +0200 cyrus-sasl2 (2.1.28+dfsg-3) unstable; urgency=high * Set MIT/Heimdal CFLAGS instead of CPPFLAGS * Drop unnecessary 0027-properly-create-libsasl2.pc.patch * Prevent installing outdated ChangeLog (Closes: #1009681) * Remove debug log message and its logcheck rule (Closes: #805310) * Self-reference pluginviewer man as saslpluginviewer (Closes: #1009380) * Get rid of broken README.configure-options * Add sasldbconverter2.8 manpage * d/copyright: Add missing KTH license * Install libsasl.5 manpage [ Debian Janitor ] * Remove constraints unnecessary since buster -- Bastian Germann Fri, 15 Apr 2022 12:02:13 +0200 cyrus-sasl2 (2.1.28+dfsg-2) unstable; urgency=medium * Remove cruft -- Bastian Germann Fri, 25 Feb 2022 18:58:54 +0100 cyrus-sasl2 (2.1.28+dfsg-1) experimental; urgency=medium * Drop upstream patches * Import new release signing key * Reset repacksuffix * New upstream version 2.1.28+dfsg (CVE-2022-24407) * Rebase 0027-properly-create-libsasl2.pc.patch -- Bastian Germann Tue, 22 Feb 2022 23:40:47 +0100 cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium [ Andreas Hasenack ] * Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152) -- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100 cyrus-sasl2 (2.1.27+dfsg2-2) unstable; urgency=medium [ Helmut Grohne ] * Fix FTCBFS: (Closes: #928512) + cross.patch: Support caching SPNEGO support test. + Provide SPNEGO support test result. [ Vagrant Cascadian ] * Set date in man pages (Closes: #995145) -- Bastian Germann Wed, 17 Nov 2021 01:23:49 +0100 cyrus-sasl2 (2.1.27+dfsg2-1) unstable; urgency=medium * Add bage to uploaders (Closes: #799864) * Use upstream patches where possible * Amend off-by-one in _sasl_add_string function * Replace some patches by upstream equivalents * Apply the patches in order of to their prefixes * Add missing caret (^) in logcheck rule (Closes: #830764) * Remove unnecessary GPL copy * Add missing copyright/licenses * Repack, getting rid of more problematic files * Build html documentation * Make the package rebuildable * Remove outdated README.Debian info * Disable autostart via debhelper * Drop unnecessary patch * Remove alternative, old build dep libmysqlclient-dev Annotate documentation Build-Depends with :native [ Frédéric Brière ] * Make logcheck snippet compatible with systemd journal -- Bastian Germann Sun, 14 Nov 2021 14:11:18 +0100 cyrus-sasl2 (2.1.27+dfsg-2.3) unstable; urgency=medium * Non-maintainer upload. * d/watch: Check the github releases page * Get rid of a patch's patch * Recover upstream-compatible patch license (Closes: #996866) + Relicense libobj patch * Fix lintian: unused-override ### Old Ubuntu Delta ### cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1) jammy; urgency=medium * SECURITY UPDATE: SQL injection in SQL plugin - debian/patches/CVE-2022-24407.patch: escape password for SQL insert/update commands in plugins/sql.c. - CVE-2022-24407 -- Marc Deslauriers Tue, 22 Feb 2022 14:17:18 -0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1971272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-package
[Touch-packages] [Bug 1677781] Re: Missing dep8 tests
Fixed in https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-6 ** Changed in: cyrus-sasl2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1677781 Title: Missing dep8 tests Status in cyrus-sasl2 package in Ubuntu: Fix Released Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source cyrus-sasl2 zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/cyrus-sasl2 status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1 3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe 4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5 WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5 Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G WY9JzBOc6MUi46Hh9ZN5 =szTz -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+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 1973760] Re: Crash when using DIGEST-MD5 with SSF>=128
Fixed in https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-6 ** Changed in: cyrus-sasl2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1973760 Title: Crash when using DIGEST-MD5 with SSF>=128 Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I'm still troubleshooting this, but at the moment apps negotiating a DIGEST-MD5 authentication and requesting some form of transport encryption (ssf != 0) are crashing. The only example I have so far is the openldap client tools (so just one app really). ssf=0 works: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=0 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 0 dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth ssf=128 crashes: $ ldapwhoami -U ubuntu@lxd -w ubuntusecret -O maxssf=128 SASL/DIGEST-MD5 authentication started SASL username: ubuntu@lxd SASL SSF: 128 SASL data security layer installed. Segmentation fault (core dumped) The crash seems to be inside openssl. I'll get a proper stack trace. 2.1.27, also built with openssl3, does not crash. So far only 2.1.28 (in kinetic-proposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1973760/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
Dear, my ubuntu is already uptodate and the result of the command is : $ dpkg -l | grep wpasupplicant ii wpasupplicant2:2.10-6ubuntu1 amd64client support for WPA and WPA2 (IEEE 802.11i) for the moment I use a 18.04.6 version when i need to be connected to this hotspot (all other recent efi Linux version I have tested present the same problem (fedora 35; debian 11.3; freeBSD) thanks for your support -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1975496] [NEW] package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu
Public bug reported: I had fixed an earlier problem with /etc/ssh/sshd_config but this error persists. I've tried removing the package, rebooting, and adding the openssh-server. package. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: firefox-locale-en:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 06:37:07 2022 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-06 (593 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-09-29 (235 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1975496 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: I had fixed an earlier problem with /etc/ssh/sshd_config but this error persists. I've tried removing the package, rebooting, and adding the openssh-server. package. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: firefox-locale-en:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 06:37:07 2022 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-06 (593 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-09-29 (235 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1975496/+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 1975430] Re: I can select the Xorg Nouveau server, but not click on "apply"
confirming my guess: this error occurs when having somehow "exotic" linux-image-* package names - even thoug dpkg-deb can build them and dpkg is installing them without compaints, they lead to an error here. A custom built mainline kernel without special naming can be installed without triggering the bug described here! likely its the regular expression in Line 86 of kerneldetection.py that I am right now unable to improve... the goal would probably be either to improve the expression to be able to deal with all legal package names, or give an error/exception that the kernel name/version could not be parsed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1975430 Title: I can select the Xorg Nouveau server, but not click on "apply" Status in software-properties package in Ubuntu: New Bug description: I want to switch back from the nvidia driver to nouveau. In the dialog the last row lets me select the Nouveau driver, but the "apply" button is inactive and doesnt let me apply the change. There is also no message or anything that would allow me to understand, why this is the case, and what i could do about it. heres also the outout of ubuntu-drivers debug that I learned in anothe bug can be important: === log messages from detection === DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on video abi DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on video abi DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video abi DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:Skipping check for rt
[Touch-packages] [Bug 1975430] Re: I can select the Xorg Nouveau server, but not click on "apply"
OK, tracking down this stacktrace I found the problem: it appears that kerneldetection.py fails when I have a custom built mainline package installed. that would make this a bug in "ubuntu-drivers-common" It appears to be irrelevant that I am *running* the standard Ubuntu generic kernel - the error occurs when I just have this kernel package installed, and it goes away when I remove it! Maybe it doesnt happen with all custom packages, i have a slightly special name: linux-image-5.17.9-hs-custom-2022-05-22-a - I assumed when dpkg-deb can build it, this name is fine. Might add more detail later... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1975430 Title: I can select the Xorg Nouveau server, but not click on "apply" Status in software-properties package in Ubuntu: New Bug description: I want to switch back from the nvidia driver to nouveau. In the dialog the last row lets me select the Nouveau driver, but the "apply" button is inactive and doesnt let me apply the change. There is also no message or anything that would allow me to understand, why this is the case, and what i could do about it. heres also the outout of ubuntu-drivers debug that I learned in anothe bug can be important: === log messages from detection === DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on video abi DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on video abi DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video abi DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:Skipping check for rtl8812au-dkms
[Touch-packages] [Bug 1975430] Re: I can select the Xorg Nouveau server, but not click on "apply"
Another additional info:
I checked if I can do it on the commandline, but I get a Python
stacktrace instead:
# ubuntu-drivers list
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 465, in list
linux_modules = UbuntuDrivers.detect.get_linux_modules_metapackage(cache,
package)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 1290, in
get_linux_modules_metapackage
linux_image_meta = get_linux_image(apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 1224, in
get_linux_image
return kernel_detection.get_linux_image_metapackage()
File "/usr/lib/python3/dist-packages/UbuntuDrivers/kerneldetection.py", line
153, in get_linux_image_metapackage
return self._get_linux_metapackage('image')
File "/usr/lib/python3/dist-packages/UbuntuDrivers/kerneldetection.py", line
99, in _get_linux_metapackage
if self._is_greater_than(current_version,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/kerneldetection.py", line
51, in _is_greater_than
term2 = '%s-%s' % (match2.group(1),
AttributeError: 'NoneType' object has no attribute 'group'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1975430
Title:
I can select the Xorg Nouveau server, but not click on "apply"
Status in software-properties package in Ubuntu:
New
Bug description:
I want to switch back from the nvidia driver to nouveau.
In the dialog the last row lets me select the Nouveau driver, but the
"apply" button is inactive and doesnt let me apply the change.
There is also no message or anything that would allow me to
understand, why this is the case, and what i could do about it.
heres also the outout of ubuntu-drivers debug that I learned in anothe
bug can be important:
=== log messages from detection ===
DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on
video abi
DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend
on video abi
DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on
video abi
DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on
video abi
DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video
abi
DEBUG:root:_get_db_name: output
ID_PCI_CLASS_FROM_DATABASE=Display controller
ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]
DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0,
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
DEBUG:root:_get_db_name: output
ID_PCI_CLASS_FROM_DATABASE=Display controller
ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]
DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0,
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
DEBUG:root:_get_db_name: output
ID_PCI_CLASS_FROM_DATABASE=Display controller
ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]
DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0,
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
DEBUG:root:_get_db_name: output
ID_PCI_CLASS_FROM_DATABASE=Display controller
ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
ID_PCI_INTERFACE_FROM
[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4
Hi Barto,
Sorry for the delay on getting beck to this one.
Is dhcp running? It seems there is a network configuration issue here.
Therefore, I am marking this bug as invalid.
If you still believe this is a bug and not a configuration issue,
please, add the steps needed to get the issue reproduced and include the
ssh debugging logs here.
** Tags removed: server-triage-discuss
** Changed in: openssh (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1964642
Title:
Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
but can connect to Ubuntu 20.4
Status in openssh package in Ubuntu:
Invalid
Bug description:
Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a
Windows 10 host with Packer 1.5.6, using an unattended installation.
The Packer command was:
"boot_command": [
" ",
"autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
""
],
The user-data file was:
#cloud-config
autoinstall:
version: 1
identity:
realname: mclibre
hostname: ubuntu
password:
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
username: mclibre
locale: es_ES.UTF-8
keyboard:
layout: es
network:
network:
version: 2
ethernets:
ens33: {dhcp4: true, dhcp-identifier: mac}
ssh:
install-server: true
late-commands:
- sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/'
/target/etc/dhcp/dhclient.conf
- 'sed -i "s/dhcp4: true/&\n dhcp-identifier: mac/"
/target/etc/netplan/00-installer-config.yaml'
Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using
packer 1.5.6 but Packer can't create the image because once the installation is
done, after rebooting the SSH server does not answer (the packer log error
says: SSH handshake err: Timeout during SSH handshake).
I have tried with the last version of Packer, Packer 1.8.0, and the result is
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server
20.4.1, .2, .3 or .4 image.
I can provide as much aditional information as you want.
Thanking you in advance,
Bartolome Sintes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+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 1975459] Re: Prints blank pages
Thank you very much. As this bug can easily get worked around and as it is also fixed in cups-filters 2.x, I will not provide a fix here. Closing ... ** Changed in: cups (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1975459 Title: Prints blank pages Status in cups package in Ubuntu: Won't Fix Bug description: When printing using a wireless printer from Ubuntu it only prints blank pages. Occasinally, but not reproducable, it prints 1 job after boot and then fails. Printing from ipad and android devies to the same printer always works. This problem has persisted for several years, different versions of ubuntu on different networks and computers and several different printers. The attached file contains the cups debug log. The machine was booted 24 hours earlier. The first print job succeeded, the second failed with printer busy. I then tried to log out and back in, and only got blank pages. When that happens, the printer will continue to print blank pages until the tray is empty or removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1975459] Re: Prints blank pages
Yes, that worked. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1975459 Title: Prints blank pages Status in cups package in Ubuntu: Incomplete Bug description: When printing using a wireless printer from Ubuntu it only prints blank pages. Occasinally, but not reproducable, it prints 1 job after boot and then fails. Printing from ipad and android devies to the same printer always works. This problem has persisted for several years, different versions of ubuntu on different networks and computers and several different printers. The attached file contains the cups debug log. The machine was booted 24 hours earlier. The first print job succeeded, the second failed with printer busy. I then tried to log out and back in, and only got blank pages. When that happens, the printer will continue to print blank pages until the tray is empty or removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
Just update your Ubuntu and make sure to have wpasupplicant version 2.10-6ubuntu1. In a shell you should see: $ dpkg -l | grep wpasupplicant ii wpasupplicant2:2.10-6ubuntu1 -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1974456] Re: regression: apt.postint fails if never previously configured
@David I was able to reproduce this with mmdebstrap as it uses -updates pocket, but not with debootstrap as it only uses the release pockets. Which tool were you using to bootstrap your system? It's possible we might just want keep the fix in -proposed and not release it to updates if it does not affect the supported bootstrapping tools. ** Description changed: + [Impact] + bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. + + This is not a problem on updates, only on new installs, so impact is + limited to bootstrapping tools that enable -updates, such as mmdebstrap. + + [Test case] + + bootstrapping with -updates enabled can easily be tested with + mmdebstrap: + + mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal + + for example, on focal: + + Setting up apt (2.0.8) ... + /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found + dpkg: error processing package apt (--configure): + installed apt package post-installation script subprocess returned error exit status 127 + + [Regression potential] + We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. + + [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: - # create kernel autoremoval blacklist on update - if dpkg --compare-versions "$2" lt 0.9.9.3; then - /etc/kernel/postinst.d/apt-auto-removal - fi + # create kernel autoremoval blacklist on update + if dpkg --compare-versions "$2" lt 0.9.9.3; then + /etc/kernel/postinst.d/apt-auto-removal + fi If I understand correctly, "$2" is the most-recently-configured-version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: - $ dpkg --configure -a - [...] - Setting up apt (2.0.8) ... - /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found - dpkg: error processing package apt (--configure): - installed apt package post-installation script subprocess returned error exit status 127 + $ dpkg --configure -a + [...] + Setting up apt (2.0.8) ... + /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found + dpkg: error processing package apt (--configure): + installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed
[Touch-packages] [Bug 1005169] Re: Regression bug after ssl update.
Can you check if this 12 years old bug is still the case on a currently supported Ubuntu release? https://wiki.ubuntu.com/Releases If not please provide details as requested in the previous comment. ** Changed in: openssl (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1005169 Title: Regression bug after ssl update. Status in openssl package in Ubuntu: Incomplete Bug description: After the latest Secure Socket Layer update, my computer unable to mount shares on the from other computers on the network. The odd thing is Rythembox will open, and mount the shared music directories on the network. Connection can be established by Using Connect to server ,and using the computers names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1005169/+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 1013012] Re: regression with sendmail and Android clients
Can you check if this 10 years old bug is still the case on a currently supported Ubuntu release? https://wiki.ubuntu.com/Releases ** Changed in: openssl (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1013012 Title: regression with sendmail and Android clients Status in openssl package in Ubuntu: Incomplete Bug description: Something appear to be broken between the Android SSL library used by K-9 Mail (and the native Android "E-mail" client), and the 1.0.0 openssl in 12.04 as used by sendmail. I am seeing this error with K-9 Mail clients trying to talk to sendmail: http://code.google.com/p/k9mail/issues/detail?id=3022 If I downgrade the sendmail-bin package to the version from Natty (which uses openssl 0.9.8), everything is fine again. Oddly, the logs in K-9 Mail show successful post-SSL-handshake communication. It is extremely unclear what is going on here. Since nothing changed in the sendmail package between natty and precise, I'm opening this against openssl. The problem could probably be anywhere in openssl, sendmail, K-9 Mail, or the Android SSL libraries, but there is at least a visible regression seen when changing from 0.9.8 to 1.0.0 on Ubuntu. :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1013012/+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 989608] Re: upgrade crashes
This is an upgrade issue on an obsolete Ubuntu release, likely fixed or no longer applicable. Let us know otherwise. ** Changed in: openssl (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/989608 Title: upgrade crashes Status in openssl package in Ubuntu: Incomplete Bug description: after doing: sudo apt-get update sudo apt-get upgrade I get: You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: openssl : Depends: libssl1.0.0 (>= 1.0.1) but 1.0.0e-2ubuntu4.5 is installed E: Unmet dependencies. Try using -f. System is after upgrade from 11.10 to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/989608/+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 591713] Re: Illegal instruction in AES ciphers on WinChip C6
Can you check if this 12 years old bug is still the case on a currently supported Ubuntu release? https://wiki.ubuntu.com/Releases ** Changed in: openssl (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/591713 Title: Illegal instruction in AES ciphers on WinChip C6 Status in openssl package in Ubuntu: Incomplete Bug description: Binary package hint: openssl Some ciphers from openssl-0.9.8k-7ubuntu8 in Ubuntu 10.04 terminate with an Illegal instruction signal (SIGILL) when running on a WinChip C6 processor: $ cat openssl.sh #!/bin/sh for c in `openssl list-cipher-commands` do echo $c echo -n Hello | openssl enc -$c -K 0 -iv 0 > /dev/null done $ openssl.sh aes-128-cbc Illegal instruction aes-128-ecb Illegal instruction aes-192-cbc Illegal instruction aes-192-ecb Illegal instruction aes-256-cbc Illegal instruction aes-256-ecb Illegal instruction base64 bf bf-cbc bf-cfb bf-ecb bf-ofb cast cast-cbc cast5-cbc cast5-cfb cast5-ecb cast5-ofb des des-cbc des-cfb des-ecb des-ede des-ede-cbc des-ede-cfb des-ede-ofb des-ede3 des-ede3-cbc des-ede3-cfb des-ede3-ofb des-ofb des3 desx rc2 rc2-40-cbc rc2-64-cbc rc2-cbc rc2-cfb rc2-ecb rc2-ofb rc4 rc4-40 I'm using a default kernel: $ uname -a Linux vdr 2.6.32-22-386 #36-Ubuntu SMP Fri Jun 4 00:27:09 UTC 2010 i586 GNU/Linux This is the CPU info: $ cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 5 model : 4 model name : WinChip C6 stepping: 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de msr mce cx8 mmx centaur_mcr up bogomips: 399.48 clflush size: 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management: I ran into this when I couldn't access this machine via ssh 4.7p1, because this version selects the aes128-cbc cipher by default. Ssh immediately terminates with "Connection closed by ...". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/591713/+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 119294] Re: OpenSSL should support VIA PadLock
>PadLock for x86_64 is supported by OpenSSL 1.0.1 and the trunk (1.1.0) >branches - but not on the 1.0.0 and previous branches. >Is there a chance Ubuntu will release OpenSSL 1.0.1+ packages in a PPA or >provide instructions on how to properly build OpenSSL yourself for Ubuntu? Every supported version of Ubunti now has 1.0.1+. ** Changed in: openssl (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/119294 Title: OpenSSL should support VIA PadLock Status in ssl-cert: Fix Released Status in openssh package in Ubuntu: Invalid Status in openssl package in Ubuntu: Fix Released Status in openssl package in Debian: Fix Released Bug description: VIA PadLock is a hardware cryptography engine for AES and SHA1/256. OpenSSL now supports PadLock, but a cache logic bug prevents the use of the PadLock engine. A fairly trivial patch exists and has been merged in OpenSSL 0.9.8g upstream. See bug #119295 for the patch and more details. Initial work on PadLock support was done some time ago : http://www.logix.cz/michal/devel/padlock/ To manage notifications about this bug go to: https://bugs.launchpad.net/ssl-cert/+bug/119294/+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 1975407] Re: pulseaudio is getting crashed
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1975407 Title: pulseaudio is getting crashed Status in pulseaudio package in Ubuntu: Incomplete Bug description: Operating System: Ubuntu 22.04 Life cycle: LTS Architecture: AMD64 Kernel version (uname -a): 5.15.0-30-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnm 3822 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 22 12:08:58 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.104 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.68 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.33 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4540s dmi.product.sku: B7A48EA#ABV dmi.product.version: A1008C11 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2022-01-28T22:42:20.933634 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1975407/+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 1972790] Re: Can't connect to hotspot created on ubuntu
Thanks, it means at least we can get the WPA3 case out of this report and focus on the other issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1974037] Re: openssl: EVP_EC_gen() segfault without init
** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1974037 Title: openssl: EVP_EC_gen() segfault without init Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Jammy: Confirmed Status in openssl source package in Kinetic: Confirmed Status in openssl package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1010958: Source: sscg Version: 3.0.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sscg&ver=3.0.2-1%2Bb1 ... 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11 SIGSEGV 04:32:21 MALLOC_PERTURB_=87 /<>/obj-x86_64-linux-gnu/generate_rsa_key_test ... Summary of Failures: 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11 SIGSEGV Ok: 9 Expected Fail: 0 Fail: 1 Unexpected Pass:0 Skipped:0 Timeout:0 dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 make: *** [debian/rules:6: binary-arch] Error 25 This has also been reported on the openssl-users mailing list: https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+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 1974035] Re: openssl: Merge 3.0.3-4 from Debian unstable
Here's a MP using git-ubuntu (well, with a lot of manual fiddling): https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 I'd appreciate it the upload would be using rich history support: https://lists.ubuntu.com/archives/ubuntu-devel/2021-October/041649.html as the delta is fairly substantial, this would make future merges probably easier. ** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1974035 Title: openssl: Merge 3.0.3-4 from Debian unstable Status in openssl package in Ubuntu: Confirmed Bug description: The version 3.0.3-4 from Debian unstable should be merged in Kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974035/+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 1975459] Re: Prints blank pages
The bug itself is that the implicitclass CUPS backend used by cups- browsed is not able to determine the correct parameters to generate Apple Raster from the PDF input. Your printer needs 600 dpi and for some reason 1200 dpi got sent. In cups-filters 2.x (to appear in Ubuntu 22.10) this is fixed. For the time being, please create an explicit print queue for your printer (instead of letting cups-browsed auto-creating one): lpadmin -p Brother -E -v 'ipp://Brother%20HL-L2357DW._ipp._tcp.local/' -m everywhere Try to print on this queue. Does it work? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1975459 Title: Prints blank pages Status in cups package in Ubuntu: Incomplete Bug description: When printing using a wireless printer from Ubuntu it only prints blank pages. Occasinally, but not reproducable, it prints 1 job after boot and then fails. Printing from ipad and android devies to the same printer always works. This problem has persisted for several years, different versions of ubuntu on different networks and computers and several different printers. The attached file contains the cups debug log. The machine was booted 24 hours earlier. The first print job succeeded, the second failed with printer busy. I then tried to log out and back in, and only got blank pages. When that happens, the printer will continue to print blank pages until the tray is empty or removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1354110] Re: Merge openssl 1.0.1i-2 (main) from Debian unstable (main)
*** This bug is a duplicate of bug 1608200 *** https://bugs.launchpad.net/bugs/1608200 ** This bug has been marked a duplicate of bug 1608200 please merge openssl from Debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1354110 Title: Merge openssl 1.0.1i-2 (main) from Debian unstable (main) Status in openssl package in Ubuntu: Confirmed Bug description: debdiff attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1354110/+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 1971650] Re: wrong check for "server" in libssl3.postinst
FWIW, Debian just scrapped the postinst entirely, advising users to use needrestart or checkrestart instead. In my upcoming merge I'll revert the deletion, but I'd be happy to go back and remove that part of the delta once I understand how all the pieces fit together. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971650 Title: wrong check for "server" in libssl3.postinst Status in openssl package in Ubuntu: New Bug description: A security update has just been applied to my system for openssl, and the 'reboot required' message just popped on my desktop. I looked to see why this was, and found the following code in the libssl3 postinst: # Here we issue the reboot notification for upgrades and # security updates. We do want services to be restarted when we # update for a security issue, but planned by the sysadmin, not # automatically. # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/lib/xorg/Xorg > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi Now, AFAIK this is the only package that interfaces with notify- reboot-required but omits the notification on desktops, so that seems to be an inconsistent policy; but even if we thought that was the correct policy to apply, the above check for a desktop is not because it doesn't match in the case the user is running Xwayland, which most users not using the nvidia driver will be doing now by default. Also, this is now inside a block that checks for the presence of needrestart, which is part of the server seed; so in effect this notification now *never* fires on servers, it *only* fires on desktops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 5 05:39:06 2022 InstallationDate: Installed on 2019-12-23 (863 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-15 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971650/+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 1974456] Re: regression: apt.postint fails if never previously configured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Bionic) Status: New => Confirmed -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Bug description: #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Focal) Status: New => Confirmed -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Bug description: #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Confirmed Bug description: #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1975459] Re: Prints blank pages
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1975459 Title: Prints blank pages Status in cups package in Ubuntu: New Bug description: When printing using a wireless printer from Ubuntu it only prints blank pages. Occasinally, but not reproducable, it prints 1 job after boot and then fails. Printing from ipad and android devies to the same printer always works. This problem has persisted for several years, different versions of ubuntu on different networks and computers and several different printers. The attached file contains the cups debug log. The machine was booted 24 hours earlier. The first print job succeeded, the second failed with printer busy. I then tried to log out and back in, and only got blank pages. When that happens, the printer will continue to print blank pages until the tray is empty or removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1975467] [NEW] package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' befor
Public bug reported: While updating Ubuntu 20.04.4 TLS I'm getting an error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 11:45:21 2022 DuplicateSignature: package:passwd:1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] Unpacking passwd (1:4.8.1-1ubuntu5.20.04.2) over (1:4.8.1-1ubuntu5.20.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-43VTuR/5-passwd_1%3a4.8.1-1ubuntu5.20.04.2_amd64.deb (--unpack): unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted InstallationDate: Installed on 2021-05-24 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: shadow Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1975467 Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted Status in shadow package in Ubuntu: New Bug description: While updating Ubuntu 20.04.4 TLS I'm getting an error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 11:45:21 2022 DuplicateSignature: package:passwd:1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] Unpacking passwd (1:4.8.1-1ubuntu5.20.04.2) over (1:4.8.1-1ubuntu5.20.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-43VTuR/5-passwd_1%3a4.8.1-1ubuntu5.20.04.2_amd64.deb (--unpack): unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted InstallationDate: Installed on 2021-05-24 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: shadow Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1975467/+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 1975459] [NEW] Prints blank pages
You have been subscribed to a public bug: When printing using a wireless printer from Ubuntu it only prints blank pages. Occasinally, but not reproducable, it prints 1 job after boot and then fails. Printing from ipad and android devies to the same printer always works. This problem has persisted for several years, different versions of ubuntu on different networks and computers and several different printers. The attached file contains the cups debug log. The machine was booted 24 hours earlier. The first print job succeeded, the second failed with printer busy. I then tried to log out and back in, and only got blank pages. When that happens, the printer will continue to print blank pages until the tray is empty or removed. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Prints blank pages https://bugs.launchpad.net/bugs/1975459 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups 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 1975347] Re: Backport OPENSSL_strcasecmp fixes from 3.0 branch
*** This bug is a duplicate of bug 1974037 ***
https://bugs.launchpad.net/bugs/1974037
** This bug has been marked a duplicate of bug 1974037
openssl: EVP_EC_gen() segfault without init
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1975347
Title:
Backport OPENSSL_strcasecmp fixes from 3.0 branch
Status in openssl package in Ubuntu:
New
Bug description:
The recent openssl update to 3.0.2-0ubuntu1.2 in jammy included some
buggy changes related to OPENSSL_strcasecmp. Briefly, it's possible
for OPENSSL_strcasecmp to be called before the global locale_t object
has been initialized, causing a crash in strcasecmp_l. For example,
this bug can be trivially triggered with the program below.
#include
int main()
{
EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
}
The problem is already fixed in the openssl-3.0 branch. Please
consider backporting this PR
https://github.com/openssl/openssl/pull/18293 or updating the ubuntu
package to a more recent commit of that branch that includes the
fixes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1975347/+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 1975460] Re: iwlwifi cannot load firmware, wifi card does not work Intel Corporation Wireless 7260
** Tags added: jammy
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
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/1975460
Title:
iwlwifi cannot load firmware, wifi card does not work Intel
Corporation Wireless 7260
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
With ubuntu 20.04, it worked.
After upgrading to 22.04, stopped working.
I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
Can't work!!
Booting back to old linux kernel 5.13.x wifi works again!
No windows installed, not a dual boot.
I have other older hp laptop which has a different wifi card, that
works well with the new kernel.
Please fix this bug.
Thank you!
Full ubuntu-bug report has been sent also.
Error msg:
[ 23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
[ 28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping
registers
[ 28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
[ 28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b
0010 d014
[ 28.356437] iwlwifi :3d:00.0: 0020:
c0608086 00c8 0100
[ 28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10
0106ec11 101100ca
[ 28.356480] iwlwifi :3d:00.0: 0060: 00080812 0405
00010001
[ 28.356523] iwlwifi :3d:00.0: 0080:
[ 28.356566] iwlwifi :3d:00.0: 00a0:
[ 28.356607] iwlwifi :3d:00.0: 00c0: c823d001
0d00 00814005 fee003f8
[ 28.356649] iwlwifi :3d:00.0: 00e0:
[ 28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000
00462031 2000 2000 000e
[ 28.356732] iwlwifi :3d:00.0: 0120:
[ 28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff
15410018 08460846 0001000b 0141cafe 00f01e1f
[ 28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
[ 28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000
0800
[ 28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144
8000 803a 80008040 00080046
[ 28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
[ 28.357034] iwlwifi :3d:00.0: : 14010001 4000
00462031 2000 2000 000e
[ 28.357075] iwlwifi :3d:00.0: 0020:
[ 28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0)
config registers:
[ 28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005
00010010 003d3d3c 01f1
[ 28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1
0040 0002010a
[ 28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008
00816405 fee002d8
[ 28.357399] iwlwifi :3c:01.0: 0060: 0034b009 04001060
04000800 8000 0a730100 76b50080 21901d27
[ 28.357440] iwlwifi :3c:01.0: 0080: 000f 3308
00790010 8000 116b 000f0022
[ 28.357482] iwlwifi :3c:01.0: 00a0:
c00d 240412d8
[ 28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010
01203c11 10110042 014803c0
[ 28.357565] iwlwifi :3c:01.0: 00e0: 00040800 0400
00010042
[ 28.357607] iwlwifi :3c:01.0: 0100: 14010001
00062011 2000 00a0
[ 28.357648] iwlwifi :3c:01.0: 0120:
[ 28.357690] iwlwifi :3c:01.0: 0140: 20c10002 0800
047f0009 8001
[ 28.357739] iwlwifi :3c:01.0: 0160:
[ 28.357780] iwlwifi :3c:01.0: 0180: 00
[Touch-packages] [Bug 1975347] Re: Backport OPENSSL_strcasecmp fixes from 3.0 branch
EVP_EC_gen() is just a macro that expands to EVP_PKEY_Q_keygen(), so
yeah, it's exactly the same as
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1975347
Title:
Backport OPENSSL_strcasecmp fixes from 3.0 branch
Status in openssl package in Ubuntu:
New
Bug description:
The recent openssl update to 3.0.2-0ubuntu1.2 in jammy included some
buggy changes related to OPENSSL_strcasecmp. Briefly, it's possible
for OPENSSL_strcasecmp to be called before the global locale_t object
has been initialized, causing a crash in strcasecmp_l. For example,
this bug can be trivially triggered with the program below.
#include
int main()
{
EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
}
The problem is already fixed in the openssl-3.0 branch. Please
consider backporting this PR
https://github.com/openssl/openssl/pull/18293 or updating the ubuntu
package to a more recent commit of that branch that includes the
fixes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1975347/+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 1975460] [NEW] iwlwifi cannot load firmware, wifi card does not work Intel Corporation Wireless 7260
Public bug reported:
With ubuntu 20.04, it worked.
After upgrading to 22.04, stopped working.
I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
Can't work!!
Booting back to old linux kernel 5.13.x wifi works again!
No windows installed, not a dual boot.
I have other older hp laptop which has a different wifi card, that works
well with the new kernel.
Please fix this bug.
Thank you!
Full ubuntu-bug report has been sent also.
Error msg:
[ 23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N
7260, REV=0x144
[ 28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
[ 28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping
registers
[ 28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
[ 28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b
0010 d014
[ 28.356437] iwlwifi :3d:00.0: 0020:
c0608086 00c8 0100
[ 28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10
0106ec11 101100ca
[ 28.356480] iwlwifi :3d:00.0: 0060: 00080812 0405
00010001
[ 28.356523] iwlwifi :3d:00.0: 0080:
[ 28.356566] iwlwifi :3d:00.0: 00a0:
[ 28.356607] iwlwifi :3d:00.0: 00c0: c823d001
0d00 00814005 fee003f8
[ 28.356649] iwlwifi :3d:00.0: 00e0:
[ 28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000
00462031 2000 2000 000e
[ 28.356732] iwlwifi :3d:00.0: 0120:
[ 28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff
15410018 08460846 0001000b 0141cafe 00f01e1f
[ 28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
[ 28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000
0800
[ 28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144
8000 803a 80008040 00080046
[ 28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
[ 28.357034] iwlwifi :3d:00.0: : 14010001 4000
00462031 2000 2000 000e
[ 28.357075] iwlwifi :3d:00.0: 0020:
[ 28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0) config
registers:
[ 28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005
00010010 003d3d3c 01f1
[ 28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1
0040 0002010a
[ 28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008
00816405 fee002d8
[ 28.357399] iwlwifi :3c:01.0: 0060: 0034b009 04001060
04000800 8000 0a730100 76b50080 21901d27
[ 28.357440] iwlwifi :3c:01.0: 0080: 000f 3308
00790010 8000 116b 000f0022
[ 28.357482] iwlwifi :3c:01.0: 00a0:
c00d 240412d8
[ 28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010
01203c11 10110042 014803c0
[ 28.357565] iwlwifi :3c:01.0: 00e0: 00040800 0400
00010042
[ 28.357607] iwlwifi :3c:01.0: 0100: 14010001
00062011 2000 00a0
[ 28.357648] iwlwifi :3c:01.0: 0120:
[ 28.357690] iwlwifi :3c:01.0: 0140: 20c10002 0800
047f0009 8001
[ 28.357739] iwlwifi :3c:01.0: 0160:
[ 28.357780] iwlwifi :3c:01.0: 0180:
[ 28.357821] iwlwifi :3c:01.0: 01a0:
[ 28.357861] iwlwifi :3c:01.0: 01c0:
[ 28.357902] iwlwifi :3c:01.0: 01e0:
[ 28.357943] iwlwifi :3c:01.0: 0200:
[ 28.357969] iwlwifi :3d:00.0: Could not load the [0] uCode section
[ 28.358001] iwlwifi :3d:00.0: Fai
[Touch-packages] [Bug 1975408] Re: Performance is much worse than expected (Normal friendly behaviors)
Thanks for the bug report. You seem to have gotten your graphics packages from the 'oibaf' PPA. That is known to be frequently broken and is UNSUPPORTED. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1975408 Title: Performance is much worse than expected (Normal friendly behaviors) Status in Ubuntu: Invalid Bug description: Operating System: Ubuntu 22.04 Life cycle: LTS Architecture: AMD64 Kernel version (uname -a): 5.15.0-30-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 22 12:10:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: sysdig/0.27.1, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:17f4] MachineType: Hewlett-Packard HP ProBook 4540s ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=cf164159-2e29-4cee-aef2-f8d16c319f1a ro snapd_recovery_mode snap_core quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.104 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.68 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.33 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4540s dmi.product.sku: B7A48EA#ABV dmi.product.version: A1008C11 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.14.1+22.04.20211217-0ubuntu2 version.libdrm2: libdrm2 2.4.110+git2205140500.3f266e~oibaf~j version.libgl1-mesa-dri: libgl1-mesa-dri 22.2~git2205160600.3c0f34~oibaf~j version.libgl1-mesa-glx: libgl1-mesa-glx 22.2~git2205170600.fffafa~oibaf~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975408/+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 1975445] Re: Crash back to login screen when connecting external monitor in 22.04 LTS
Thanks for the bug report. Firstly, you are using the (low quality) open source 'nouveau' graphics driver. It is known to cause such problems so please start by using the 'Additional Drivers' app to install an official Nvidia driver. After installing the driver and rebooting, if the problem still occurs then please follow the steps in https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: multimonitor nouveau -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975445 Title: Crash back to login screen when connecting external monitor in 22.04 LTS Status in Ubuntu: Incomplete Bug description: I upgraded my Ubuntu 20.04 LTS to 22.04 LTS using do-release-upgrade -d command on 2022/05/20 And then my external monitor, who worked well before on 20.04 LTS, was never able to connect. Everytime I try to connect it, set Joint Displays and press apply on the setting panel, the system crashes and goes back to login screen. When I switch to Windows on the same computer, external monitor is able to connect. Bug only appears on the new 22.04 LTS. System info: Device: Dell Inc. Precision 7750 Processor: Intel W-10855M Graphics: Intel UHD Graphics P630 / NVIDIA Quadro RTX 3000 Built-in Display: 1920 X 1080, 60.00 HZ External monitor where the bug appears: PHL 230B8Q (1920 X 1200, 59.950 HZ) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 11:42:00 2022 DistUpgraded: 2022-05-20 18:00:09,901 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9bf6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c4] NVIDIA Corporation TU106GLM [Quadro RTX 3000 Mobile / Max-Q] [10de:1f36] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU106GLM [Quadro RTX 3000 Mobile / Max-Q] [1028:09c4] InstallationDate: Installed on 2021-06-18 (338 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Precision 7750 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f247525-7971-47a5-b2b2-8f3a0282b3c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-05-20 (2 days ago) dmi.bios.date: 03/30/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.2 dmi.board.name: 0KT0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.2:bd03/30/2022:br1.14:svnDellInc.:pnPrecision7750:pvr:rvnDellInc.:rn0KT0MH:rvrA01:cvnDellInc.:ct10:cvr:sku09C4: dmi.product.family: Precision dmi.product.name: Precision 7750 dmi.product.sku: 09C4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975445/+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 1975454] Re: Cannot resume after suspend
Thanks for the bug report. Next time the problem happens, after rebooting run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975454 Title: Cannot resume after suspend Status in Ubuntu: Incomplete Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https:
[Touch-packages] [Bug 1975347] Re: Backport OPENSSL_strcasecmp fixes from 3.0 branch
I *think* this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037 but I'll
keep it separate for now as the API used to trigger the issue isn't the
same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1975347
Title:
Backport OPENSSL_strcasecmp fixes from 3.0 branch
Status in openssl package in Ubuntu:
New
Bug description:
The recent openssl update to 3.0.2-0ubuntu1.2 in jammy included some
buggy changes related to OPENSSL_strcasecmp. Briefly, it's possible
for OPENSSL_strcasecmp to be called before the global locale_t object
has been initialized, causing a crash in strcasecmp_l. For example,
this bug can be trivially triggered with the program below.
#include
int main()
{
EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
}
The problem is already fixed in the openssl-3.0 branch. Please
consider backporting this PR
https://github.com/openssl/openssl/pull/18293 or updating the ubuntu
package to a more recent commit of that branch that includes the
fixes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1975347/+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 1975400] Re: Unable to change Display resolution to its full capacity
Thanks for the bug report. I am guessing this is caused by the kernel graphics driver. Please run: grep . /sys/class/drm/*/modes > modes.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975400 Title: Unable to change Display resolution to its full capacity Status in linux package in Ubuntu: Incomplete Bug description: It's showing 'unknown display'. Running this 'ubuntu-drivers devices' showed no output. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 22 11:22:50 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2022-05-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. H81M-S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=963a4763-1838-41e9-ab01-dff1efefa136 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-S dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/19/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-S dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975400/+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 1972790] Re: Can't connect to hotspot created on ubuntu
As written in the bug report before i can't connect with "WPA & WPA2 Personal" with the message "Failed to connect to the network". With "WPA3 Personal" i always got the error message that the password is wrong. After the update "WPA & WPA2 Personal" still don't work (same error message), but "WPA3 Personal" works now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1975369] Re: conky is not visible - Ubuntu 22.04
*** This bug is a duplicate of bug 1947185 *** https://bugs.launchpad.net/bugs/1947185 Thanks for the bug report. It appears 'conky' is an X11 app but you are using Wayland. Wayland sessions do not support the 'dock' X11 window type. You will either need a version of conky that supports Wayland natively, or a gnome-shell extension to replace it. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1975369 Title: conky is not visible - Ubuntu 22.04 Status in Ubuntu: Invalid Bug description: conky is running from terminal but does not show on the desktop: conky: desktop window (800015) is subwindow of root window (96) conky: window type - dock conky: drawing to create window (0xa02) conky: drawing to double buffer This is only happening in Ubuntu 22.04! conky is visible in Ubuntu 18.04 20.04, Kubuntu 20.04, Kubuntu 22.04, and KDE Neon ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 21 03:27:48 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] InstallationDate: Installed on 2022-04-22 (28 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=5c6021ec-5923-467d-b2f9-d0a62f8823b2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2011 dmi.bios.release: 18.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd12/07/2011:br18.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:sku: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975369/+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 1974427] Re: window redraw wrong size when plug in hdmi
*** This bug is a duplicate of bug 1972151 *** https://bugs.launchpad.net/bugs/1972151 Sounds like bug 1972151. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1972151 App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor) -- 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/1974427 Title: window redraw wrong size when plug in hdmi Status in mutter package in Ubuntu: New Bug description: If I have a window open on the primary display (laptop) and plug in an HDMI monitor (secondary) the window (primary) redraws without accounting for the top status bar. In other words, the window status bar is COVERING UP the top of the application window (no min, max close). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 20 06:40:06 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:38ef] InstallationDate: Installed on 2022-05-14 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81D2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=ff8cc35c-2ad1-4b44-b02e-649148be44fa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr7VCN24WW:bd06/15/2018:br1.24:efr1.24:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:skuLENOVO_MT_81D2_BU_idea_FM_ideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1974427/+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 1975454] [NEW] Cannot resume after suspend
Public bug reported: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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 freeze 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/1975454 Title: Cannot resume after suspend Status in xorg package in Ubuntu: New Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous s
