[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Ben, XPS 13 should have no problems with the factory-installed certified (by
us) images:
https://ubuntu.com/certified?q=XPS+13=20=22.04+LTS
Certainly when we were certifying the latest XPS 13 Plus (with 4K), the
only blocking issue I saw was a multi-monitor bug that we fixed before
launch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code:
[Touch-packages] [Bug 1978942] Re: Sound problem. The sound is a few minutes away. A buzzer signal then appears. The image is also bad.
[Expired for gst-plugins-good1.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978942 Title: Sound problem. The sound is a few minutes away. A buzzer signal then appears. The image is also bad. Status in gst-plugins-good1.0 package in Ubuntu: Expired Bug description: Sound problem. The sound is a few minutes away. A buzzer signal then appears. The image is also bad. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gstreamer1.0-plugins-good 1.20.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 16 15:17:35 2022 InstallationDate: Installed on 2022-05-19 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gst-plugins-good1.0 UpgradeStatus: Upgraded to kinetic on 2022-06-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1978942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986606] Re: When locking computer with Win+L, screen goes black permanently
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1986606 Title: When locking computer with Win+L, screen goes black permanently Status in xorg package in Ubuntu: New Bug description: I had a workaround for this in 20.04, press and hold Win+L so it types letters into the input field as you lock the computer. This kept the screen from going black, and I could manually dim the laptop screen (fn+brightness) and walk away. In 22.04 the screen now fades to black immediately when I press Win+L, even though I can see the first few characters being entered on the input field as the screen fades to black. Black screen (as in fade to black for inactivity) seems to be irreversible on this computer, no amount of mouse-wiggling, 3 finger salute (ctrl-alt-delete), or usb dongle removal and reattachment will cause the display to wake up. In 20.04 I could get around this on computer lock by continuing to press Win+L until the input box had lots of input. That seemed to stop the screen from dimming in 20.04. Not working in 22.04. The only way I have found out of this is to do a hard power down (7+ seconds pressing power button). For obvious reasons I prefer not to do this often. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:03:08 2022 DistUpgraded: 2022-08-15 15:36:20,169 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:121a] InstallationDate: Installed on 2022-03-14 (154 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-576 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-15 (0 days ago) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: KBL dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr1.10:svnAcer:pnAspireE5-576:pvrV1.32:rvnKBL:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire E 15 dmi.product.name: Aspire E5-576 dmi.product.sku: dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1986606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986606] [NEW] When locking computer with Win+L, screen goes black permanently
You have been subscribed to a public bug: I had a workaround for this in 20.04, press and hold Win+L so it types letters into the input field as you lock the computer. This kept the screen from going black, and I could manually dim the laptop screen (fn+brightness) and walk away. In 22.04 the screen now fades to black immediately when I press Win+L, even though I can see the first few characters being entered on the input field as the screen fades to black. Black screen (as in fade to black for inactivity) seems to be irreversible on this computer, no amount of mouse-wiggling, 3 finger salute (ctrl-alt-delete), or usb dongle removal and reattachment will cause the display to wake up. In 20.04 I could get around this on computer lock by continuing to press Win+L until the input box had lots of input. That seemed to stop the screen from dimming in 20.04. Not working in 22.04. The only way I have found out of this is to do a hard power down (7+ seconds pressing power button). For obvious reasons I prefer not to do this often. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:03:08 2022 DistUpgraded: 2022-08-15 15:36:20,169 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:121a] InstallationDate: Installed on 2022-03-14 (154 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-576 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-15 (0 days ago) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: KBL dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr1.10:svnAcer:pnAspireE5-576:pvrV1.32:rvnKBL:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire E 15 dmi.product.name: Aspire E5-576 dmi.product.sku: dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- When locking computer with Win+L, screen goes black permanently https://bugs.launchpad.net/bugs/1986606 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Joseph, out of interest, what model of XPS 13 do you have? I'm getting
new XPS 13 soon and wondering if it'll have the same issue (I guess it's
likely given the 4k screen).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
** No longer affects: gtk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981623] Re: Save As Dialog Box does not allow filename change
See also bug 1949340
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1981623
Title:
Save As Dialog Box does not allow filename change
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
as expected, but do not permit changing the filename. Text entry
triggers the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1981623/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980146] Re: dnsmasq often using 100% of CPU
I don't have to do anything to reproduce it, just boot the machine and
it starts happening:
⏵ sudo strace -p 823
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}], 8, -1) =
1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(33704),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="4\312\1\0\0\1\0\0\0\0\0\0\0014\19\18\0015\1c\1d\0017\0016\0016\1b"...,
iov_len=4096}], msg_iovlen=1, msg_control=[{cmsg_len=28,
cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0}, 0)
= 90
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(13,
"4\312\1\0\0\1\0\0\0\0\0\0\0014\19\18\0015\1c\1d\0017\0016\0016\1b"...,
90, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 90
As mentioned, I think it happens when an address is denied by dnsmasq.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU
Status in dnsmasq package in Ubuntu:
New
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980146] Re: dnsmasq often using 100% of CPU
⏵ journalctl -f
Nothing new coming up.
⏵ cat /var/run/NetworkManager/resolv.conf
# Generated by NetworkManager
search socal.rr.com
nameserver 127.0.0.53
options edns0 trust-ad
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU
Status in dnsmasq package in Ubuntu:
New
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980146] Re: dnsmasq often using 100% of CPU
This is over ssh. No one is logged in at desktop, although lightdm is
up.
dnsmasq:
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
dnsmasq 823 97.7 0.0 15724 2268 ?R15:22 23:35
/usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -7
/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service
--trust-anchor=.,20326,8,2,e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
** Attachment added: "ps_aux.txt"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+attachment/5608924/+files/ps_aux.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU
Status in dnsmasq package in Ubuntu:
New
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980146] Re: dnsmasq often using 100% of CPU
⏵ cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or directory
⏵ cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
[device]
wifi.scan-rand-mac-address=no
⏵ cat /etc/dnsmasq.conf
## everything is commented out here ##
⏵ cat /run/dnsmasq/resolv.conf
cat: /run/dnsmasq/resolv.conf: No such file or directory
⏵ cat /var/run/dhcpd.leases /run/dhcpd.leases
cat: /var/run/dhcpd.leases: No such file or directory
cat: /run/dhcpd.leases: No such file or directory
(This is an otherwise standard Ubuntu Mate system on Jammy, with dnsmasq and
ssh installed.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU
Status in dnsmasq package in Ubuntu:
New
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980146] Re: dnsmasq often using 100% of CPU
** Attachment added: "dpkg_sels.txt"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+attachment/5608923/+files/dpkg_sels.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU
Status in dnsmasq package in Ubuntu:
New
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986583] [NEW] Screen after some time get shifted and starts to overlap
Public bug reported: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. Computer should be used to run 8hours straight (it is intended for customer) When i switch from graphic display to tty (ctrl+alt+num) and back, display gets "restarted" and problem is fixed. But it is just temporary. Restart fixes it also. Last time i encountered this behavior today between 17-18hour. But have no idea what or where to look for. yes, and when one connects to display over X11 or teamviewer screen appears to be okay, so one will notice this problem if using pc remotely 1) lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) expect that display will stay where it is on the start of computer 4) display gets shifted to some distance from unknown reason (Maybe x11vnc or teamviewer usage or something). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:27:55 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (179 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (13 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1986583 Title: Screen after some time get shifted and starts to overlap Status in xorg package in Ubuntu: New Bug description: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu10
---
zlib (1:1.2.11.dfsg-2ubuntu10) kinetic; urgency=medium
* d/p/410-lp1961427.patch ported from zlib #410, fixing
compressBound() with hw acceleration. LP: #1961427
Thanks to Ilya Leoshkevich .
In addition a patch is needed for bedtools.
-- Frank Heimes Thu, 21 Jul 2022 09:30:05
+0100
** Changed in: zlib (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
In Progress
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Released
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
Fix Committed
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
Fix Committed
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected by the zlib issue.
* The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
* The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.
* Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not
[Touch-packages] [Bug 1986552] Re: package python3 3.10.4-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1986552 Title: package python3 3.10.4-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: I attempted to upgraded from Ubuntu 20.04 to 22.04 and received a failure notification but it seemed to install anyway. Now when I try to install an app or update anything I am receiving errors. The system says it is running Ubuntu 22.04.1 LTS, even though the upgrade supposedly failed. I received a notice of updates, via Software & Updates (a pop-up - Live Patch, I am guessing) while I was busy with other files on my computer. I accepted the updates and here we are. I'm kind of new to Ubuntu still, even though I have had a small course on it, and this is my first major issue, as well as my first bug report. So I am not too certain what all I need to include. I have attempted several installs via the terminal since the upgrade as well and all have failed. Wish I could roll-back to 20.04 and start over on the upgrade. My next steps are to attempt a repair if I don't receive any other recommendations. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3 3.10.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 13 19:52:20 2022 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2020-09-14 (699 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: python3-defaults Title: package python3 3.10.4-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-08-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1986552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986552] [NEW] package python3 3.10.4-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Public bug reported: I attempted to upgraded from Ubuntu 20.04 to 22.04 and received a failure notification but it seemed to install anyway. Now when I try to install an app or update anything I am receiving errors. The system says it is running Ubuntu 22.04.1 LTS, even though the upgrade supposedly failed. I received a notice of updates, via Software & Updates (a pop-up - Live Patch, I am guessing) while I was busy with other files on my computer. I accepted the updates and here we are. I'm kind of new to Ubuntu still, even though I have had a small course on it, and this is my first major issue, as well as my first bug report. So I am not too certain what all I need to include. I have attempted several installs via the terminal since the upgrade as well and all have failed. Wish I could roll-back to 20.04 and start over on the upgrade. My next steps are to attempt a repair if I don't receive any other recommendations. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3 3.10.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 13 19:52:20 2022 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2020-09-14 (699 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: python3-defaults Title: package python3 3.10.4-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-08-14 (1 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1986552 Title: package python3 3.10.4-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: I attempted to upgraded from Ubuntu 20.04 to 22.04 and received a failure notification but it seemed to install anyway. Now when I try to install an app or update anything I am receiving errors. The system says it is running Ubuntu 22.04.1 LTS, even though the upgrade supposedly failed. I received a notice of updates, via Software & Updates (a pop-up - Live Patch, I am guessing) while I was busy with other files on my computer. I accepted the updates and here we are. I'm kind of new to Ubuntu still, even though I have had a small course on it, and this is my first major issue, as well as my first bug report. So I am not too certain what all I need to include. I have attempted several installs via the terminal since the upgrade as well and all have failed. Wish I could roll-back to 20.04 and start over on the upgrade. My next steps are to attempt a repair if I don't receive any other recommendations. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: python3 3.10.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 13 19:52:20 2022 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2020-09-14 (699 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: python3-defaults Title: package python3 3.10.4-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-08-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1986552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983665] Re: Problem loading private RSA key with pkcs11 engine, tpm2 module
Update: We managed to use PKCS11 with OpenSSL version 3 by utilizing provider "tpm2-openssl" (the new syntax goes along the lines of `openssl req -new -provider tpm2 -provider base ...`). So we do not consider this a bug but a change in OpenSSL, and we think this issue can be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1983665 Title: Problem loading private RSA key with pkcs11 engine, tpm2 module Status in openssl package in Ubuntu: New Bug description: Problem: We have prepared an rsa2048 keypair in tpm2 and would like to access it using the pkcs11 engine of OpenSSL which fails as described below. Please note that the error messages pasted below look somewhat related to https://bugs.launchpad.net/ubuntu/+source/tpm2-tss/+bug/1983160 Is the fix mentioned in that bug already published or could this be a different error? Setup: The TPM2 device: ~# dmesg | grep TPM [0.006201] ACPI: TPM2 0x7EB75000 4C (v04 BOCHS BXPCTPM2 0001 BXPC 0001) [0.006209] ACPI: Reserving TPM2 table memory at [mem 0x7eb75000-0x7eb7504b] [0.372512] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1, rev-id 1) The RSA keypair in TPM2: ~# pkcs11-tool --module /usr/lib/x86_64-linux-gnu/pkcs11/libtpm2_pkcs11.so --login --list-objects WARNING: Getting tokens from fapi backend failed. Using slot 0 with a present token (0x1) Logging in to "testlabel". Please enter User PIN: Private Key Object; RSA label: ID: 31323731386436643066616361643434 Usage: decrypt, sign Access: sensitive, always sensitive, never extractable, local Allowed mechanisms: RSA-X-509,RSA-PKCS-OAEP,RSA-PKCS,SHA256-RSA-PKCS,SHA384-RSA-PKCS,SHA512-RSA-PKCS,RSA-PKCS-PSS,SHA1-RSA-PKCS-PSS,SHA256-RSA-PKCS-PSS,SHA384-RSA-PKCS-PSS Public Key Object; RSA 2048 bits label: ID: 31323731386436643066616361643434 Usage: encrypt, verify Access: local Here the openssl.cnf: openssl_conf = openssl_init [openssl_init] engines = engine_section [engine_section] pkcs11 = pkcs11_section [pkcs11_section] engine_id = pkcs11 # See also note on dynamic_path = ... below MODULE_PATH = /usr/lib/x86_64-linux-gnu/pkcs11/libtpm2_pkcs11.so init = 0 [ req ] distinguished_name = req_dn string_mask = utf8only utf8 = yes basicConstraints = critical,CA:FALSE subjectKeyIdentifier = hash req_extensions = v3_req [ v3_req ] keyUsage = critical, digitalSignature, keyEncipherment extendedKeyUsage = critical, clientAuth [ req_dn ] commonName = Test Subject We test the pcks11 engine availability: ~# openssl engine pkcs11 -t (pkcs11) pkcs11 engine [ available ] Now we try using OpenSSL to generate a CSR: ~# openssl req -config ./openssl.cnf -verbose -new -engine pkcs11 -keyform engine -key slot_1-id_38636232383264363035316365623962 -out ./test.csr -subj /CN=some.test.name Results in an error: Engine "pkcs11" set. Using configuration from ./openssl.cnf WARNING: Getting tokens from fapi backend failed. Enter PKCS#11 token PIN for openvpn: ERROR:esys_crypto:src/tss2-esys/esys_crypto_ossl.c:754:iesys_cryptossl_pk_encrypt() ErrorCode (0x00070001) Could not create rsa key. ERROR:esys:src/tss2-esys/esys_iutil.c:521:iesys_compute_encrypted_salt() During encryption. ErrorCode (0x00070001) ERROR:esys:src/tss2-esys/api/Esys_StartAuthSession.c:226:Esys_StartAuthSession_Async() Error in parameter encryption. ErrorCode (0x00070001) ERROR:esys:src/tss2-esys/api/Esys_StartAuthSession.c:113:Esys_StartAuthSession() Error in async function ErrorCode (0x00070001) ERROR: Esys_StartAuthSession: esapi:Catch all for all errors not otherwise specified ERROR: Could not start Auth Session with the TPM. ERROR: Error unsealing wrapping key Login failed Login to token failed, returning NULL... PKCS11_get_private_key returned NULL Could not read private key from org.openssl.engine:pkcs11:slot_1-id_38636232383264363035316365623962 80DB703FD47F:error:0396:digital envelope routines:fromdata_init:operation not supported for this keytype:../crypto/evp/pmeth_gn.c:354: 80DB703FD47F:error:4185:PKCS#11 module:ERR_CKR_error:General Error:p11_slot.c:245: 80DB703FD47F:error:1380:engine routines:ENGINE_load_private_key:failed loading private key:../crypto/engine/eng_pkey.c:79: On a sidenote, we do no specify dynamic_path in the openssl.cnf. If we set in openssl.cnf: dynamic_path = /usr/lib/x86_64-linux-gnu/engines-3/libpkcs11.so then we receive a different error: ... 807B8B140C7F:error:1280006A:DSO support routines:dlfcn_bind_func:could not bind to the requested symbol name:../crypto/dso/dso_dlfcn.c:188:symname(EVP_PKEY_base_id): /usr/lib/x86_64-linux-gnu/engines-3/libpkcs11.so:
[Touch-packages] [Bug 1971323] Re: Merge six from Debian unstable for kinetic
six 1.16.0-4 1.16.0-3ubuntu1 ** Changed in: six (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1971323 Title: Merge six from Debian unstable for kinetic Status in six package in Ubuntu: New Bug description: Upstream: tbd Debian: 1.16.0-3 Ubuntu: 1.16.0-3ubuntu1 Debian typically updates six every 2 months on average, but it was last updated 21.12 and looks overdue. Check back in on this monthly. ### New Debian Changes ### six (1.16.0-3) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. [ Colin Watson ] * Link directly to upstream in Homepage and debian/copyright. -- Colin Watson Sun, 26 Dec 2021 02:24:26 + six (1.16.0-2) unstable; urgency=medium * Team upload. [ Andreas Beckmann ] * python-six/python3-six: Copy Breaks: python (<< 2.7.18), python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18), python-iso8601 (<< 0.1.12-2~), python-pbr (<< 5.4.5) from python2.7 to ensure removal of the unversioned python packages (and some persisting obsolete Python 2 module packages) on upgrades from buster. In some upgrade scenarios (mostly involving openstack packages) these Breaks in python2.7 were ineffective because the unversioned python packages got higher scores than python2.7. python-six/python3-six are usually very high scoring Python module packages in these cases, making them ideal candidates for such copies of the Breaks. (Closes: #991433) -- Stefano Rivera Tue, 27 Jul 2021 11:44:18 -0400 six (1.16.0-1) unstable; urgency=medium * New upstream release. -- Colin Watson Sun, 09 May 2021 11:40:54 +0100 six (1.15.0-2) unstable; urgency=medium [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. [ Colin Watson ] * Remove Barry Warsaw from Uploaders, with thanks for their previous contributions (closes: #970181). -- Colin Watson Tue, 10 Nov 2020 00:16:45 + six (1.15.0-1) unstable; urgency=medium [ Debian Janitor ] * Update standards version to 4.5.0, no changes needed. [ Colin Watson ] * New upstream release. -- Colin Watson Sun, 24 May 2020 10:23:22 +0100 six (1.14.0-3) unstable; urgency=medium * Dont run unittests for python2 binary, to reduce pytest rdeps -- Sandro Tosi Mon, 13 Apr 2020 20:16:04 -0400 six (1.14.0-2) unstable; urgency=medium * Build-depend on python2 rather than python. -- Colin Watson Tue, 21 Jan 2020 09:44:26 + six (1.14.0-1) unstable; urgency=medium [ Debian Janitor ] * Remove unnecessary team-upload line in changelog. * Set upstream metadata fields: Bug-Database, Repository. * Set upstream metadata fields: Bug-Submit, Repository-Browse. [ Colin Watson ] * New upstream release. -- Colin Watson Mon, 20 Jan 2020 21:39:42 + six (1.13.0-1) unstable; urgency=medium [ Emmanuel Arias ] * New upstream version 1.13.0 * d/control: Bump Standard-Version to 4.4.1 * d/control: Bump debhelper-compat to 12 (from 9) [ Colin Watson ] * Replace manually-written basic autopkgtests with 'Testsuite: autopkgtest-pkg-python'. * Remove build-dependencies on python-py and python3-py, no longer used upstream. * Fix HTML paths in doc-base control file. -- Colin Watson Tue, 12 Nov 2019 08:10:54 + six (1.12.0-2) unstable; urgency=medium ### Old Ubuntu Delta ### six (1.16.0-3ubuntu1) jammy; urgency=medium * Drop Breaks on python to allow python-is-python2 to remain when upgrading from Focal (LP: #1958720) -- Robie Basak Wed, 13 Apr 2022 21:08:40 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1971323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986542] [NEW] Issue building the debian source archive
Public bug reported: I cannot build the ubuntu source package gst-plugins- good1.0_1.20.3-0ubuntu1.dsc. I am doing: > dget -q > http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc > cd gst-plugins-good1.0-1.20.3/ > DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b and I receive the error: ../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown variable "static_build". I am testing inside of an ubuntu:jammy-20220801 container. I have narrowed the issue down to a patch in the changelog on the 15th Mar which states "Import plugins from -bad that are needed for main applications". This patch imports some "bad" plugins into the source but the meson file isn't setup correctly for this to work. Manually removing the patches related to the bad plugins fixed the issue. ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1986542 Title: Issue building the debian source archive Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: I cannot build the ubuntu source package gst-plugins- good1.0_1.20.3-0ubuntu1.dsc. I am doing: > dget -q http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc > cd gst-plugins-good1.0-1.20.3/ > DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b and I receive the error: ../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown variable "static_build". I am testing inside of an ubuntu:jammy-20220801 container. I have narrowed the issue down to a patch in the changelog on the 15th Mar which states "Import plugins from -bad that are needed for main applications". This patch imports some "bad" plugins into the source but the meson file isn't setup correctly for this to work. Manually removing the patches related to the bad plugins fixed the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1986542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy
Thanks for doing the SRU verification @pprincipeza! I re-triggered the flaky autopkgtest on systemd/249.11-0ubuntu3.4 (armhf) to make it pass. All looking good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1972029 Title: dhclient overriding stub-resolv.conf file on Jammy Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Jammy: Fix Committed Status in isc-dhcp source package in Kinetic: Fix Released Bug description: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
The fix was make for Kinetic Kudu (0.8.36+nmu1ubuntu4). It would take an SRU to port the fix to Jammy. The stable release upgrade process is described here: https://wiki.ubuntu.com/StableReleaseUpdates Do you want to give it a try? Best regards Heinrich -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
Hi, as of today the fix is not available via apt at Ubuntu jammy x64. Am I doing something wrong? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763570] Re: file does not fully recognize ISO images
This is fixed in 22.04. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1763570 Title: file does not fully recognize ISO images Status in file package in Ubuntu: Confirmed Bug description: Environment: Xubuntu 18.04 $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ apt-cache policy file file: Installed: 1:5.32-2 Candidate: 1:5.32-2 Version table: *** 1:5.32-2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Steps-to-reproduce: 1) Download Xubuntu 16.04 ISO from http://cdimages.ubuntu.com/xubuntu/releases/16.04/release/xubuntu-16.04-desktop- amd64.iso 2) run: file --mime-type xubuntu-16.04-desktop-amd64.iso 3) run: file xubuntu-16.04-desktop-amd64.iso Expected results: Result of (2) should be: $ file --mime-type xubuntu-16.04-desktop-amd64.iso xubuntu-16.04-desktop-amd64.iso: application/x-iso9660-image ... and result of (3) should be: $ file xubuntu-16.04-desktop-amd64.iso xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'Xubuntu 16.04 LTS amd64' (bootable); partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 2410708, 4736 sectors Actual results: $ file --mime-type xubuntu-16.04-desktop-amd64.iso xubuntu-16.04-desktop-amd64.iso: application/octet-stream $ file xubuntu-16.04-desktop-amd64.iso xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector; partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 2410708, 4736 sectors ubuntuforums thread: https://ubuntuforums.org/showthread.php?t=2388736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1763570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986536] [NEW] Running ifup@ for all interfaces breaks no-auto-down
Public bug reported:
We (mythic-beasts.com) run a "Raspberry Pi cloud", consisting of
Raspberry Pis with no SD card and an NFS root file system. This requires
special considerations for shutting down, as bringing down eth0 will
break the file system and cause the shutdown process to hang forever.
ifupdown has a config option for exactly this situation: no-auto-down.
We set this flag in /etc/network/interfaces.d/eth0.
However, this flag only prevents `ifdown -a` from bringing down the
interface; `ifdown eth0` still does. Unfortunately, ifup@eth0.service
does exactly this when bringing down the system.
This isn't an issue on Debian, because Debian only starts ifup@.service
for services marked "allow-hotplug"; non-hotplug services are started
and stopped by networking.service, which just uses `if{up,down} -a`.
Ubuntu, on the other hand, brings up ifup@.service for all services
marked auto. (This was an intentional change - see the Ubuntu ifupdown
changelog.)
As such, unless I'm missing something, there's no way on Ubuntu to have
an interface that's automatically brought up on boot, but not
automatically brought down on shutdown.
Tested on bionic and focal:
root@rpi-bionic-arm64:~# lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
root@rpi-bionic-arm64:~# apt-cache policy ifupdown
ifupdown:
Installed: 0.8.17ubuntu1.1
Candidate: 0.8.17ubuntu1.1
Version table:
*** 0.8.17ubuntu1.1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64
Packages
100 /var/lib/dpkg/status
0.8.17ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
root@rpi-focal-arm64:~# lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
root@rpi-focal-arm64:~# apt-cache policy ifupdown
ifupdown:
Installed: 0.8.35ubuntu1
Candidate: 0.8.35ubuntu1
Version table:
*** 0.8.35ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages
100 /var/lib/dpkg/status
I can't easily test on jammy, as we're not producing jammy images yet;
but I'm happy to create one (or try upgrading a pi from focal) if people
think it's likely to do something interesting.
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1986536
Title:
Running ifup@ for all interfaces breaks no-auto-down
Status in ifupdown package in Ubuntu:
New
Bug description:
We (mythic-beasts.com) run a "Raspberry Pi cloud", consisting of
Raspberry Pis with no SD card and an NFS root file system. This
requires special considerations for shutting down, as bringing down
eth0 will break the file system and cause the shutdown process to hang
forever.
ifupdown has a config option for exactly this situation: no-auto-down.
We set this flag in /etc/network/interfaces.d/eth0.
However, this flag only prevents `ifdown -a` from bringing down the
interface; `ifdown eth0` still does. Unfortunately, ifup@eth0.service
does exactly this when bringing down the system.
This isn't an issue on Debian, because Debian only starts
ifup@.service for services marked "allow-hotplug"; non-hotplug
services are started and stopped by networking.service, which just
uses `if{up,down} -a`. Ubuntu, on the other hand, brings up
ifup@.service for all services marked auto. (This was an intentional
change - see the Ubuntu ifupdown changelog.)
As such, unless I'm missing something, there's no way on Ubuntu to
have an interface that's automatically brought up on boot, but not
automatically brought down on shutdown.
Tested on bionic and focal:
root@rpi-bionic-arm64:~# lsb_release -rd
Description: Ubuntu 18.04.6 LTS
Release: 18.04
root@rpi-bionic-arm64:~# apt-cache policy ifupdown
ifupdown:
Installed: 0.8.17ubuntu1.1
Candidate: 0.8.17ubuntu1.1
Version table:
*** 0.8.17ubuntu1.1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64
Packages
100 /var/lib/dpkg/status
0.8.17ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
root@rpi-focal-arm64:~# lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04
root@rpi-focal-arm64:~# apt-cache policy ifupdown
ifupdown:
Installed: 0.8.35ubuntu1
Candidate: 0.8.35ubuntu1
Version table:
*** 0.8.35ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages
100 /var/lib/dpkg/status
I can't easily test on jammy, as we're not producing jammy images yet;
but I'm happy to create one (or try upgrading a pi from focal) if
people think it's likely to do something interesting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1986536/+subscriptions
[Touch-packages] [Bug 1986513] Re: Software & Updates doesn't handle sources files properly when an entry has options
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1986513 Title: Software & Updates doesn't handle sources files properly when an entry has options Status in software-properties package in Ubuntu: Confirmed Bug description: — SYNOPSIS — Software & Updates (software-properties-gtk) has a tab "Other Software" that lists all entries in /etc/apt/sources.list and in /etc/apt/sources.list.d/*.list Some entries have an option in square brackets, e.g.: deb [arch=amd64] ... But, Software & Updates doesn't handle these options properly. 1. It removes the option if you edit the entry. 2. If the option contains "signed-by", Software & Updates doesn't even list the entry, and thus allows you to add a duplicate entry (normally prevented). — EXAMPLES — Example of point 1: Consider Google Chrome: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main #Chrome If you edit this entry in Software & Updates, it removes [arch=amd64]. The same applies to [trusted=yes]. Example of point 2: Consider SpiderOakONE, which needs "signed-by". deb [signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE This also happens with combinations: deb [arch=amd64 signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE Software & Updates doesn't even display this entry. Thus, you can manually re-add this deb, albeit without the signed-by option. — MORE DETAIL — Confusingly, you can add the option [arch=amd64] or [trusted=yes] (or both) when you add an entry in Software & Updates, but if you then edit the entry, Software & Updates removes the option. — EXPECTED BEHAVIOUR — Software & Updates should: • Display all entries • Preserve all options when editing an entry • Allow you to add suitable options when adding an entry • Allow you to edit options when editing an entry — VERSIONS — Ubuntu version: Tested on Ubuntu 20.04.4 and Ubuntu 22.04.1 software-properties-gtk version: 0.99.9.8 (on Ubuntu 20.04) 0.99.22.3 (on Ubuntu 22.04) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.3 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 09:19:51 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-05-05 (101 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1986513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy
@vorlon, Upon installing the jammy-proposed version of the isc-dhcp-client on a Jammy instance (4.4.1-2.3ubuntu2.2), I am no longer able to reproduce the reported issue; running `dhclient` does not get the resolv.conf/stub-resolv.conf files overwritten. As of the reported regression, I did not find anything in the excuses page at all. Anyway, marking as complete from my side. Thanks! BR, pprincipeza ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1972029 Title: dhclient overriding stub-resolv.conf file on Jammy Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Jammy: Fix Committed Status in isc-dhcp source package in Kinetic: Fix Released Bug description: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu
Tested it with another nuc (hp elitedesk 800 G1 Business PC) and have still the same issues.. Can't connect with any device, but i also get "nl80211" error. It's quite weired that i get the same error on 2 different nuc's (from 2 different brands). Also i'm not sure how i can check if the "nl80211" error is the cause of my hotspot problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981531] Re: package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
Wondering where the symlink went ** Changed in: grub2 (Ubuntu) Status: Incomplete => New ** Package changed: grub2 (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981531 Title: package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Upgrading from 21.10 to 22.04, root-on-zfs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-52.59-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jul 13 06:37:26 2022 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: grub2 Title: package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-07-13 (0 days ago) mtime.conffile..etc.logrotate.d.apport: 2022-04-06T10:45:01.573806 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981531] [NEW] package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: Upgrading from 21.10 to 22.04, root-on-zfs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-52.59-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jul 13 06:37:26 2022 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: grub2 Title: package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-07-13 (0 days ago) mtime.conffile..etc.logrotate.d.apport: 2022-04-06T10:45:01.573806 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- package grub-efi-amd64 2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/1981531 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980238] Re: apport-gtk: AssertionError when importing Gdk
Fixed upstream:
https://github.com/canonical/apport/commit/5672172ff19501a2acb221004c5bcdeab15f2c21
** Changed in: apport
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1980238
Title:
apport-gtk: AssertionError when importing Gdk
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Triaged
Bug description:
Latest occurrence on Ubuntu 22.04 with apport 2.20.11-0ubuntu82.1
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 19, in
from gi.repository import GLib, Wnck, GdkX11, Gdk
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 145, in
load_module
importlib.import_module('gi.repository.' + dep.split("-")[0])
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 145, in
load_module
importlib.import_module('gi.repository.' + dep.split("-")[0])
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 146, in
load_module
dynamic_module = load_overrides(introspection_module)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 118,
in load_overrides
override_mod = importlib.import_module(override_package_name)
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/usr/lib/python3/dist-packages/gi/overrides/Gdk.py", line 83, in
Color = override(Color)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 195,
in override
assert g_type != TYPE_NONE
AssertionError
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu82.1, the problem page at
https://errors.ubuntu.com/problem/24396b7376ebda08c45e990a2c6b695b2f981de8
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1980238/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980561] Re: apport-gtk: ImportError: cannot import name '_gi' from partially initialized module 'gi'
Fixed upstream: https://github.com/canonical/apport/commit/dd432ca42a95be03fdd70e6132559dfbe7dcf28d ** Changed in: apport Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1980561 Title: apport-gtk: ImportError: cannot import name '_gi' from partially initialized module 'gi' Status in Apport: Fix Committed Status in apport package in Ubuntu: Triaged Bug description: Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 16, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in from . import _gi ImportError: cannot import name '_gi' from partially initialized module 'gi' (most likely due to a circular import) (/usr/lib/python3/dist-packages/gi/__init__.py) The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.1, the problem page at https://errors.ubuntu.com/problem/f5c8cca5c7852cd7b758bc7cb0add4221c47ebf5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1980561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980553] Re: /usr/share/apport/apport-kde:NameError:/usr/share/apport/apport-kde@19:/usr/share/apport/apport-kde@58
Fixed upstream: * https://github.com/canonical/apport/commit/c50707e8e191e39c17f83a8348e1567e90b44489 * https://github.com/canonical/apport/commit/df2c48384d43df06a6d55b8ebda06d644ab03b48 ** Changed in: apport Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1980553 Title: /usr/share/apport/apport-kde:NameError:/usr/share/apport/apport- kde@19:/usr/share/apport/apport-kde@58 Status in Apport: Fix Committed Status in apport package in Ubuntu: Triaged Bug description: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 19, in import sip ModuleNotFoundError: No module named 'sip' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 58, in apport.fatal( NameError: name 'apport' is not defined The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.22.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/094315607321c36064c78d9fb74646ebf6feff74 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1980553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986521] [NEW] ssh client spins if output fd closed
Public bug reported: The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the bug described at https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and https://bugzilla.mindrot.org/show_bug.cgi?id=3405 A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up an xterm, ask for whatever authentication is needed, close the xterm, and leave the ssh client spinning consuming CPU time for 60 seconds before it exits. It should leave the ssh client idle for 60 seconds. Many uses of ssh to launch graphical applications will be caught by this bug. This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its release notes at https://www.openssh.com/txt/release-9.0 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1986521 Title: ssh client spins if output fd closed Status in openssh package in Ubuntu: New Bug description: The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the bug described at https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and https://bugzilla.mindrot.org/show_bug.cgi?id=3405 A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up an xterm, ask for whatever authentication is needed, close the xterm, and leave the ssh client spinning consuming CPU time for 60 seconds before it exits. It should leave the ssh client idle for 60 seconds. Many uses of ssh to launch graphical applications will be caught by this bug. This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its release notes at https://www.openssh.com/txt/release-9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1986521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945225] Re: udev produces unpredictable net names when PCI device is a bridge
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1945225 Title: udev produces unpredictable net names when PCI device is a bridge Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [Impact] udev can produce unpredictable network interface names by default when multiple devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2 system, I see the following when booting a system with udev 245.4-4ubuntu3.13: ubuntu@akis:~$ ls /sys/class/net enp134s0f0 enp6s0 ens103 ens107 eth3 eth9 enp134s0f1 ens102 ens106 eth1eth7 lo For each ens* device, there is a sibling eth* device that maps to the same slot because both devices are behind the same bridge. Unpredictable names present well known problems, but I'll describe a specific issue I'm having. We currently do automated network testing that MAAS deploys a system and then configures 2 specific NICs on the system. While MAAS does take care to always restore the names used during commissioning (eth3 will always be the same NIC on every deploy), these names can change each time the system is commissioned. So today we need to go in and edit the NIC names manually in MAAS any time the system is re-commissioned. [Test Case] Boot with kernel option net.naming-scheme=v247; verify that all network interfaces receive predictable names. [Fix] This issue was addressed upstream by adding a new v247 naming scheme that detects this scenario and disables usage of slot-based names for these devices. Obviously changing the default naming scheme in a released LTS series could break users. However, we could introduce the v247 scheme in a focal SRU, and keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users impacted by this could then opt-in to the v247 scheme by passing net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. I could add this to DGX2 systems via a kernel_opts MAAS tag to always get predictable names during commissioning. [Regression Risk] This would change the behavior of any users who select net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945225] Re: udev produces unpredictable net names when PCI device is a bridge
Thanks for the investigation, I'm 100% +1 on comment #5. The MR introduces some (low) risk of breaking existing use cases (#5.1), while not fixing the issue for anyone directly. Instead, it provides an (easier/additional?) workaround to the issue, which still needs to be applied to any individual machine hitting this issue. So If there's any way to deploy the .link override configs, as suggested by @ddstreet, we should push for that instead of patching systemd. I would assume most deployment mechanisms (be it MAAS/cloud-init/...) should allow for placing additional udev config files. Worst case, it needs a reboot in between, I guess. If anybody can prove that the .link override approach is not viable, we should ask the SRU team for their risk assesment of #5.1 and continue with the MR if they are +1 on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1945225 Title: udev produces unpredictable net names when PCI device is a bridge Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [Impact] udev can produce unpredictable network interface names by default when multiple devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2 system, I see the following when booting a system with udev 245.4-4ubuntu3.13: ubuntu@akis:~$ ls /sys/class/net enp134s0f0 enp6s0 ens103 ens107 eth3 eth9 enp134s0f1 ens102 ens106 eth1eth7 lo For each ens* device, there is a sibling eth* device that maps to the same slot because both devices are behind the same bridge. Unpredictable names present well known problems, but I'll describe a specific issue I'm having. We currently do automated network testing that MAAS deploys a system and then configures 2 specific NICs on the system. While MAAS does take care to always restore the names used during commissioning (eth3 will always be the same NIC on every deploy), these names can change each time the system is commissioned. So today we need to go in and edit the NIC names manually in MAAS any time the system is re-commissioned. [Test Case] Boot with kernel option net.naming-scheme=v247; verify that all network interfaces receive predictable names. [Fix] This issue was addressed upstream by adding a new v247 naming scheme that detects this scenario and disables usage of slot-based names for these devices. Obviously changing the default naming scheme in a released LTS series could break users. However, we could introduce the v247 scheme in a focal SRU, and keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users impacted by this could then opt-in to the v247 scheme by passing net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. I could add this to DGX2 systems via a kernel_opts MAAS tag to always get predictable names during commissioning. [Regression Risk] This would change the behavior of any users who select net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
** Description changed: - On the hirsute Pi desktop, under a wayland session with the "full" KMS - overlay enabled, and "kms-modifiers" present in the - org.gnome.mutter/experimental-features, the body of a window containing - an HTML renderer (e.g. help text or a login page) displays corruption. + On the jammy Pi desktop, under a wayland session, the body of a window + containing an HTML renderer (e.g. help text or a login page) displays + corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
@juliank: I was affected by this bug when upgrading to 22.04.1 from
20.04 at the weekend. (originally installed as 18.04)
Unfortunately the system did *not* auto-recover.
Manually picking the previous kernel options from grub gave the same
"error: out of memory."
I was able to recover the system through live cd -> decrypt -> chroot ->
MODULES=dep.
This got me to initramfs on next boot, where I was able to `cryptsetup
luksOpen` and mounting /root manually before continuing the boot.
After getting back into the system, a final `update-initramfs` gave me a
cleanly booting system.
I've seen various other reports in Google of similar problems on Dell
XPS 13 hardware like my own with 22.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on
[Touch-packages] [Bug 1986513] [NEW] Software & Updates doesn't handle sources files properly when an entry has options
Public bug reported: — SYNOPSIS — Software & Updates (software-properties-gtk) has a tab "Other Software" that lists all entries in /etc/apt/sources.list and in /etc/apt/sources.list.d/*.list Some entries have an option in square brackets, e.g.: deb [arch=amd64] ... But, Software & Updates doesn't handle these options properly. 1. It removes the option if you edit the entry. 2. If the option contains "signed-by", Software & Updates doesn't even list the entry, and thus allows you to add a duplicate entry (normally prevented). — EXAMPLES — Example of point 1: Consider Google Chrome: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main #Chrome If you edit this entry in Software & Updates, it removes [arch=amd64]. The same applies to [trusted=yes]. Example of point 2: Consider SpiderOakONE, which needs "signed-by". deb [signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE This also happens with combinations: deb [arch=amd64 signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE Software & Updates doesn't even display this entry. Thus, you can manually re-add this deb, albeit without the signed-by option. — MORE DETAIL — Confusingly, you can add the option [arch=amd64] or [trusted=yes] (or both) when you add an entry in Software & Updates, but if you then edit the entry, Software & Updates removes the option. — EXPECTED BEHAVIOUR — Software & Updates should: • Display all entries • Preserve all options when editing an entry • Allow you to add suitable options when adding an entry • Allow you to edit options when editing an entry — VERSIONS — Ubuntu version: Tested on Ubuntu 20.04.4 and Ubuntu 22.04.1 software-properties-gtk version: 0.99.9.8 (on Ubuntu 20.04) 0.99.22.3 (on Ubuntu 22.04) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.3 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 09:19:51 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-05-05 (101 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1986513 Title: Software & Updates doesn't handle sources files properly when an entry has options Status in software-properties package in Ubuntu: New Bug description: — SYNOPSIS — Software & Updates (software-properties-gtk) has a tab "Other Software" that lists all entries in /etc/apt/sources.list and in /etc/apt/sources.list.d/*.list Some entries have an option in square brackets, e.g.: deb [arch=amd64] ... But, Software & Updates doesn't handle these options properly. 1. It removes the option if you edit the entry. 2. If the option contains "signed-by", Software & Updates doesn't even list the entry, and thus allows you to add a duplicate entry (normally prevented). — EXAMPLES — Example of point 1: Consider Google Chrome: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main #Chrome If you edit this entry in Software & Updates, it removes [arch=amd64]. The same applies to [trusted=yes]. Example of point 2: Consider SpiderOakONE, which needs "signed-by". deb [signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE This also happens with combinations: deb [arch=amd64 signed-by=/usr/share/keyrings/spideroakone.gpg] https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE Software & Updates doesn't even display this entry. Thus, you can manually re-add this deb, albeit without the signed-by option. — MORE DETAIL — Confusingly, you can add the option [arch=amd64] or [trusted=yes] (or both) when you add an entry in Software & Updates, but if you then edit the entry, Software & Updates removes the option. — EXPECTED BEHAVIOUR — Software & Updates should: • Display all entries • Preserve all options when editing an entry • Allow you to add suitable options when adding an entry • Allow you to edit options when
[Touch-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock
** Summary changed: - ubuntu dock bug + Can't click context menu items when they cover the dock ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Summary changed: - Can't click context menu items when they cover the dock + Can't click context menu items when they cover the dock (in a Xorg session) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1986451 Title: Can't click context menu items when they cover the dock (in a Xorg session) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: ubuntu dock in bottom position won't let me click on button (convert java file to Kotlin file) in android studio, but in the left position everything works correctly. That is, if the menu android studio overlaps the ubuntu dock, then the menu buttons will not be pressed. https://youtu.be/KsOVG7Uucow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Aug 14 10:52:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2022-07-13 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 106.121 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0603 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.3 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1986451/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964718] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
*** This bug is a duplicate of bug 1965830 *** https://bugs.launchpad.net/bugs/1965830 ** This bug is no longer a duplicate of bug 1965672 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' ** This bug has been marked a duplicate of bug 1965830 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' ** This bug is no longer a duplicate of bug 1965830 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' ** This bug has been marked a duplicate of bug 1965830 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1964718 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in apport package in Ubuntu: New Bug description: I was disregarding a crash from iperf (it just crashes sometimes when doing dual link testing) by unchecking both boxes and clicking continue, then for some reason this made apport-kde crashed, unlike iperf crashing apport-kde could really be a PITA so i am bothering to report that ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 Uname: Linux 5.17.0-051700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CrashReports: 640:1000:124:205567:2022-03-13 06:40:27.695312976 -0400:2022-03-13 06:40:28.695312976 -0400:/var/crash/_usr_bin_iperf.1000.crash 640:1000:124:179589:2022-03-13 13:44:27.904567956 -0400:2022-03-13 13:44:36.348689351 -0400:/var/crash/_usr_share_apport_apport-kde.1000.crash 640:1000:124:4046013:2022-03-12 18:18:26.441912651 -0500:2022-03-12 18:18:27.441912651 -0500:/var/crash/_usr_bin_birdtray.1000.crash CurrentDesktop: KDE Date: Sun Mar 13 13:44:28 2022 ExecutablePath: /usr/share/apport/apport-kde InstallationDate: Installed on 2021-11-26 (107 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash LD_PRELOAD= Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: /usr/bin/python3.10, Python 3.10.2, unpackaged RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965685] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
*** This bug is a duplicate of bug 1965830 *** https://bugs.launchpad.net/bugs/1965830 ** This bug is no longer a duplicate of bug 1965672 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' ** This bug has been marked a duplicate of bug 1965830 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1965685 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in apport package in Ubuntu: New Bug description: Crash at boot time ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 Uname: Linux 5.16.16-051616-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: KDE Date: Sat Mar 19 10:12:10 2022 ExecutablePath: /usr/share/apport/apport-kde InstallationDate: Installed on 2022-02-05 (43 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: LANGUAGE=en_US:en_GB PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1965685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965672] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
*** This bug is a duplicate of bug 1965830 *** https://bugs.launchpad.net/bugs/1965830 ** Changed in: apport Milestone: 2.23.0 => 2.21.0 ** This bug has been marked a duplicate of bug 1965830 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1965672 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 303, in QTimer.singleShot(0, lambda: self.ui.collect_info(on_finished=self.collect_done)) File "/usr/lib/python3/dist-packages/apport/ui.py", line 1118, in collect_info self.ui_start_info_collection_progress() File "/usr/share/apport/apport-kde", line 400, in ui_start_info_collection_progress self.dialog.spinner.setGeometry(rect.width() / 2 - self.dialog.spinner.width() / 2, TypeError: arguments did not match any overloaded call: setGeometry(self, QRect): argument 1 has unexpected type 'float' setGeometry(self, int, int, int, int): argument 1 has unexpected type 'float' Original report --- Crashed while idle. Nothing more to add... ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 600:116:124:37:2022-03-20 08:15:30.016937092 -0400:2022-03-20 08:15:30.016937092 -0400:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_DiscoverNotifier.1000.uploaded 640:1000:124:2419681:2022-03-20 08:15:24.688904523 -0400:2022-03-20 08:15:25.809905511 -0400:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_DiscoverNotifier.1000.crash 664:1000:124:0:2022-03-20 08:15:25.791905376 -0400:2022-03-20 08:15:25.791905376 -0400:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_DiscoverNotifier.1000.upload 640:1000:124:184832:2022-03-20 08:20:02.843002236 -0400:2022-03-20 08:20:02.842002228 -0400:/var/crash/_usr_share_apport_apport-kde.1000.crash CurrentDesktop: KDE Date: Sun Mar 20 08:15:03 2022 ExecutablePath: /usr/share/apport/apport-kde InstallationDate: Installed on 2022-02-18 (30 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Release amd64 (20211012) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1965672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965830] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.21.0 ** Changed in: apport Status: New => Fix Released ** Changed in: apport Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1965830 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Fix Released Bug description: this crash did happen after i successfully submitted my last report. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 18:22:47 2022 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= SHELL=/bin/bash LANG=de_DE.UTF-8 Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm games lpadmin plugdev sudo users vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1965830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965810] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
*** This bug is a duplicate of bug 1965830 *** https://bugs.launchpad.net/bugs/1965830 ** This bug is no longer a duplicate of bug 1965672 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' ** This bug has been marked a duplicate of bug 1965830 apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1965810 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in apport package in Ubuntu: New Bug description: No, sorry ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: KDE Date: Mon Mar 21 16:06:53 2022 ExecutablePath: /usr/share/apport/apport-kde InstallationDate: Installed on 2022-03-13 (8 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Alpha amd64 (20210613) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash LANGUAGE=de:en_US Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: Upgraded to jammy on 2022-03-13 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1965810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986168] Re: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS
At a guess, you have a Xorg config file but are using Wayland by default (like most users of 22.04). Please try selecting 'Ubuntu on Xorg' on the login screen. ** Tags added: jammy ** Package changed: xorg (Ubuntu) => libinput (Ubuntu) ** Also affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1986168 Title: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: 1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf etc according to https://help.ubuntu.com/community/Logitech_Marblemouse_USB 2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are still in place but the Marble Mouse buttons I configured previously are not working. Expected behavior is they should still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1986168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986373] Re: Xorg config logout when using wayland with multiple monitors
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: multimonitor wayland wayland-session ** Summary changed: - Xorg config logout when using wayland with multiple monitors + Logout when using wayland with multiple monitors ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: hybrid multigpu nouveau radeon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1986373 Title: Logout when using wayland with multiple monitors Status in Ubuntu: Incomplete Bug description: I have a 5 monitor setup. Below is the xrandr account of the monitors: xrandr --listmonitors Monitors: 5 0: +*DisplayPort-0 1920/509x1080/286+0+1124 DisplayPort-0 1: +HDMI-0 1920/477x1080/268+1920+1080 HDMI-0 2: +DVI-1 1920/519x1200/324+3840+1110 DVI-1 3: +DVI-I-1-1 1680/473x1050/296+3840+60 DVI-I-1-1 4: +VGA-1-1 1920/521x1080/293+1920+0 VGA-1-1 All works fine if Wayland is disabled in /etc/gd3/custom.conf but if it is the default enabled an attempt to adjust monitor layout or which is primary leads to a logout when apply is punched. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 just upgraded from 20.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 12 14:33:16 2022 DistUpgraded: 2022-08-12 10:35:15,953 DEBUG running apport_crash() DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03ea] NVIDIA Corporation G96C [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. G96C [GeForce 9400 GT] [19da:2107] InstallationDate: Installed on 2018-07-21 (1482 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: MSI MS-7758 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=000141a2-0f41-4525-accb-1cd881fa7072 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) dmi.bios.date: 11/01/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G41 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd11/01/2013:br4.6:svnMSI:pnMS-7758:pvr3.0:rvnMSI:rnZ77A-G41(MS-7758):rvr3.0:cvnMSI:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1986373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1985983] Re: Horiontal nav flicks
Thanks for the bug report. Please attach a video showing the problem. The easiest way to do that is to press PrtScn. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1985983 Title: Horiontal nav flicks Status in Ubuntu: Incomplete Bug description: When i hover my mouse on the left side horizontal navigation page and then use ALT+TAB to switch to a full-screen app, such as chrome or the terminal, the navigation page flicks between visible and hidden forever. Video descrpition in here: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 12 09:44:19 2022 DistUpgraded: 2022-08-12 08:59:18,023 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-43-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/470.141.03, 5.15.0-46-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2021-06-12 (426 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Avell High Performance Avell A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=bebf872e-8428-4ce7-8439-4f0eee074aae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnAvellA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: QC dmi.product.name: Avell A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1985983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1984456] Re: display resolution max is 1920x1080, video card supports higher resolution, would like 2560x1440
** Tags added: nouveau ** Summary changed: - display resolution max is 1920x1080, video card supports higher resolution, would like 2560x1440 + [nouveau] display resolution max is 1920x1080, video card supports higher resolution, would like 2560x1440 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1984456 Title: [nouveau] display resolution max is 1920x1080, video card supports higher resolution, would like 2560x1440 Status in linux package in Ubuntu: New Bug description: Current wayland display resolution max is 1920x1080, video card supports higher resolution, would like 2560x1440 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39 Uname: Linux 5.15.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 13:32:12 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-45-generic, x86_64: installed virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. G96C [GeForce 9500 GT] [106b:00b3] InstallationDate: Installed on 2022-06-20 (51 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Apple Inc. MacPro3,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-45-generic root=/dev/mapper/vgubuntu-root ro quiet splash video=eDP-1:2560x1440@60 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/29/08 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP31.88Z.006C.B05.0802291410 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42C88C8 dmi.board.vendor: Apple Inc. dmi.board.version: Proto1 dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42C88C8 dmi.modalias: dmi:bvnAppleInc.:bvrMP31.88Z.006C.B05.0802291410:bd02/29/08:br0.1:svnAppleInc.:pnMacPro3,1:pvr1.0:rvnAppleInc.:rnMac-F42C88C8:rvrProto1:cvnAppleInc.:ct2:cvrMac-F42C88C8:skuSystemSKU#: dmi.product.family: MacPro dmi.product.name: MacPro3,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
Which version of mesa on focal is that? The current backport version is from jammy and doesn't enable gallium for riscv64. Radeonsi requires llvm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-14 package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-14 source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-14 source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
