[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
Before going any further please upgrade the Motherboard firmware to the latest release and re-test. By my count there have been 13 upgrades since: DMI: ASUS System Product Name/ROG STRIX Z590-E GAMING WIFI, BIOS 0232 01/06/2021 with the latest being 2203 2024/04/17 according to https://rog.asus.com/motherboards/rog-strix/rog-strix-z590-e-gaming- wifi-model/helpdesk_bios/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed
Recent kernels: 6.8.0-25 from Noble and the mainline kernel builds from e.g: https://kernel.ubuntu.com/mainline/v6.8/amd64/ Used for ensuring support for recent hardware. If these will be rebuilt without module compression for LTS/HWE kernel releases then this issue isn't so vital, but it will make testing a recent kernel (often asked for when hitting hardware/kernel issues) extremely challenging and for most non-technical operators, impossible. On balance I'd think adding those two wildcards is a win. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057808 Title: [LTS] cryptsetup-initramfs fails when kernel modules are compressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057808] [NEW] [LTS] cryptsetup-initramfs fails when kernel modules are compressed
Public bug reported: This is the same cause as the Mantic bug "cryptsetup autopkgtest fails with zstd compressed kernel modules" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120 where hooks/cryptroot::add_modules() needs postfix wildcards after $glob.ko on 2 lines. It affects 22.04 LTS with recent kernel or local kernel built with CONFIG_MODULE_COMPRESS_* I think the fix needs cherry-picking into LTS release(s). https://salsa.debian.org/cryptsetup- team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750 At boot-time it results in the cryptic (pun intended) messages: device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT) device-mapper: ioctl: error adding target to table device-mapper: reload ioctl on luks_os (253:0) failed: No such file or directory ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Description changed: This is the same cause as the Mantic bug "cryptsetup autopkgtest fails with zstd compressed kernel modules" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120 where hooks/cryptroot::add_modules() needs postfix wildcards after $glob.ko on 2 lines. It affects 22.04 LTS with recent kernel or local kernel built with CONFIG_MODULE_COMPRESS_* I think the fix needs cherry-picking into LTS release(s). https://salsa.debian.org/cryptsetup- team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750 At boot-time it results in the cryptic (pun intended) messages: - device-mapper: table: 253:0 crypt: Error allocation crypto tfm (-ENOENT) + device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT) device-mapper: ioctl: error adding target to table device-mapper: reload ioctl on luks_os (253:0) failed: No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057808 Title: [LTS] cryptsetup-initramfs fails when kernel modules are compressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2035120] Re: cryptsetup autopkgtest fails with zstd compressed kernel modules
This also affects LTS releases with HWE, and/or locally built kernels. I hit it today building v6.8.0 with CONFIG_MODULES_COMPRESS_XZ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2035120 Title: cryptsetup autopkgtest fails with zstd compressed kernel modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948525] Re: Alters Performance options > Cache mode causing start failure
Remaining problem could be with SeaBIOS. Copying here my question to
OFTC #virt
Doing some GRUB bios-mode boot testing with qemu/x86_64. Attached 2 IDE
devices, a small HDD (file with mbr and 2 partitions) and a CDROM (iso
file). If SeaBIOS boots the CD GRUB can see both devices ("(cd) (hd0)")
but if SeaBIOS boots the HDD GRUB can only see the HD ("(hd0)").
Is this a SeaBios issue or something about how the guest is
(mis)configured
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948525
Title:
Alters Performance options > Cache mode causing start failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948525] Re: Alters Performance options > Cache mode causing start failure
After reserching the NFS lock issue it seems I found the solution on the Debian 11 Bullseye server: $ sudo systemctl enable rpc-statd Created symlink /etc/systemd/system/nfs-server.service.wants/rpc-statd.service → /lib/systemd/system/rpc-statd.service. $ sudo systemctl start rpc-statd Now, the guest VM on the client has started ... but GRUB isn't seeing the virtual IDE CDROM device. I'd expect to see a second hd device. This is testing GRUB BIOS mode for building various GRUB configs - no OS image just a raw msdos label partitioned MBR with core image and a /boot/ file-system with GRUB modules and a vmlinux. Nothing out of line in the libvirt/qemu log file. I'll dig further -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948525 Title: Alters Performance options > Cache mode causing start failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948525] Re: Alters Performance options > Cache mode causing start failure
One issue is that when the libvirt cache mode is set to "none" what is
passed to qemu is "write-cache=on". If I set libvirt cache mode to
"writethrough" qemu gets "write-cache=off" !
The remaining problem is solving the lock issue on NFS. Came back to
this issue again today and its again blocked everything.
The reason qemu cannot write the lock-file is the user/group it runs as
(libvirt-qemu/kvm) do not exist on the NFS server so there is no
possible NFS mapping for those. So, despite reading the other bugs and
the various links within them I'm still not clear how to simply tell
qemu not to bother with locking at all - I KNOW it is safe, so do what I
damned well tell you!
The qemu log ends with:
2021-11-12T20:35:51.527063Z qemu-system-x86_64: -device ide-
cd,bus=ide.0,unit=0,share-
rw=on,drive=libvirt-1-format,id=ide0-0-0,write-cache=off: Failed to lock
byte 100: No locks available
The relevant lines for the qemu-system-x86_64 command-line from the same
log file are:
-blockdev
'{"node-name":"libvirt-2-format","read-only":true,"discard":"ignore","cache":{"direct":true,"no-flush":false},"driver":"raw","file":"libvirt-2
-storage"}' \
-device
virtio-blk-pci,bus=pci.0,addr=0x7,drive=libvirt-2-format,id=virtio-disk0,bootindex=1,write-cache=on
\
-blockdev
'{"driver":"file","filename":"/srv/NAS/Sunny/Downloads/ISO/kubuntu-21.04-desktop-amd64.iso","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}'
\
I tried adding various lines to:
/etc/apparmor.d/local/abstractions/libvirt-qemu
/srv/NAS/Sunny/Downloads/** rk,
or
/srv/NAS/Sunny/Downloads/**/* rk,
But of course these aren't going to help because they have no effect on
the underlying NFS permissions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948525
Title:
Alters Performance options > Cache mode causing start failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950095] [NEW] [github] 20.04: Apt fails to download URLs with non-encoded querystrings
Public bug reported: I've just helped a group of Ubuntu 20.04 users with Microsoft Surface devices. They rely upon a github repository releases pocket as the apt archive. Those users recently hit a bug "Ubuntu: Apt update fails with Error 401 Unauthorized" [1] The initial simple Github URL gets a Location: redirect to a complex URL with un-escaped query-string. The resulting complex URL causes apt to fail to fetch the resource. $ sudo apt upgrade -y Err:1 https://pkg.surfacelinux.com/debian release/main amd64 libwacom-surface amd64 1.12-2 401 Unauthorized [IP: 185.199.110.133 443] The URL can be manually corrected. One of the Surface users provided this example: bad: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256 Credential=AKIAIWNJYAX4CSVEH53A/20211105/us- east-1/s3/aws4_request=20211105T161053Z Expires=300 Signature=2bc0c28946db539ada250b1030c37249dae909d73a68c90b5e7bfe7fecd5d347 SignedHeaders=host_id=0_id=0_id=139604852 content-disposition=attachment; filename=libwacom- surface_1.12-2_amd64.deb=application/octet-stream good: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256 Credential=AKIAIWNJYAX4CSVEH53A%2F20211105%2Fus- east-1%2Fs3%2Faws4_request=20211105T160935Z Expires=300 Signature=44d9307e66dfb5b3672ee0082b8801ad2532ac4b6be61c3442fb265ffce72852 SignedHeaders=host_id=0_id=0_id=139604852 content-disposition=attachment%3B%20filename%3Dlibwacom- surface_1.12-2_amd64.deb=application%2Foctet- stream I found this also affects a github repository I recently added for Zotero on 20.04. The problem is fixed in later versions of apt upstream, in Debian and Ubuntu releases. I cherry-picked the 4 commits [3] and provided a package for Focal in my PPA [2] which multiple users have reported (in [1]) solves the issue. It would be really good to get those patches included in 20.04 as an SRU. As the code is in later versions of apt and is focused on the URL encoding only it has minimal potential for causing regressions. [1] https://github.com/linux-surface/linux-surface/issues/625 [2] https://launchpad.net/~tj/+archive/ubuntu/bugfixes [3] https://salsa.debian.org/apt- team/apt/-/commit/06ec0067057e0578f3bc515f6a97d6a9d70824f6 ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950095 Title: [github] 20.04: Apt fails to download URLs with non-encoded querystrings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1950095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/5538304/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574341 Title: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1574341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch
Although most other issues are solved there is still no multitouch for
this device with kernel v5.15 and xserver-xorg 1.20.13-1ubuntu1 using
Kubuntu 21.10.
# xinput
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ Asus TouchPad id=10 [slave pointer (2)]
⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Mouse id=15 [slave pointer
(2)]
⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=16 [slave pointer (2)]
⎜ ↳ BT5.0 Mouse id=20 [slave pointer (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
↳ Power Button id=6[slave keyboard (3)]
↳ Asus Wireless Radio Control id=7[slave keyboard (3)]
↳ Video Bus id=8[slave keyboard (3)]
↳ Sleep Button id=9[slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=11 [slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=12 [slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=13 [slave keyboard (3)]
↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)]
↳ SYNAPTICS Synaptics Touch Digitizer V04 Stylusid=17 [slave
keyboard (3)]
↳ Asus WMI hotkeys id=18 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=19 [slave keyboard (3)]
# for id in {15..17}; do xinput --list $id; done
SYNAPTICS Synaptics Touch Digitizer V04 Mouse id=15 [slave pointer (2)]
Reporting 7 classes:
Class originated from: 15. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right"
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz
Wheel Right"
Button state:
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 3:
Label: Rel Vert Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIScrollClass
Scroll info for Valuator 2
type: 2 (horizontal)
increment: 15.00
flags: 0x0
Class originated from: 15. Type: XIScrollClass
Scroll info for Valuator 3
type: 1 (vertical)
increment: 15.00
flags: 0x0
SYNAPTICS Synaptics Touch Digitizer V04 id=16 [slave pointer (2)]
Reporting 6 classes:
Class originated from: 16. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right"
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz
Wheel Right"
Button state:
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs MT Position X
Range: 0.00 - 65535.00
Resolution: 0 units/m
Mode: absolute
Current value: 44291.812165
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs MT Position Y
Range: 0.00 - 65535.00
Resolution: 0 units/m
Mode: absolute
Current value: 39378.849306
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 3:
[Bug 1945596] Re: Autopkgtest fail of 1.0.1-2ubuntu3 - Activation failed because the device is unmanaged
Here's the reproducer that shows that dummy0 is being created in the host network namespace. This is an upstream bug (oversight) so far as I can tell from its purpose. # what the host sees initially root@t300chi:~# nmcli con NAME UUID TYPE DEVICE USB3hub 85f05002-c66a-4b03-b340-21f512ac72fd ethernet eth0 soggyb9e78bf8-9e6d-4292-9390-d56876fa8300 wifi wlp2s0 virbr0 b09a6211-605c-4d0c-bff7-996c5f58299c bridgevirbr0 # add the new network namespace root@t300chi:~# ip netns add test # run nmcli in the network namespace root@t300chi:~# ip netns exec test nmcli connection add type dummy con-name dummy0 ifname dummy0 ip4 10.0.0.2 gw4 10.0.0.1 Connection 'dummy0' (2bdfbb93-f51a-48d8-87f3-d2a2b5a72aee) successfully added. # check if the interface has been added - strange, it lists dummy0 and the host interfaces!! root@t300chi:~# ip netns exec test nmcli con NAME UUID TYPE DEVICE dummy0 2bdfbb93-f51a-48d8-87f3-d2a2b5a72aee dummy dummy0 USB3hub 85f05002-c66a-4b03-b340-21f512ac72fd ethernet eth0 soggyb9e78bf8-9e6d-4292-9390-d56876fa8300 wifi wlp2s0 virbr0 b09a6211-605c-4d0c-bff7-996c5f58299c bridgevirbr0 # activate - note this succeeds on my system for a reason explained below root@t300chi:~# ip netns exec test nmcli con up dummy0 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConn ection/7) # lets check what interfaces exist in the network namespace root@t300chi:~# ip netns exec test ip link show 1: lo: mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 # aha! so dummy0 isn't in the namespace. # interface is created on the parent network namespace where NetworkManager daemon is oot@t300chi:~# nmcli con NAME UUID TYPE DEVICE dummy0 2bdfbb93-f51a-48d8-87f3-d2a2b5a72aee dummy dummy0 USB3hub 85f05002-c66a-4b03-b340-21f512ac72fd ethernet eth0 soggyb9e78bf8-9e6d-4292-9390-d56876fa8300 wifi wlp2s0 virbr0 b09a6211-605c-4d0c-bff7-996c5f58299c bridgevirbr0 --- So the expectation that dummy0 is being created in the network namespace is incorrect. nmcli is talking to NetworkManager over DBus which is a daemon in the parent namespace. Why is it failing on Ubuntu (but not on my system) ? Due to my override of 10-globally-managed-devices.conf: root@t300chi:~# ls -l /usr/lib/NetworkManager/conf.d/10-globally- managed-devices.conf /etc/NetworkManager/conf.d/ -rw-r--r-- 1 root root 80 Sep 27 16:07 /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf /etc/NetworkManager/conf.d/: total 4 -rw-r--r-- 1 root root 0 Oct 31 04:48 10-globally-managed-devices.conf -rw-r--r-- 1 root root 32 Sep 27 16:07 default-wifi-powersave-on.conf root@t300chi:~# cat /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf [keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma The "unmanaged" result is due to this exclusion that was originally added presumably to only have NM manage wireless devices. I have to disable it to manage Ethernet connections but the wildcard "*" will include type:dummy as unmanaged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945596 Title: Autopkgtest fail of 1.0.1-2ubuntu3 - Activation failed because the device is unmanaged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1945596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948525] [NEW] Alters Performance options > Cache mode causing start failure
Public bug reported:
Ubuntu 20.04 amd64. Originally thought this was virt-manager but tested
via virsh and found it appears to be caused by libvirt.
$ apt-cache policy libvirt-daemon virt-manager | grep -E '(^[^ ]|Installed)'
libvirt-daemon:
Installed: 6.0.0-0ubuntu8.14
virt-manager:
Installed: 1:2.2.1-3ubuntu2.1
$ virsh start 1804test
error: Failed to start domain 1804test
error: internal error: qemu unexpectedly closed the monitor:
2021-10-23T10:27:43.756117Z qemu-system-x86_64: -device
ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1,bootindex=1,write-cache=on:
Failed to lock byte 100
Notice the "write-cache=on". In the domain definition it is set to
"none":
I found that changing this (via virt-manager) sometimes does, and
sometimes does not, get reflected in the underlying call to qemu-system.
The reason for disabling caching is the ISOs are stored on an NFS file-
system and with caching the attempt to write-lock fails.
The full command-line captured as the machine was being started was:
/usr/bin/qemu-system-x86_64 -name guest=1804test,debug-threads=on
-S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-23-1804test/master-key.aes
-machine pc-i440fx-focal,accel=kvm,usb=of
f,vmport=off,dump-guest-core=off -cpu
EPYC-Rome,x2apic=on,tsc-deadline=on,hypervisor=on,tsc-adjust=on,arch-capabilities=on,xsaves=on,cmp-legacy=on
,virt-ssbd=on,svme-addr-chk=on,rdctl-no=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,clwb=off,umip=off,rdpid=off,wbnoinvd=off,amd-stibp=of
f -m 4096 -overcommit mem-lock=off -smp 4,sockets=4,cores=1,threads=1 -uuid
7272b57e-3428-493c-b126-a7816af4f9e7 -no-user-config -nodefaults -char
dev socket,id=charmonitor,fd=31,server,nowait -mon
chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global
kvm-pit.lost_ti
ck_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
PIIX4_PM.disable_s4=1 -boot menu=on,strict=on -device ich9-usb-ehci1,i
d=usb,bus=pci.0,addr=0x5.0x7 -device
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
-device ich9-usb-uhci2,masterb
us=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device
ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device
virtio-serial-pci,id
=virtio-serial0,bus=pci.0,addr=0x6 -blockdev
{"driver":"file","filename":"/var/lib/libvirt/images/1804test.qcow2","node-name":"libvirt-2-storage",
"auto-read-only":true,"discard":"unmap"} -blockdev
{"node-name":"libvirt-2-format","read-only":false,"driver":"qcow2","file":"libvirt-2-storage","
backing":null} -device
ide-hd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0 -blockdev
{"driver":"file","filename":"/srv/NAS/Sunny/Downloads/
ISO/lubuntu-18.04-desktop-amd64.iso","node-name":"libvirt-1-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unm
ap"} -blockdev
{"node-name":"libvirt-1-format","read-only":true,"cache":{"direct":true,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"
} -device
ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1,bootindex=1,write-cache=on
-netdev tap,fd=33,id=hostnet0 -device e1000,netdev
=hostnet0,id=net0,mac=52:54:00:c9:b5:59,bus=pci.0,addr=0x3 -chardev
pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-d
evice usb-tablet,id=input0,bus=usb.0,port=1 -spice
port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
-device
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
-device intel-hda,id=sound0,
bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0
-chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=
charredir0,id=redir0,bus=usb.0,port=2 -chardev
spicevmc,id=charredir1,name=usbredir -device
usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=
3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg
timestamp=on
The full domain definition:
1804test
7272b57e-3428-493c-b126-a7816af4f9e7
4194304
4194304
4
hvm
destroy
restart
destroy
/usr/bin/qemu-system-x86_64
[Bug 1948525] Re: Alters Performance options > Cache mode causing start failure
** Attachment added: "Screenshot from virt-manager" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+attachment/5535410/+files/Screenshot_2021-10-23_11-17-02.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948525 Title: Alters Performance options > Cache mode causing start failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1948525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931024] Re: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]
I'm currently working on getting my optimisation patches into the mainline kernel and to Debian's initramfs-tools. After that I'll investigate dracut. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931024 Title: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947336] [NEW] grub-probe: info: unknown LVM type writecache
Public bug reported: On LVM systems where an LV is fronted by a dm-writecache LV grub-probe fails to identify the filesystem type: root@sunny:~# grub-probe -d /dev/mapper/SUNNY-usr_local -t fs error: invalid segment. error: invalid segment. grub-probe: error: disk `lvmid/9jfMwj-Zq6X-U8VT-Dt7o-8NQO-CZnP-8SIDgx/H8qr1q-N9se-U1iU-2HpR-zgIR-BiEw-bOBwAM' not found. root@sunny:~# file -sL /dev/mapper/SUNNY-usr_local /dev/mapper/SUNNY-usr_local: Linux rev 1.0 ext4 filesystem data, UUID=63874235-ad0b-4e60-8638-4121e5d5664a, volume name "usr_local" (extents) (64bit) (large files) (huge files) The error reports percolate up to "update-grub" / "grub-mkconfig" giving the impression there's something very wrong and reboot might fail. In this case though grub-probe is being triggered by os-prober (via /etc/grub.d/30_os-prober and /usr/lib/os-probes/50mounted-tests /dev/mapper/SUNNY-usr_local) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947336 Title: grub-probe: info: unknown LVM type writecache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451032] Re: keyscript option in crypttab not implemented
Update: Lennart's AF_SOCKET solution was added to systemd v248 in: commit e2c2f868b28f1445e061bf7eb475b0c49efe3ac2 Author: Lennart Poettering Date: Wed Nov 4 17:24:53 2020 +0100 cryptsetup: port cryptsetup's main key file logic over to read_full_file_full() Previously, we'd load the file with libcryptsetup's calls. Let's do that in our own, so that we can make use of READ_FULL_FILE_CONNECT_SOCKET, i.e. read in keys via AF_UNIX sockets, so that people can plug key providers into our logic. This provides functionality similar to Debian's keyscript= crypttab option (see → #3007), as it allows key scripts to be run as socket activated services, that have stdout connected to the activated socket. In contrast to traditional keyscript= support this logic runs stuff out of process however, which is beneficial, since it allows sandboxing and similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451032 Title: keyscript option in crypttab not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1451032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451032] Re: keyscript option in crypttab not implemented
This really should not be marked Invalid since it represents a very real regression on recommended and documented functionality that many installs using LUKS rely upon. Workarounds of varying security quality abound as a result instead of a single, well designed and integrated solution. Indeed, in December 2020 Lennart Poettering created a simple patch for this by extending the cryptsetup code to read an AF_SOCKET [1] and recommended linking that with a system-service that sets StandardOutput=socket [2][3] where the key data can be read from. [1] hasn't been merged into systemd as yet but with some additional push upstream that could likely happen. [1] https://github.com/poettering/systemd/commit/e2c2f868b28f1445e061bf7eb475b0c49efe3ac2 [2] https://github.com/systemd/systemd/pull/3007#issuecomment-710212323 [3] https://github.com/systemd/systemd/pull/3007#issuecomment-713860129 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451032 Title: keyscript option in crypttab not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1451032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945065] [NEW] side scroll bar far too small
Public bug reported: scroll bar was so small as to be almost invisible even when I hovered over where it should be - it did work once or twice but I had to get lucky in where I clicked to move the info in the window up or down. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: qterminal 0.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt Date: Sat Sep 25 10:35:22 2021 LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Beta amd64 (20210923) SourcePackage: qterminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qterminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945065 Title: side scroll bar far too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1945065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945064] [NEW] no scroll bar on window
Public bug reported: no scrollbar on the software selection window. (arrow keys did work) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: discover (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt Date: Sat Sep 25 10:31:42 2021 LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Beta amd64 (20210923) SourcePackage: discover UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: discover (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945064 Title: no scroll bar on window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/discover/+bug/1945064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944468] Re: Electron applications all crash upon launch
I suspect these may be related: https://github.com/electron/electron/pull/30893 "fix: crash when launching app with systemd v249" https://github.com/microsoft/vscode/issues/132609 "Electron 14+ required? Potential systemd 249 / nVidia issue" Electron patch backported from Chromium: https://github.com/electron/electron/commit/1d531f29eeb8392195262bea038abed75fb51b8c Also, have you considered this could be caused by a recent Electron update that has made its way into these applications? https://www.electronjs.org/releases/stable Electron Sandboxing Overview https://www.electronjs.org/docs/tutorial/sandbox ** Bug watch added: github.com/microsoft/vscode/issues #132609 https://github.com/microsoft/vscode/issues/132609 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944468 Title: Electron applications all crash upon launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1944468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
This was just brought to my attention so I took a look at the source- code. Thanks to oldfred's comment #20 showing part of the installer log that helps isolate the source-code responsible. It looks like this is a result of this code - written in 206 - assuming a debconf entry that is empty and in consequence choosing a default device. Adding some debug prints into the code might confirm that and allow it to be fixed. See specifically line 45 in grubinstaller.py (Python code) https://git.launchpad.net/ubuntu/+source/ubiquity/tree/ubiquity/components/grubinstaller.py#n45 Calling misc.grub_default() from: https://git.launchpad.net/ubuntu/+source/ubiquity/tree/ubiquity/misc.py#n370 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940908] Re: resolved: closes listening socket too rapidly and sends Destination port unreachable
I've cherry-picked the upstream patches and built the package in my bug- fixes PPA: https://launchpad.net/~tj/+archive/ubuntu/bugfixes Verified it solves the issue even in the face of a 1000ms delay being imposed by the router using: ## example traffic control to slow down UDP port 53 traffic from a specific upstream DNS server being forwarded by router for egress from the LOCAL bridge device. # tc qdisc add dev LOCAL root handle 1:0 prio # tc qdisc add dev LOCAL parent 1:2 handle 10: netem delay 1000ms # tc filter add dev LOCAL protocol ipv6 parent 1: prio 1 u32 match ip6 src fddc:7e00:e001:ee00::1/64 match ip6 sport 53 0x flowid 10:1 # tc filter add dev LOCAL protocol ipv6 parent 1: prio 1 u32 match ip6 dst fddc:7e00:e001:ee00::1/64 match ip6 dport 53 0x flowid 10:1 tc -s qdisc ls dev LOCAL qdisc prio 1: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 4643351 bytes 7676 pkt (dropped 0, overlimits 0 requeues 0) backlog 138b 1p requeues 0 qdisc netem 10: parent 1:2 limit 1000 delay 1s Sent 2682417 bytes 3245 pkt (dropped 0, overlimits 0 requeues 0) backlog 138b 1p requeues 0 ## prio[rity] creates 3 bands (classes :1 :2 :3) by default. Interactive/immediate packets (UDP 53 DNS) should have Type Of Service (TOS 0x1000) set in the IP packet header by the resolvers. Default priomap puts those packets in the 2nd band (:2 for Interactive/Minimise delay). The netem delay qdisc is attached to $parent:2 with handle 10: (major:minor - minor defaults to 0). u32 (unsigned 32-bit) filters that match the UDP port 53 traffic direct it to the handle of the netem qdisc (flowid 10:1 - :1 being the first leaf) where a 300ms delay is imposed. # tcpdump -vvvni enp2s0 "(ip6 and port 53) or (icmp6[icmp6type] = 1 and icmp6[icmp6code] = 4)" ... 21:01:49.232778 IP6 (flowlabel 0xc8a82, hlim 64, next-header UDP (17) payload length: 56) fddc:7e00:e001:ee00:fa75:a4ff:fef3:42b4.59484 > fddc:7e0 0:e001:ee00::1.53: [bad udp cksum 0x7528 -> 0x9b42!] 25832+ [1au] ? packages.ubuntu.com. ar: . OPT UDPsize=512 (48) 21:01:49.232862 IP6 (flowlabel 0x9137e, hlim 64, next-header UDP (17) payload length: 56) fddc:7e00:e001:ee00:fa75:a4ff:fef3:42b4.43177 > fddc:7e0 0:e001:ee00::1.53: [bad udp cksum 0x7528 -> 0x5114!] 61129+ [1au] ? packages.ubuntu.com. ar: . OPT UDPsize=512 (48) 21:01:49.319885 IP6 (flowlabel 0x5decb, hlim 63, next-header UDP (17) payload length: 84) fddc:7e00:e001:ee00::1.53 > fddc:7e00:e001:ee00:fa75:a4f f:fef3:42b4.43177: [udp sum ok] 61129 q: ? packages.ubuntu.com. 1/0/1 packages.ubuntu.com. [10m] 2a01:7e00:e001:ee64::5bbd:5e25 ar: . OPT UDPsize=1232 (76) 21:01:49.319920 IP6 (flowlabel 0x45773, hlim 63, next-header UDP (17) payload length: 84) fddc:7e00:e001:ee00::1.53 > fddc:7e00:e001:ee00:fa75:a4f f:fef3:42b4.59484: [udp sum ok] 25832 q: ? packages.ubuntu.com. 1/0/1 packages.ubuntu.com. [10m] 2a01:7e00:e001:ee64::5bbd:5e25 ar: . OPT UDPsize=1232 (76) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940908 Title: resolved: closes listening socket too rapidly and sends Destination port unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940908] Re: resolved: closes listening socket too rapidly and sends Destination port unreachable
The local systemd-resolved fails to resolve the name so client applications return failures. Most notably it shows up in web browsers but also for apt package updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940908 Title: resolved: closes listening socket too rapidly and sends Destination port unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940908] Re: resolved: closes listening socket too rapidly and sends Destination port unreachable
** Description changed: Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248) With systemd v245 (and v247) and systemd-resolved we're seeing frequent problems due to resolved rapidly closing the socket on which it sends out a query before the server has answered. The server answers and then resolved sends an ICMP Destination Unreachable (Port Unreachable) response! This breaks name lookups frequently. In our case the DNS server is reached via a Wireguard tunnel over a satellite link and latencies can vary. A typical example captured via tcpdump: 07:22:03.446919 IP6 fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4.45338 > fddc:7e00:e001:ee00::1.53: 2963+ [1au] ? contile-images.services.mozilla.com. (64) 07:22:03.501089 IP6 fddc:7e00:e001:ee00::1.53 > fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4.45338: 2963 1/0/1 2a01:7e00:e001:ee64::2278:7366 (92) 07:22:03.501152 IP6 fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4 > fddc:7e00:e001:ee00::1: ICMP6, destination unreachable, unreachable port, fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4 udp port 45338, length 148 The time difference here is only 0.054170 and there is no way to alter the timeout in resolved. There are recent upstream commits to fix this which ought to be cherry- picked. See: https://github.com/systemd/systemd/issues/17421 https://github.com/systemd/systemd/pull/17535 https://github.com/systemd/systemd/commit/e03d156f78cb5a0cac85d1e1310d89fdfa4f1b88 + + If I am reading the code correctly the timeout is very short: + + src/resolve/resolved-dns-transaction.c:22:#define DNS_TIMEOUT_USEC + (SD_RESOLVED_QUERY_TIMEOUT_USEC / DNS_TRANSACTION_ATTEMPTS_MAX) + + src/resolve/resolved-def.h:79:#define SD_RESOLVED_QUERY_TIMEOUT_USEC + (120 * USEC_PER_SEC) + + src/resolve/resolved-dns-transaction.h:212:#define + DNS_TRANSACTION_ATTEMPTS_MAX 24 + + So in micro-seconds that is 120 /24 = 5 per query with, as inferred, up + to 24 attempts (I don't see multiple duplicate requests on the wire so + not sure DNS_TRANSACTION_ATTEMPTS_MAX affects this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940908 Title: resolved: closes listening socket too rapidly and sends Destination port unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940908] Re: resolved: closes listening socket too rapidly and sends Destination port unreachable
** Description changed: + Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248) + With systemd v245 (and v247) and systemd-resolved we're seeing frequent problems due to resolved rapidly closing the socket on which it sends out a query before the server has answered. The server answers and then resolved sends an ICMP Destination Unreachable (Port Unreachable) response! This breaks name lookups frequently. In our case the DNS server is reached via a Wireguard tunnel over a satellite link and latencies can vary. A typical example captured via tcpdump: 07:22:03.446919 IP6 fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4.45338 > fddc:7e00:e001:ee00::1.53: 2963+ [1au] ? contile-images.services.mozilla.com. (64) 07:22:03.501089 IP6 fddc:7e00:e001:ee00::1.53 > fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4.45338: 2963 1/0/1 2a01:7e00:e001:ee64::2278:7366 (92) 07:22:03.501152 IP6 fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4 > fddc:7e00:e001:ee00::1: ICMP6, destination unreachable, unreachable port, fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4 udp port 45338, length 148 The time difference here is only 0.054170 and there is no way to alter the timeout in resolved. There are recent upstream commits to fix this which ought to be cherry- picked. See: https://github.com/systemd/systemd/issues/17421 https://github.com/systemd/systemd/pull/17535 https://github.com/systemd/systemd/commit/e03d156f78cb5a0cac85d1e1310d89fdfa4f1b88 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940908 Title: resolved: closes listening socket too rapidly and sends Destination port unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940908] [NEW] resolved: closes listening socket too rapidly and sends Destination port unreachable
Public bug reported: With systemd v245 (and v247) and systemd-resolved we're seeing frequent problems due to resolved rapidly closing the socket on which it sends out a query before the server has answered. The server answers and then resolved sends an ICMP Destination Unreachable (Port Unreachable) response! This breaks name lookups frequently. In our case the DNS server is reached via a Wireguard tunnel over a satellite link and latencies can vary. A typical example captured via tcpdump: 07:22:03.446919 IP6 fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4.45338 > fddc:7e00:e001:ee00::1.53: 2963+ [1au] ? contile-images.services.mozilla.com. (64) 07:22:03.501089 IP6 fddc:7e00:e001:ee00::1.53 > fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4.45338: 2963 1/0/1 2a01:7e00:e001:ee64::2278:7366 (92) 07:22:03.501152 IP6 fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4 > fddc:7e00:e001:ee00::1: ICMP6, destination unreachable, unreachable port, fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4 udp port 45338, length 148 The time difference here is only 0.054170 and there is no way to alter the timeout in resolved. There are recent upstream commits to fix this which ought to be cherry- picked. See: https://github.com/systemd/systemd/issues/17421 https://github.com/systemd/systemd/pull/17535 https://github.com/systemd/systemd/commit/e03d156f78cb5a0cac85d1e1310d89fdfa4f1b88 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940908 Title: resolved: closes listening socket too rapidly and sends Destination port unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940332] Re: hci0: Failed to send firmware data (-38)
User is long-gone after workaround solved their issue. This report is FYI in case other users hit the same error messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940332 Title: hci0: Failed to send firmware data (-38) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940481] Re: dhclient.conf should set send DHCPv6 host-name option
** Description changed: Despite the fix in 2012 (bug #991360) the default configuration shipped - with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the - DHCPv6 hostname option by default. All it needs is: + with isb-dhcp-client /etc/dhcp/dhclient.conf in 2021 still does not set + the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940481 Title: dhclient.conf should set send DHCPv6 host-name option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1940481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940481] [NEW] dhclient.conf should set send DHCPv6 host-name option
Public bug reported: Despite the fix in 2012 (bug #991360) the default configuration shipped with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Description changed: Despite the fix in 2012 (bug #991360) the default configuration shipped with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); - With this option it causes dhcpy6d's dynamic DNS update (to bind9) to + Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940481 Title: dhclient.conf should set send DHCPv6 host-name option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1940481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940332] Re: hci0: Failed to send firmware data (-38)
** Description changed: This report is related to a problem reported in IRC #ubuntu whereby (Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot time but can later. Appears to be a race condition between the wifi chipset setting up the device and enabling the attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. - Reporting user tells us this works around the problem + Reporting user tells us this works around the problem. + + The code responsible is net/bluetooth/hci_request.c::__hci_cmd_sync_ev() + and/or + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n147 + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n234 + + as the result of the calls: + + err = wait_event_interruptible_timeout(...) + + since only these are followed by calls to + net/bluetooth/lib.c::bt_to_errno() and that is the only function that + can return -ENOSYS (-38) + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/lib.c#n132 + + default: + return ENOSYS; + } -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940332 Title: hci0: Failed to send firmware data (-38) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940332] [NEW] hci0: Failed to send firmware data (-38)
Public bug reported: This report is related to a problem reported in IRC #ubuntu whereby (Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot time but can later. Appears to be a race condition between the wifi chipset setting up the device and enabling the attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "Kernel Log" https://bugs.launchpad.net/bugs/1940332/+attachment/5518599/+files/kernel.log ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940332 Title: hci0: Failed to send firmware data (-38) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879923] Re: Update Scan Data Over Internet fails
I've built a package with this fix applied in my PPA at: https://launchpad.net/~tj/+archive/ubuntu/bugfixes/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879923 Title: Update Scan Data Over Internet fails To manage notifications about this bug go to: https://bugs.launchpad.net/kaffeine/+bug/1879923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879923] Re: Update Scan Data Over Internet fails
** Attachment added: "Screenshot of Scantable Update success" https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/+attachment/5517930/+files/kaffeine-scantable-success.png ** Changed in: kaffeine (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879923 Title: Update Scan Data Over Internet fails To manage notifications about this bug go to: https://bugs.launchpad.net/kaffeine/+bug/1879923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879923] Re: Update Scan Data Over Internet fails
Attached patch cherry-picked from upstream and confirmed working ** Patch added: "Update for focal 20.04" https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/+attachment/5517929/+files/kaffeine_2.0.18-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879923 Title: Update Scan Data Over Internet fails To manage notifications about this bug go to: https://bugs.launchpad.net/kaffeine/+bug/1879923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879923] Re: Update Scan Data Over Internet fails
** Changed in: kaffeine (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Description changed:
- Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop. Update Scan
- Data Over Internet fails with message: Scan data update failed
+ Workaround from Tj; 3 commands (ignore word-wrapping by launchpad):
+
+ cd ~/.local/share/kaffeine
+ mv scanfile.dvb{,.$(awk 'C==1{print;exit}/^\[date\]/{C=1}' scanfile.dvb)}
+ wget https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/scantable.dvb -O
scanfile.dvb
+
+
+
+
+ Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop. Update Scan Data
Over Internet fails with message: Scan data update failed
I believe Kaffeine is looking for a file called scanfile.dvb or perhaps
scanfile.dvb.qz
https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/ shows a file
called scantable.dvb (Different file name)
The wiki here (https://linuxtv.org/wiki/index.php/Dtv-scan-tables) says
that this file will be autocreated and eventually be located here:
https://autoconfig.kde.org/kaffeine/ The file i see at this location
is currently called: scantable.dvb.qz
Perhaps this is just a file naming issue?
Thanks,
Iestyn Guest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879923
Title:
Update Scan Data Over Internet fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/kaffeine/+bug/1879923/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879923] Re: Update Scan Data Over Internet fails
Confirming this is still an issue on 20.04 with
$ apt-cache policy kaffeine
kaffeine:
Installed: 2.0.18-1build1
Candidate: 2.0.18-1build1
Version table:
*** 2.0.18-1build1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
The file is a sequence of zlib-encoded bytes created using QT's
QFile.qCompress()
https://doc.qt.io/qt-5/qbytearray.html#qCompress
QByteArray qCompress(const QByteArray , int compressionLevel = -1)
where compressionLevel = 9 (best).
Analyzing the received file shows:
$ binwalk /tmp/scantable.dvb.gz
DECIMAL HEXADECIMAL DESCRIPTION
4 0x4 Zlib compressed data, best compression
The file being requested is:
https://autoconfig.kde.org/kaffeine/scantable.dvb.qz
src/dvb/dvbconfigdialog.cpp:636:job =
KIO::get(QUrl("https://autoconfig.kde.org/kaffeine/scantable.dvb.qz;),
KIO::NoReload,
Enabling KIO debugging reveals the file is downloaded:
kf5.kio.kio_http: Sending Header:
kf5.kio.kio_http: "GET /kaffeine/scantable.dvb.qz HTTP/1.1"
kf5.kio.kio_http: "Host: autoconfig.kde.org"
kf5.kio.kio_http: "Connection: keep-alive"
kf5.kio.kio_http: "User-Agent: Mozilla/5.0 (X11; Linux x86_64) KHTML/5.68.0
(like Gecko) Konqueror/5 KIO/5.68"
kf5.kio.kio_http: "Accept: text/html, text/*;q=0.9, image/jpeg;q=0.9,
image/png;q=0.9, image/*;q=0.9, */*;q=0.8"
kf5.kio.kio_http: "Accept-Encoding: gzip, deflate, x-gzip, x-deflate"
kf5.kio.kio_http: "Accept-Charset: utf-8,*;q=0.5"
kf5.kio.kio_http: "Accept-Language: en-GB,en;q=0.9"
kf5.kio.kio_http: sent it!
kf5.kio.kio_http:
kf5.kio.kio_http: Received Status Response:
kf5.kio.kio_http: "HTTP/1.1 200 OK"
kf5.kio.kio_http: QUrl("https://autoconfig.kde.org/kaffeine/scantable.dvb.qz;)
response code: 200 previous response code: 0
kf5.kio.kio_http: wasAuthError= false isAuthError= false sameAuthError= false
kf5.kio.kio_http: -- full response:
"HTTP/1.1 200 OK\r\nDate: Sun, 15 Aug 2021 07:07:46 GMT\r\nServer:
Apache/2.4.29 (Ubuntu)\r\nUpgrade: h2\r\nConnection: Upgrade, Keep-Alive\r\nLa
st-Modified: Tue, 04 May 2021 17:52:06 GMT\r\nAccept-Ranges:
bytes\r\nContent-Length: 102499\r\nCache-Control: max-age=0\r\nExpires: Sun, 15
Aug 2
021 07:07:46 GMT\r\nStrict-Transport-Security:
max-age=15768000\r\nReferrer-Policy:
strict-origin-when-cross-origin\r\nX-XSS-Protection: 1; mode=b
lock\r\nX-Content-Type-Options: nosniff\r\nX-Frame-Options:
sameorigin\r\nPermissions-Policy: interest-cohort=()\r\nKeep-Alive: timeout=5,
max=100
"
kf5.kio.kio_http: parsed expire date from 'expires' header: "Sun, 15 Aug 2021
07:07:46 GMT"
kf5.kio.kio_http: Cache needs validation
kf5.kio.kio_http:
kf5.kio.kio_http: Previous Response: 0
kf5.kio.kio_http: Current Response: 200
kf5.kio.kio_http: "102499" bytes left.
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499 Chunked: false
BytesLeft: 98403
kf5.kio.kio_http: Determining mime-type from content...
kf5.kio.kio_http: Mimetype buffer size: 4096
kf5.kio.kio_http: Using default mimetype: "text/html"
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499 Chunked: false
BytesLeft: 94307
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499 Chunked: false
BytesLeft: 90211
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499 Chunked: false
BytesLeft: 86115
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499 Chunked: false
BytesLeft: 82019
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499 Chunked: false
BytesLeft: 77923
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499 Chunked: false
BytesLeft: 73827
kf5.kio.kio_http: bytesReceived: 4096 m_iSize: 102499
[Bug 1939935] Re: scan/dvbscan fail using both dtv-scan-tables DVBv5 and DVBv3 channel format files
** Description changed: The packaging nor man-pages do not make clear that these tools only support a very old "legacy" tuner format (DVBv3) and as such fail to work using various instruction sources. The tuner files are installed via the dependency on 'dtv-scan-tables' and are predominantly DVBv5 format. For example, scan will fail with: $ scan /usr/share/dvb/dvb-t/uk-X - scanning /usr/share/dvb/dvb-t/uk-X - using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' - ERROR: cannot parse'[C49 BBC A] - ' - ERROR: cannot parse'DELIVERY_SYSTEM = DVBT - ' - ERROR: cannot parse'FREQUENCY = 69800 + scanning /usr/share/dvb/dvb-t/uk-X + using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' + ERROR: cannot parse'[C49 BBC A] + ' + ERROR: cannot parse'DELIVERY_SYSTEM = DVBT + ' + ERROR: cannot parse'FREQUENCY = 69800 ' What is not made clear is that 'dtv-scan-tables' also installs the 'legacy' tables under /usr/share/dvb/dvb-legacy/ Where the equivalent for the command above would be: $ scan /usr/share/dvb/dvb-legacy/dvb-t/uk-X However, the tools still fail to parse these files: - scanning /usr/share/dvb/dvb-legacy/dvb-t/uk-Waltham - using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' - initial transponder 69800 0 2 9 3 1 0 0 - initial transponder 737833000 0 2 9 3 1 0 0 - ERROR: invalid enum value '5540' - ERROR: invalid enum value '' - ERROR: invalid enum value '0' + scanning /usr/share/dvb/dvb-legacy/dvb-t/uk- + using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' + initial transponder 69800 0 2 9 3 1 0 0 + initial transponder 737833000 0 2 9 3 1 0 0 + ERROR: invalid enum value '5540' + ERROR: invalid enum value '' + ERROR: invalid enum value '0' ERROR: invalid enum value '8MHz' ERROR: invalid enum value '2/3' ERROR: invalid enum value 'NONE' ERROR: invalid enum value 'QAM2' initial transponder 2 3 9 9 6 2 4 4 initial transponder 53800 0 3 9 3 1 0 0 initial transponder 60200 0 3 9 3 1 0 0 initial transponder 76200 0 3 9 3 1 0 0 ERROR: invalid enum value '7700' ERROR: invalid enum value '' ERROR: invalid enum value '0' ERROR: invalid enum value '8MHz' ERROR: invalid enum value '2/3' ERROR: invalid enum value 'NONE' ERROR: invalid enum value 'QAM2' initial transponder 2 3 9 9 6 2 4 4 ERROR: invalid enum value '7540' ERROR: invalid enum value '' ERROR: invalid enum value '0' ERROR: invalid enum value '8MHz' ERROR: invalid enum value '2/3' ERROR: invalid enum value 'NONE' ERROR: invalid enum value 'QAM2' initial transponder 2 3 9 9 6 2 4 4 initial transponder 51400 0 3 9 0 1 0 0 >>> tune to: 69800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: >>> tuning failed!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939935 Title: scan/dvbscan fail using both dtv-scan-tables DVBv5 and DVBv3 channel format files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linuxtv-dvb-apps/+bug/1939935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939935] [NEW] scan/dvbscan fail using both dtv-scan-tables DVBv5 and DVBv3 channel format files
Public bug reported: The packaging nor man-pages do not make clear that these tools only support a very old "legacy" tuner format (DVBv3) and as such fail to work using various instruction sources. The tuner files are installed via the dependency on 'dtv-scan-tables' and are predominantly DVBv5 format. For example, scan will fail with: $ scan /usr/share/dvb/dvb-t/uk-X scanning /usr/share/dvb/dvb-t/uk-X using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' ERROR: cannot parse'[C49 BBC A] ' ERROR: cannot parse'DELIVERY_SYSTEM = DVBT ' ERROR: cannot parse'FREQUENCY = 69800 ' What is not made clear is that 'dtv-scan-tables' also installs the 'legacy' tables under /usr/share/dvb/dvb-legacy/ Where the equivalent for the command above would be: $ scan /usr/share/dvb/dvb-legacy/dvb-t/uk-X However, the tools still fail to parse these files: scanning /usr/share/dvb/dvb-legacy/dvb-t/uk-Waltham using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 69800 0 2 9 3 1 0 0 initial transponder 737833000 0 2 9 3 1 0 0 ERROR: invalid enum value '5540' ERROR: invalid enum value '' ERROR: invalid enum value '0' ERROR: invalid enum value '8MHz' ERROR: invalid enum value '2/3' ERROR: invalid enum value 'NONE' ERROR: invalid enum value 'QAM2' initial transponder 2 3 9 9 6 2 4 4 initial transponder 53800 0 3 9 3 1 0 0 initial transponder 60200 0 3 9 3 1 0 0 initial transponder 76200 0 3 9 3 1 0 0 ERROR: invalid enum value '7700' ERROR: invalid enum value '' ERROR: invalid enum value '0' ERROR: invalid enum value '8MHz' ERROR: invalid enum value '2/3' ERROR: invalid enum value 'NONE' ERROR: invalid enum value 'QAM2' initial transponder 2 3 9 9 6 2 4 4 ERROR: invalid enum value '7540' ERROR: invalid enum value '' ERROR: invalid enum value '0' ERROR: invalid enum value '8MHz' ERROR: invalid enum value '2/3' ERROR: invalid enum value 'NONE' ERROR: invalid enum value 'QAM2' initial transponder 2 3 9 9 6 2 4 4 initial transponder 51400 0 3 9 0 1 0 0 >>> tune to: >>> 69800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: >>> tuning failed!!! ** Affects: linuxtv-dvb-apps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939935 Title: scan/dvbscan fail using both dtv-scan-tables DVBv5 and DVBv3 channel format files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linuxtv-dvb-apps/+bug/1939935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492621] Re: Cannot start VMs without routable IPv4 address
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Sourceware.org Bugzilla #12398 https://sourceware.org/bugzilla/show_bug.cgi?id=12398 ** Also affects: glibc via https://sourceware.org/bugzilla/show_bug.cgi?id=12398 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492621 Title: Cannot start VMs without routable IPv4 address To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1492621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937883] [NEW] ssh-agent Shielded Private Key Extraction
Public bug reported: Possible vulnerability with an active proof of concept that may well become a CVE. ssh-agent Shielded Private Key Extraction https://security.humanativaspa.it/openssh-ssh-agent-shielded-private- key-extraction-x86_64-linux/ ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937883 Title: ssh-agent Shielded Private Key Extraction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1937883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context
@Cyan - is that on 21.10 (Impish) because your report has changed the status for the 20.04 (Focal) report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906479 Title: qemu:handle_cpu_signal received signal outside vCPU context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931024] [NEW] BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]
Public bug reported: I've been working with a user for the last 2 days on a failure to even start the kernel when installing 20.04 or 21.04 (possibly other releases) with a UEFI boot. System is Dell XPS 9550 amd64 with Ubuntu Budgie. The symptom is that after GRUB successfully loads the kernel into RAM, it fails to return from loading the initrd into RAM. This was proved by adding guard 'echo' and 'sleep' around each stage n grub.cfg. After much investigation since this seemed initially related to a LUKS install I noticed the initrd.img files generated with MODULES=most are 105MB. Most of that is unneeded firmware and other files so I changed to MODULES=dep. Resulting initrd.img's are around 55MB. System then boots correctly. This looks like a possible issue with the UEFI on these XPS models but as initrd.img sizes get ridiculously large this is likely to hit more systems and users. For several years I carry optimisation patches to initramfs-tools that don't add most firmwares except those specifically required (certainly not adding AMD GPU firmware when system has only Intel or Nvidia GPUs - and visa versa) My initrd.img's are a hybrid of MODULES=dep and result in less than 20MB. My recommendation is to add optimisations to initramfs-tools or adopt MODULES=dep. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931024 Title: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
We've installed 5.12.0 on Callum's PC and the latest qemu-user-static (5.2+dfsg-9ubuntu3) from 21.04 and so far it also appears to be working. We're not sure what has been happening but we'll chalk this one down to user-error for now unless it re-occurs! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
Before I forget and in case others find it useful I wrote a simple Python tool to check binfmt magic bytes registered with the kernel with particular files. It can be found here: https://iam.tj/projects/misc/binfmt-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
Testing by trying to execute /sbin/ldconfig within the aarch64 Debian bullseye chroot on 20.04 amd64 host for all installed kernels is working, including 5.12.0, the version booted to by default ! That is: 5.4.0-73-lowlatency 5.8.0-41-lowlatency 5.10.2 5.11.0+ 5.12.0-elloe+ This is extremely difficult to understand since I only got involved in reproducing and testing this on my PC when my colleague hit this issue (recall his PC is on v5.10.0). Now, using qemu-debootstrap to build a new Debian bullseye also works (remembering to set ownership on the directory to root first!). $ uname -a Linux elloe000 5.12.0-elloe+ #31 SMP PREEMPT Sat May 1 10:46:45 BST 2021 x86_64 x86_64 x86_64 GNU/Linux $ sudo mkdir bullseye2-arm64 $ sudo qemu-debootstrap --arch=arm64 bullseye bullseye2-arm64 http://ftp.debian.o rg/debian I: Running command: debootstrap --arch arm64 --foreign bullseye bullseye2-arm64 http://ftp.debian.org/debian I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id 0146DC6D4A0B2914BDED34DB648ACFD622F3D138) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://ftp.debian.org/debian... ... I: Running command: chroot bullseye2-arm64 /debootstrap/debootstrap --second-stage I: Installing core packages... ... I: Unpacking the base system... ... I: Configuring libc-bin... I: Base system installed successfully. $ sudo chroot bullseye2-arm64/ /sbin/ldconfig -v /sbin/ldconfig: Can't stat /usr/local/lib/aarch64-linux-gnu: No such file or directory /sbin/ldconfig: Path `/usr/lib/aarch64-linux-gnu' given more than once /sbin/ldconfig: Path `/lib/aarch64-linux-gnu' given more than once /sbin/ldconfig: Path `/usr/lib/aarch64-linux-gnu' given more than once /sbin/ldconfig: Path `/usr/lib' given more than once /lib/aarch64-linux-gnu: libSegFault.so -> libSegFault.so ... /sbin/ldconfig: /lib/aarch64-linux-gnu/ld-2.31.so is the dynamic linker, ignoring ld-linux-aarch64.so.1 -> ld-2.31.so ... libgcrypt.so.20 -> libgcrypt.so.20.2.8 /usr/local/lib: /lib: Seemingly now working - so now I am extremely confused :s I'll retest on my colleagues PC tomorrow ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
All tests using chroot's on my host are with kernel v5.12.0 with the ubuntu kernel .config as base + 'make olddefconfig'. I'll try the standard Ubuntu 20.04 kernel, and HWE, just in case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
I stepped back to the chroot and tried qemu-aarch64-static from 21.04's qemu-user-static (5.2+dfsg-9ubuntu2) but *debootstrap* fails in the same way as previously reported. HOWEVER, this works: $ sudo chroot bullseye-arm64 /usr/bin/qemu-aarch64-static /sbin/ldconfig -v /sbin/ldconfig: Can't stat /usr/local/lib/aarch64-linux-gnu: No such file or directory /sbin/ldconfig: Path `/usr/lib/aarch64-linux-gnu' given more than once /sbin/ldconfig: Can't stat /usr/local/lib: No such file or directory /sbin/ldconfig: Path `/lib/aarch64-linux-gnu' given more than once /sbin/ldconfig: Path `/usr/lib/aarch64-linux-gnu' given more than once /sbin/ldconfig: Path `/usr/lib' given more than once /lib/aarch64-linux-gnu: libSegFault.so -> libSegFault.so libpam_misc.so.0 -> libpam_misc.so.0.82.1 libpcprofile.so -> libpcprofile.so libext2fs.so.2 -> libext2fs.so.2.4 libattr.so.1 -> libattr.so.1.1.2448 libssl.so.1.1 -> libssl.so.1.1 libnsl.so.2 -> libnsl.so.2.0.1 libc.so.6 -> libc-2.31.so libgcc_s.so.1 -> libgcc_s.so.1 libudev.so.1 -> libudev.so.1.7.0 libz.so.1 -> libz.so.1.2.11 libdb-5.3.so -> libdb-5.3.so libtic.so.6 -> libtic.so.6.2 libxxhash.so.0 -> libxxhash.so.0.8.0 libnss_files.so.2 -> libnss_files-2.31.so libnsl.so.1 -> libnsl-2.31.so libcrypt.so.1 -> libcrypt.so.1.1.0 libss.so.2 -> libss.so.2.0 libp11-kit.so.0 -> libp11-kit.so.0.3.0 libgpg-error.so.0 -> libgpg-error.so.0.29.0 libuuid.so.1 -> libuuid.so.1.3.0 libgmp.so.10 -> libgmp.so.10.4.1 libnettle.so.8 -> libnettle.so.8.3 libhogweed.so.6 -> libhogweed.so.6.3 libpcreposix.so.3 -> libpcreposix.so.3.13.3 libffi.so.7 -> libffi.so.7.1.0 libpcre2-8.so.0 -> libpcre2-8.so.0.10.1 libapt-pkg.so.6.0 -> libapt-pkg.so.6.0.0 libnss_dns.so.2 -> libnss_dns-2.31.so libnss_hesiod.so.2 -> libnss_hesiod-2.31.so libblkid.so.1 -> libblkid.so.1.1.0 libpamc.so.0 -> libpamc.so.0.82.1 libzstd.so.1 -> libzstd.so.1.4.8 libkeyutils.so.1 -> libkeyutils.so.1.9 libmount.so.1 -> libmount.so.1.1.0 libselinux.so.1 -> libselinux.so.1 libtasn1.so.6 -> libtasn1.so.6.6.0 libcap-ng.so.0 -> libcap-ng.so.0.0.0 libsemanage.so.1 -> libsemanage.so.1 libmemusage.so -> libmemusage.so libgssapi_krb5.so.2 -> libgssapi_krb5.so.2.2 libanl.so.1 -> libanl-2.31.so libdl.so.2 -> libdl-2.31.so libpthread.so.0 -> libpthread-2.31.so libe2p.so.2 -> libe2p.so.2.3 libpam.so.0 -> libpam.so.0.85.1 libresolv.so.2 -> libresolv-2.31.so libcrypto.so.1.1 -> libcrypto.so.1.1 libthread_db.so.1 -> libthread_db-1.0.so libnss_compat.so.2 -> libnss_compat-2.31.so libdebconfclient.so.0 -> libdebconfclient.so.0.0.0 /sbin/ldconfig: /lib/aarch64-linux-gnu/ld-2.31.so is the dynamic linker, ignoring ld-linux-aarch64.so.1 -> ld-2.31.so liblzma.so.5 -> liblzma.so.5.2.5 libkrb5support.so.0 -> libkrb5support.so.0.1 libacl.so.1 -> libacl.so.1.1.2253 libkrb5.so.3 -> libkrb5.so.3.3 libaudit.so.1 -> libaudit.so.1.0.0 libsepol.so.1 -> libsepol.so.1 libbz2.so.1.0 -> libbz2.so.1.0.4 libtinfo.so.6 -> libtinfo.so.6.2 libstdc++.so.6 -> libstdc++.so.6.0.28 libk5crypto.so.3 -> libk5crypto.so.3.1 libsystemd.so.0 -> libsystemd.so.0.30.0 libcom_err.so.2 -> libcom_err.so.2.1 libpcre.so.3 -> libpcre.so.3.13.3 libsmartcols.so.1 -> libsmartcols.so.1.1.0 libtirpc.so.3 -> libtirpc.so.3.0.0 libunistring.so.2 -> libunistring.so.2.1.0 libapt-private.so.0.0 -> libapt-private.so.0.0.0 libseccomp.so.2 -> libseccomp.so.2.5.1 liblz4.so.1 -> liblz4.so.1.9.3 libm.so.6 -> libm-2.31.so libgnutls.so.30 -> libgnutls.so.30.29.1 libutil.so.1 -> libutil-2.31.so libidn2.so.0 -> libidn2.so.0.3.7 librt.so.1 -> librt-2.31.so libBrokenLocale.so.1 -> libBrokenLocale-2.31.so libgcrypt.so.20 -> libgcrypt.so.20.2.8 /lib: I'm not entirely clear on how to further debug this since executing under gdb in the correct context -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
Ok, that was an easy solve: $ sudo chown 0:0 bullseye-arm64 And with that installation runs to completion. This is inside a 21.04 amd64 desktop KVM virtual machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
In a 21.04 amd64 desktop virtual machine it fails but with a different error apparently related to bullseye systemd package, not sure if I can untangle this mix of problems: $ sudo apt install qemu-user-static debootstrap $ sudo qemu-debootstrap --arch=arm64 bullseye bullseye-arm64/ http://ftp.debian.org/debian W: qemu-debootstrap is deprecated. Please use regular debootstrap directly I: Running command: debootstrap --arch=arm64 bullseye bullseye-arm64/ http://ftp.debian.org/debian ... I: Configuring libc-bin... I: Unpacking the base system... W: Failure trying to run: chroot "/home/ubuntu/chroot/bullseye-arm64" dpkg --force-overwrite --force-confold --skip-same-version --install /var/cache/apt/archives/libapparmor1_2.13.6-10_arm64.deb /var/cache/apt/archives/libargon2-1_0~20171227-0.2_arm64.deb /var/cache/apt/archives/libcryptsetup12_2%3a2.3.5-1_arm64.deb /var/cache/apt/archives/libip4tc2_1.8.7-1_arm64.deb /var/cache/apt/archives/libjson-c5_0.15-2_arm64.deb /var/cache/apt/archives/libkmod2_28-1_arm64.deb /var/cache/apt/archives/libcap2_1%3a2.44-1_arm64.deb /var/cache/apt/archives/dmsetup_2%3a1.02.175-2.1_arm64.deb /var/cache/apt/archives/libdevmapper1.02.1_2%3a1.02.175-2.1_arm64.deb /var/cache/apt/archives/systemd_247.3-5_arm64.deb /var/cache/apt/archives/systemd-timesyncd_247.3-5_arm64.deb W: See /home/ubuntu/chroot/bullseye-arm64/debootstrap/debootstrap.log for details (possibly the package systemd is at fault) --- log --- ... Setting up systemd (247.3-5) ... Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service -> /lib/systemd/system/getty@.service. Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target -> /lib/systemd/system/remote-fs.target. Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service -> /lib/systemd/system/systemd-pstore.service. Initializing machine ID from random generator. Detected unsafe path transition / -> /var during canonicalization of /var/log/journal. Detected unsafe path transition / -> /var during canonicalization of /var/log/journal. Detected unsafe path transition / -> /var during canonicalization of /var/log/journal. dpkg: error processing package systemd (--install): installed systemd package post-installation script subprocess returned error exit status 73 Processing triggers for libc-bin (2.31-11) ... Errors were encountered while processing: systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
First simple test with 21.04 amd64 LXD host with kernel 5.12.0 results in the same issue. I'll need to repeat in a virtual machine next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
Another data point. We tried installing qemu-aarch64-static from Debian's qemu-user-static amd64 packages from testing (1:5.2+dfsg-10) (bullseye) and experimental (6.0+dfsg-1~exp0) into the chroot. Both result in the same error. On my PC I have kernel 5.12.0-elloe+ and Callum has 5.10.0. We both see the same seg-fault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
Looking closer we've just noticed the bullseye's ldconfig claims to be dynamically linked but buster's is statically linked. This reminds of bug #1908331 we solved earlier this year in qemu itself due to the build flag -static-pie $ file bullseye-arm64/sbin/ldconfig bullseye-arm64/sbin/ldconfig: ELF 64-bit LSB shared object, ARM aarch64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=6cca288a8f9e39114be7ce6d9761f252990f5214, for GNU/Linux 3.7.0, stripped $ file buster-arm64/sbin/ldconfig buster-arm64/sbin/ldconfig: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.7.0, BuildID[sha1]=078feba3f88616e37d2a77a1997d9de2343df80b, stripped -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
Will do - I run builds of the mainline kernel tracking upstream so that part isn't a problem. We are operating on bare-metal on the host. I suspect it is glibc and/or compilation options since trying to manually call, for example, /bin/dash or other executables hits the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] [NEW] Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
Public bug reported: On 20.04 amd64 trying to build a Debian bullseye chroot using debootstrap we hit a segfault apparently calling /sbin/ldconfig ,,, but don't have the same issue building a Debian buster chroot. Can't make out if this is problems with our older qemu or something in the bullseye compilation options or a bit of both. Myself and a colleague have both hit this. $ sudo qemu-debootstrap --arch=arm64 bullseye bullseye-arm64 http://ftp.debian.org/debian I: Running command: debootstrap --arch arm64 --foreign bullseye bullseye-arm64 http://ftp.debian.org/debian I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id 0146DC6D4A0B2914BDED34DB648ACFD622F3D138) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://ftp.debian.org/debian... ... I: Extracting zlib1g... I: Running command: chroot bullseye-arm64 /debootstrap/debootstrap --second-stage W: Failure trying to run: /sbin/ldconfig W: See //debootstrap/debootstrap.log for details $ tail bullseye-arm64/debootstrap/debootstrap.log 2021-05-11 11:42:17 URL:http://ftp.debian.org/debian/pool/main/u/util-linux/mount_2.36.1-7_arm64.deb [181404/181404] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/mount_2.36.1-7_arm64.deb" [1] 2021-05-11 11:42:20 URL:http://ftp.debian.org/debian/pool/main/u/util-linux/util-linux_2.36.1-7_arm64.deb [1096872/1096872] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/util-linux_2.36.1-7_arm64.deb" [1] 2021-05-11 11:42:21 URL:http://ftp.debian.org/debian/pool/main/v/vim/vim-common_8.2.2434-3_all.deb [226160/226160] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/vim-common_2%3a8.2.2434-3_all.deb" [1] 2021-05-11 11:42:22 URL:http://ftp.debian.org/debian/pool/main/v/vim/vim-tiny_8.2.2434-3_arm64.deb [692844/692844] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/vim-tiny_2%3a8.2.2434-3_arm64.deb" [1] 2021-05-11 11:42:23 URL:http://ftp.debian.org/debian/pool/main/v/vim/xxd_8.2.2434-3_arm64.deb [191516/191516] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/xxd_2%3a8.2.2434-3_arm64.deb" [1] 2021-05-11 11:42:23 URL:http://ftp.debian.org/debian/pool/main/x/xxhash/libxxhash0_0.8.0-2_arm64.deb [18544/18544] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/libxxhash0_0.8.0-2_arm64.deb" [1] 2021-05-11 11:42:24 URL:http://ftp.debian.org/debian/pool/main/x/xz-utils/liblzma5_5.2.5-2_arm64.deb [164528/164528] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/liblzma5_5.2.5-2_arm64.deb" [1] 2021-05-11 11:42:24 URL:http://ftp.debian.org/debian/pool/main/z/zlib/zlib1g_1.2.11.dfsg-2_arm64.deb [87944/87944] -> "/media/tj/SLBS/EV/IT/chroot/bullseye-arm64//var/cache/apt/archives/partial/zlib1g_1%3a1.2.11.dfsg-2_arm64.deb" [1] qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) $ file bullseye-arm64/bin/qemu-aarch64-static bullseye-arm64/bin/qemu-aarch64-static: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=9bf7d733705830e1a1c179ed45bddce8f5190797, for GNU/Linux 3.2.0, stripped $ apt list qemu-user-static Listing... Done qemu-user-static/focal-updates 1:4.2-3ubuntu6.16 amd64 [upgradable from: 1:4.2-3ubuntu6.15] ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Description changed: On 20.04 amd64 trying to build a Debian bullseye chroot using debootstrap we hit a segfault apparently calling /sbin/ldconfig ,,, but don't have the same issue building a Debian buster chroot. Can't make out if this is problems with our older qemu or something in the bullseye compilation options or a bit of both. + Myself and a colleague have both hit this. $ sudo qemu-debootstrap --arch=arm64 bullseye bullseye-arm64 http://ftp.debian.org/debian I: Running command: debootstrap --arch arm64 --foreign bullseye bullseye-arm64 http://ftp.debian.org/debian - I: Retrieving InRelease - I: Checking Release signature - I: Valid Release signature (key id 0146DC6D4A0B2914BDED34DB648ACFD622F3D138) - I: Retrieving Packages - I: Validating Packages
[Bug 1923352] Re: speedtest-cli crashed with ValueError in get_config(): invalid literal for int() with base 10: ''
** Description changed:
+ SRU justification (created by Tj)
+
+ [Impact]
+
+ Without this patch `speedtest-cli` is unable to download the list of
+ servers it needs to fetch each time it is invoked and causes a Python
+ exception and terminates, rendering the tool unusable.
+
+ Applying the upstream fix (commit cadc68b5aef20) and backporting it
+ enables the tool to function as intended.
+
+ The fix handles the case where `ignoreids` is empty or contains empty
+ ids.
+
+ [Test Plan]
+
+ Reproduce:
+
+ $ speedtest-cli
+ Retrieving speedtest.net configuration...
+ Traceback (most recent call last):
+ File "/usr/bin/speedtest-cli", line 11, in
+ load_entry_point('speedtest-cli==2.1.2', 'console_scripts',
'speedtest-cli')()
+ File "/usr/lib/python3/dist-packages/speedtest.py", line 1986, in main
+ shell()
+ File "/usr/lib/python3/dist-packages/speedtest.py", line 1872, in shell
+ speedtest = Speedtest(
+ File "/usr/lib/python3/dist-packages/speedtest.py", line 1091, in __init__
+ self.get_config()
+ File "/usr/lib/python3/dist-packages/speedtest.py", line 1173, in get_config
+ ignore_servers = list(
+ ValueError: invalid literal for int() with base 10: ''
+
+ After applying the fix:
+
+ $ speedtest-cli
+ Retrieving speedtest.net configuration...
+ Testing from Starlink (176.116.125.19)...
+ Retrieving speedtest.net server list...
+ Selecting best server based on ping...
+ Hosted by toob Ltd (London) [2.56 km]: 42.699 ms
+ Testing download
speed
+ Download: 222.97 Mbit/s
+ Testing upload
speed
+ Upload: 41.19 Mbit/s
+
+ [Where problems could occur]
+
+ Unlikely this can cause any unwanted reaction.
+
+
+
I just tried to run speedtest-cli and it crashed.
ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: speedtest-cli 2.1.2-2
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Sun Apr 11 05:52:59 2021
ExecutablePath: /usr/bin/speedtest-cli
InstallationDate: Installed on 2018-08-10 (974 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
InterpreterPath: /usr/bin/python3.9
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/speedtest-cli
Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.2-2
PythonArgs: ['/usr/bin/speedtest-cli']
PythonDetails: N/A
SourcePackage: speedtest-cli
Title: speedtest-cli crashed with ValueError in get_config(): invalid literal
for int() with base 10: ''
UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sbuild
sudo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923352
Title:
speedtest-cli crashed with ValueError in get_config(): invalid literal
for int() with base 10: ''
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1923352/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914555] Re: cal should report today
No, this is incorrect. called as 'cal' the intention is to be bit compatible with the original 'cal'. 'ncal' added the highlight option and as the man-page shows '-h' is only valid when it is called as 'ncal'. Secondly highlighting when called as 'cal' was a (Debian) bug #9848389 which is referenced in the changelog for bsdmainutils (12.1.6): * Cal should not highlight the current day. (Closes: #904839) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904839 ** Bug watch added: Debian Bug tracker #904839 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904839 ** Changed in: bsdmainutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914555 Title: cal should report today To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/1914555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923628] Re: speedtest-cli crashes (known bug)
** Patch added: "Upstream fix applied" https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1923628/+attachment/5493343/+files/speedtest-cli_2.1.2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923628 Title: speedtest-cli crashes (known bug) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1923628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916767] Re: firejail version in Ubuntu 20.04 LTS is vulnarable to CVE-2021-26910
** Patch added: "Debdiff provided by Reiner" https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1916767/+attachment/5488486/+files/firejail-cve.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916767 Title: firejail version in Ubuntu 20.04 LTS is vulnarable to CVE-2021-26910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1916767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921355] Re: cgroups related kernel panics
CPU: 0 PID: 1 Comm: systemd Tainted: G OE 5.4.0-66-generic #74~18.04.2-Ubuntu The stand-out info in the log fragments is the kernel is tainted with GPL (G) unsigned (E) out-of-tree (O) modules: openvswitch(OE) mlx5_core(OE) mlxfw(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) mlx_compat(OE) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921355 Title: cgroups related kernel panics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1921355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923202] [NEW] Fails to build directory, tar or btrfs subvolumes
Public bug reported:
All attempts to build non disk-image targets 'directory' 'tar'
'subvolume' (lightweight containers) fail with the same error. The only
fix appears to be to upgrade to latest mainline code (mkosi version 9).
Example:
root@elloe000:~# mkosi -t directory
DISTRIBUTION:
Distribution: ubuntu
Release: focal
Mirror: http://archive.ubuntu.com/ubuntu
OUTPUT:
Output Format: directory
Output: /root/image
Output Checksum: n/a
Output Signature: n/a
Output Bmap: n/a
Output nspawn Settings: n/a
Incremental: no
Read-only: no
FS Compression: no
XZ Compression: no
Encryption: no
Verity: no
PACKAGES:
Packages: none
Package Cache: none
Extra Trees: none
Skeleton Trees: none
Build Script: none
Build Sources: /root
Source File Transfer: none
Build Directory: none
Build Packages: none
Postinstall Script: none
Finalize Script: none
Scripts with network: no
nspawn Settings: none
HOST CONFIGURATION:
Extra search paths: none
‣ Detaching namespace...
‣ Detaching namespace complete.
‣ Setting up package cache...
‣ Setting up package cache /root/.mkosi-w5vbxui5 complete.
‣ Setting up temporary workspace.
‣ Temporary workspace in /root/.mkosi-4ayq5hqy is now set up.
‣ Mounting image...
Traceback (most recent call last):
File "/usr/bin/mkosi", line 4539, in
main()
File "/usr/bin/mkosi", line 4535, in main
run_verb(args)
File "/usr/bin/mkosi", line 4507, in run_verb
build_stuff(args)
File "/usr/bin/mkosi", line 4333, in build_stuff
raw, tar, root_hash = build_image(args, workspace,
do_run_build_script=False, cleanup=True)
File "/usr/bin/mkosi", line 4147, in build_image
with mount_image(args, workspace.name, loopdev, encrypted_root,
encrypted_home, encrypted_srv):
File "/usr/lib/python3.8/contextlib.py", line 113, in __enter__
return next(self.gen)
File "/usr/bin/mkosi", line 961, in mount_image
if args.xbootldr_partno is not None:
AttributeError: 'CommandLineArguments' object has no attribute 'xbootldr_partno'
Traceback (most recent call last):
File "/usr/lib/python3.8/weakref.py", line 642, in _exitfunc
f()
File "/usr/lib/python3.8/weakref.py", line 566, in __call__
return info.func(*info.args, **(info.kwargs or {}))
File "/usr/lib/python3.8/tempfile.py", line 957, in _cleanup
cls._rmtree(name)
File "/usr/lib/python3.8/tempfile.py", line 953, in _rmtree
_rmtree(name, onerror=onerror)
File "/usr/lib/python3.8/shutil.py", line 715, in rmtree
_rmtree_safe_fd(fd, path, onerror)
File "/usr/lib/python3.8/shutil.py", line 656, in _rmtree_safe_fd
onerror(os.rmdir, fullname, sys.exc_info())
File "/usr/lib/python3.8/shutil.py", line 654, in _rmtree_safe_fd
os.rmdir(entry.name, dir_fd=topfd)
OSError: [Errno 16] Device or resource busy: 'root'
** Affects: mkosi (Ubuntu)
Importance: Undecided
Status: Confirmed
** Description changed:
- All attempts to build non disk-image targets fail with the same error.
- The only fix appears to be to upgrade to latest mainline code (mkosi
- version 9). Example:
+ All attempts to build non disk-image targets (lightweight containers)
+ fail with the same error. The only fix appears to be to upgrade to
+ latest mainline code (mkosi version 9). Example:
- root@elloe000:~# mkosi -t directory
- DISTRIBUTION:
- Distribution: ubuntu
-Release: focal
- Mirror: http://archive.ubuntu.com/ubuntu
-
- OUTPUT:
- Output Format: directory
- Output: /root/image
-Output Checksum: n/a
- Output Signature: n/a
-Output Bmap: n/a
[Bug 1923145] Re: Actually support Ubuntu
** Description changed: version 5-1 does not support Ubuntu correctly in that it tries to use the version number rather than version codename in arguments to debootstrap. + + $ sudo mkosi + ... + Traceback (most recent call last): + File "/usr/bin/mkosi", line 4539, in + main() + File "/usr/bin/mkosi", line 4535, in main + run_verb(args) + File "/usr/bin/mkosi", line 4507, in run_verb + build_stuff(args) + File "/usr/bin/mkosi", line 4333, in build_stuff + raw, tar, root_hash = build_image(args, workspace, do_run_build_script=False, cleanup=True) + File "/usr/bin/mkosi", line 4153, in build_image + install_distribution(args, workspace.name, + File "/usr/bin/mkosi", line 1987, in install_distribution + install[args.distribution](args, workspace, do_run_build_script) + File "/usr/lib/python3.8/contextlib.py", line 75, in inner + return func(*args, **kwds) + File "/usr/bin/mkosi", line 1717, in install_ubuntu + install_debian_or_ubuntu(args, workspace, do_run_build_script=do_run_build_script, mirror=args.mirror) + File "/usr/bin/mkosi", line 1633, in install_debian_or_ubuntu + run(cmdline, check=True) + File "/usr/bin/mkosi", line 69, in run + return subprocess.run(cmdline, **kwargs) + File "/usr/lib/python3.8/subprocess.py", line 512, in run + raise CalledProcessError(retcode, process.args, + subprocess.CalledProcessError: Command '['debootstrap', '--verbose', '--variant=minbase', '--include=systemd-sysv', '--exclude=sys + v-rc,initscripts,startpar,lsb-base,insserv', '--components=main', '--merged-usr', '"20.04"', '/var/tmp/mkosi-akzr5g4y/root', 'http + ://archive.ubuntu.com/ubuntu']' returned non-zero exit status 1. + + + Notice the "20.04" argument passed to debootstrap, which should be "focal". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923145 Title: Actually support Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mkosi/+bug/1923145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923145] Re: Actually support Ubuntu
This applies for 21.04, 21.10 and 20.04 ** Patch added: "Debdiff from 5-1" https://bugs.launchpad.net/ubuntu/+source/mkosi/+bug/1923145/+attachment/5485893/+files/mkosi_5-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923145 Title: Actually support Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mkosi/+bug/1923145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923145] [NEW] Actually support Ubuntu
Public bug reported: version 5-1 does not support Ubuntu correctly in that it tries to use the version number rather than version codename in arguments to debootstrap. ** Affects: mkosi (Ubuntu) Importance: Undecided Status: In Progress ** Changed in: mkosi (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923145 Title: Actually support Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mkosi/+bug/1923145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Had my techie test the SRU for 20.04 on the affected E495 and can confirm this works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1873895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922510] [NEW] streamtuner2 frozen [lubuntu 21.04 daily]
Public bug reported: Froze twice on me. 1) Started up OK, selected preferences fine, then froze when I chose which streaming service and category to listen to. 2) Started up OK, chose one streaming service and station (played fine), then chose another music category and froze (had to kill -9 it again). I appear to be able to freeze it reliably when I choose a new "Category" of music. Thanks ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: streamtuner2 2.2.1+dfsg-2.1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Apr 4 13:57:33 2021 ExecutablePath: /usr/bin/streamtuner2 InstallationDate: Installed on 2021-04-03 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.2-2 PythonDetails: N/A SourcePackage: streamtuner2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: streamtuner2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922510 Title: streamtuner2 frozen [lubuntu 21.04 daily] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/streamtuner2/+bug/1922510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922462] [NEW] Missing Startup Menu Items [Lubuntu 21.04 daily]
Public bug reported: There is no menu item for installed Jupyter-console under "Programming" or under "Accessories". Similarly, installed GNU PSPP only has a menu item under "Other" but not also under "Education". Finally, installed R (statistical software) only has a menu item under "Graphics", but not also under "Education". Thanks ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: jupyter 4.7.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 3 17:58:27 2021 InstallationDate: Installed on 2021-04-03 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) PackageArchitecture: all SourcePackage: jupyter-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jupyter-core (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922462 Title: Missing Startup Menu Items [Lubuntu 21.04 daily] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jupyter-core/+bug/1922462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922444] Re: Octave GUI command line editing display problems in Lubuntu 21.04 daily
** Summary changed: - Octave GUI command line editing display problems in Lubuntu 21.04 alpha + Octave GUI command line editing display problems in Lubuntu 21.04 daily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922444 Title: Octave GUI command line editing display problems in Lubuntu 21.04 daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1922444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922444] [NEW] Octave GUI command line editing display problems in Lubuntu 21.04 alpha
Public bug reported: Command line editing is all messed up: sometimes there is excess space between characters, sometimes characters disappear when editing. It seems like the cursor is often in the wrong place (too much space behind it, especially as a longer command is typed out). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: octave 6.1.1~hg.2021.01.26-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 3 11:11:56 2021 ExecutablePath: /usr/libexec/octave/6.1.1~hg.2021.01.26/exec/x86_64-pc-linux-gnu/octave-gui InstallationDate: Installed on 2021-04-03 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: octave UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: octave (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922444 Title: Octave GUI command line editing display problems in Lubuntu 21.04 alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1922444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918051] Re: CD-Audio Silent tracks when burning more than one copy
** Description changed: $ apt-cache policy k3b k3b: Installed: 19.12.3-0ubuntu1 On Xubuntu 20.04 we've discovered a very strange issue. All but the first copy of a CD-audio burn result in tracks with complete silence. This happens whether we do one burn operation with "Copies" set greater than 1, or if we do several burn operations each with "Copies" set to 1. If we quit and restart k3b the first copy is good. We use K3B to burn CD audio newsletters for blind people. We master in Ardour and produce a red book CD-audio WAVe file (44k1, 2 channel, s16le) and CUE sheet. Until recently we only created a single CD master and then duplicated it - on other equipment so didn't notice this. As the number of required - copies required has reduced as our listeners switch to USB it is now - more efficient to write the few CDs directly on the PC. + on other equipment so didn't notice this. As the number of copies + required has reduced as our listeners switch to USB it is now more + efficient to write the few CDs directly on the PC. We've analysed the resulting CDs and they all contain all the tracks with the expected lengths but those tracks contain silence. We ripped one of these and checked - the waveform is a flat-line at the zero crossing so it's not as if just the amplitude is affected. We do not use k3b's Normalise option. We've done some research and found one similar bug report but in that it is apparently due to UTF encoded characters in the source file paths. In our case we have pure ASCII and no spaces. "burns silent track when unusual characters present in path to file" https://bugs.kde.org/show_bug.cgi?id=424899 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918051 Title: CD-Audio Silent tracks when burning more than one copy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1918051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918051] Re: CD-Audio Silent tracks when burning more than one copy
** Description changed: $ apt-cache policy k3b k3b: - Installed: 19.12.3-0ubuntu1 + Installed: 19.12.3-0ubuntu1 On Xubuntu 20.04 we've discovered a very strange issue. All but the first copy of a CD-audio burn result in tracks with complete silence. This happens whether we do one burn operation with "Copies" set greater than 1, or if we do several burn operations each with "Copies" set to 1. If we quit and restart k3b the first copy is good. We use K3B to burn CD audio newsletters for blind people. We master in Ardour and produce a red book CD-audio WAVe file (44k1, 2 channel, s16le) and CUE sheet. Until recently we only created a single CD master and then duplicated it on other equipment so didn't notice this. As the number of required copies required has reduced as our listeners switch to USB it is now more efficient to write the few CDs directly on the PC. We've analysed the resulting CDs and they all contain all the tracks with the expected lengths but those tracks contain silence. We ripped one of these and checked - the waveform is a flat-line at the zero crossing so it's not as if just the amplitude is affected. We do not use k3b's Normalise option. + + We've done some research and found one similar bug report but in that it + is apparently due to UTF encoded characters in the source file paths. In + our case we have pure ASCII and no spaces. + + "burns silent track when unusual characters present in path to file" + + https://bugs.kde.org/show_bug.cgi?id=424899 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918051 Title: CD-Audio Silent tracks when burning more than one copy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1918051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918051] [NEW] CD-Audio Silent tracks when burning more than one copy
Public bug reported: $ apt-cache policy k3b k3b: Installed: 19.12.3-0ubuntu1 On Xubuntu 20.04 we've discovered a very strange issue. All but the first copy of a CD-audio burn result in tracks with complete silence. This happens whether we do one burn operation with "Copies" set greater than 1, or if we do several burn operations each with "Copies" set to 1. If we quit and restart k3b the first copy is good. We use K3B to burn CD audio newsletters for blind people. We master in Ardour and produce a red book CD-audio WAVe file (44k1, 2 channel, s16le) and CUE sheet. Until recently we only created a single CD master and then duplicated it on other equipment so didn't notice this. As the number of required copies required has reduced as our listeners switch to USB it is now more efficient to write the few CDs directly on the PC. We've analysed the resulting CDs and they all contain all the tracks with the expected lengths but those tracks contain silence. We ripped one of these and checked - the waveform is a flat-line at the zero crossing so it's not as if just the amplitude is affected. We do not use k3b's Normalise option. ** Affects: k3b (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918051 Title: CD-Audio Silent tracks when burning more than one copy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1918051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905800] Re: Apparmor denies pid file creation for dhclient when started by network-manager
** Changed in: isc-dhcp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905800 Title: Apparmor denies pid file creation for dhclient when started by network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1905800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804334] Re: Live/overlayfs apparmor DENIED open "upper/etc/mysql/conf.d" mysql-server-5.7 package post-installation script subprocess returned error exit status 1
** Summary changed: - package mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 + Live/overlayfs apparmor DENIED open "upper/etc/mysql/conf.d" mysql-server-5.7 package post-installation script subprocess returned error exit status 1 ** Description changed: + This occurs when installing on an overlayfs, typically in the installer + Try ... live environment when apparmor denies a read of the mysql + configuration: + + audit: type=1400 audit(1542755429.021:244): apparmor="DENIED" + operation="open" info="Failed name lookup - disconnected path" error=-13 + profile="/usr/sbin/mysqld" name="upper/etc/mysql/conf.d" pid=7525 + comm="mysqld" requested_mask="r" + + this causes + + /usr/share/mysql/mysql-systemd-start + + to fail and return exit code 1 when called during the POSTINST phase of + package configuration. + + + I was installing mysql-server but error came. I have zero knowledge about linux and ubuntu ProblemType: Package DistroRelease: Ubuntu 18.04 Package: mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Tue Nov 20 23:10:29 2018 ErrorMessage: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Logs.var.log.daemon.log: - + MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: - [mysqldump] - quick - quote-names - max_allowed_packet = 16M + [mysqldump] + quick + quote-names + max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: - [mysqld_safe] - syslog + [mysqld_safe] + syslog MySQLVarLibDirListing: ['ib_buffer_pool', 'debian-5.7.flag', 'sys', 'performance_schema', 'mysql', 'auto.cnf', 'ib_logfile0', 'ib_logfile1', 'ibdata1'] ProcCmdline: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: - dpkg 1.19.0.5ubuntu2 - apt 1.6.3 + dpkg 1.19.0.5ubuntu2 + apt 1.6.3 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: mysql-5.7 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804334 Title: Live/overlayfs apparmor DENIED open "upper/etc/mysql/conf.d" mysql- server-5.7 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1804334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915259] [NEW] manual debian/rules build fails
Public bug reported: With the current package in 21.04 dev (4.4-1) manually downloaded via dget an initial build fails due to artifacts (symlinks to system- installed fonts) of the build process. Comparing to the builder logs I see that a 'clean' is required to remove them. I've never hit this with other package's builds and I've done many so wondering if this is a bug with this package. $ dget -x http://archive.ubuntu.com/ubuntu/pool/universe/g/gnucash-docs/gnucash-docs_4.4-1.dsc ... $ cd gnucash-docs-4.4 $ debian/rules build ... configure: WARNING: unrecognized options: --disable-maintainer-mode, --disable-dependency-tracking debian/rules override_dh_auto_build make[1]: Entering directory '/media/ubuntu/SourceCode/gnucash/gnucash-docs-4.4' mkdir -pv fonts/truetype ln -sv /usr/share/fonts/truetype/horai-umefont/ume-tgo4.ttffonts/truetype/ # fonts-horai-umefont ln: failed to create symbolic link 'fonts/truetype/ume-tgo4.ttf': File exists make[1]: *** [debian/rules:31: override_dh_auto_build] Error 1 make[1]: Leaving directory '/media/ubuntu/SourceCode/gnucash/gnucash-docs-4.4' make: *** [debian/rules:13: build] Error 2 ** Affects: gnucash-docs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915259 Title: manual debian/rules build fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash-docs/+bug/1915259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914278] Re: apt autoremove is not removing unused kernels
Erich, looks like that code wasn't reached or if it was the object
(list) "auto_removable" was empty.
Maybe the problem is outside this code. Does apt think those packages
are still installed?
apt list --installed 'linux-image*'
Also, what is the actual content of /boot/ ("ls -latr /boot/") ? I'm wondering
if it could be that the kernels (linux-image-*) packages have been removed but
the (space-eating) initrd,img* files have remained. Each of those can be close
to 50MB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914278
Title:
apt autoremove is not removing unused kernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914278] Re: apt autoremove is not removing unused kernels
I haven't been able to test this since the systems I have here don't
have any kernel images lying around, but wondering if this patch could
help narrow down the cause?
Apply to a (copy) of /usr/bin/unattended-upgrade - possibly put in
/usr/local/bin/ so it is called before the package-installed version
(don't forget to clear the bash hash cache ("hash -r") first)
Then:
sudo /usr/local/bin/unattended-upgrade --verbose --debug
** Patch added: "Kernel pkg debugging"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+attachment/5459187/+files/kernel-pkg-debug.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914278
Title:
apt autoremove is not removing unused kernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914278] Re: apt autoremove is not removing unused kernels
I'm also wondering if these are laptops or desktops, and if laptops, are they mainly on battery whilst not sleeping/charging? I ask since apt- daily-upgrade.service has: ConditionACPower=true and so may be reporting: Condition check resulted in Daily apt upgrade and clean activities being skipped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914278 Title: apt autoremove is not removing unused kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911798] [NEW] 20.04 - You are building kernel with non-retpoline compiler. Please update your compiler
Public bug reported:
On 20.04 amd64 with gcc-{9,10}-arm-linux-gnueabihf packages installed in
order to cross compile for a TI arm beagle-like board kernel I get:
$ echo $OOTB
../builds/arm-beagle
$ echo $CROSS_COMPILE
arm-linux-gnueabihf-
$ make -j7 arch=arm O=$OOTB prepare zImage modules dtbs |& tee /tmp/build.log
make[1]: Entering directory '/media/tj/SourceCode/builds/arm-beagle'
GEN ./Makefile
scripts/kconfig/conf --syncconfig Kconfig
You are building kernel with non-retpoline compiler.
Please update your compiler.
make[1]: *** [arch/x86/Makefile:317: checkbin] Error 1
make[1]: Leaving directory '/media/tj/SourceCode/builds/arm-beagle'
make: *** [Makefile:146: sub-make] Error 2
** Affects: gcc-9-cross (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911798
Title:
20.04 - You are building kernel with non-retpoline compiler. Please
update your compiler
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-9-cross/+bug/1911798/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904907] Re: Bad arg length for Socket::inet_ntoa, length is 16, should be 4 at /usr/share/perl5/HTTP/Daemon.pm line 51
Looking at the Debian changelog looks like both Ubuntu 18.04 and 20.04 needs at least 6.01-2 whereas it has 6.01-1. Ubuntu 20.10 has 6.12-1: libhttp-daemon-perl (6.01-2) unstable; urgency=medium ... [ Fabian Grünbichler ] * switch to IO::Socket::IP to add IPv6 support (Closes: #667738) [ gregor herrmann ] * Add (build) dependency on libio-socket-ip-perl. * Mark package as autopkgtest-able. * Declare compliance with Debian Policy 4.3.0. * Bump debhelper compatibility level to 11. * Add /me to Uploaders. -- gregor herrmann Thu, 28 Feb 2019 17:45:03 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904907 Title: Bad arg length for Socket::inet_ntoa, length is 16, should be 4 at /usr/share/perl5/HTTP/Daemon.pm line 51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhttp-daemon-perl/+bug/1904907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909802] [NEW] Should build ninfod to support IPv6 Node Information requests
Public bug reported: iputils-ping includes ping6 which can send Node Information requests, e.g: ping6 -N name ipv6:addr::ess but there is no system daemon to listen and respond. iputils package contains ninfod which performs that function but it isn't built or packaged. For IPv6 networks Node Information is a valuable service in that it allows nodes to enhance ND/NA by providing their FQDN (Name query) and list of addresses (Addresses query). See: https://tools.ietf.org/html/rfc4620.html#section-6 ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909802 Title: Should build ninfod to support IPv6 Node Information requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1909802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490347] Re: [Regression] 16:04 and later - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes
Another follow-up. Had the same problem with 20.04 amd64. My solution detailed above would not work when using the GUI where the Blueman bluetooth applet was in the notification area. Eventually I found it worked from a real tty console (switched from GUI to tty2 with Ctrl+Alt+F2) and running the bluetoothctl sequence as detailed. ** Summary changed: - [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes + [Regression] 16:04 and later - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490347 Title: [Regression] 16:04 and later - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1490347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context
Hi Christian, sorry I missed your updates on this one. I've only just come back to the issue yesterday and apparently I've hit another issue: bug #1908331 "Regression: qemu-user-static binaries are dynamically linked" That side-tracked me whilst trying to do the git-bisect and I've still not solved that bug - spent the best part of 8 hours on it. I was going to ping you on IRC later today. I've pulled in your backport build and extracted just qemu- aarch64-static. It's currently running and is unpacking so I *think* this has solved the current issue, BUT, it looks to be affected by the bug mentioned above as well: $ file ../qemu-aarch64_v5.0-backport ../qemu-aarch64_v5.0-backport: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=31ee6e0f3235e1d9a6da328cfa6a25c7b4c92487, for GNU/Linux 3.2.0, stripped $ ldd ../qemu-aarch64_v5.0-backport statically linked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906479 Title: qemu:handle_cpu_signal received signal outside vCPU context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908331] Re: Regression: qemu-user-static binaries are dynamically linked
I've posted a question to the qemu-devel mailing list with subject "Are user static builds really dynamically linked ?" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908331 Title: Regression: qemu-user-static binaries are dynamically linked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908331] Re: Regression: qemu-user-static binaries are dynamically linked
To be sure I built upstream v4.2.1 and it reports the expected and required linkage. Build needs some additional tweaking to avoid libssh deprecated functions causing -Werror to trigger: $ sudo apt install liblzma-dev $ ../../qemu/configure --target-list=aarch64-linux-user --static --disable-system --enable-linux-user --extra-cflags='-Wno-deprecated- declarations' $ make -j8 V=1 $ file ./aarch64-linux-user/qemu-aarch64 ./aarch64-linux-user/qemu-aarch64: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=70f5e10ac0eb9b63d7758850e2f18d0a047d4b79, for GNU/Linux 3.2.0, with debug_info, not stripped -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908331 Title: Regression: qemu-user-static binaries are dynamically linked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908331] Re: Regression: qemu-user-static binaries are dynamically linked
** Description changed: On 20.04 (qemu 4.2) the binaries built for qemu-user-static - specifically in the case I've hit /usr/bin/qemu-aarch64-static - are completely static executables. The same binaries from a qemu 5.x build are not. Although they don't link to other shared libraries they are dynamically linked to glibc and therefore require the same version of the glibc shared libraries at runtime. This breaks many uses in foreign architecture chroots; in my case an aarch64 being built with debootstrap: On focal: $ file /usr/bin/qemu-aarch64-static /usr/bin/qemu-aarch64-static: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=abad039a2cfc5bc87215554230a572b085fbc37a, for GNU/Linux 3.2.0, with debug_info, not stripped $ dpkg -S /usr/bin/qemu-aarch64-static qemu-user-static: /usr/bin/qemu-aarch64-static $ apt list qemu-user-static qemu-user-static/focal-updates,focal-security,now 1:4.2-3ubuntu6.10 amd64 [installed] But recent builds of 5.2 are not; for example from hirsute (qemu-user- static_5.2+dfsg-2ubuntu1_amd64.deb) $ file /tmp/qemu-aarch64-static /tmp/qemu-aarch64-static: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=91fda2fa08f46d1bb6d19b6f72a4819a7c20fd7e, for GNU/Linux 3.2.0, stripped I hit this whilst trying to track down another bug and building upstream git HEAD on 20.04 with: $ ../../qemu/configure --disable-system --enable-linux-user --static --target-list=aarch64-linux-user $ make $ file qemu-aarch64 qemu-aarch64: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=546ba11f0de940f7f3cbfaffae3c2bb54b683386, for GNU/Linux 3.2.0, with debug_info, not stripped It looks like changes to the qemu build system are responsible. I asked on OFTC #qemu and at that time no-one was particularly aware of the significance/difference. Looking at the configure output summary between the focal and hirsute/upstream builds I noticed that there is no longer a separate summary for LDFLAGS - it now only reports QEMU_LDFLAGS. That seems significant since focal passed "-static" with LDFLAGS not QEMU_LDFLAGS: - LDFLAGS -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -pie -m64 -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed - QEMU_LDFLAGS + LDFLAGS -Wl,--warn-common -m64 -static -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed + QEMU_LDFLAGS whereas hirsute shows: - QEMU_LDFLAGS: -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -m64 -g -O2 - -fdebug-prefix-map=/<>/qemu-5.2+dfsg=. -fstack-protector- - strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 - -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -fstack-protector- - strong + QEMU_LDFLAGS: -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static-pie -m64 + -g -O2 -fdebug-prefix-map=/<>/qemu-5.2+dfsg=. -fstack- + protector-strong -Wformat -Werror=format-security -Wdate-time + -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as- + needed -fstack-protector-strong + + (notice it is -static-pie not -static now) I've seen mention in qemu commit messages of the meson build system changes causing issues around passing of linker flags but it needs someone familiar with the project and build system to figure this out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908331 Title: Regression: qemu-user-static binaries are dynamically linked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908331] [NEW] Regression: qemu-user-static binaries are dynamically linked
Public bug reported: On 20.04 (qemu 4.2) the binaries built for qemu-user-static - specifically in the case I've hit /usr/bin/qemu-aarch64-static - are completely static executables. The same binaries from a qemu 5.x build are not. Although they don't link to other shared libraries they are dynamically linked to glibc and therefore require the same version of the glibc shared libraries at runtime. This breaks many uses in foreign architecture chroots; in my case an aarch64 being built with debootstrap: On focal: $ file /usr/bin/qemu-aarch64-static /usr/bin/qemu-aarch64-static: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=abad039a2cfc5bc87215554230a572b085fbc37a, for GNU/Linux 3.2.0, with debug_info, not stripped $ dpkg -S /usr/bin/qemu-aarch64-static qemu-user-static: /usr/bin/qemu-aarch64-static $ apt list qemu-user-static qemu-user-static/focal-updates,focal-security,now 1:4.2-3ubuntu6.10 amd64 [installed] But recent builds of 5.2 are not; for example from hirsute (qemu-user- static_5.2+dfsg-2ubuntu1_amd64.deb) $ file /tmp/qemu-aarch64-static /tmp/qemu-aarch64-static: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=91fda2fa08f46d1bb6d19b6f72a4819a7c20fd7e, for GNU/Linux 3.2.0, stripped I hit this whilst trying to track down another bug and building upstream git HEAD on 20.04 with: $ ../../qemu/configure --disable-system --enable-linux-user --static --target-list=aarch64-linux-user $ make $ file qemu-aarch64 qemu-aarch64: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=546ba11f0de940f7f3cbfaffae3c2bb54b683386, for GNU/Linux 3.2.0, with debug_info, not stripped It looks like changes to the qemu build system are responsible. I asked on OFTC #qemu and at that time no-one was particularly aware of the significance/difference. Looking at the configure output summary between the focal and hirsute/upstream builds I noticed that there is no longer a separate summary for LDFLAGS - it now only reports QEMU_LDFLAGS. That seems significant since focal passed "-static" with LDFLAGS not QEMU_LDFLAGS: LDFLAGS -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -pie -m64 -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed QEMU_LDFLAGS whereas hirsute shows: QEMU_LDFLAGS: -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -m64 -g -O2 -fdebug-prefix-map=/<>/qemu-5.2+dfsg=. -fstack-protector- strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -fstack-protector- strong I've seen mention in qemu commit messages of the meson build system changes causing issues around passing of linker flags but it needs someone familiar with the project and build system to figure this out. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Description changed: On 20.04 (qemu 4.2) the binaries built for qemu-user-static - specifically in the case I've hit /usr/bin/qemu-aarch64-static - are - completely static executables. Although they don't link to other shared - libraries they are dynamically linked to glibc and therefore require the - same version of the glibc shared libraries at runtime. This breaks many - uses in foreign architecture chroots; in my case an aarch64 being built - with debootstrap: + completely static executables. + + The same binaries from a qemu 5.x build are not. Although they don't + link to other shared libraries they are dynamically linked to glibc and + therefore require the same version of the glibc shared libraries at + runtime. This breaks many uses in foreign architecture chroots; in my + case an aarch64 being built with debootstrap: + + On focal: $ file /usr/bin/qemu-aarch64-static /usr/bin/qemu-aarch64-static: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=abad039a2cfc5bc87215554230a572b085fbc37a, for GNU/Linux 3.2.0, with debug_info, not stripped $ dpkg -S /usr/bin/qemu-aarch64-static qemu-user-static: /usr/bin/qemu-aarch64-static $ apt list qemu-user-static qemu-user-static/focal-updates,focal-security,now 1:4.2-3ubuntu6.10 amd64 [installed] + But recent builds of 5.2 are not; for example from hirsute (qemu-user- + static_5.2+dfsg-2ubuntu1_amd64.deb) - But recent builds of 5.2 are not; for example from hirsute (qemu-user-static_5.2+dfsg-2ubuntu1_amd64.deb) - - $ file /tmp/qemu-aarch64-static + $ file /tmp/qemu-aarch64-static /tmp/qemu-aarch64-static: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=91fda2fa08f46d1bb6d19b6f72a4819a7c20fd7e, for GNU/Linux 3.2.0, stripped I hit this whilst trying to track down another bug and building upstream git HEAD on 20.04 with: $ ../../qemu/configure --disable-system --enable-linux-user --static --target-list=aarch64-linux-user $ make - $ file qemu-aarch64 + $
[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context
** Description changed: On 20.04 amd64 trying to run 'aptitude full-upgrade' inside a Debian buster chroot: mkdir debian-buster-aarch64 sudo debootstrap --arch=arm64 --foreign buster debian-buster-aarch64 http://deb.debian.org/debian sudo cp -a /usr/bin/qemu-aarch64-static debian-buster-aarch64/usr/bin/ sudo chroot debian-buster-aarch64 debootstrap/debootstrap --second-stage sudo chroot debian-buster-aarch64 apt install locales sudo chroot debian-buster-aarch64 dpkg-reconfigure locales sudo chroot debian-buster-aarch64 update-locale en_GB.UTF-8 + sudo chroot debian-buster-aarch64 apt install aptitude sudo cp -a debian-buster-aarch64 debian-sid-aarch64 sudo sed -i 's/buster/sid/g' debian-sid-aarch64/etc/apt/sources.list sudo chroot debian-sid-aarch64 apt update sudo chroot debian-sid-aarch64 aptitude full-upgrade ... Need to get 110 MB of archives. After unpacking 195 MB will be used. Do you want to continue? [Y/n/?] y qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6027796c qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60001a4e - This seems to have been reported for other architectures over a long period with some reports seeming to indicate at least on cause has been fixed. https://github.com/vivier/qemu-m68k/issues/33 https://github.com/vivier/qemu-m68k/issues/38 https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1254828 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu-user-static 1:4.2-3ubuntu6.10 Uname: Linux 5.10.0-051000rc5-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 2 06:48:43 2020 InstallationDate: Installed on 2020-04-08 (237 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND MachineType: LENOVO 20NECTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-051000rc5-lowlatency root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:br1.12:efr1.12:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906479 Title: qemu:handle_cpu_signal received signal outside vCPU context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906479] [NEW] qemu:handle_cpu_signal received signal outside vCPU context
Public bug reported: On 20.04 amd64 trying to run 'aptitude full-upgrade' inside a Debian buster chroot: mkdir debian-buster-aarch64 sudo debootstrap --arch=arm64 --foreign buster debian-buster-aarch64 http://deb.debian.org/debian sudo cp -a /usr/bin/qemu-aarch64-static debian-buster-aarch64/usr/bin/ sudo chroot debian-buster-aarch64 debootstrap/debootstrap --second-stage sudo chroot debian-buster-aarch64 apt install locales sudo chroot debian-buster-aarch64 dpkg-reconfigure locales sudo chroot debian-buster-aarch64 update-locale en_GB.UTF-8 sudo cp -a debian-buster-aarch64 debian-sid-aarch64 sudo sed -i 's/buster/sid/g' debian-sid-aarch64/etc/apt/sources.list sudo chroot debian-sid-aarch64 apt update sudo chroot debian-sid-aarch64 aptitude full-upgrade ... Need to get 110 MB of archives. After unpacking 195 MB will be used. Do you want to continue? [Y/n/?] y qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6027796c qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60001a4e This seems to have been reported for other architectures over a long period with some reports seeming to indicate at least on cause has been fixed. https://github.com/vivier/qemu-m68k/issues/33 https://github.com/vivier/qemu-m68k/issues/38 https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1254828 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu-user-static 1:4.2-3ubuntu6.10 Uname: Linux 5.10.0-051000rc5-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 2 06:48:43 2020 InstallationDate: Installed on 2020-04-08 (237 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND MachineType: LENOVO 20NECTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-051000rc5-lowlatency root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:br1.12:efr1.12:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906479 Title: qemu:handle_cpu_signal received signal outside vCPU context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906131 Title: No rule to make target 'scripts/module.lds' while building out-of-tree modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906131] [NEW] No rule to make target 'scripts/module.lds' while building out-of-tree modules
Public bug reported:
kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess
module linker script" ) that affects where and how scripts/module.lds is
used and causes external modules to fail to build since that linker
script is not shipped in the linux-{image,header} packages.
I've been testing the mainline PPA kernel v5.10-rc5 and today installed
v4l2loopback-dkms and hit this issue.
It will affect all DKMS packages. Ubuntu carries 39 DKMS packages.
See the LKML discussion:
https://lkml.org/lkml/2020/8/31/455
DKMS make.log for v4l2loopback-0.12.3 for kernel 5.10.0-051000rc5-lowlatency
(x86_64)
Sun 29 Nov 02:48:58 GMT 2020
Building v4l2-loopback driver...
make -C /lib/modules/5.10.0-051000rc5-lowlatency/build
M=/var/lib/dkms/v4l2loopback/0.12.3/build modules
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
make[3]: *** No rule to make target 'scripts/module.lds', needed by
'/var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.ko'. Stop.
make[3]: *** Waiting for unfinished jobs
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.mod.o
make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make[1]: *** [Makefile:1703: modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #975571
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571
** Also affects: linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571
Importance: Unknown
Status: Unknown
** Description changed:
- kernel v5.10-rc1 introduced a change that affects where and how
- scripts/module.lds is used and causes external modules to fail to build
- since that linker script is not shipped in the linux-{image,header}
- packages.
+ kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess
+ module linker script" ) that affects where and how scripts/module.lds is
+ used and causes external modules to fail to build since that linker
+ script is not shipped in the linux-{image,header} packages.
I've been testing the mainline PPA kernel v5.10-rc5 and today installed
v4l2loopback-dkms and hit this issue.
It will affect all DKMS packages. Ubuntu carries 39 DKMS packages.
-
DKMS make.log for v4l2loopback-0.12.3 for kernel 5.10.0-051000rc5-lowlatency
(x86_64)
Sun 29 Nov 02:48:58 GMT 2020
Building v4l2-loopback driver...
make -C /lib/modules/5.10.0-051000rc5-lowlatency/build
M=/var/lib/dkms/v4l2loopback/0.12.3/build modules
make[1]: Entering directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
- CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
- MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
+ CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
+ MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
make[3]: *** No rule to make target 'scripts/module.lds', needed by
'/var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.ko'. Stop.
make[3]: *** Waiting for unfinished jobs
- CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.mod.o
+ CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.mod.o
make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make[1]: *** [Makefile:1703: modules] Error 2
make[1]: Leaving directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
** Description changed:
kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess
module linker script" ) that affects where and how scripts/module.lds is
used and causes external modules to fail to build since that linker
script is not shipped in the linux-{image,header} packages.
I've been testing the mainline PPA kernel v5.10-rc5 and today installed
v4l2loopback-dkms and hit this issue.
It will affect all DKMS packages. Ubuntu carries 39 DKMS packages.
+
+ See the LKML discussion:
+
+ https://lkml.org/lkml/2020/8/31/455
+
DKMS make.log for v4l2loopback-0.12.3 for kernel 5.10.0-051000rc5-lowlatency
(x86_64)
Sun 29 Nov 02:48:58 GMT 2020
Building v4l2-loopback driver...
make -C /lib/modules/5.10.0-051000rc5-lowlatency/build
M=/var/lib/dkms/v4l2loopback/0.12.3/build modules
make[1]: Entering directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
make[3]: *** No rule to make target 'scripts/module.lds', needed by
'/var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.ko'. Stop.
[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click
Similar issues with Logitech wireless keyboard and mouse after updating Hirsute. Mouse freezes intermittently but is mostly usable. Keyboard is essentially unusable (this is posted via onscreen keyboard). All hardware fully functional on Hirsute with 5.8.0-25 and 5.8.0-26 before updates on 11/27 and/or 11/28. Overlapping updated packages with corradoventu appear to be linux-firmware and apport related ones. Booting in recovery mode on both kernels keyboard is also unusable. No issues in updated Groovy or elementary OS. Intel i9, Asus MB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905946 Title: Mouse stop moving after few seconds. restart at click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] Re: Actual kernel don't want to make more than 64 cpus available
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904735] [NEW] package libpam-systemd:amd64 204-5ubuntu20.31 failed to install/upgrade: package libpam-systemd:amd64 is already installed and configured
Public bug reported: ?? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpam-systemd:amd64 204-5ubuntu20.31 ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.29 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: amd64 CrashReports: 664:1000:1000:0:2020-11-18 07:19:05.946248135 -0500:2020-11-18 07:19:05.946248135 -0500:/var/crash/_usr_bin_update-manager.1000.upload 600:0:0:514260:2020-11-18 07:41:45.339034795 -0500:2020-11-18 07:41:46.339034795 -0500:/var/crash/libpam-systemd:amd64.0.crash 600:0:0:514269:2020-11-18 07:41:46.325027707 -0500:2020-11-18 07:41:46.314022207 -0500:/var/crash/language-selector-common.0.crash 640:1000:1000:80959:2020-11-18 07:19:01.562940597 -0500:2020-11-18 07:19:02.562940597 -0500:/var/crash/_usr_bin_update-manager.1000.crash 600:0:0:514259:2020-11-18 07:41:46.312021207 -0500:2020-11-18 07:41:46.295012708 -0500:/var/crash/accountsservice.0.crash Date: Wed Nov 18 07:41:46 2020 DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.31:package libpam-systemd:amd64 is already installed and configured ErrorMessage: package libpam-systemd:amd64 is already installed and configured InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.24 SourcePackage: dpkg Title: package libpam-systemd:amd64 204-5ubuntu20.31 failed to install/upgrade: package libpam-systemd:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904735 Title: package libpam-systemd:amd64 204-5ubuntu20.31 failed to install/upgrade: package libpam-systemd:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1904735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819543] Re: Does not exit correctly, have to "kill -9
So far when this affects me (20.04) it is when I've opened the media from a file manager or started VLC via the menu.In both cases it uses "vlc --start-from-file ..." - if I start vlc on the command-line without that option it seems to quit/terminate correctly and not hang about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819543 Title: Does not exit correctly, have to "kill -9 To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1819543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901488] [NEW] Encrypted LVM on UEFI prevents GRUB booting successfully
*** This bug is a duplicate of bug 1876989 *** https://bugs.launchpad.net/bugs/1876989 Public bug reported: 20.04.1 Encrypted LVM install, sda4 > LUKSv2 > VG > LVs cryptsetup creates LUKSv2 containers. GRUB can only understand LUKSv1 and therefore cannot access its root device making the installation unbootable. Making matters worse, installer has not added GRUB_ENABLE_CRYPTODISK=y to /etc/default/grub.d/local.cfg so grub-install hasn't passed the crypto device info to GRUB's core and thus there is no cryptomount command in /EFI/ubuntu/grub.cfg ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1876989 Encrypted LVM install with no separate /boot results in unbootable system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901488 Title: Encrypted LVM on UEFI prevents GRUB booting successfully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1901488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901482] [NEW] E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Public bug reported: 20.04.1, when applying updates, 'full log' is reporting for every package install: E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device) This should either be corrected (by mounting devpts into the /target/ or redirecting the error to /dev/null to avoid causing the administrator wasting time trying to determine if there's a fault with the installation. ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901482 Title: E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1901482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901480] [NEW] Custom storage does not refresh to reflect changes
Public bug reported: 20.04.1, Custom storage layout This view does not refresh when underlying changes have occurred, whether using the "Reset" option, or using 'Back' to move back through the pages. Specific scenario is related to "Unable to add a GPT partition with 400+GB free space" bug #1901478 After using Help > Root Shell and using gdisk to create a partition with the free space, and ensuring the kernel's view of the device is updated (confirmed via /proc/partitions), there appears no way to cause the installer to refresh its information and therefore it continues to report only 4 partitions and 400GB free space when there are 5 partitions and 0 free space! ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901480 Title: Custom storage does not refresh to reflect changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1901480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901478] [NEW] Unable to add a GPT partition with 400+GB free space
Public bug reported: 20.04.1 installer, Custom storage layout On a device with 400+ GB free space and 4 existing GPT partitions the option to add a GPT partition is disabled. Apparently the logic cannot code with dis-contiguous partitions! root@ubuntu-server:/# gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 1953459632 sectors, 931.5 GiB Model: LOGICAL VOLUME Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 05564500-64D5-40BE-A6EE-39476C575604 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1953459598 Partitions will be aligned on 2048-sector boundaries Total free space is 843898221 sectors (402.4 GiB) Number Start (sector)End (sector) Size Code Name 12048 206847 100.0 MiB EF00 EFI system partition 2 206848 468991 128.0 MiB 0C01 Microsoft reserved ... 3 468992 133304319 63.3 GiB0700 Basic data partition 4 977199104 1953458175 465.5 GiB 0700 Basic data partition ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Unable to add a GPT partition" https://bugs.launchpad.net/bugs/1901478/+attachment/5427149/+files/subiquity-20.04.1-GPT.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901478 Title: Unable to add a GPT partition with 400+GB free space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1901478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901401] Re: SD card does not work on linux, but window (O2Micro)
May be fixed by upstream commits: 7b7d897e8898 2020-07-24 12:34:42 +0200 N shirley her mmc: sdhci-pci-o2micro: Add HW tuning for SDR104 mode cdd2b769789a 2020-07-24 12:30:36 +0200 N shirley her mmc: sdhci-pci-o2micro: Bug fix for O2 host controller Seabird1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901401 Title: SD card does not work on linux, but window (O2Micro) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901464] [NEW] cloud-initramfs-copymods sometimes breaks systems with self-contained kernel/initrd
Public bug reported: I've been working with a colleague with an ubuntu-server install in a Xen virtual machine. The install doesn't use an external kernel/initrd.img but due to having package ubuntu-server installed also installs cloud-initramfs-copymods. The initial report was the system suffering repeated loss of the xenfs.ko module after reboots. Eventually tracked down to /lib/modules/ being a tmpfs which is created by /usr/share/initramfs-tools/scripts/init-bottom/copymods There's a bug which causes it to unconditionally create the tmpfs mount on /lib/ even when the kernel command-line does not contain "copymods=force". We're trying to figure out how this is getting triggered. On the face of it the only way it could occur is if the rootfs is missing /lib/modules/ OR is missing /lib/modules/$myver or the rootfs hasn't been mounted to $rootmnt at the time this script executes. This was an encrypted separate /boot/ and / install using debootstrap of ubuntu-server + the kernel packages due to the 20.04 live server installer not being able to deal with this layout. Therefore there may be some quirk of this method triggering the issue, although it is unclear what. ** Affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Description changed: I've been working with a colleague with an ubuntu-server install in a Xen virtual machine. The install doesn't use an external kernel/initrd.img but due to having package ubuntu-server installed also installs cloud-initramfs-copymods. The initial report was the system suffering repeated loss of the xenfs.ko module after reboots. Eventually tracked down to /lib/modules/ being a tmpfs which is created by /usr/share/initramfs-tools/scripts/init-bottom/copymods There's a bug which causes it to unconditionally create the tmpfs mount on /lib/ even when the kernel command-line does not contain "copymods=force". We're trying to figure out how this is getting triggered. On the face of it the only way it could occur is if the rootfs is missing /lib/modules/ - OR is missing /lib/modules/$myver or the rootfs hasn't been mount to + OR is missing /lib/modules/$myver or the rootfs hasn't been mounted to $rootmnt at the time this script executes. This was an encrypted separate /boot/ and / install using debootstrap of ubuntu-server + the kernel packages due to the 20.04 live server installer not being able to deal with this layout. Therefore there may be some quirk of this method triggering the issue, although it is unclear what. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901464 Title: cloud-initramfs-copymods sometimes breaks systems with self-contained kernel/initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1901464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
