[Bug 1968636] Re: cryptroot-unlock doesn't work at all when terminal width is below 51
After looking deeper into the repo history, I see the questionable implementation of pgrep_exe() was introduced by this patch https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/comments/11 in attempt to adopt the debian code to the ubuntu environment. Aside for other things, it ignores the fact the first line in "ps" output is the header. It was enough to replace .. ps -eo pid= | while read pid; do with .. ps | sed 1d | while read pid _; do and pgrep_exe() would just work. This way terminal width does not affect the ps output in any way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968636 Title: cryptroot-unlock doesn't work at all when terminal width is below 51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1968636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968636] Re: cryptroot-unlock doesn't work at all when terminal width is below 51
Commenting on #2: When building busybox, there is a number of config switches. For your binary to support "ps -w" you need this in the config: - CONFIG_DESKTOP is not set - CONFIG_FEATURE_PS_WIDE=y On my 22.04 systems I've got 2 busybox binaries: /usr/bin/busybox (2.1M) from busybox-static package and /usr/lib/initramfs-tools/bin/busybox (311K) from busybox-initramfs package. The former was built using debian/config/pkg/static from the source package (CONFIG_DESKTOP=y), it does not support "ps -w". The latter was built with debian/config/pkg/initramfs from the source package (no CONFIG_DESKTOP, CONFIG_FEATURE_PS_WIDE=y), it supports "ps -w" and, evidently, it is the one that gets packaged into initramfs. If your non-desktop busybox was built without CONFIG_FEATURE_PS_WIDE=y, there should be no problem described in this bug report. In the case, terminal width would be assumed 79 [1] To make it work no matter if "ps -w" is supported or not, there are two options, both based on [2] 1. "ps https://git.launchpad.net/ubuntu/+source/busybox/tree/procps/ps.c?h=applied/ubuntu/jammy#n650 [2] https://git.launchpad.net/ubuntu/+source/busybox/tree/libbb/xfuncs.c?h=applied/ubuntu/jammy#n292 [3] https://git.launchpad.net/ubuntu/+source/busybox/tree/libbb/xfuncs.c?h=applied/ubuntu/jammy#n235 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968636 Title: cryptroot-unlock doesn't work at all when terminal width is below 51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1968636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058133] Re: [SRU] update-manager crashes when ua security-status response is an error
Coming here from my dup bug report 2060971. Can confirm that the newer version of update-manager seems to fix the issue. And indeed, my livepatch install is a little jankey on my system for some reason, but instead of being greeted with a crash every morning, I'm now presented with pending updates as expected \o/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058133 Title: [SRU] update-manager crashes when ua security-status response is an error To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2058133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Following up again. Disabling retries reduced the frequency of this bug, but didn't eliminate it. On the other hand, the patch I shared does seem to fix the bug. No occurrences since we shipped it ~2 weeks ago. I encourage others to try it out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064042] [NEW] No proper power management
Public bug reported: nvme shows that power management is enabled and device is most of the time in power state 4, but disk get hot (+50.9°C) and drains battery. The same disk has much lower temperatures (about 35C, similar to mainboard) when running Kubuntu 23.10 root@nevo:~# uname -a Linux nevo 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux root@nevo:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble root@nevo:~# nvme list Node Generic SN Model Namespace Usage Format FW Rev - - -- -- /dev/nvme0n1 /dev/ng0n150026B7686B2B506 KINGSTON SKC3000S1024G 0x1 1.02 TB / 1.02 TB512 B + 0 B EIFK51.2 root@nevo:~# nvme fw-log /dev/nvme0 Firmware Log for device:nvme0 afi : 0x1 frs1 : 0x322e31354b464945 (EIFK51.2) root@nevo:~# nvme get-feature -f 0x0c -H /dev/nvme0n1 get-feature:0x0c (Autonomous Power State Transition), Current value:0x0001 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 100 ms Idle Transition Power State (ITPS): 4 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 100 ms Idle Transition Power State (ITPS): 4 . Entry[ 2] . Idle Time Prior to Transition (ITPT): 100 ms Idle Transition Power State (ITPS): 4 . Entry[ 3] . Idle Time Prior to Transition (ITPT): 100 ms Idle Transition Power State (ITPS): 4 . Entry[ 4] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 5] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 6] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 7] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 8] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 9] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[10] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[11] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[12] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[13] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[14] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[15] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[16] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[17] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[18] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[19] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[20] . Idle Time Prior to
[Bug 2060971] Re: Software Updater crashes upon login
Hi Grant! I keep my system updated regularly, but indeed I'm on slightly older: --- :~$ dpkg -l|grep update-manager ii python3-update-manager 1:22.04.19 all python 3.x module for update-manager ii update-manager 1:22.04.19 all GNOME application that manages apt updates ii update-manager-core1:22.04.19 all manage release upgrades --- Looks like it's phasing for me, so I'll override that and let you know if that helps any! --- The following packages have been kept back: python3-update-manager update-manager update-manager-core --- Can confirm the issue happened again this morning, so should be easy to tell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060971 Title: Software Updater crashes upon login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
FWIW, this is what we did in Fedora: https://src.fedoraproject.org/rpms/fail2ban/c/24c973f252f6d1b4231ee49ee4d5efac785a2fe8?branch=rawhide i.e., we depend on packages of the asynchat and asyncore libs that were added to pypi for this kind of purpose - https://pypi.org/project/pyasynchat/ and https://pypi.org/project/pyasyncore/ - and we also had to disable a couple of tests. I don't know if Ubuntu/Debian packaged the split-out asynchat and asyncore libs yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063179] [NEW] package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic package post-installation scr
Public bug reported: the problem occurred during installation while trying to remove previous package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 23 09:40:31 2024 ErrorMessage: installed linux-modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-01-25 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: linux-restricted-modules-hwe-6.5 Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063179 Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux- modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.5/+bug/2063179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
OK, so I just tried this out on the same host I did my Fedora 40 testing, a Windows 11 23H2 system with Intel graphics (no NVIDIA) and VMWare Player 17. I grabbed the Ubuntu 24.04 beta desktop image - ubuntu-24.04-beta- desktop-amd64.iso - and booted it. From that environment I could reproduce the bug. I tested using "Files" (nautilus) - I ran it and it was completely messed up in much the same way as on Fedora, lots of bits of the UI just not shown at all. Then I ran an install. I guess your installs work differently from ours, they don't just dump the live environment onto the disk, because when I booted the installed system, it had mesa 24.0.5 already (verified with `dpkg -l`). And for me, the bug is indeed fixed. Now when I run Files, it renders perfectly. Ditto Text Editor (another GTK4 app). However, reading Oliver's original description again, it really doesn't sound like the same bug. I didn't observe any "black flickering artifacts" during install, and I never saw such a thing in Fedora 40 testing either. I also didn't see anything like "desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player". For me, both in Ubuntu and Fedora, when a system is affected by this bug, GTK 4-based apps tend to be missing large amounts of UI elements, but the desktop shell itself is not affected at all, let alone does it lock up or become unresponsive. So, I think Oliver is seeing something else, but I don't know what. I'd recommend you get a few more folks to test and see what they see, and report the host hardware config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
FWIW, I did my testing - which found this is broken for a Fedora 40 guest with mesa 24.0.4, but fixed with 24.0.5 - on a Windows 11 (23H2) host. No idea what's different for Oliver, sorry :( I guess I could try with an Ubuntu guest on my test setup, I've got a bit of spare time today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060906] Re: attempt to add opensc using modutil suddenly fails
@mdeslaur did you mean to set this bug invalid? It looked like you intended to set bug #2060968 instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060906 Title: attempt to add opensc using modutil suddenly fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/2060906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942616] Re: Settings Power says high hardware temperature
I'm on 22.04.4, I have an i3-8100 processor (does not support turbo), and I was previously running into this issue. After installing the updated ppd from your PPA, I am no longer seeing this, and I am able to switch to performance mode. Thank you for the fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942616 Title: Settings Power says high hardware temperature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059976] Re: unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution proposed
> I have implemented the listing of uncompressed cpio archives (roughly 120 lines of code). Now I have to add the decompression support Finding offsets of the embedded archives is the only time consuming part of the whole script. Mby it is better to create a separate tool, say "scaninitramfs", to only list offsets and size of embedded archives, just like my tools' "-s" option does, and use it in the original script? Scan output can be of interest beyond unmkinitramfs. For example, if you need to know the compression used in some initrd. With a scan tool you can quickly get the offset of the compressed cpio and "dd .. | file .." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059976 Title: unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060168] Re: Prebuilt signed grub images should include f2fs and exfat modules
> isn't really an intended use-case But there is /boot/grub/loopback.cfg since at least 14.04! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060168 Title: Prebuilt signed grub images should include f2fs and exfat modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2060168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060168] Re: Prebuilt signed grub images should include f2fs and exfat modules
> any practical utility Recent ubuntu desktop iso images are way over 4Gb in size, which is the max file size for fat32. Fat32 for long time was the obvious choice to keep iso images on. Exfat is of interest for those who still need compatibility with w/ndows, like it was with fat32. F2fs is of interest for those who want to use their flash storage with the flash tailored fs. BTW Debian's signed grub image includes f2fs module for 4 years already[1] [1] https://salsa.debian.org/grub- team/grub/-/commit/146d21cc9db01cca6f945e466e4adc31d165782b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060168 Title: Prebuilt signed grub images should include f2fs and exfat modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2060168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060168] [NEW] Prebuilt signed grub images should include f2fs and exfat modules
Public bug reported: I guess this is the correct source package to send a feature request for debian/build-efi-images script. Here is what I ask for: --- build-efi-images +++ build-efi-images.new @@ -101,7 +101,9 @@ echo efifwsetup efinet + exfat ext2 + f2fs fat font gettext Motivation: it is pretty easy to make recent ubuntu iso images loopback-boot from f2fs and exfat partitions, but it would not work with secureboot because the signed grub images from grub-efi-amd64-signed do not contain the modules. There are already bug reports for casper to make it boot from f2fs[1] and exfat[2] [1] https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2058826 [2] https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2038694 ** Affects: grub2-unsigned (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060168 Title: Prebuilt signed grub images should include f2fs and exfat modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2060168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058826] Re: f2fs should be recognized by casper as a supported fs
The script from the post is deprecated now, I converted it into a generic "make casper aware of fs X, add kernel modules Y to the initrd" one. You can get it here https://github.com/slowpeek/ubuntu-remaster-bbb and make 14.04+ images bootable from f2fs like this: ubuntu-remaster-f2fs input.iso output.iso or, without the f2fs shortcut: ubuntu-remaster-bbb --fs f2fs --module f2fs,~crc32_generic,~crc32-pclmul input.iso output.iso If using the docker image: ubuntu-remaster-bbb.docker --fs f2fs --module f2fs,~crc32_generic,~crc32-pclmul -- input.iso output.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058826 Title: f2fs should be recognized by casper as a supported fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2058826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038694] Re: Now that exfat filesystem is in the kernel, allow using it for storing isos loopback booting and storing the persistence file
Previously I created a script to make ubuntu iso images bootable from f2fs partitions. After discovering this bug, I converted it into a generic "make casper aware of fs X, add kernel modules Y to the initrd" one. You can get it here https://github.com/slowpeek/ubuntu-remaster-bbb and make 20.04+ images bootable from exfat like this: ubuntu-remaster-exfat input.iso output.iso or, without the exfat shortcut: ubuntu-remaster-bbb --fs exfat --module exfat input.iso output.iso If using the docker image: ubuntu-remaster-bbb.docker --fs exfat --module exfat -- input.iso output.iso This way 18.04.5+ can boot from exfat as well, but only with the hwe kernel. Hence in case of live-server 18.04.5+, extra '--hwe-only' option is required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038694 Title: Now that exfat filesystem is in the kernel, allow using it for storing isos loopback booting and storing the persistence file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2038694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059976] [NEW] unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution proposed
Public bug reported:
Since 23.10 the initrd consists of 4 embedded cpio:
- amd microcode
- intel microcode
- firmware + kernel modules
- rest (compressed)
Previously it was:
- amd microcode
- intel microcode
- rest (compressed)
There is no archive size header for cpio, so unmkinitramfs has to parse
headers of each entry in uncompressed archives.
> time unmkinitramfs 23.04/{initrd,unpack}
real0m3.625s
user0m1.595s
sys 0m3.467s
> time unmkinitramfs 23.10/{initrd,unpack}
real0m15.982s
user0m20.174s
sys 0m6.995s
> for dir in 23.04/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find "$dir"
> | wc -l)"; done
23.04/unpack/early 5
23.04/unpack/early2 6
> for dir in 23.10/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find "$dir"
> | wc -l)"; done
23.10/unpack/early 5
23.10/unpack/early2 6
23.10/unpack/early3 2874
Here https://github.com/slowpeek/unmkinitramfs-turbo I've made it a lot faster
with two changes:
- bash instead of sh for bash's "read -N"
- xxd dump of initrd instead of raw binary data
I wonder, if the developers are interested in accepting my improvements into
the code base?
> time unmkinitramfs-classic-turbo 23.10/{initrd,unpack}
real0m2.209s
user0m2.161s
sys 0m1.341s
> time unmkinitramfs-turbo 23.10/{initrd,unpack}
early .. +
early2 .. +
early3 .. +
main .. +
real0m1.973s
user0m2.094s
sys 0m1.244s
All tools in the repo, even the classic one, feature -s/--scan option. With it,
the tools only dump offset + size for embedded archives, nothing is unpacked.
It can be used to measure parsing speed.
In the repo there are three tools:
- unmkinitramfs-classic: the original tool
- unmkinitramfs-classic-turbo: the improved tool with minimal changes
- unmkinitramfs-turbo: the improved tool with many changes to my tastes, extra
dependency on "file" and some additional features (-ss option, decompression
with 7za)
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059976
Title:
unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution
proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059976/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059190] [NEW] Crash on fresh install
Public bug reported: Crash on install - See logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.20 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 23:13:14 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.20 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059190 Title: Crash on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2059190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Following up, `Acquire::Retries=0` seems to be avoiding the bug in prod, which strengthens my suspicion that it's related to retries. As for the actual bug, when apt is hanging, I notice that the work queue has items in it, but they have not been delegated to a worker. There is a condition that is supposed to "unstuck" the queue here[1], but for some reason `GetFetchAfter` is returning a zeroed time_point which avoids that condition[2]. The way we're setting `FetchAfter` looks OK to me[3] though I'm not familiar with std::chrono. Maybe there's some other place where we're partially copying the item or instantiating a new item and failing to copy the `FetchAfter` value. A bandaid patch is attached. I'm not sure if there's any downside in calling `Cycle` there. A real bugfix IMO would address the zeroed `FetchAfter` value described above, or potentially refactor so that work items are immediately delegated instead of having to rely on calling `Cycle` at the right time. I am missing a lot of context so that maybe that's not possible. [1] https://salsa.debian.org/apt- team/apt/-/blob/db797312548f6e7d6d1d1faa9f1e48c1e521d290/apt- pkg/acquire.cc#L738-740 [2] https://salsa.debian.org/apt- team/apt/-/blob/db797312548f6e7d6d1d1faa9f1e48c1e521d290/apt- pkg/acquire.cc#L733-736 [3] https://salsa.debian.org/apt- team/apt/-/blob/db797312548f6e7d6d1d1faa9f1e48c1e521d290/apt- pkg/acquire-worker.cc#L651-655 ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+attachment/5759339/+files/patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038694] Re: Now that exfat filesystem is in the kernel, allow using it for storing isos loopback booting and storing the persistence file
@Adrian Feliks (mexit) I've just filed a similar bug about f2fs. The module is in initrd since 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038694 Title: Now that exfat filesystem is in the kernel, allow using it for storing isos loopback booting and storing the persistence file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2038694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058826] Re: f2fs should be recognized by casper as a supported fs
** Description changed:
Ubuntu iso images bundle the f2fs driver in initrd since 20.04, but
casper does not recognize f2fs as a supported fs even in 24.04. Hence,
the images cant loop-boot from f2fs partitions.
A 2-lines change is all that's required since 20.04 (casper-helpers
since 22.04, previously this code was in lupin-helpers)
- --- casper-helpers
- +++ casper-helpers.new
- @@ -350,7 +350,7 @@
- is_supported_fs(){
- [ -z "${1}" ] && return 1
- case ${1} in
- -ext2|ext3|ext4|xfs|jfs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
- +ext2|ext3|ext4|xfs|jfs|f2fs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
- return 0
- ;;
- esac
- @@ -370,6 +370,7 @@
- modprobe reiserfs
- modprobe xfs
- modprobe jfs
- +modprobe f2fs
- modprobe vfat
- modprobe fuse
- [ "$quiet" != "y" ] && log_end_msg "...devs loaded..."
+ --- casper-helpers
+ +++ casper-helpers.new
+ @@ -350,7 +350,7 @@
+ is_supported_fs(){
+ [ -z "${1}" ] && return 1
+ case ${1} in
+ -ext2|ext3|ext4|xfs|jfs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
+ +ext2|ext3|ext4|xfs|jfs|f2fs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
+ return 0
+ ;;
+ esac
+ @@ -370,6 +370,7 @@
+ modprobe reiserfs
+ modprobe xfs
+ modprobe jfs
+ +modprobe f2fs
+ modprobe vfat
+ modprobe fuse
+ [ "$quiet" != "y" ] && log_end_msg "...devs loaded..."
-
- With some efforts (copy f2fs and crc32 modules from the squashed filesystem
into the initrd) it works down to 18.04 live server and 15.10 desktop.
+ With some efforts (copy f2fs and crc32 modules from the squashed
+ filesystem into the initrd) it works down to 18.04 live server and 15.10
+ desktop.
With such patch it works in 14.04.3 .. 14.04.6 desktop as well
- --- casper-helpers
- +++ casper-helpers.new
- @@ -46,7 +46,15 @@
- echo $FSTYPE
- return 0
- fi
- -/sbin/blkid -s TYPE -o value $1 2>/dev/null
- +/sbin/blkid -s TYPE -o value $1 2>/dev/null || {
- +# Check for f2fs
- +case "$(dd if="$1" skip=2 count=1 2>/dev/null)" in
- +"$(printf '\x10\x20\xf5\xf2')"*)
- +echo f2fs
- +return 0 ;;
- +esac
- +return 1
- +}
- }
-
- where_is_mounted() {
+ --- casper-helpers
+ +++ casper-helpers.new
+ @@ -46,7 +46,15 @@
+ echo $FSTYPE
+ return 0
+ fi
+ -/sbin/blkid -s TYPE -o value $1 2>/dev/null
+ +/sbin/blkid -s TYPE -o value $1 2>/dev/null || {
+ +# Check for f2fs
+ +case "$(dd if="$1" skip=2 count=1 2>/dev/null)" in
+ +"$(printf '\x10\x20\xf5\xf2')"*)
+ +echo f2fs
+ +return 0 ;;
+ +esac
+ +return 1
+ +}
+ }
+ where_is_mounted() {
- My script to apply the changes:
https://github.com/slowpeek/ubuntu-remaster-f2fs
+ My script to apply the changes: https://github.com/slowpeek/ubuntu-
+ remaster-f2fs
** Description changed:
Ubuntu iso images bundle the f2fs driver in initrd since 20.04, but
casper does not recognize f2fs as a supported fs even in 24.04. Hence,
the images cant loop-boot from f2fs partitions.
A 2-lines change is all that's required since 20.04 (casper-helpers
since 22.04, previously this code was in lupin-helpers)
- --- casper-helpers
- +++ casper-helpers.new
- @@ -350,7 +350,7 @@
- is_supported_fs(){
- [ -z "${1}" ] && return 1
- case ${1} in
- -ext2|ext3|ext4|xfs|jfs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
- +ext2|ext3|ext4|xfs|jfs|f2fs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
- return 0
- ;;
- esac
- @@ -370,6 +370,7 @@
- modprobe reiserfs
- modprobe xfs
- modprobe jfs
- +modprobe f2fs
- modprobe vfat
- modprobe fuse
- [ "$quiet" != "y" ] && log_end_msg "...devs loaded..."
+ --- casper-helpers
+ +++ casper-helpers.new
+ @@ -350,7 +350,7 @@
+ is_supported_fs(){
+ [ -z "${1}" ] && return 1
+ case ${1} in
+ -ext2|ext3|ext4|xfs|jfs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
+ +ext2|ext3|ext4|xfs|jfs|f2fs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
+ return 0
+ ;;
+ esac
+ @@ -370,6 +370,7 @@
+ modprobe reiserfs
+ modprobe xfs
+ modprobe jfs
+ +modprobe f2fs
+ modprobe vfat
+ modprobe fuse
+ [ "$quiet" != "y" ] && log_end_msg "...devs loaded..."
With some efforts (copy f2fs and crc32 modules from the squashed
filesystem into the initrd) it works down to 18.04 live server and 15.10
desktop.
With such patch it works in 14.04.3 ..
[Bug 2038694] Re: Now that exfat filesystem is in the kernel, allow using it for storing isos loopback booting and storing the persistence file
@Adrian Feliks (mexit) How is it supposed to work with just that? Looking into initrd of 24.04 daily unpacked with unmkinitramfs. According to main/lib/modules/6.8.0-11-generic/modules.builtin, exfat is not a builtin module. And there is no exfat in early3/usr/lib/modules/6.8.0-11-generic/kernel/fs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038694 Title: Now that exfat filesystem is in the kernel, allow using it for storing isos loopback booting and storing the persistence file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2038694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058826] [NEW] f2fs should be recognized by casper as a supported fs
Public bug reported:
Ubuntu iso images bundle the f2fs driver in initrd since 20.04, but
casper does not recognize f2fs as a supported fs even in 24.04. Hence,
the images cant loop-boot from f2fs partitions.
A 2-lines change is all that's required since 20.04 (casper-helpers
since 22.04, previously this code was in lupin-helpers)
--- casper-helpers
+++ casper-helpers.new
@@ -350,7 +350,7 @@
is_supported_fs(){
[ -z "${1}" ] && return 1
case ${1} in
-ext2|ext3|ext4|xfs|jfs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
+ext2|ext3|ext4|xfs|jfs|f2fs|reiserfs|vfat|ntfs|iso9660|btrfs|udf)
return 0
;;
esac
@@ -370,6 +370,7 @@
modprobe reiserfs
modprobe xfs
modprobe jfs
+modprobe f2fs
modprobe vfat
modprobe fuse
[ "$quiet" != "y" ] && log_end_msg "...devs loaded..."
With some efforts (copy f2fs and crc32 modules from the squashed filesystem
into the initrd) it works down to 18.04 live server and 15.10 desktop.
With such patch it works in 14.04.3 .. 14.04.6 desktop as well
--- casper-helpers
+++ casper-helpers.new
@@ -46,7 +46,15 @@
echo $FSTYPE
return 0
fi
-/sbin/blkid -s TYPE -o value $1 2>/dev/null
+/sbin/blkid -s TYPE -o value $1 2>/dev/null || {
+# Check for f2fs
+case "$(dd if="$1" skip=2 count=1 2>/dev/null)" in
+"$(printf '\x10\x20\xf5\xf2')"*)
+echo f2fs
+return 0 ;;
+esac
+return 1
+}
}
where_is_mounted() {
My script to apply the changes: https://github.com/slowpeek/ubuntu-remaster-f2fs
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058826
Title:
f2fs should be recognized by casper as a supported fs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2058826/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058774] [NEW] Crash on install attempt
Public bug reported: Crash during install attempt. Crashed after names selection and writing to disks. No clear error reason. See logs. No odd options selected ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.20 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 15:46:43 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.20 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058774 Title: Crash on install attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2058774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Hello, also affected by this. I'm able to reproduce the bug using Walter's mock server. I suspect it may be related to the retry code that kicks in when a transient error is encountered (like a 503). Retries are enabled by default since apt 2.3.2, which seems to fit the regression window people have mentioned here. Frustratingly, I can't reproduce while step debugging, I'm guessing because the bug is clock-dependent. Setting either `Acquire::Retries::Delay=false` or `Acquire::Retries=0` seems to mitigate it. I'm curious if that works for others as well. I'll be testing this in prod soon and will report back. In the mean time I'll keep trying to find the actual bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058628] [NEW] initramfs-tools dhcpcd timeout
Public bug reported:
Hi,
We found an issue in `initramfs-tools-core` (noble,now 0.142ubuntu20
all) related to this change :
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024164
(dhclient replaced by dhcpcd).
dhclient was faster to give an IP. In the `initramfs-tools-core`
scripts, in **/usr/share/initramfs-tools/scripts/functions**, the
ROUNDTTT iterations at _2, 3, 4 or even 6 seconds_ fail. This delays
obtaining an IPv4 by at least 20 seconds.
```
# support ip options see linux sources
# Documentation/filesystems/nfs/nfsroot.txt
# Documentation/frv/booting.txt
for ROUNDTTT in 2 3 4 6 9 16 25 36 64 100; do
local iter_entry_time iter_exit_time
iter_entry_time=$(time_elapsed)
if [ -z "${DEVICE}" ]; then
_set_available_devices_to_up
fi
case ${IP} in
none|done|off)
# Do nothing
IP="done"
;;
""|on|any|dhcp|bootp|both)
dhcpcd -1 -t $ROUNDTTT -4 ${DEVICE:+"${DEVICE}"}
;;
*)
ipconfig -t ${ROUNDTTT} -d "$IP"
```
dhcpcd takes at least 5/6 seconds to give an ipv4 because of the arp
probbing to check that the ip is not already in use.
**Possible Fixes**: `dhcpcd --noarp` prevents waiting, otherwise
redistribute the ROUNDTTT iterations by deleting the iterations at 2 3 4
or even 6 seconds.
NB: this problem probably only concerns obtaining an IP in IPv4, I have
not checked if the problem also arises in IPv6.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058628
Title:
initramfs-tools dhcpcd timeout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2058628/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058286] Re: Requesting SRU for Octavia 10.1.1
** Description changed: Howdy! - I have a customer in case 00381750 requesting a time frame for when - Octavia 10.1.1 can be SRUed, as they mentioned they are interested in - some fixes included in that version for issues they are experiencing. - I'm having trouble finding when that version was actually released[1], - but looking at the last-modify times on the source files, I'd - guesstimate on or around 08 Feb 2024. + This is just a generic request for Octavia 10.1.1 to be SRUed, as there + are a number of useful fixes that it would be nice to see pulled in. I'm + having trouble finding when that version was actually released[1], but + looking at the last-modify times on the source files, I'd guesstimate on + or around 08 Feb 2024. Thanks! [1] https://docs.openstack.org/releasenotes/octavia/yoga.html ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058286 Title: Requesting SRU for Octavia 10.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/2058286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056730] Re: noble-daily (20240310) cannot be installed offline
This bug also prevents an ubuntu-server noble autoinstall installation with NVMe disks attached via PCIe. Noble 20230223. My configuration was a simple storage: direct, with a disk: match specifying 'smallest' and 'ssd: true' (I have 3 NVMe drives, one 128 GB for OS, two 3.6TB for data.). Mine is an offline install (true air gap). Interestingly, the live CD autoinstall process correctly finds and prepares the NVMe drive, installs the system and kernel fine. lsblk even shows all 3 drives. lsmod shows nvme, nvme_core and nvme_common are loaded - no nvme-cli or nvme-stas mentioned. It seems it is subiquity adding those drivers. Interestingly, the package search site shows noble has these packages:- https://packages.ubuntu.com/noble/nvme-cli I'm going to try the daily from last night to see if they are now included. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056730 Title: noble-daily (20240310) cannot be installed offline To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2056730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056140] [NEW] Nvidia crashes very often ( static image)
Public bug reported: Ubuntu 22.04.4 LTS NVIDIA driver metapackage from nvdia-driver-470 (proprietary,tested) crashes regurarly (static image ) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-515 (not installed) ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 09:27:44 2024 InstallationDate: Installed on 2024-01-25 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nvidia-graphics-drivers-525 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056140 Title: Nvidia crashes very often ( static image) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2056140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/92 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
> The count_bytes solution looks better to me The updated patch is attached. I've just checked: all the *_bytes flags were introduced to dd in the same commit https://github.com/coreutils/coreutils/commit/140eca15c4a3d3213629a048cc307fde0d094738, so it is safe to throw in count_bytes in the mix. > I see four dd calls in unmkinitramfs. Can you check those as well? The other dd calls are good: - 2x of bs=1 kind - the last one is "dump from X till the end" utilizing skip_bytes for X, which is correct > Debian is affected as well. If you can spare the time, please submit your patch Will do when they activate my just created account on salsa ** Patch added: "Add count_bytes iflag" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+attachment/5749755/+files/dd-count-2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
Just found out, aside for skip_bytes iflag, there is also count_bytes one. So another fix count be: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes,count_bytes 2> /dev/null | ** Description changed: Speaking about this line in unmkinitramfs: - 113: dd < "$initramfs" skip=$start count=$((end - start)) + 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | - - dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. + dd's block size is 512 by default. iflag=skip_bytes does not change + that. Both $end and $start are byte-offsets. Hence the count is + ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). + If there is still a need to explicitly limit data fed to cpio, dd is + impractical in this case. The only way to count= in bytes is bs=1, which + makes dd extremely slow on lengthy data chunks. For example + ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded + uncompressed cpio archives of such sizes: - If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: - - 77312 - 7200768 - 78615040 + 77312 + 7200768 + 78615040 A combo of dd+head could be used intead to skip and count respectively: - 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | - head -c$((end - start)) + 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | + head -c$((end - start)) | Or even tail+head: - 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) + 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055055] [NEW] unmkinitramfs: wrong and unneeded count= in a dd call
Public bug reported: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Patch added: "dd-count.patch" https://bugs.launchpad.net/bugs/2055055/+attachment/5749511/+files/dd-count.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] Re: [BPO] ipmctl with support for CPS hardware
@ddstreet: no, I failed to get a sponsor, despite subscribing the bug to ~ubuntu-sponsors. I may be doing something wrong as I haven't ever done such a sponsored upload to Ubuntu directly. The code works on Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
Ok, don't know which package produce that value in debconf passwd/user- password-crypted but when I reset it using debconf-communicate, installation was completed. Unfortunately system not booted successfully, so I will dig deeper in the future. Maybe it's not a bug then, but maybe some validation of passwd/user-password-crypted can make ubiquity more robust. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
Check once again. I can install jammy on that VM without touching anything in the VM settings. Just boot, proceed all unnecessary for normal Ubuntu steps from my case, and start ubiquity the same way. Installation was successful but in logs there are all that access denied messages. I can upload that logs if that can help. Jammy booted from virtual drive and seems to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
Once again, steps that I performed: 1.) boot VM from skywavelinux-4.3.0-flashback.iso 2.) setup internet connection manually 3.) sudo apt-get update 4.) sudo apt-get install ubiquity ubiquity-frontend-gtk ubiquity-frontend-gtk-panel ubiquity-slideshow-ubuntu ubiquity-casper 5.) sudo mount /dev/loop0 /media/cdrom 6.) sudo ls -s /media/cdrom /cdrom 7.) ubiquity -d gtk_ui 8.) Try to perform normal graphical installation (with erase and install option) I mount loop0 since without that there was an error with adding cdrom to apt. When I comment out usermode command from user-setup-apply Ubiquity report successful installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
This is a virtual drive. And I was able to install focal and jammy on the same setup normally. ** Changed in: ubiquity (Ubuntu) Status: Invalid => Incomplete ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubiquity (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
Ok, I read the logs once more. The error string for usermod was in fact "10 passwd/user-password-crypted-casper-backup doesn't exist" so it is the other field that I provide from frontend which was "passwd/user- password". So the filed is in fact missing? But error handling here still can be handy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
I know that it is the problem with other Ubuntu based OS, but thing I address is bug with error handling in ubiquity itself. I think it should throw and error at the beginning when it got error when trying to preseed (I guess) the 'passwd/user-fullname' or in best case use password I chose in frontend. And now the behavior is that it try to use error string as a parameter for usermode and fails due the space character after '10'. Other thing is that I can't find any presseed file on that ISO - there is preseed directory but it is empty. Also I'm not see any 'file=' parameters in boot menu. So what is the source of all those preseeded values? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1976177/+attachment/5593616/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] UbiquityPartman.txt
apport information ** Attachment added: "UbiquityPartman.txt" https://bugs.launchpad.net/bugs/1976177/+attachment/5593615/+files/UbiquityPartman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] UbiquityDebug.txt
apport information ** Attachment added: "UbiquityDebug.txt" https://bugs.launchpad.net/bugs/1976177/+attachment/5593614/+files/UbiquityDebug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1976177/+attachment/5593613/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
apport information ** Tags added: apport-collected third-party-packages ** Description changed: System: Skywave Linux Flashback Release: 4.3.0 - this is a Focal Remix live-cd based on Ubuntu 20.04.4 (https://skywavelinux.com/) Ubiquity Version: 20.04.15.19 I want to install this live distro on VM (standalone HVM on Qubes OS - but I think this not make any difference). I installed ubiquity, ubiquity-casper, ubiquity-casper, ubiquity-frontend-gtk,ubiquity- frontend-gtk-panel and ubiquity-slideshow-ubuntu via apt after 'sudo apt-get update'. I also mounted booted iso as cdrom (using: 'sudo mount /dev/loop0 /media/cdrom' and 'sudo ls -s /media/cdrom /cdrom') Then poceded installation as normal. When it comes to "Who are you?" page all fields without password was filed by some garbage/error "10 passwd/user-fulname-casper-backup doesn't exist". I changed it to values desired by me and chose some simple password. Instalaltion crashed on user-setup. After some dbugging I found out that $PASSWD variable that is used by setpassword() in user-setup-apply script file is set to "10 passwd/user-fulname-casper-backup doesn't exist" despite I was trying to set a new password via UI. - I also add question about that behavior to find some workaround - (https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/701995). + I also add question about that behavior to find some workaround (https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/701995). + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: GNOME-Flashback:GNOME + DistroRelease: Skywave Linux Flashback 4.3.0 + InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper live-media-path=/casper initrd=/casper/initrd fsck.mode=skip threadirqs clocksource=tsc tsc=reliable elevator=mq-deadline --- + Package: ubiquity 20.04.15.19 [origin: Ubuntu] + PackageArchitecture: amd64 + ProcEnviron: + TERM=alacritty + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: focal third-party-packages ubiquity-20.04.15.19 + Uname: Linux 5.15.14-rt27-xanmod1 x86_64 + UnreportableReason: This is not an official Skywave package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip lpadmin plugdev pulse-access sambashare sudo video + _MarkForUpload: True ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1976177/+attachment/5593611/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1976177/+attachment/5593612/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] [NEW] Ubiquity not using password provided by UI
Public bug reported: System: Skywave Linux Flashback Release: 4.3.0 - this is a Focal Remix live-cd based on Ubuntu 20.04.4 (https://skywavelinux.com/) Ubiquity Version: 20.04.15.19 I want to install this live distro on VM (standalone HVM on Qubes OS - but I think this not make any difference). I installed ubiquity, ubiquity-casper, ubiquity-casper, ubiquity-frontend-gtk,ubiquity- frontend-gtk-panel and ubiquity-slideshow-ubuntu via apt after 'sudo apt-get update'. I also mounted booted iso as cdrom (using: 'sudo mount /dev/loop0 /media/cdrom' and 'sudo ls -s /media/cdrom /cdrom') Then poceded installation as normal. When it comes to "Who are you?" page all fields without password was filed by some garbage/error "10 passwd/user-fulname-casper-backup doesn't exist". I changed it to values desired by me and chose some simple password. Instalaltion crashed on user-setup. After some dbugging I found out that $PASSWD variable that is used by setpassword() in user-setup-apply script file is set to "10 passwd/user-fulname-casper-backup doesn't exist" despite I was trying to set a new password via UI. I also add question about that behavior to find some workaround (https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/701995). ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Log Files zipped" https://bugs.launchpad.net/bugs/1976177/+attachment/5593604/+files/logs.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964025] Re: Do not support OpenSSL 3
Should these updates appear automatically at one point or do I have to activate some repos or so? I'm still having the same issues like others as well: https://stackoverflow.com/questions/71987581/openssl-3-0-error-when- booting-vagrantbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964025 Title: Do not support OpenSSL 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-bcrypt-pbkdf/+bug/1964025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working
** Changed in: maas Status: Triaged => Fix Released ** Changed in: maas Milestone: None => 3.0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890803 Title: Groovy amd64 / arm64 / PowerPC deployment seems not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1890803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen
Finally got the crashdump uploaded but had to add all the details to a new ticket: LP#1973615 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
Still having upload trouble, i'll find a way to get a crash-report through another means ** Attachment added: "upload failure crash report" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+attachment/5589244/+files/Screenshot%20from%202022-05-12%2008-47-13.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
I removed one of the extensions i was using, but still am running into the issue. 1) I've got a crash report that still fails to upload. ``` -rw-r- 1 addyess whoopsie 94220558 May 12 08:03 _usr_bin_gnome-shell.1000.crash -rw-rw-r-- 1 addyess whoopsie0 May 12 08:03 _usr_bin_gnome-shell.1000.upload -rw--- 1 whoopsie whoopsie 37 May 11 07:52 _usr_bin_gnome-shell.1000.uploaded ``` 2) I see quite a few error reports from this machine https://errors.ubuntu.com/user/8eaca27982a15b33b4b9f42f3dd0ebec1c722ebd7e4b75d5295113bbfa5dd75eac97ca19154d1c2f29debc0c302aeb5336a5dcb48526688b9f300d1f844ae3e6 3) Applying workaround from 993921 and its uploading the latest report now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971987] Re: On release upgrade, Snaps don't change channel
I'll attach mine since it was asked. However mine is a very old original installation and I can't remember the complete history of what I've done with snap. ** Attachment added: "upgrade log from an old installation" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971987/+attachment/5588559/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971987 Title: On release upgrade, Snaps don't change channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
I have a crash report for gnome-shell as well -- but i can't seem to get it uploaded to launchpad at the moment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
Another "side-effect" of this event is that the screen will instantly go black after 30 idle seconds (it doesn't dim to black or use my normal screen blank at 3 min inactivity setting). This "side-effect" goes away if I log-out of the gnome session and then back in again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
This happens to me as well. These are the loaded extensions.
~/.local/share/gnome-shell/extensions
❯ /usr/bin/cat **/metadata.json
{
"_generated": "Generated by SweetTooth, do not edit",
"description": "A human-readable clock for the gnome-shell panel",
"name": "Fuzzy Clock",
"shell-version": [
"3.34",
"3.36",
"3.38",
"40.0",
"41.0",
"42.0"
],
"url": "https://github.com/dallagi/gnome-shell-fuzzy-clock;,
"uuid": "Fuzzy_Clock@dallagi",
"version": 9
}
{
"_generated": "Generated by SweetTooth, do not edit",
"description": "The cat tells you the CPU usage by running speed",
"name": "RunCat",
"shell-version": [
"3.38",
"40",
"41",
"42"
],
"url": "https://github.com/win0err/gnome-runcat;,
"uuid": "run...@kolesnikov.se",
"version": 18
}%
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972812
Title:
The operating system does not ask for a password after unlocking the
screen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972279] Re: Clock region doesn't follow language settings or correctly divine from location
** Description changed: I'm in Brussels, setting up a fresh new Xubuntu 22.04 LTS system that otherwise so far respects my settings of en-GB (with a UK keyboard) Panel clock for some reason provides a date in Dutch. (mandaag 09 mei 2022) and it is not obvious how to persuade it to do otherwise. I never expressed during configuration a preference for Dutch, so this would appear to be a bug. Also note that my IP address corresponds, per whois, to an ISP in - Charleroi, Wallonia, which is French-speaking. (Brussels-capital-region, - which I set as my city for timezone purposes, is _de jure_ bilingual but - _de facto_ about 90% Francophone, followed by Engish, followed by - Dutch). If you can't cope with not having a nice neat one-language-per- - country mapping, and can't cope with people who are not using the local - language, then just respect the user settings rather than trying to - second-guess based on IP. + Charleroi, Wallonia, which is French-speaking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972279 Title: Clock region doesn't follow language settings or correctly divine from location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1972279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972719] [NEW] imv-wayland Aborted (Core dump) on launch
Public bug reported: $ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 $ apt-cache policy imv imv: Installed: 4.3.0-1build1 Candidate: 4.3.0-1build1 Version table: *** 4.3.0-1build1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages 100 /var/lib/dpkg/status When attempting to run the following command from within a sway session, I expect to see the image file displayed on screen. Instead there is an error message, and no image is shown. $ imv-wayland somephoto.jpg listener function for opcode 4 of wl_output is NULL Aborted (core dumped) This appears to have been addressed upstream in version 4.3.1: https://todo.sr.ht/~exec64/imv/1 https://git.sr.ht/~exec64/imv/commit/c7306a6325df0282c16d60b7201b6bd963f76756 ** Affects: imv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972719 Title: imv-wayland Aborted (Core dump) on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imv/+bug/1972719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972279] Re: Clock region doesn't follow language settings or correctly divine from location
This is apparently an issue with misconfigured locale. I'm not sure if this was set automatically (making it an Xubuntu installer bug) or if I inadvertently clicked OK on some "helpful" suggestions (though given I'd specified that I was asking the system to be in English it seems a slightly odd default); but either way it's not a bug in xfce4-panel, so this bug can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972279 Title: Clock region doesn't follow language settings or correctly divine from location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1972279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972279] Re: Clock region doesn't follow language settings or correctly divine from location
OK, on looking more closely at the whois for my IP address, there are two addresses in Wallonia (Liege and Charleroi, both francophone) and one in Brussels-capital-region. Point stands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972279 Title: Clock region doesn't follow language settings or correctly divine from location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1972279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972279] [NEW] Clock region doesn't follow language settings or correctly divine from location
Public bug reported: I'm in Brussels, setting up a fresh new Xubuntu 22.04 LTS system that otherwise so far respects my settings of en-GB (with a UK keyboard) Panel clock for some reason provides a date in Dutch. (mandaag 09 mei 2022) and it is not obvious how to persuade it to do otherwise. I never expressed during configuration a preference for Dutch, so this would appear to be a bug. Also note that my IP address corresponds, per whois, to an ISP in Charleroi, Wallonia, which is French-speaking. (Brussels-capital-region, which I set as my city for timezone purposes, is _de jure_ bilingual but _de facto_ about 90% Francophone, followed by Engish, followed by Dutch). If you can't cope with not having a nice neat one-language-per- country mapping, and can't cope with people who are not using the local language, then just respect the user settings rather than trying to second-guess based on IP. ** Affects: xfce4-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972279 Title: Clock region doesn't follow language settings or correctly divine from location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1972279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
Sorry, I have changed it from Fix Commited to Fix Released by mistake but I cannot change it back. Sorry! ** Changed in: xl2tpd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS
** Changed in: maas Status: Expired => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594317 Title: Cannot start lxd-bridge.service when MAAS is managing DNS To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1594317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
Hi! Same problem here. Clean install, Nvidia-510 + new updates. GTX 960M Still cannot login Wayland sessions on 22.04 after the updates. Missing Wayland login option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
Hi! Same problem here. Clean install, Nvidia-510 + new updates. GTX 960M Still cannot login Wayland sessions on 22.04 after the updates. Missing Wayland login option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969820] Re: Wayland doesn't work after updating, eventhough in conf WaylandEnable is true
*** This bug is a duplicate of bug 1968929 *** https://bugs.launchpad.net/bugs/1968929 Hi! Same problem here. Clean install, Nvidia-510 + new updates. GTX 960M Still cannot login Wayland sessions on 22.04 after the updates. Missing Wayland login option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969820 Title: Wayland doesn't work after updating, eventhough in conf WaylandEnable is true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970418] [NEW] Whiptail no longer accepts input when in a pipe with sudo
Public bug reported: See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010059. Affects Jammy and Bookworm as far as I can tell. echo | sudo whiptail --msgbox test 20 20 #Can't select 'Ok' echo | whiptail --msgbox test 20 20 #Can select 'Ok' Tested on Ubuntu 22.04 LTS ** Affects: newt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970418 Title: Whiptail no longer accepts input when in a pipe with sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1970418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965535] Re: Stop recommending snap
+1 to this until (at minimum) the below issues are resolved: => https://bugs.launchpad.net/snapd/+bug/1575053 => https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706 Seeing these issues open for so long is worrying to me, considering a growing number of critical packages such as Firefox are now distributed as snaps which have crippled usability. Ubuntu has *a lot* going for it, but after 10 years of loyalty, snaps may be the one thing that drive me away.. Unless proper controls are implemented prior to porting applications such as Firefox, snap is heading down the wrong path. I do applaud the snap developers for what they have achieved, and what snap is capable of (It *definitely* has it's place), but fundamental usage issues such as snapd/+bug/1643706 are absolutely crippling it. @Alex Cabal within the +bug/1575053 summaries this perfectly: "Now that Firefox is being delivered as only a Snap in 22.04, I'm essentially being strong-armed into using snaps, because Firefox is probably the most critical piece of software on my system and I cannot work without it." I hope canonical take note, as I believe the community is becoming uneasy, as I now am. At a minimum, allow system critical packages/apps to ship as non snap until proper controls are implemented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674492] Re: cron: /etc/default/cron should not actually be deprecated
Still affects Ubuntu Server 22.04 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674492 Title: cron: /etc/default/cron should not actually be deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1674492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962225] Re: preinst check that kernel revision < 255 now does more harm than good
I did some testing and I didn't run into any issues after updating to
the newer libc6 from -proposed. Looks good.
FROM ubuntu:focal
ENV DEBIAN_FRONTEND noninteractive
RUN mv /bin/uname /bin/uname.orig
RUN printf '#!/bin/bash\n\nif [[ "$1" == "-r" ]] ;then\n echo '5.4.277-277'\n
exit\nelse\n uname.orig "$@"\nfi' > /bin/uname
RUN chmod 755 /bin/uname
RUN echo "deb http://archive.ubuntu.com/ubuntu/ focal-proposed main" >>
/etc/apt/sources.list
RUN apt-get update && apt-get upgrade -y libc6
RUN apt-get install --reinstall libc6
docker build -t ${USER}:focal-libc6 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962225
Title:
preinst check that kernel revision < 255 now does more harm than good
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
I have the same problem that happened with Mesa Intel® Xe Graphics (TGL GT2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934608] Re: setcap does not recognize CAP_PERFMON
Still broken in 20.04 LTS. Unsure if this is related, but the capabilities man page also does not list CAP_PERFMON. Can the fix from newer versions be backported? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934608 Title: setcap does not recognize CAP_PERFMON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap/+bug/1934608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] Re: [BPO] ipmctl with support for CPS hardware
** Patch added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+attachment/5577710/+files/ipmctl.focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] Re: [BPO] ipmctl with support for CPS hardware
> Do you have a sponsor lined up for this? No, I don't. It's also my first ever backport in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] [NEW] [BPO] ipmctl with support for CPS hardware
Public bug reported: [Impact] * Hardware enablement of Optane DC persistent memory. The version of ipmctl in Focal supports Apache Pass and Barlow Pass DIMMs but not the new generation, Crow Pass. We got a request from an end user -- there should be no need to build such tools from source if Ubuntu can ship a backport. [Scope] * The version in Jammy is good, any version 03.* includes support for CPS (with decreasing bugginess as version numbers after the point grow...); Jammy currently has 03.00.00.0423-1 * Focal for now. [Other Info] * I'm the Debian maintainer of this package; a naive backport succeeded after lowering debhelper level to 12 (as would using the debhelper=13 backport). ** Affects: ipmctl (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: ipmctl (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966491] Re: Online Account login exits when selecting Google Account
Now its not crashing just giving empty screen. ** Attachment added: "Screenshot from 2022-04-06 15-25-58.png" https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1966491/+attachment/5577650/+files/Screenshot%20from%202022-04-06%2015-25-58.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966491 Title: Online Account login exits when selecting Google Account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1966491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
@emsan, I have just removed the installed xl2tpd version and installed the 1.3.12 from github: https://github.com/xelerance/xl2tpd/releases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
Downgraded to 1.3.12, works fine on 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966491] [NEW] Online Account login exits when selecting Google Account
Public bug reported: When trying to add Google Online Account in 22.04, the settings just crashes and exit. ** Affects: xl2tpd (Ubuntu) Importance: Undecided Status: New ** Tags: online-account-google -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966491 Title: Online Account login exits when selecting Google Account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1966491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
I can also confirm the bug. Same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965983] [NEW] ZFS snapshots without etc directory causes grub.cfg build failure
Public bug reported:
In /etc/grub.d/10_linux_zfs (built during install from
util/grub.d/10_linux_zfs.in), get_dataset_info() tries to unmount mount
locations starting with the logic
```
case "${etc_dir}" in /.zfs/snapshot/*/etc)
```
This process occasionally and silently fails while building /boot/grub/grub.cfg
when running in FIPS mode (with FIPS kernels), which leaves the generated
/boot/grub/grub.cfg without any kernel (linux ...) lines.
It appears that not all ZFS snapsshots that match the switch statement actually
have an .../etc directory.
As ZFS is only an option in the Focal Desktop installer, this issue was
only tested with Focal running Canonical's FIPS packages.
In order to reproduce this issue in FIPS mode, the ubuntu-fips and fips-
initramfs-generic packages both need to implement a couple of patches
that haven't released yet. Without these two patches and without manual
intervention, the FIPS kernel will be unable to boot with a ZFS /boot
device. I can provide these additional patches -- please feel free to
reach out to me!
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "Patch built for the grub2=2.04-1ubuntu26.13 package"
https://bugs.launchpad.net/bugs/1965983/+attachment/5571994/+files/grubcfg-zfs-snapshot-generation-failure.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965983
Title:
ZFS snapshots without etc directory causes grub.cfg build failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1965983/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848471] Re: No infiniband support in netplan renderer
** Also affects: maas Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848471 Title: No infiniband support in netplan renderer To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1848471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954692] Re: Reconsider compressed kernels on arm64
** Changed in: maas-images Status: In Progress => Fix Committed ** Changed in: maas-images Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954692 Title: Reconsider compressed kernels on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1954692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
Still an issue in: $ snap version snap2.54.3+20.04.1ubuntu0.2 snapd 2.54.3+20.04.1ubuntu0.2 series 16 ubuntu 20.04 kernel 5.13.0-30-generic $ pycharm-community cannot create user data directory: /home/adam/snap/pycharm-community/267: Stale file handle $ brackets cannot create user data directory: /home/adam/snap/brackets/138: Stale file handle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960705] Re: fish from 3.3.1+ds-2 package does not know its version
This should be fixed in 3.3.1+ds-3 which has been imported to Universe. ** Changed in: fish (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960705 Title: fish from 3.3.1+ds-2 package does not know its version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fish/+bug/1960705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955671] Re: support for rocky linux UEFI
** Changed in: curtin (Ubuntu) Status: New => Incomplete ** Changed in: curtin (Ubuntu) Status: Incomplete => In Progress ** Also affects: curtin Importance: Undecided Status: New ** Changed in: curtin Status: New => In Progress ** Changed in: curtin Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955671 Title: support for rocky linux UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1955671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935709] Re: grpc++-dev doesn't install gRPCConfig.cmake
Not having this is super inconvenient. Please include the cmake config files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935709 Title: grpc++-dev doesn't install gRPCConfig.cmake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/1935709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960705] [NEW] fish from 3.3.1+ds-2 package does not know its version
Public bug reported: fish 3.3.1+ds-2 contains a mistake in the packaging which renders `fish --version` inoperable; this causes other packages which try to check the version to fail, and users to report multiple bugs to the upstream developers (including me). The Debian bug report is https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1001583 The upstream reports include: https://github.com/fish-shell/fish-shell/issues/8580 https://github.com/fish-shell/fish-shell/issues/8689 Please do not include this broken package in your LTS release. (There are other important bugs as well, such as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1001584 .) ** Affects: fish (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: fish (Debian) Importance: Unknown Status: Unknown ** Description changed: fish 3.3.1+ds-2 contains a mistake in the packaging which renders `fish --version` inoperable; this causes other packages which try to check the version to fail, and users to report multiple bugs to the upstream developers (including me). - The Debian bug report is https://github.com/fish-shell/fish- - shell/issues/8689 + The Debian bug report is https://bugs.debian.org/cgi- + bin/bugreport.cgi?bug=1001583 https://github.com/fish-shell/fish-shell/issues/8580 https://github.com/fish-shell/fish-shell/issues/8689 Please do not include this broken package in your LTS release. (There are other important bugs as well, such as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1001584 .) ** Bug watch added: Debian Bug tracker #1001583 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001583 ** Also affects: fish (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001583 Importance: Unknown Status: Unknown ** Description changed: fish 3.3.1+ds-2 contains a mistake in the packaging which renders `fish --version` inoperable; this causes other packages which try to check the version to fail, and users to report multiple bugs to the upstream developers (including me). The Debian bug report is https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1001583 + The upstream reports include: https://github.com/fish-shell/fish-shell/issues/8580 https://github.com/fish-shell/fish-shell/issues/8689 Please do not include this broken package in your LTS release. (There are other important bugs as well, such as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1001584 .) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960705 Title: fish from 3.3.1+ds-2 package does not know its version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fish/+bug/1960705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942010] Re: Ensure lockout for failed password attempts is configured
Since we have not heard back from you in this bug report since September and Richard was unable to reproduce the issue, we'll mark this as "Incomplete" for now. Please feel free to add more information to this report if you'd like for us to troubleshoot more! ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942010 Title: Ensure lockout for failed password attempts is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943188] Re: Ensure chrony is configured (Automated)
Since we have not heard back from you in this bug report since September and Richard was unable to reproduce the issue, we'll mark this as "Incomplete" for now. Please feel free to add more information to this report if you'd like for us to troubleshoot more! ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943188 Title: Ensure chrony is configured (Automated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1943188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957154] [NEW] Can't boot after kernel 5.11.0-44 update
Public bug reported: - With kernel 5.11.0-41 everything is ok. - Choosing updated kernel 5.11.0-44 or 5.11.0-46 in Grub results in glitch lines at top of screen and instant reboot. - It may be related to nvidia-driver-470? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-44-generic 5.11.0-44.48 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 1523 F mate-settings-d adam 1928 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Jan 12 10:00:59 2022 InstallationDate: Installed on 2021-10-03 (101 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision T3600 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=014ec6ad-d170-40b9-8b77-af7620c76daf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-41-generic N/A linux-backports-modules-5.11.0-41-generic N/A linux-firmware 1.197.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/21/2018:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:sku:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957154 Title: Can't boot after kernel 5.11.0-44 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943188] Re: Ensure chrony is configured (Automated)
** Changed in: ubuntu-advantage-tools (Ubuntu) Assignee: Richard Maciel Costa (richardmaciel) => Adam Bell (arbell) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943188 Title: Ensure chrony is configured (Automated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1943188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942010] Re: Ensure lockout for failed password attempts is configured
** Changed in: ubuntu-advantage-tools (Ubuntu) Assignee: Richard Maciel Costa (richardmaciel) => Adam Bell (arbell) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942010 Title: Ensure lockout for failed password attempts is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956526] [NEW] Reinstalling root to a larger partition aaaannnnd crash
Public bug reported: Running out of space in / Free space in NTFS (100GB) - Unallocate it At 4 partitions on disk Pop in boot drive, reboot pc, format / Reinstall / onto 100GB +20GB (original size of /) Error during install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-encode-390_390.132-0ubuntu2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 15:50:47 2022 InstallCmdLine: persistent file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956526 Title: Reinstalling root to a larger partition d crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1956526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
The bug has returned unfortunately. Terribly annoying. Only restarting my computer seems to set it back to normal. Affects all text entry apps, including Terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1954762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
A few days ago an Xorg update came in. After this update, the problem hasn't presented itself again. Therefore, I think we can consider this bug now resolved. Many thanks to Daniel and Brian for taking a look at it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1954762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
It seems to affect different apps. Certainly it affects Mozilla Firefox, Gnome Text Editor Gedit, a Java-based translation app I use called OmegaT, and Microsoft Office Word and Excel 2006 running under Wine32. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1954762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954762] Re: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically
On 100% scaling it is certainly less noticeable, though the cursor sometimes appears slightly moved to the right of where it actually is. The screen resolution I am using is (and always has been) 3000x2000. Maybe it has something to do with this less common screen ratio. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954762 Title: When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or even just mouse clicking within text, the cursor jumps backwards and forwards erratically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1954762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
