[Touch-packages] [Bug 1772094] Re: Surface Pro 4: Keyboard not functional during LUKS password prompt
This bug was fixed in the package initramfs-tools - 0.142ubuntu17 --- initramfs-tools (0.142ubuntu17) noble; urgency=medium * install hid-multitouch module for Surface Pro 4 keyboard (LP: #1772094) * test: log build_initramfs calls -- Benjamin Drung Wed, 15 Nov 2023 19:16:46 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1772094 Title: Surface Pro 4: Keyboard not functional during LUKS password prompt Status in initramfs-tools package in Ubuntu: Fix Released Bug description: I installed Ubuntu 18.04 desktop edition on a Microsoft Surface Pro 4, using LVM and full disk encryption. When LUKS prompts for the password, however, the type cover keyboard does not work. I had to plug in a USB keyboard to type in the password and boot. However, the solution is simple. Edit the /etc/initramfs- tools/modules file, add "hid_multitouch" to a line on its own, then run "update-initramfs -u". Now the typecover keyboard can be used to enter the LUKS password on boot. The Ubuntu 18.04 desktop installer should be modified to detect if it is running on Surface Pro hardware, and add the module, above, as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1772094/+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 2043636] [NEW] all https downloads fail on armhf (confirmed bug)
Public bug reported: Release: Ubuntu Focal Architecture: armhf wget version: 1.20.3-1ubuntu2 The following affects Ubuntu focal and likely future releases as well on armhf platforms. No this is not a missing certificate issue. Attempting to download a file with wget using https fails to verify the certificate always. This does not happen on other architectures. The bug is described in more detail here: https://archlinuxarm.org/forum/viewtopic.php?t=16337 The fix there was to add build options `-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64` for armhf builds which fixes the issue for them. As an example try to download a file from raw.githubusercontent.com on armhf and it will fail with such an error wget https://raw.githubusercontent.com/probonopd/AppImages/master/excludelist -O- --2023-11-16 04:28:37-- https://raw.githubusercontent.com/probonopd/AppImages/master/excludelist Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.110.133, 185.199.111.133, 185.199.108.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.110.133|:443... connected. ERROR: cannot verify raw.githubusercontent.com's certificate, issued by 'CN=DigiCert TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US': Unable to locally verify the issuer's authority. To connect to raw.githubusercontent.com insecurely, use `--no-check-certificate'. ** Affects: wget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/2043636 Title: all https downloads fail on armhf (confirmed bug) Status in wget package in Ubuntu: New Bug description: Release: Ubuntu Focal Architecture: armhf wget version: 1.20.3-1ubuntu2 The following affects Ubuntu focal and likely future releases as well on armhf platforms. No this is not a missing certificate issue. Attempting to download a file with wget using https fails to verify the certificate always. This does not happen on other architectures. The bug is described in more detail here: https://archlinuxarm.org/forum/viewtopic.php?t=16337 The fix there was to add build options `-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64` for armhf builds which fixes the issue for them. As an example try to download a file from raw.githubusercontent.com on armhf and it will fail with such an error wget https://raw.githubusercontent.com/probonopd/AppImages/master/excludelist -O- --2023-11-16 04:28:37-- https://raw.githubusercontent.com/probonopd/AppImages/master/excludelist Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.110.133, 185.199.111.133, 185.199.108.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.110.133|:443... connected. ERROR: cannot verify raw.githubusercontent.com's certificate, issued by 'CN=DigiCert TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US': Unable to locally verify the issuer's authority. To connect to raw.githubusercontent.com insecurely, use `--no-check-certificate'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2043636/+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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
** Description changed: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) - The SRU information has been added to the fthree bug reports and I am + The SRU information has been added to the three bug reports and I am attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git- ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture- dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are positive reports on github. Unfortunately they are not always completely targeted at these patches only and therefore I will not link directly to them but they have also been encouraging. [Where problems could occur] The change is spread over several patches which touch the internals of openssl. As such, the engine and provider functionality could be broken by these changes. Fortunately, in addition to upstream's code review, these patches are included in openssl 3.0.4 (iirc) and therefore in kinetic. No issue related to these changes was reported on launchpad or upstream. However, it is possible that there were more patch dependencies than these in either 3.0.3 or 3.0.4. In that case there could be problems. [Patches] The patches come directly from
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
SUSE and Fedora have started to compress repodata with zstd, so it is now
impossible to bootstrap those distributions from Ubuntu via dnf/zypper due to
the lack of zstd support in libsolve. This affects my CI jobs running in Jammy.
The fix is trivial as the version already supports it, but it needs to
build-depend on libzstd and enable the build config flag for it. I will prepare
SRUs for mantic/lunar/jammy. It will be fixed in noble with the next sync from
Debian unstable, at version 0.7.26-2.
** Changed in: libsolv (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
Fix Released
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Fix Released
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
Confirmed
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
Invalid
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in python-debian package in Ubuntu:
Fix Released
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in reprepro source package in Focal:
Fix Released
Status in reprepro source package in Groovy:
Fix Released
Status in reprepro source package in Hirsute:
Fix Released
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see
Re: [Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Thanks for your response, Piotr. I tried that, but wasn't given the option for "Play HiFi quality Music". Pro Audio was the only option in the drop down menu. There were some Analog Stereo options, but they were all unplugged and unavailable. Any other suggestions? On Wednesday, November 15, 2023 at 07:20:25 AM EST, Piotr Kowalczyk <2043...@bugs.launchpad.net> wrote: I had same issue. I managed to fix it with pavucontrol (in "configuration" tab I changed Profile to "Play HiFi quality Music" (earlier it was "Pro Audio"). -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq: owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+subscriptions -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server
This bug was fixed in the package openssh - 1:9.4p1-1ubuntu1 --- openssh (1:9.4p1-1ubuntu1) noble; urgency=medium * Merge with Debian unstable. Remaining changes: - debian/rules: modify dh_installsystemd invocations for socket-activated sshd - debian/openssh-server.postinst: handle migration of sshd_config options to systemd socket options on upgrade. - debian/README.Debian: document systemd socket activation. - debian/patches/socket-activation-documentation.patch: Document in sshd_config(5) that ListenAddress and Port no longer work. - debian/openssh-server.templates: include debconf prompt explaining when migration cannot happen due to multiple ListenAddress values - debian/.gitignore: drop file - debian/openssh-server.postrm: remove systemd drop-ins for socket-activated sshd on purge - debian/openssh-server.ucf-md5sum: update for Ubuntu delta - debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move /run/sshd creation out of the systemd unit to a tmpfile config so that sshd can be run manually if necessary without having to create this directory by hand. - debian/patches/systemd-socket-activation.patch: Fix sshd re-execution behavior when socket activation is used - debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket activation functionality. - d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no for some tests * Dropped changes, fixed upstream: - d/p/fix-authorized-principals-command.patch: Fix the situation where sshd ignores AuthorizedPrincipalsCommand if AuthorizedKeysCommand is also set by checking if the value pointed to by the pointer 'charptr' is NULL. - debian/patches/CVE-2023-38408-1.patch: terminate process if requested to load a PKCS#11 provider that isn't a PKCS#11 provider in ssh-pkcs11.c. - debian/patches/CVE-2023-38408-2.patch: disallow remote addition of FIDO/PKCS11 provider in ssh-agent.1, ssh-agent.c. - debian/patches/CVE-2023-38408-3.patch: ensure FIDO/PKCS11 libraries contain expected symbols in misc.c, misc.h, ssh-pkcs11.c, ssh-sk.c. * Dropped changes, affected package versions not published in supported releases: - debian/openssh-server.postint: do not try to restart systemd units, and instead indicate that a reboot is required - debian/tests/systemd-socket-activation: Reboot the testbed before starting the test - debian/rules: Do not stop ssh.socket on upgrade openssh (1:9.4p1-1) unstable; urgency=medium * New upstream release (https://www.openssh.com/releasenotes.html#9.4p1): - ssh-agent(1): PKCS#11 modules must now be specified by their full paths. Previously dlopen(3) could search for them in system library directories. - ssh(1): allow forwarding Unix Domain sockets via ssh -W. - ssh(1): add support for configuration tags to ssh(1). This adds a ssh_config(5) "Tag" directive and corresponding "Match tag" predicate that may be used to select blocks of configuration similar to the pf.conf(5) keywords of the same name. - ssh(1): add a "match localnetwork" predicate. This allows matching on the addresses of available network interfaces and may be used to vary the effective client configuration based on network location. - ssh(1), sshd(8), ssh-keygen(1): infrastructure support for KRL extensions. This defines wire formats for optional KRL extensions and implements parsing of the new submessages. No actual extensions are supported at this point. - sshd(8): AuthorizedPrincipalsCommand and AuthorizedKeysCommand now accept two additional %-expansion sequences: %D which expands to the routing domain of the connected session and %C which expands to the addresses and port numbers for the source and destination of the connection. - ssh-keygen(1): increase the default work factor (rounds) for the bcrypt KDF used to derive symmetric encryption keys for passphrase protected key files by 50%. - ssh-agent(1): improve isolation between loaded PKCS#11 modules by running separate ssh-pkcs11-helpers for each loaded provider. - ssh(1): make -f (fork after authentication) work correctly with multiplexed connections, including ControlPersist (closes: #348741). - ssh(1): make ConnectTimeout apply to multiplexing sockets and not just to network connections. - ssh-agent(1), ssh(1): improve defences against invalid PKCS#11 modules being loaded by checking that the requested module contains the required symbol before loading it. - sshd(8): fix AuthorizedPrincipalsCommand when AuthorizedKeysCommand appears before it in sshd_config. Since OpenSSH 8.7 the AuthorizedPrincipalsCommand directive was incorrectly ignored in this situation. - sshd(8), ssh(1), ssh-keygen(1):
[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay
** Tags added: server-todo -- 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/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: New Status in dnsmasq source package in Jammy: Triaged Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 824477] Re: sudo is remakably unhelpful when the target app is missing
This is still present on 22.04 USER@HOSTNAME:/etc/pam.d$ sudo /usr/bin/cmd-not-found [sudo] password for USER: Sorry, try again. [sudo] password for USER: Nov 15 21:27:49 HOSTNAME sudo: pam_unix(sudo:auth): conversation failed Nov 15 21:27:49 HOSTNAME sudo: pam_unix(sudo:auth): auth could not identify password for [USER] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/824477 Title: sudo is remakably unhelpful when the target app is missing Status in sudo package in Ubuntu: Confirmed Bug description: sudoers.d contains: backup ALL=NOPASSWD: /usr/bin/rsync --config=/etc/rsync-backup.conf --server --daemon . server# su backup server$ sudo /usr/bin/rsync --config=/etc/rsync-backup.conf --server --daemon . [sudo] password for backup: wtf? This setup works on all my other servers, why is it prompting for a password here? Let's check the auth.log Aug 11 11:35:19 server sudo: pam_unix(sudo:auth): conversation failed Aug 11 11:35:19 server sudo: pam_unix(sudo:auth): auth could not identify password for [backup] "conversation failed" means nothing to me, and backup has password- based login disabled, so not having a password is intentional... After lots of messing around, I *accidentally* stumbled across the fact that /usr/bin/rsync was missing. If it weren't for this accident, I probably never would have figured it out. Can we please have an error message more useful than "conversation failed"? Even now that I know what the problem was, I have no idea how that message was supposed to help me find it... ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: sudo 1.7.4p4-5ubuntu7.1 ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6 Uname: Linux 3.0.0-4-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Aug 11 12:44:46 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/824477/+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 824477] Re: sudo is remakably unhelpful when the target app is missing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/824477 Title: sudo is remakably unhelpful when the target app is missing Status in sudo package in Ubuntu: Confirmed Bug description: sudoers.d contains: backup ALL=NOPASSWD: /usr/bin/rsync --config=/etc/rsync-backup.conf --server --daemon . server# su backup server$ sudo /usr/bin/rsync --config=/etc/rsync-backup.conf --server --daemon . [sudo] password for backup: wtf? This setup works on all my other servers, why is it prompting for a password here? Let's check the auth.log Aug 11 11:35:19 server sudo: pam_unix(sudo:auth): conversation failed Aug 11 11:35:19 server sudo: pam_unix(sudo:auth): auth could not identify password for [backup] "conversation failed" means nothing to me, and backup has password- based login disabled, so not having a password is intentional... After lots of messing around, I *accidentally* stumbled across the fact that /usr/bin/rsync was missing. If it weren't for this accident, I probably never would have figured it out. Can we please have an error message more useful than "conversation failed"? Even now that I know what the problem was, I have no idea how that message was supposed to help me find it... ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: sudo 1.7.4p4-5ubuntu7.1 ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6 Uname: Linux 3.0.0-4-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Aug 11 12:44:46 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/824477/+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 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
Status in bash package in Ubuntu:
New
Bug description:
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
Expected:
debian_chroot part of xterm title should update dynamically; with the
following PS1 contents by default
$ set | fgrep PS1 | head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
Actual result without patch:
debian_chroot part of xterm title got evaluated only during bash
startup, as can be seen in PS1 contents
$ set | fgrep PS1 | head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+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 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
Status in bash package in Ubuntu:
New
Bug description:
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
Expected:
debian_chroot part of xterm title should update dynamically; with the
following PS1 contents by default
$ set | fgrep PS1 | head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
Actual result without patch:
debian_chroot part of xterm title got evaluated only during bash
startup, as can be seen in PS1 contents
$ set | fgrep PS1 | head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+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 2043114] Re: sshd segmentation fault on 20.04.6 (focal)
Thank you for providing more information. Unfortunately I am still unable to reproduce the problem. I tried using a container and a VM, to no avail. But I did open the coredump: (gdb) bt #0 _int_free (av=av@entry=0x7fcbaccd8b80 , p=p@entry=0x558afb81e0c0, have_lock=, have_lock@entry=1) at malloc.c:4341 #1 0x7fcbacb84f22 in _int_realloc (av=av@entry=0x7fcbaccd8b80 , oldp=oldp@entry=0x558afb81e070, oldsize=oldsize@entry=8208, nb=80) at malloc.c:4644 #2 0x7fcbacb86fb6 in __GI___libc_realloc (oldmem=0x558afb81e080, bytes=64) at malloc.c:3226 #3 0x7fcbacb77748 in _IO_mem_finish (fp=0x558afb805e80, dummy=) at memstream.c:131 #4 0x7fcbacb6de41 in _IO_new_fclose (fp=fp@entry=0x558afb805e80) at libioP.h:948 #5 0x7fcbacc03ddb in __vsyslog_internal (pri=, fmt=0x558afa13ac80 "%.500s", ap=0x7ffd8170e5c0, mode_flags=2) at ../misc/syslog.c:237 #6 0x7fcbacc04363 in __syslog_chk (pri=pri@entry=7, flag=flag@entry=1, fmt=fmt@entry=0x558afa13ac80 "%.500s") at ../misc/syslog.c:136 #7 0x558afa0f8b78 in syslog (__fmt=0x558afa13ac80 "%.500s", __pri=7) at /usr/include/x86_64-linux-gnu/bits/syslog.h:31 #8 do_log (level=level@entry=SYSLOG_LEVEL_DEBUG1, fmt=, args=args@entry=0x7ffd8170ef00) at ../../log.c:476 #9 0x558afa0f8ff8 in debug (fmt=) at ../../log.c:229 #10 0x558afa0ae3fe in server_accept_loop (config_s=0x7ffd8170f050, newsock=, sock_out=, sock_in=) at ../../sshd.c:1338 #11 main (ac=, av=) at ../../sshd.c:2040 This stack trace is a bit intriguing. It's realloc that is crashing, way too deep into glibc. It seems to point at some weird interaction between your setup and the memory management involved in syslog. I spent time trying to find upstream bugs to see if there was anything remotely similar, but couldn't find anything either. Can you provide more details on the setup you're using to reproduce the problem? For example, are you using a VM, a container, bare metal? How many (v)CPUs? What about memory? If it's a container/VM, what's the underlying host? Also, since you can reproduce the issue pretty reliably, could you perhaps check if the same crash happens on Jammy? Thank you. -- 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/2043114 Title: sshd segmentation fault on 20.04.6 (focal) Status in openssh package in Ubuntu: Confirmed Bug description: We have a physical server running Ubuntu 20.04.6 LTS (amd64) and openssh-server 1:8.2p1-4ubuntu0.9. Sometimes sshd crashes with a segmentation fault on remote login with key authentication: [193107.651745] sshd[1229630]: segfault at 5557eba6a008 ip 7f2326a2ca53 sp 7ffcba40c510 error 4 in libc-2.31.so[7f23269b8000+178000] We’ve changed only the following values in the stock sshd_config file: LogLevel DEBUG PasswordAuthentication no MaxStartups 100:30:100 The server is used for automated software testing, and sometimes our test suite might make a large amount of SSH connections in a short period of time, which seems to be correlated with the crashes. But at the same time, I have to note that the connection count was not near the MaxStartups limit, and we’ve had crashes before adding that setting. Since the backtrace shows the debug logging function in the stack, we’re currently experimenting with using `LogLevel INFO` to try and isolate the issue. I am attaching the backtrace. I could provide the full dump file, although I am hesitant due to the possibility of private keys or other sensitive information leaking. # apt-cache policy openssh-server openssh-server: Installed: 1:8.2p1-4ubuntu0.9 Candidate: 1:8.2p1-4ubuntu0.9 Version table: *** 1:8.2p1-4ubuntu0.9 500 500 http://mirrors.storpool.com/ubuntu/archive focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:8.2p1-4 500 500 http://mirrors.storpool.com/ubuntu/archive focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-128.144-generic 5.4.210 Tags: focal Uname: Linux 5.4.0-128-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-01-13 (1030 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2043114/+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 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly
I myself honestly don't know what I want in this case. From my perspective the UX was suddenly some web fonts look horrible, and for a long while I had no idea why. It was a lot of work to try and figure out where the problem actually was coming from, and then what on earth to do about it. So I don't know what more useful feedback to give than that. I can't speculate what my preference could be to any degree that seems useful, I think... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/412195 Title: ttf-tahoma-replacement makes some web-sites look ugly Status in fontconfig package in Ubuntu: Invalid Status in wine1.2 package in Ubuntu: Fix Released Bug description: Binary package hint: wine1.2 This font package is good for wine 1.2; however, it also makes sites look ugly in Firefox and other browsers. I had to manually remove the fonts from /usr/share/fonts/ to rectfiy this, because removing the package through apt would have made me remove wine 1.2 and I didn't want that. ProblemType: Bug Architecture: i386 Date: Wed Aug 12 00:23:40 2009 DistroRelease: Ubuntu 9.10 Package: ttf-tahoma-replacement 1.1.27-0ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: wine1.2 Uname: Linux 2.6.31-5-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+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 1954320] Re: Add privacy screen modules to the initrd
This bug was fixed in the package initramfs-tools - 0.142ubuntu16 --- initramfs-tools (0.142ubuntu16) noble; urgency=medium * Install nvmem, soc, power, and System Power Management Interface (SPMI) kernel modules on ARM/RISC-V for MediaTek boards (LP: #2038512) * Install intel_lpss_pci and spi_pxa2xx_platform kernel modules for keyboard on MacBook Pro 2017 (LP: #2042710) * Install surface_aggregator_registry for keyboard on Surface Laptop 4 (LP: #2007050) * framebuffer: Add privacy screen modules to the initrd (LP: #1954320) -- Benjamin Drung Tue, 14 Nov 2023 19:34:42 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1954320 Title: Add privacy screen modules to the initrd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Confirmed Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
This bug was fixed in the package initramfs-tools - 0.142ubuntu16 --- initramfs-tools (0.142ubuntu16) noble; urgency=medium * Install nvmem, soc, power, and System Power Management Interface (SPMI) kernel modules on ARM/RISC-V for MediaTek boards (LP: #2038512) * Install intel_lpss_pci and spi_pxa2xx_platform kernel modules for keyboard on MacBook Pro 2017 (LP: #2042710) * Install surface_aggregator_registry for keyboard on Surface Laptop 4 (LP: #2007050) * framebuffer: Add privacy screen modules to the initrd (LP: #1954320) -- Benjamin Drung Tue, 14 Nov 2023 19:34:42 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Mantic: New Status in linux source package in Mantic: Invalid Bug description: [ Impact ] With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the needed driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst Test case on Microsoft Surface Laptop 4: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs). [ Apport report ] ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl
[Touch-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
This bug was fixed in the package initramfs-tools - 0.142ubuntu16 --- initramfs-tools (0.142ubuntu16) noble; urgency=medium * Install nvmem, soc, power, and System Power Management Interface (SPMI) kernel modules on ARM/RISC-V for MediaTek boards (LP: #2038512) * Install intel_lpss_pci and spi_pxa2xx_platform kernel modules for keyboard on MacBook Pro 2017 (LP: #2042710) * Install surface_aggregator_registry for keyboard on Surface Laptop 4 (LP: #2007050) * framebuffer: Add privacy screen modules to the initrd (LP: #1954320) -- Benjamin Drung Tue, 14 Nov 2023 19:34:42 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in initramfs-tools package in Ubuntu: Fix Released Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Ubuntu Version] Jammy [initramfs-tools] 0.140ubuntu13.4 [Kernel version] 5.15 -> 6.2 (Generate initrd.img-6.2.0 on 5.15 kernel.) [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs
This bug was fixed in the package initramfs-tools - 0.142ubuntu16 --- initramfs-tools (0.142ubuntu16) noble; urgency=medium * Install nvmem, soc, power, and System Power Management Interface (SPMI) kernel modules on ARM/RISC-V for MediaTek boards (LP: #2038512) * Install intel_lpss_pci and spi_pxa2xx_platform kernel modules for keyboard on MacBook Pro 2017 (LP: #2042710) * Install surface_aggregator_registry for keyboard on Surface Laptop 4 (LP: #2007050) * framebuffer: Add privacy screen modules to the initrd (LP: #1954320) -- Benjamin Drung Tue, 14 Nov 2023 19:34:42 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2042710 Title: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1) due to missing kernel modules in initramfs Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Mantic: New Bug description: [ Impact ] I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs- tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the SPI and PCI driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst Test case on MacBook Pro 2017 laptops: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs). [ Remaining original report ] I did a bit of digging into what changed for 23.10. It could potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do not install ARM/RISCV specific modules on other architectures". I had a look into how dracut handles it. Turns out that they specifically include "spi_pxa2xx_platform" after reporting a similar bug report in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2166209 I don't know how (if?) they handle the 2nd module, "intel_lpss_pci". Anyway, I don't need an immediate fix since the workaround works for me. Just posting this for further investigation, and for any other MacBook Pro users in the same situation. Thanks for working on Ubuntu, I think you're all amazing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
thanks! ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Invalid ** Changed in: webkit2gtk (Ubuntu) Status: Incomplete => Fix Released ** Changed in: yelp (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 2040113] Re: gdb crashes upon `run` on some arm64 machines
Uploaded -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Lunar: In Progress Bug description: [ Impact ] * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- registers.patch`. [ Test Plan ] * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. * This could be tested by running any program under lunar's gdb on any ARM64 PAC machine. [ Where problems could occur ] * Problems aren't particularly likely as the exact patch was included in the last Debian stable. * In theory, a gdb rebuild could possibly cause breakage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Uploaded as 42.3-0ubuntu3.1, because we can re-use version numbers that never make it into the archive. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025339] Re: FDE image fails to run e2fsck
Further to a conversation in #ubuntu-devel I'm setting the Lunar task to Won't Fix. Further details: https://irclogs.ubuntu.com/2023/11/15/%23ubuntu-devel.html ** Changed in: e2fsprogs (Ubuntu Lunar) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs package in Debian: Fix Released Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. The decision to disable this feature by default has already been taken for mantic and is not planned to be revised soon as far as I know. So this fix is also useful to implement a common behavior between the 2 series (and following ones). This fix is also motivated by the fact that snapd is using mkfs.ext4 without any options. The possibility to give options for mkfs.ext4 was removed in snapd at some point for good reasons and it would be more complex to handle a special case only for lunar in snapd than disabling this feature by default in e2fsprogs I think. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. It should be noted that before lunar, users did not have access to this feature and since mantic it is disabled by default, so I suspect the population expecting this feature to be enabled by default is rather small. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+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 2040113] Re: gdb crashes upon `run` on some arm64 machines
** Changed in: gdb (Ubuntu) Status: New => Fix Released ** Changed in: gdb (Ubuntu Lunar) Status: New => In Progress ** Changed in: gdb (Ubuntu Lunar) Assignee: (unassigned) => Graham Inggs (ginggs) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Lunar: In Progress Bug description: [ Impact ] * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- registers.patch`. [ Test Plan ] * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. * This could be tested by running any program under lunar's gdb on any ARM64 PAC machine. [ Where problems could occur ] * Problems aren't particularly likely as the exact patch was included in the last Debian stable. * In theory, a gdb rebuild could possibly cause breakage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+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 2043598] Re: A vertical strip on the screen is unresponsive or does not allow iteration
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2043598 Title: A vertical strip on the screen is unresponsive or does not allow iteration Status in xorg package in Ubuntu: New Bug description: A fraction of the screen, located on the right side of the entire vertical, that is, from the minimize, restore and maximize buttons to the bottom of the screen, the click action (single or double) does not work. Today I am forced to make the window smaller to be able to close it, for example. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 12:50:44 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0792] InstallationDate: Installed on 2023-11-03 (11 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Dell Inc. Vostro 14-3468 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=b18f1fb8-30b8-49f3-81fe-227de68fb188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2019 dmi.bios.release: 3.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.3.0 dmi.board.name: 02HKXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.3.0:bd01/17/2019:br3.3:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn02HKXD:rvrA00:cvnDellInc.:ct9:cvr:sku0792: dmi.product.family: Vostro dmi.product.name: Vostro 14-3468 dmi.product.sku: 0792 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2043598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu Jammy) Assignee: (unassigned) => Graham Inggs (ginggs) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043598] [NEW] A vertical strip on the screen is unresponsive or does not allow iteration
You have been subscribed to a public bug: A fraction of the screen, located on the right side of the entire vertical, that is, from the minimize, restore and maximize buttons to the bottom of the screen, the click action (single or double) does not work. Today I am forced to make the window smaller to be able to close it, for example. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 12:50:44 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0792] InstallationDate: Installed on 2023-11-03 (11 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Dell Inc. Vostro 14-3468 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=b18f1fb8-30b8-49f3-81fe-227de68fb188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2019 dmi.bios.release: 3.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.3.0 dmi.board.name: 02HKXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.3.0:bd01/17/2019:br3.3:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn02HKXD:rvrA00:cvnDellInc.:ct9:cvr:sku0792: dmi.product.family: Vostro dmi.product.name: Vostro 14-3468 dmi.product.sku: 0792 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu -- A vertical strip on the screen is unresponsive or does not allow iteration https://bugs.launchpad.net/bugs/2043598 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This has been fixed for a couple of releases now (since lunar I believe), and if I recall correctly the issue was indeed the wpe backend mentioned in comment 17. That would suggest this should be "invalid" for gtk and yelp, and "fix released" for webkit2gtk. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Incomplete Status in webkit2gtk package in Ubuntu: Incomplete Status in yelp package in Ubuntu: Incomplete Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 2043597] [NEW] Kernal-sound: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: The input and output audio does not work for my system and I cannot find a kernel to install to fix this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:jacques1494 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 10:47:30 2023 InstallationDate: Installed on 2022-11-22 (358 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Title: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P07AKK.620.220407.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950QED-KB1US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLB182A1Z-C01-G002-S0001+10.0.22000 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP07AKK.620.220407.SH:bd04/07/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950QED:pvrP07AKK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950QED-KB1US:rvrSGLB182A1Z-C01-G002-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PAKK: dmi.product.family: Galaxy Book2 Pro 360 dmi.product.name: 950QED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PAKK dmi.product.version: P07AKK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kernel-sound wayland-session ** Tags added: kernel-sound -- 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/2043597 Title: Kernal-sound: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: The input and output audio does not work for my system and I cannot find a kernel to install to fix this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:jacques1494 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 10:47:30 2023 InstallationDate: Installed on 2022-11-22 (358 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Title: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P07AKK.620.220407.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950QED-KB1US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLB182A1Z-C01-G002-S0001+10.0.22000 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP07AKK.620.220407.SH:bd04/07/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950QED:pvrP07AKK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950QED-KB1US:rvrSGLB182A1Z-C01-G002-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PAKK: dmi.product.family: Galaxy Book2 Pro 360 dmi.product.name: 950QED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PAKK dmi.product.version: P07AKK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043597/+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 1869673] Re: Updating initramfs - possible missing amdgpu firmware
Thank you for taking the time to report this bug and helping to make Ubuntu better. This is not a bug but a harmless warning that can be ignored (as long as there are included firmware files). You can check with following command that amdgpu firmware files were added to the initramfs: $ lsinitramfs /boot/initrd.img | grep amdgpu usr/lib/firmware/amdgpu usr/lib/firmware/amdgpu/aldebaran_mec.bin.zst usr/lib/firmware/amdgpu/aldebaran_mec2.bin.zst usr/lib/firmware/amdgpu/aldebaran_rlc.bin.zst [...] Feel free to continue to report any other bugs you may find. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid -- 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/1869673 Title: Updating initramfs - possible missing amdgpu firmware Status in initramfs-tools package in Ubuntu: Invalid Bug description: On a clean install of Ubuntu 20.04 the following messages are printed while updating the initramfs. update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic W: Possible missing firmware /lib/firmware/amdgpu/navi12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu I: The initramfs will attempt to resume from /dev/nvme0n1p2 I: (UUID=610d0eae-f18f-4d55-86a0-9cb12375dafb) I: Set the RESUME variable to override Checking in /lib/firmware/amdgpu/ I have a fair number of firmware files but those listed. I'm not sure if these are missing or not needed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 09:48:49 2020 InstallationDate: Installed on 2020-03-20 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) PackageArchitecture: all SourcePackage: initramfs-tools 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/1869673/+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 1814384] Re: update-initramfs: failed for with 1.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Do you still experience this problem with a recent Ubuntu version like 22.04 LTS (jammy) or 23.10 (mantic)? ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1814384 Title: update-initramfs: failed for with 1. Status in initramfs-tools package in Ubuntu: Incomplete Bug description: lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic Within installation linux kernel 4.15.0.45 error occurred: !!! x86_64-linux-gnu_EGL.conf is not an issue here !!! Setting up linux-image-4.15.0-45-generic (4.15.0-45.48) ... Setting up linux-headers-4.15.0-45 (4.15.0-45.48) ... Setting up linux-headers-4.15.0-45-generic (4.15.0-45.48) ... Processing triggers for linux-image-4.15.0-45-generic (4.15.0-45.48) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-4.15.0-45-generic mkinitramfs: for device none missing /sys/dev/block/0:0 mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-4.15.0-45-generic (--configure): installed linux-image-4.15.0-45-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-4.15.0-45-generic E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814384/+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 86577] Re: out-of-the-box initrd images do not include 32bit pccard support
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/86577 Title: out-of-the-box initrd images do not include 32bit pccard support Status in initramfs-tools package in Ubuntu: Incomplete Bug description: Binary package hint: initramfs-tools I use an external hdd for testing Feisty. My notebook has only builtin USB1.1, so I decided to use a FireWire PCcard. The desktop CD (herd4) has no problems to detect the FireWire card and the external disk. Installation worked without problems. Because my BIOS doesn't know a thing about FireWire I had to do the following: To boot Feisty on the external drive I had to copy Feisty's /boot/* over to my internal hdd (containing my Edgy system) and tweak my grub configuration. Everything worked up to the point where the initrd image tried to mount the Feisty root partition (on the FireWire disk). This failed because the initrd image does not contain the yenta_socket module for 32 bit PCcard support. My workaround: build a new initrd image with the line "yenta_socket" added to /etc/initramfs-tools/modules. Now I can boot Feisty flawlessly. My suggestion: as you support plain old PCMCIA with the current initrd image, you should support 32 bit PC cards, too! ProblemType: Bug Date: Tue Feb 20 22:07:35 2007 DistroRelease: Ubuntu 7.04 Uname: Linux pollux 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/86577/+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 1769346] Re: Unable to install 18.04 server AMD64 with targeted kernel: initramfs-tools
Thank you for taking the time to report this bug and helping to make Ubuntu better. I am closing this bug since it is old and upgrading the BIOS resolved it. Feel free to continue to report any other bugs you may find. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1769346 Title: Unable to install 18.04 server AMD64 with targeted kernel: initramfs- tools Status in initramfs-tools package in Ubuntu: Invalid Bug description: Trying to install from: ubuntu-18.04-server-amd64.iso at boot: F6->expert mode and F4->minimal VM I go through the usual steps but when it comes to the "install the system" phase, if I select normal (not live) and then "targeted", the installation stops with an error on initramfs. The error doesn't occur if I use a generic kernel instead of the targeted one. at that phase I'm not yet able to install reportbug so below you'll find what I found in syslog. VM running under ESXi 6.7. Thanks! May 5 12:52:58 in-target: (Reading database ... 100%^M(Reading database ... 11077 files and directories currently installed.)^M May 5 12:52:58 in-target: Preparing to unpack .../0-linux-headers-4.15.0-20_4.15.0-20.21_all.deb ...^M May 5 12:52:58 in-target: Unpacking linux-headers-4.15.0-20 (4.15.0-20.21) ...^M May 5 12:53:03 in-target: Selecting previously unselected package linux-headers-4.15.0-20-generic.^M May 5 12:53:03 in-target: Preparing to unpack .../1-linux-headers-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M May 5 12:53:03 in-target: Unpacking linux-headers-4.15.0-20-generic (4.15.0-20.21) ...^M May 5 12:53:05 in-target: Selecting previously unselected package linux-headers-generic.^M May 5 12:53:05 in-target: Preparing to unpack .../2-linux-headers-generic_4.15.0.20.23_amd64.deb ...^M May 5 12:53:05 in-target: Unpacking linux-headers-generic (4.15.0.20.23) ...^M May 5 12:53:05 in-target: Selecting previously unselected package linux-headers-virtual.^M May 5 12:53:05 in-target: Preparing to unpack .../3-linux-headers-virtual_4.15.0.20.23_amd64.deb ...^M May 5 12:53:05 in-target: Unpacking linux-headers-virtual (4.15.0.20.23) ...^M May 5 12:53:05 in-target: Selecting previously unselected package linux-modules-4.15.0-20-generic.^M May 5 12:53:05 in-target: Preparing to unpack .../4-linux-modules-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M May 5 12:53:05 in-target: Unpacking linux-modules-4.15.0-20-generic (4.15.0-20.21) ...^M May 5 12:53:08 in-target: Selecting previously unselected package linux-image-4.15.0-20-generic.^M May 5 12:53:08 in-target: Preparing to unpack .../5-linux-image-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M May 5 12:53:08 in-target: Unpacking linux-image-4.15.0-20-generic (4.15.0-20.21) ...^M May 5 12:53:08 in-target: Selecting previously unselected package linux-image-virtual.^M May 5 12:53:08 in-target: Preparing to unpack .../6-linux-image-virtual_4.15.0.20.23_amd64.deb ...^M May 5 12:53:08 in-target: Unpacking linux-image-virtual (4.15.0.20.23) ...^M May 5 12:53:08 in-target: Selecting previously unselected package linux-virtual.^M May 5 12:53:08 in-target: Preparing to unpack .../7-linux-virtual_4.15.0.20.23_amd64.deb ...^M May 5 12:53:08 in-target: Unpacking linux-virtual (4.15.0.20.23) ...^M May 5 12:53:09 in-target: Setting up linux-modules-4.15.0-20-generic (4.15.0-20.21) ...^M May 5 12:53:09 in-target: Setting up linux-image-4.15.0-20-generic (4.15.0-20.21) ...^M May 5 12:53:09 in-target: I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.15.0-20-generic^M May 5 12:53:09 in-target: I: /initrd.img.old is now a symlink to boot/initrd.img-4.15.0-20-generic^M May 5 12:53:09 in-target: I: /vmlinuz is now a symlink to boot/vmlinuz-4.15.0-20-generic^M May 5 12:53:09 in-target: I: /initrd.img is now a symlink to boot/initrd.img-4.15.0-20-generic^M May 5 12:53:09 in-target: Setting up linux-image-virtual (4.15.0.20.23) ...^M May 5 12:53:10 in-target: Setting up linux-headers-4.15.0-20 (4.15.0-20.21) ...^M May 5 12:53:10 in-target: Setting up linux-headers-4.15.0-20-generic (4.15.0-20.21) ...^M May 5 12:53:10 in-target: Setting up linux-headers-generic (4.15.0.20.23) ...^M May 5 12:53:10 in-target: Setting up linux-headers-virtual (4.15.0.20.23) ...^M May 5 12:53:10 in-target: Setting up linux-virtual (4.15.0.20.23) ...^M May 5 12:53:10 in-target: Processing triggers for linux-image-4.15.0-20-generic (4.15.0-20.21) ...^M May 5 12:53:10 in-target: /etc/kernel/postinst.d/initramfs-tools:^M May 5 12:53:10 in-target: update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic^M May 5 12:53:10 in-target: mkinitramfs: failed to determine device for /^M May 5 12:53:10
[Touch-packages] [Bug 1616262] Re: Unable to update initramfs with small boot partition
** Tags added: rls-nn-incoming -- 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/1616262 Title: Unable to update initramfs with small boot partition Status in initramfs-tools package in Ubuntu: Triaged Bug description: I have a small 100MB boot paritition and an initramfs that is 37MB. Once you add in all the usual clutter in /boot there is 25MB or so of free space left. I have a single kernel installed, there are no older versions floating about. When I run the update-initramfs script, it fails with : gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1. Looking at the default update-initramfs script, it appears to try and create the new initramfs image on the boot partition, then rename it to the current one in use. It fails at the cpio step as there is insufficient room for both initramfs images in the partition. I have tweaked the script to allow it to create the initramfs image in /tmp and then move it to the desired location (as opposed to creating it / renaming it in the same location), however while it works for me (tm) I'm unsure if this breaks any other behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Aug 24 10:36:33 2016 InstallationDate: Installed on 2016-08-23 (0 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: initramfs-tools 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/1616262/+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 1878378] Re: add_mountroot_fail_hook uses wrong target name
*** This bug is a duplicate of bug 1871154 *** https://bugs.launchpad.net/bugs/1871154 This particular bug has already been reported and is a duplicate of bug #1871154, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1871154 Error message displayed during boot (mountroot hook, premount) -- 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/1878378 Title: add_mountroot_fail_hook uses wrong target name Status in initramfs-tools package in Ubuntu: New Bug description: Upon boot of a system that uses LVM2 you get the message: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory This is because the script /usr/share/initramfs-tools/scripts/init- premount/lvm2 uses the add_mountroot_fail_hook function from /usr/share/initramfs-tools/scripts/functions (which is sources right before), but this function contains a bug that takes the full path of the source script instead of the given argument as name for the target. Version of Ubuntu: 20.04 LTS Version of initramfs-tools: 0.136ubuntu6 For a live installation, this may be fixed with (all on one line): sudo sed -i 's,\(ln -s "\$0" /tmp/mountroot-fail- hooks\.d/\)"\$0",\1"\$1",' /usr/share/initramfs- tools/scripts/functions && sudo update-initramfs -u and verified by checking that this message now disappears on next boot: sudo journalctl -b | grep mountroot-fail-hooks A proposed patch for the source distribution is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1878378/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Changed in: pulseaudio (Ubuntu) Assignee: Dave Jones (waveform) => (unassigned) -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Invalid Status in pulseaudio source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: Invalid Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Invalid Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1616262] Re: Unable to update initramfs with small boot partition
Thank you for taking the time to report this bug and helping to make Ubuntu better. Storing the temporary initramfs in /tmp has a drawback that /tmp might be on a different volume that /boot and that it conflicts with the -b parameter. I suggest to implement following: * Add a global variable for setting the temporary directory which defaults to /boot * This global variable can be overridden by the configuration file in /etc/initramfs-tools/update-initramfs.conf * Add an option to update-initramfs to change the temporary directory (overrides the global variable) That way the current behavior is preserved, but you can change the directory in /etc/initramfs-tools/update-initramfs.conf ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1616262 Title: Unable to update initramfs with small boot partition Status in initramfs-tools package in Ubuntu: Triaged Bug description: I have a small 100MB boot paritition and an initramfs that is 37MB. Once you add in all the usual clutter in /boot there is 25MB or so of free space left. I have a single kernel installed, there are no older versions floating about. When I run the update-initramfs script, it fails with : gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-4.4.0-21-generic with 1. Looking at the default update-initramfs script, it appears to try and create the new initramfs image on the boot partition, then rename it to the current one in use. It fails at the cpio step as there is insufficient room for both initramfs images in the partition. I have tweaked the script to allow it to create the initramfs image in /tmp and then move it to the desired location (as opposed to creating it / renaming it in the same location), however while it works for me (tm) I'm unsure if this breaks any other behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 [modified: usr/sbin/update-initramfs] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Aug 24 10:36:33 2016 InstallationDate: Installed on 2016-08-23 (0 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: initramfs-tools 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/1616262/+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 1772094] Re: Surface Pro 4: Keyboard not functional during LUKS password prompt
I staged adding hid-multitouch for the next upload of initramfs-tools to noble: https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/initramfs- tools/commit/?id=5948f1d3d8cf961785db8153ce3ec2d9a06dd5e2 ** Changed in: initramfs-tools (Ubuntu) Status: Triaged => Fix Committed -- 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/1772094 Title: Surface Pro 4: Keyboard not functional during LUKS password prompt Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: I installed Ubuntu 18.04 desktop edition on a Microsoft Surface Pro 4, using LVM and full disk encryption. When LUKS prompts for the password, however, the type cover keyboard does not work. I had to plug in a USB keyboard to type in the password and boot. However, the solution is simple. Edit the /etc/initramfs- tools/modules file, add "hid_multitouch" to a line on its own, then run "update-initramfs -u". Now the typecover keyboard can be used to enter the LUKS password on boot. The Ubuntu 18.04 desktop installer should be modified to detect if it is running on Surface Pro hardware, and add the module, above, as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1772094/+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 1455769] Re: cannot enter cryptsetup passphrase with wireless keyboard
Thank you for taking the time to report this bug and helping to make Ubuntu better. I checked Ubuntu 23.10 (mantic) and hid-logitech-hidpp is included in the initramfs there: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep hidpp usr/lib/modules/6.5.0-10-generic/kernel/drivers/hid/hid-logitech-hidpp.ko.zst $ find /lib/modules/6.5.0-10-generic/ -iname '*hidpp*' /lib/modules/6.5.0-10-generic/kernel/drivers/hid/hid-logitech-hidpp.ko.zst Do you still experience issues typing the password in to graphical mode? ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1455769 Title: cannot enter cryptsetup passphrase with wireless keyboard Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After upgrade from 14.04 to 14.10 it became impossible to enter passphrase for LUKS root partition in graphical dialogue. Ctrl-Alt- Delete worked fro rebooting and on the second boot the text mode came up and the passphrase could be entered. Now after upgrade to 15.04 I no longer can reboot in the graphical mode with Ctrl-Alt-Delete with my wireless logitech keyboard. I managed to find old wired USB keyboard that behaves exactly the same as the the wireless was in 14.10. No input in graphical mode but rebooting is possible, text mode works fine. In fact, I was hoping that upgrade to 15.04 will solve the problem but it got worse. I have tried adding modules hid_generic, hid-logitech, hid-logitech-dj to module list for initrd as suggested by different bug reporst. No change there. I have tried changing BIOS settings but only disabling Legacy USB option made grub boot menu unresponsive. Both keyboards are working fine once the system is fully booted. I have noticed that when the boot goes to text mode the wired keyboard is unresponsive for a short period in the passphrase dialogue and comes to live after flashing its lights (probably some driver is loaded behind the scene?). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1455769/+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 886149] Re: Usb keyboard does not work to enter password for encrypted disk
Thank you for taking the time to report this bug and helping to make Ubuntu better. I checked Ubuntu 23.10 and hid and usbhid are included in the initramfs: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep -E "/(usb)?hid\.ko" usr/lib/modules/6.5.0-10-generic/kernel/drivers/hid/hid.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/hid/usbhid/usbhid.ko.zst So I assume this issue fixed. Please report back if that is not the case. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/886149 Title: Usb keyboard does not work to enter password for encrypted disk Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Repeatable always: Usb keyboard does not work when cryptsetup asks password to open encrypted disk in early phase of boot. Expected: It should be possible to enter pass phrase to unlock encrypted disk Ubuntu 11.10, initramfs-tools 0.99ubuntu7. As a solution I added lines hid usbhid to /etc/initramfs-tools/modules and executed update-initramfs -u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/886149/+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 2040113] Re: gdb crashes upon `run` on some arm64 machines
** Description changed: - gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon - `run` on some arm64 machines (confirmed on Apple M-series, both under - hypervisor and bare metal, everything else with PAC should also be - affected). + [ Impact ] - It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- - patches/20230316103904.1947447-1-luis.mach...@arm.com/. + * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` +on some arm64 machines (confirmed on Apple M-series, both under hypervisor +and bare metal, everything else with PAC should also be affected). - Debian bookworm's gdb_13.1-3 also includes the same patch as - `aarch64-pauth-registers.patch`. + * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- +patches/20230316103904.1947447-1-luis.mach...@arm.com/. + + * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- +registers.patch`. + + [ Test Plan ] + + * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. + + * This could be tested by running any program under lunar's gdb +on any ARM64 PAC machine. + + [ Where problems could occur ] + + * Problems aren't particularly likely as the exact patch was included in the +last Debian stable. + + * In theory, a gdb rebuild could possibly cause breakage. ** Patch added: "1-13.1-2ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+attachment/5719723/+files/1-13.1-2ubuntu2.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: New Status in gdb source package in Lunar: New Bug description: [ Impact ] * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. * Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth- registers.patch`. [ Test Plan ] * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop. * This could be tested by running any program under lunar's gdb on any ARM64 PAC machine. [ Where problems could occur ] * Problems aren't particularly likely as the exact patch was included in the last Debian stable. * In theory, a gdb rebuild could possibly cause breakage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+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 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
** Tags added: patch -- 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/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Mantic: New Status in linux source package in Mantic: Invalid Bug description: [ Impact ] With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the needed driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst Test case on Microsoft Surface Laptop 4: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs). [ Apport report ] ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3
[Touch-packages] [Bug 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs
** Tags added: patch -- 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/2042710 Title: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1) due to missing kernel modules in initramfs Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Mantic: New Bug description: [ Impact ] I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs- tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the SPI and PCI driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst Test case on MacBook Pro 2017 laptops: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs). [ Remaining original report ] I did a bit of digging into what changed for 23.10. It could potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do not install ARM/RISCV specific modules on other architectures". I had a look into how dracut handles it. Turns out that they specifically include "spi_pxa2xx_platform" after reporting a similar bug report in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2166209 I don't know how (if?) they handle the 2nd module, "intel_lpss_pci". Anyway, I don't need an immediate fix since the workaround works for me. Just posting this for further investigation, and for any other MacBook Pro users in the same situation. Thanks for working on Ubuntu, I think you're all amazing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
I had same issue. I managed to fix it with pavucontrol (in "configuration" tab I changed Profile to "Play HiFi quality Music" (earlier it was "Pro Audio"). -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 1772094] Re: Surface Pro 4: Keyboard not functional during LUKS password prompt
I checked Ubuntu 23.10 and it still does not contain hid-multitouch: $ find /lib/modules/6.5.0-10-generic -name 'hid-multitouch*' /lib/modules/6.5.0-10-generic/kernel/drivers/hid/hid-multitouch.ko.zst $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep hid-multitouch ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1772094 Title: Surface Pro 4: Keyboard not functional during LUKS password prompt Status in initramfs-tools package in Ubuntu: Triaged Bug description: I installed Ubuntu 18.04 desktop edition on a Microsoft Surface Pro 4, using LVM and full disk encryption. When LUKS prompts for the password, however, the type cover keyboard does not work. I had to plug in a USB keyboard to type in the password and boot. However, the solution is simple. Edit the /etc/initramfs- tools/modules file, add "hid_multitouch" to a line on its own, then run "update-initramfs -u". Now the typecover keyboard can be used to enter the LUKS password on boot. The Ubuntu 18.04 desktop installer should be modified to detect if it is running on Surface Pro hardware, and add the module, above, as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1772094/+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 2043579] [NEW] initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2
Public bug reported: The autopkgtest of initramfs-tools fails on armhf on noble: ``` qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture armhf isn't listed. unit-tests PASS qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 ``` The /usr/sbin/mkinitramfs call in build_initramfs() has following output: ``` cryptsetup: ERROR: Couldn't resolve device /dev/sda2 cryptsetup: WARNING: Couldn't determine root device copying from directory /tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir ``` The two cryptsetup log lines are printed by /usr/share/initramfs- tools/hooks/cryptroot (which comes from cryptsetup-initramfs) ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/2043579 Title: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 Status in cryptsetup package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Bug description: The autopkgtest of initramfs-tools fails on armhf on noble: ``` qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture armhf isn't listed. unit-tests PASS qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 ``` The /usr/sbin/mkinitramfs call in build_initramfs() has following output: ``` cryptsetup: ERROR: Couldn't resolve device /dev/sda2 cryptsetup: WARNING: Couldn't determine root device copying from directory /tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir ``` The two cryptsetup log lines are printed by /usr/share/initramfs- tools/hooks/cryptroot (which comes from cryptsetup-initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2043579/+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 2040113] Re: gdb crashes upon `run` on some arm64 machines
** Also affects: gdb (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2040113 Title: gdb crashes upon `run` on some arm64 machines Status in gdb package in Ubuntu: New Status in gdb source package in Lunar: New Bug description: gdb 13.1 shipped in lunar, is affected by a bug where it crashes upon `run` on some arm64 machines (confirmed on Apple M-series, both under hypervisor and bare metal, everything else with PAC should also be affected). It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- patches/20230316103904.1947447-1-luis.mach...@arm.com/. Debian bookworm's gdb_13.1-3 also includes the same patch as `aarch64-pauth-registers.patch`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2040113/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu
** Description changed: - This was reported by someone else upstream and is already fixed by - https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. + + [ Impact ] + * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs + + * This was reported by someone else upstream and is already fixed by +https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. + + [ Test Plan ] + + * I've tested the patch on an affected macOS host running Ubuntu in UTM with +OpenGL enabled on both Mantic and Noble VMs. + + * Anyone else can do the same on an affected host by simply installing the +patched package and booting to the desktop. + + [ Where problems could occur ] + + * This patch fixes an upstream mesa regression which caused libvirglrendrer to +crash on the host side. + + * This makes a non-working use case work, VirGL on affected hosts cannot +regress as it simply didn't work before. + + * Risk of breakage is mainly from other packages possible affected by a mesa +rebuild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Mantic: New Status in mesa source package in Noble: Confirmed Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2025339] Re: FDE image fails to run e2fsck
SRU abandoned to not change the expected default behavior in lunar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Fix Released Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. The decision to disable this feature by default has already been taken for mantic and is not planned to be revised soon as far as I know. So this fix is also useful to implement a common behavior between the 2 series (and following ones). This fix is also motivated by the fact that snapd is using mkfs.ext4 without any options. The possibility to give options for mkfs.ext4 was removed in snapd at some point for good reasons and it would be more complex to handle a special case only for lunar in snapd than disabling this feature by default in e2fsprogs I think. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. It should be noted that before lunar, users did not have access to this feature and since mantic it is disabled by default, so I suspect the population expecting this feature to be enabled by default is rather small. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+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 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
initramfs-tools 0.142ubuntu15.1 debdiff for mantic attached. ** Description changed: + [ Impact ] + With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. - - -- + [ Test Plan ] + + The -generic kernel and probably all kernel flavors contain the needed driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: + $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' + + After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: + $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'surface_aggregator_registry\|intel-lpss-pci' + usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst + usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst + + Test case on Microsoft Surface Laptop 4: Remove all previous + workarounds. Install the fixed initramfs-tools version. Then the + keyboard should work during boot to enter the passphrase. + + [ Where problems could occur ] + + This is making the initramfs slightly bigger. In my testing, both added + were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs). + + [ Apport report ] ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: - adduser 3.118ubuntu5 - apt 2.4.8 - apt-utils 2.4.8 - busybox-initramfs 1:1.30.1-7ubuntu3 - ca-certificates 20211016ubuntu0.22.04.1 - coreutils 8.32-4.1ubuntu1 - cpio 2.13+dfsg-7 - debconf 1.5.79ubuntu1 - debconf-i18n 1.5.79ubuntu1 - dmsetup 2:1.02.175-2.1ubuntu4 - dpkg 1.21.1ubuntu2.1 - gcc-12-base 12.1.0-2ubuntu1~22.04 - gettext-base 0.21-4ubuntu4 - gpgv 2.2.27-3ubuntu2.1 - grub-common 2.06-2ubuntu7.1 - grub-gfxpayload-lists 0.7 - grub-pc 2.06-2ubuntu7.1 - grub-pc-bin 2.06-2ubuntu7.1 - grub2-common 2.06-2ubuntu7.1 - init-system-helpers 1.62 - initramfs-tools 0.140ubuntu13.1 - initramfs-tools-bin 0.140ubuntu13.1 - initramfs-tools-core 0.140ubuntu13.1 - klibc-utils 2.0.10-4 - kmod 29-1ubuntu1 - libacl1 2.3.1-1 - libapt-pkg6.0 2.4.8 - libattr1 1:2.5.1-1build1 - libaudit-common 1:3.0.7-1build1 - libaudit1 1:3.0.7-1build1 - libblkid1 2.37.2-4ubuntu3 - libbrotli1 1.0.9-2build6 - libbz2-1.0 1.0.8-5build1 - libc6 2.35-0ubuntu3.1 - libcap-ng0 0.7.9-2.2build3 - libcap2 1:2.44-1build3 - libcom-err2 1.46.5-2ubuntu1.1 - libcrypt1 1:4.4.27-1 - libdb5.3 5.3.28+dfsg1-0.8ubuntu3 - libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 - libefiboot1 37-6ubuntu2 - libefivar1 37-6ubuntu2 - libffi8 3.4.2-4 - libfreetype6 2.11.1+dfsg-1ubuntu0.1 - libfuse3-3 3.10.5-1build1 - libgcc-s1 12.1.0-2ubuntu1~22.04 - libgcrypt20 1.9.4-3ubuntu3 - libgmp10 2:6.2.1+dfsg-3ubuntu1 - libgnutls30 3.7.3-4ubuntu1.1 - libgpg-error0 1.43-3 - libgssapi-krb5-2 1.19.2-2ubuntu0.1 - libhogweed6 3.7.3-1build2 - libidn2-0 2.3.2-2build1 - libk5crypto3 1.19.2-2ubuntu0.1 - libkeyutils1 1.6.1-2ubuntu3 - libklibc 2.0.10-4 - libkmod2 29-1ubuntu1 - libkrb5-3 1.19.2-2ubuntu0.1 - libkrb5support0 1.19.2-2ubuntu0.1 - liblocale-gettext-perl 1.07-4build3 - liblz4-1 1.9.3-2build2 - liblzma5 5.2.5-2ubuntu1 - libmount1 2.37.2-4ubuntu3 - libnettle8 3.7.3-1build2 - libnsl2 1.3.0-2build2 - libp11-kit0 0.24.0-6build1 - libpam-modules 1.4.0-11ubuntu2.3 - libpam-modules-bin 1.4.0-11ubuntu2.3 - libpam0g 1.4.0-11ubuntu2.3 - libpcre2-8-0 10.39-3ubuntu0.1 - libpng16-16 1.6.37-3build5 - libseccomp2 2.5.3-2ubuntu2 - libselinux1 3.3-1build2 - libsemanage-common 3.3-1build2 - libsemanage2 3.3-1build2 - libsepol2 3.3-1build1 - libsmartcols1 2.37.2-4ubuntu3 - libssl3 3.0.2-0ubuntu1.8 - libstdc++6 12.1.0-2ubuntu1~22.04 - libsystemd0 249.11-0ubuntu3.6 - libtasn1-6 4.18.0-4build1 - libtext-charwidth-perl 0.04-10build3 - libtext-iconv-perl 1.7-7build3 - libtext-wrapi18n-perl 0.06-9 - libtinfo6 6.3-2 - libtirpc-common 1.3.2-2ubuntu0.1 - libtirpc3 1.3.2-2ubuntu0.1 - libudev1 249.11-0ubuntu3.6 - libunistring2 1.0-1 - libuuid1 2.37.2-4ubuntu3 - libxxhash0 0.8.1-1 - libzstd1 1.4.8+dfsg-3build1 - linux-base 4.5ubuntu9 - linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 - logsave 1.46.5-2ubuntu1.1 - lsb-base 11.1.0ubuntu4 - mount
[Touch-packages] [Bug 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs
initramfs-tools 0.142ubuntu15.1 debdiff for mantic attached. ** Patch added: "initramfs-tools_0.142ubuntu15.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+attachment/5719505/+files/initramfs-tools_0.142ubuntu15.1.debdiff -- 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/2042710 Title: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1) due to missing kernel modules in initramfs Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Mantic: New Bug description: [ Impact ] I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs- tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the SPI and PCI driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst Test case on MacBook Pro 2017 laptops: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs). [ Remaining original report ] I did a bit of digging into what changed for 23.10. It could potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do not install ARM/RISCV specific modules on other architectures". I had a look into how dracut handles it. Turns out that they specifically include "spi_pxa2xx_platform" after reporting a similar bug report in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2166209 I don't know how (if?) they handle the 2nd module, "intel_lpss_pci". Anyway, I don't need an immediate fix since the workaround works for me. Just posting this for further investigation, and for any other MacBook Pro users in the same situation. Thanks for working on Ubuntu, I think you're all amazing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs
** Description changed: + [ Impact ] + I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs-tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. + [ Test Plan ] + + The -generic kernel and probably all kernel flavors contain the SPI and PCI driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: + $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' + + After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: + $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' + usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst + usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst + + Test case on MacBook Pro 2017 laptops: Remove all previous workarounds. + Install the fixed initramfs-tools version. Then the keyboard should work + during boot to enter the passphrase. + + [ Where problems could occur ] + + This is making the initramfs slightly bigger. In my testing, both added + were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs). + + [ Remaining original report ] + I did a bit of digging into what changed for 23.10. It could potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do not install ARM/RISCV specific modules on other architectures". I had a look into how dracut handles it. Turns out that they specifically include "spi_pxa2xx_platform" after reporting a similar bug report in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2166209 I don't know how (if?) they handle the 2nd module, "intel_lpss_pci". Anyway, I don't need an immediate fix since the workaround works for me. Just posting this for further investigation, and for any other MacBook Pro users in the same situation. Thanks for working on Ubuntu, I think you're all amazing! -- 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/2042710 Title: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1) due to missing kernel modules in initramfs Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Mantic: New Bug description: [ Impact ] I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs- tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the SPI and PCI driver (on amd64). On mantic systems, you can verify the current initrd doesn't contain these modules by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up the kernel modules: $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 'spi-pxa2xx-platform\|intel-lpss-pci' usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst Test case on MacBook Pro 2017 laptops: Remove all previous workarounds. Install the fixed initramfs-tools version. Then the keyboard should work during boot to enter the passphrase. [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, both added were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs). [ Remaining original report ] I did a bit of digging into what changed for 23.10. It could potentially (?) be commit
[Touch-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
** Also affects: initramfs-tools (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => Invalid -- 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/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Mantic: New Status in linux source package in Mantic: Invalid Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate:
[Touch-packages] [Bug 2025339] Re: FDE image fails to run e2fsck
** Description changed: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this - feature by explicitly listing them when invoking mkfs.ext4. + feature by explicitly listing them when invoking mkfs.ext4. The decision + to disable this feature by default has already been taken for mantic and + is not planned to be revised soon as far as I know. So this fix is also + useful to implement a common behavior between the 2 series (and + following ones). + This fix is also motivated by the fact that snapd is using mkfs.ext4 + without any options. The possibility to give options for mkfs.ext4 was + removed in snapd at some point for good reasons and it would be more + complex to handle a special case only for lunar in snapd than disabling + this feature by default in e2fsprogs I think. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. + + It should be noted that before lunar, users did not have access to this + feature and since mantic it is disabled by default, so I suspect the + population expecting this feature to be enabled by default is rather + small. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Fix Released Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. The decision to disable this feature by default has already been taken for mantic and is not planned to be revised soon as far as I know. So this fix is also useful to implement a common behavior between the 2 series (and following ones). This fix is also motivated by the fact that snapd is using mkfs.ext4 without any options. The possibility to give options for mkfs.ext4 was removed in snapd at some point for good reasons and it would be more complex to handle a special case only for lunar in snapd than disabling this feature by default in e2fsprogs I think. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is
[Touch-packages] [Bug 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error
debug-me 1.20221231-2 got synced to noble. ** Changed in: debug-me (Ubuntu) Status: Triaged => Fix Released ** Changed in: debug-me (Ubuntu) Assignee: Heinrich Schuchardt (xypron) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2033639 Title: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error Status in binutils package in Ubuntu: New Status in debug-me package in Ubuntu: Fix Released Status in debug-me package in Debian: Fix Released Bug description: debug-me 1.20221231-1 fails to build from source on ppc64el due to internal ld.gold error (binutils 2.41-4ubuntu1): ``` Linking dist/build/debug-me/debug-me ... /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050 collect2: error: ld returned 1 exit status `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1) ``` Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu- mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2033639/+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
