[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
Hi Kaihenfeng,
Thanks for your patch suggestion! I'm semantically not sure it is the right
thing - to clarify your theory is that before it checked !resuming and before
had the check for !cdev maybe just to avoid a deference error. And now you
assume that instead of !cdev it should check if there is a cdev there.
I'm unsure - if !cdev was indeed just to protect the dereference then maybe no
check at all might be better. Which would then read "if the event is
IO_SCH_ORPH_UNREG or IO_SCH_UNREG then do css_sch_device_unregister.
But that I'm not immediately convinced doesn't mean much and it is easy
to test and surely worth a try, so I ran v5.11 (bad) plus your patch and
the result will be useful to know in any case. It is working fine, that
much I can tell you.
But if my thought above was right (it was only there to avoid the potential
deference error), then why check it at all. If the condition cdev==NULL is
possible it would now skip to to fully remove it - we might not need that at
all.
And Since I brought up the idea of dropping the cdev check entirely that was
worth a try as well. So now the third check of this morning is for:
--- a/drivers/s390/cio/device.c
+++ b/drivers/s390/cio/device.c
@@ -1525,8 +1525,7 @@ static int io_subchannel_sch_event(struct subchannel
*sch, int process)
switch (action) {
case IO_SCH_ORPH_UNREG:
case IO_SCH_UNREG:
- if (!cdev)
- css_sch_device_unregister(sch);
+ css_sch_device_unregister(sch);
break;
case IO_SCH_ORPH_ATTACH:
case IO_SCH_UNREG_ATTACH:
My patch with that change - in my test - is working as well.
Neither of the solutions has triggered other regressions in my setup - but then
there are so many potential use-cases that I can't be sure without a further
revew by subject matter experts.
So a summary of the recent tests:
5.11.0-16-generic #17+lp1925211v202104201520 (Seths full revert) - working
5.11.0lp1925211-patch-kaihengfeng-dirty - working
5.11.0nocdevcheck-paelzer-dirty - working
I think we'd want an answer from the IBM devs which solution (full
revert, kaihenfeng patch, cpaelzer patch, another approach) they would
prefer - then we can submit it upstream for them to include officially
and we can carry it as delta until we rebase onto a version that has it
applied anyway.
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves broken block devices around in Hirsute on
s390x
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in udev package in Ubuntu:
New
Status in linux source package in Hirsute:
Confirmed
Status in systemd source package in Hirsute:
New
Status in udev source package in Hirsute:
New
Bug description:
Repro:
#1 Get a guest
$ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x
label=daily
$ uvt-kvm wait h release=hirsute arch=s390x label=daily
#2 Attach and Detach disk
$ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M
$ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
$ virsh detach-disk h vdc
From libvirts POV it is gone at this point
$ virsh domblklist h
Target Source
--
vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow
vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow
But the guest thinks still it is present
$ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk
...
vdc252:32 0 20M 0 disk
This even remains a while after (not a race).
Any access to it in the guest will hang (as you'd expect of a non-existing
blockdev)
4 017581739 20 0 12140 4800 - S+ pts/0 0:00 |
\_ sudo mkfs.ext4 /dev/vdc
4 017591758 20 0 6924 1044 - D+ pts/0 0:00 |
\_ mkfs.ext4 /dev/vdc
The result above was originally found with hirsute-guest@hirsute-host
on s390x
I do NOT see the same with groovy-guest@hirsute-host on s390x
I DO see the same with hirsute-guest@groovy-host on s390x
=> Guest version dependent not Host/Hipervisor dependent
I DO see the same with ZFS disks AND LVM disks being added
=> not type dependent
I do NOT see the same on x86.
=> Arch dependent ??
... the evidence slowly points towards an issue in the guest, damn we are so
close to release - but non-fully detaching disks are critical in my POV :-/
Filing this as-is for awareness, but certainly this will need more debugging.
Unsure where this is going to eventually I'll now file it for
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
Thanks Frank for adding the mirror request to this, because either way we sooner or later want a discussion with the s390x developers on this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Tags added: reverse-proxy-bugzilla -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) ** Tags added: reverse-proxy-bugzilla -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
The check was for resuming flag, but now it's inverted. Please test this patch. ** Patch added: "lp1925211.patch" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1925211/+attachment/5490454/+files/lp1925211.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904369] Re: systemd 100% CPU; constantly reading service for socket activation
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1904369
Title:
systemd 100% CPU; constantly reading service for socket activation
Status in systemd package in Ubuntu:
Expired
Status in systemd source package in Bionic:
Expired
Bug description:
Hi,
We recently switched to using systemd's socket activation for per-
client limits. The configs are as follows:
| $ ls -la /etc/systemd/system/sockets.target.wants/rsyncd.socket
| lrwxrwxrwx 1 root root 33 Aug 25 00:09
/etc/systemd/system/sockets.target.wants/rsyncd.socket ->
/etc/systemd/system/rsyncd.socket
| $ cat /etc/systemd/system/sockets.target.wants/rsyncd.socket
| [Unit]
| Description=rsync daemon (socket)
| Conflicts=rsyncd.service
|
| [Socket]
| ListenStream=873
| Accept=yes
| MaxConnections=85
| MaxConnectionsPerSource=5
| KeepAlive=true
|
| [Install]
| WantedBy=sockets.target
| $ cat /etc/systemd/system/rsyncd@.service
| [Unit]
| Description=rsync daemon
| ConditionPathExists=/etc/rsyncd.conf
|
| [Service]
| ExecStart=/usr/bin/rsync --daemon
| StandardInput=socket
|
| [Install]
| WantedBy=multi-user.target
After a while, systemd runs hot consuming a whole CPU core:
| $ top -p 1
| PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
| 1 root 20 0 2057476 251560 6264 R 99.7 0.1 17903:32 systemd
strace shows it constantly doing this:
| $ sudo strace -p 1
| ...
| openat(AT_FDCWD, "/etc/systemd/system/rsyncd@.service",
O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = 14
| fcntl(14, F_GETFL) = 0x28000 (flags
O_RDONLY|O_LARGEFILE|O_NOFOLLOW)
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| read(14, "[Unit]\nDescription=rsync daemon\n"..., 4096) = 173
| read(14, "", 4096) = 0
| close(14) = 0
| openat(AT_FDCWD, "/etc/systemd/system/rsyncd@.service",
O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = 14
| fcntl(14, F_GETFL) = 0x28000 (flags
O_RDONLY|O_LARGEFILE|O_NOFOLLOW)
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| read(14, "[Unit]\nDescription=rsync daemon\n"..., 4096) = 173
| read(14, "", 4096) = 0
| close(14) = 0
| ^Cstrace: Process 1 detached
This is with 237-3ubuntu10.43 on a host running Bionic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904369/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904369] Re: systemd 100% CPU; constantly reading service for socket activation
[Expired for systemd (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1904369
Title:
systemd 100% CPU; constantly reading service for socket activation
Status in systemd package in Ubuntu:
Expired
Status in systemd source package in Bionic:
Expired
Bug description:
Hi,
We recently switched to using systemd's socket activation for per-
client limits. The configs are as follows:
| $ ls -la /etc/systemd/system/sockets.target.wants/rsyncd.socket
| lrwxrwxrwx 1 root root 33 Aug 25 00:09
/etc/systemd/system/sockets.target.wants/rsyncd.socket ->
/etc/systemd/system/rsyncd.socket
| $ cat /etc/systemd/system/sockets.target.wants/rsyncd.socket
| [Unit]
| Description=rsync daemon (socket)
| Conflicts=rsyncd.service
|
| [Socket]
| ListenStream=873
| Accept=yes
| MaxConnections=85
| MaxConnectionsPerSource=5
| KeepAlive=true
|
| [Install]
| WantedBy=sockets.target
| $ cat /etc/systemd/system/rsyncd@.service
| [Unit]
| Description=rsync daemon
| ConditionPathExists=/etc/rsyncd.conf
|
| [Service]
| ExecStart=/usr/bin/rsync --daemon
| StandardInput=socket
|
| [Install]
| WantedBy=multi-user.target
After a while, systemd runs hot consuming a whole CPU core:
| $ top -p 1
| PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
| 1 root 20 0 2057476 251560 6264 R 99.7 0.1 17903:32 systemd
strace shows it constantly doing this:
| $ sudo strace -p 1
| ...
| openat(AT_FDCWD, "/etc/systemd/system/rsyncd@.service",
O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = 14
| fcntl(14, F_GETFL) = 0x28000 (flags
O_RDONLY|O_LARGEFILE|O_NOFOLLOW)
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| read(14, "[Unit]\nDescription=rsync daemon\n"..., 4096) = 173
| read(14, "", 4096) = 0
| close(14) = 0
| openat(AT_FDCWD, "/etc/systemd/system/rsyncd@.service",
O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = 14
| fcntl(14, F_GETFL) = 0x28000 (flags
O_RDONLY|O_LARGEFILE|O_NOFOLLOW)
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| fstat(14, {st_mode=S_IFREG|0644, st_size=173, ...}) = 0
| read(14, "[Unit]\nDescription=rsync daemon\n"..., 4096) = 173
| read(14, "", 4096) = 0
| close(14) = 0
| ^Cstrace: Process 1 detached
This is with 237-3ubuntu10.43 on a host running Bionic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904369/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916245] Re: No matter how i write the lightdm.conf file, it makes the whole thing crash and i can't login. I'm trying to change the greeter to webkit2
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1916245 Title: No matter how i write the lightdm.conf file, it makes the whole thing crash and i can't login. I'm trying to change the greeter to webkit2 Status in lightdm package in Ubuntu: Expired Bug description: I installed lightdm and then rebooted. It worked fine but i wanted to change how it looks. I tried installing the web-greeter using whither as instructed here: https://askubuntu.com/questions/960334/how-can-i -install-lightdm-webkit2-greeter and the PC wouldn't open. It would be loading forever. So then i deleted the conf file and it reverted to the default. I've tried placing the same conf file at /etc/lightdm/lightdm.conf with the same results ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 19 14:49:25 2021 InstallationDate: Installed on 2020-10-14 (127 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: lightdm UpgradeStatus: Upgraded to groovy on 2020-11-26 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1916245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
Thanks Seth. I have verified 5.11.0-16-generic #17+lp1925211v202104201520 from the PPA and can confirm that the issue is gone. => The revert works as a fix \o/ For the severity/urgency at least we now know that it is s390x only (not "good" but reduces the amount of affected people). I'll later (after I'm actually awake) if it also affects non-KVM disks (e.g. channel I/O detaches) then we can decide if 0-day or the next normal round will be ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
So if only run below commands, does the audio become good or not? sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7 Or could you do a test to find the minimal group of commands to make the audio change normal? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
Same issue here Acer Swift SF315-52G Both internal and external microphones don't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
** Changed in: kbd-chooser Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: New Status in kbd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925265] Re: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925265 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925265 Title: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove Status in ubuntu-meta package in Ubuntu: New Bug description: Immediately after installing hirsute-preinstalled-desktop-arm64+raspi on a Raspberry Pi I noticed that there were packages available for autoremoval. bdmurray@bdmurray-desktop:~$ sudo apt autoremove [sudo] password for bdmurray: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64 grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot libdebian-installer4 libdevmapper-event1.02.1 libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 os-prober python3-icu python3-pam rdate thin-provisioning-tools 0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded. After this operation, 45.5 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. It seems to me the installation process should run an autoremove at the end. bdmurray@bdmurray-desktop:~$ cat /var/log/installer/version ubiquity 21.04.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925265] [NEW] Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove
Public bug reported: Immediately after installing hirsute-preinstalled-desktop-arm64+raspi on a Raspberry Pi I noticed that there were packages available for autoremoval. bdmurray@bdmurray-desktop:~$ sudo apt autoremove [sudo] password for bdmurray: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64 grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot libdebian-installer4 libdevmapper-event1.02.1 libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 os-prober python3-icu python3-pam rdate thin-provisioning-tools 0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded. After this operation, 45.5 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. It seems to me the installation process should run an autoremove at the end. bdmurray@bdmurray-desktop:~$ cat /var/log/installer/version ubiquity 21.04.19 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute raspi-image ** Tags added: raspi-image ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925265 Title: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove Status in ubuntu-meta package in Ubuntu: New Bug description: Immediately after installing hirsute-preinstalled-desktop-arm64+raspi on a Raspberry Pi I noticed that there were packages available for autoremoval. bdmurray@bdmurray-desktop:~$ sudo apt autoremove [sudo] password for bdmurray: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64 grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot libdebian-installer4 libdevmapper-event1.02.1 libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 os-prober python3-icu python3-pam rdate thin-provisioning-tools 0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded. After this operation, 45.5 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. It seems to me the installation process should run an autoremove at the end. bdmurray@bdmurray-desktop:~$ cat /var/log/installer/version ubiquity 21.04.19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Summary changed: - Hot-unplug of disks leaves broken block devices around in Hirsute + Hot-unplug of disks leaves broken block devices around in Hirsute on s390x ** Changed in: linux (Ubuntu Hirsute) Milestone: None => hirsute-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
The commit reverts cleanly. We need to confirm that reverting the commit does fix the issue. I put a test build here, please test. https://people.canonical.com/~sforshee/lp1925211/ I doubt we can get a new kernel into the release. If it's extremely urgent we can consider a day 0 SRU kernel for hirsute, otherwise we can make sure it gets into the first normal SRU kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
Problem seems to be on s390x with the 4.15 kernel, faccessat2() still returns EPERM: faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 EPERM (Operation not permitted) while on amd64 it now returns ENOSYS which is correctly handled with fallback to faccessat() faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 ENOSYS (Function not implemented) faccessat(AT_FDCWD, "/bin/bash", X_OK) = 0 (note both traces were of bash running 'test -x /bin/bash') -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg
[Touch-packages] [Bug 1923618] Re: upgrading systemd on groovy terminates sessions
Hey, Dan. Thanks for looking into this. I am attaching a journal log from the time I got the failure. Cascardo. ** Attachment added: "journalctl output" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+attachment/5490397/+files/systemd_upgrade.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: Whenever I upgrade systemd on my groovy system, my gnome session is terminated. This is very annoying, as everything that was running on that session is terminated. NetworkManager also stops running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923618] Re: upgrading systemd on groovy terminates sessions
I tried reproducing this in a VM, but it was able to upgrade systemd with no problems, is there anything in your logs indicating why the gnome session was terminated? ** Changed in: systemd (Ubuntu Groovy) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: Whenever I upgrade systemd on my groovy system, my gnome session is terminated. This is very annoying, as everything that was running on that session is terminated. NetworkManager also stops running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
Ok, let's do this in steps: 1. boot machine - CapsLock function and LED are off 2. login and press CapsLock button - now user can enter CAPITALS and CapsLock LED should be on 3. press CapsLock button again - now user can enter lowercase letters and CapsLock LED is off What else should I explain to you, Dan Streetman (ddstreet) ? ** Changed in: kbd (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed ** Description changed: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system - 4. Press key, enter some letters in capitals - 5. Press key again, enter some letters in lowercase + 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) + 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) ** Description changed: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: - * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function + * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Unknown Status in kbd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
CapsLock LED should react on CapsLock key, is not it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Unknown Status in kbd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
Was a copy-paste problem. Thank you for your comment, dear developer! ** Description changed: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase - Actual results: + Expected results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function - Expected results: + Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Unknown Status in kbd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
> Actual results: > * CapsLock key switches on CapsLock LED, the LED state indicates current > CapsLock key function > > Expected results: > * CapsLock LED is always off the 'actual results' sounds like correct behavior to me...? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Unknown Status in kbd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925215] Re: System completely freezes and requires reboot
First, 21.04 isn't released yet, so you shouldn't be using it unless you're prepared for bugs. Second, it would be better to ask for general debugging help at https://askubuntu.com/ since this is for reporting bugs. There's no information in your attached dmesg that might help, though that is probably because it's from the boot after your hang, so it doesn't include anything useful. If you have any details about any actual bug please attach it. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925215 Title: System completely freezes and requires reboot Status in systemd package in Ubuntu: Incomplete Bug description: The OS spontaneously froze whilst doing some work (firefox, VMs). I can't find anything suspect in the logs at this stage. I will keep an eye out for this issue but would like advise on what to check for, any tools I should install and commands to run when it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 20 14:28:46 2021 ExecutablePath: /usr/lib/systemd/systemd InstallationDate: Installed on 2021-04-16 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
commit 8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62
Author: Vineeth Vijayan
Date: Fri Nov 20 09:36:38 2020 +0100
s390/cio: remove pm support from ccw bus driver
As part of removing broken pm-support from s390 arch, remove
the pm callbacks from ccw-bus driver.The power-management functions
are unused since the 'commit 394216275c7d ("s390: remove broken
hibernate / power management support")'.
Signed-off-by: Vineeth Vijayan
Reviewed-by: Peter Oberparleiter
Signed-off-by: Heiko Carstens
arch/s390/include/asm/ccwdev.h | 10 --
drivers/s390/cio/cmf.c | 5 -
drivers/s390/cio/device.c | 247 +
drivers/s390/cio/device.h | 1 -
drivers/s390/cio/device_fsm.c | 6 -
drivers/s390/cio/io_sch.h | 1 -
It seems it wasn't as unused/broken as they thought :-/
BTW the referenced 394216275c7d ("s390: remove broken hibernate / power
management support") was in v5.7
Found by:
$ git bisect log
git bisect start
# good: [2c85ebc57b3e1817b6ce1a6b703928e113a90442] Linux 5.10
git bisect good 2c85ebc57b3e1817b6ce1a6b703928e113a90442
# bad: [f40ddce88593482919761f74910f42f4b84c004b] Linux 5.11
git bisect bad f40ddce88593482919761f74910f42f4b84c004b
# bad: [538fcf57aaee6ad78a05f52b69a99baa22b33418] Merge branches 'acpi-scan',
'acpi-pnp' and 'acpi-sleep'
git bisect bad 538fcf57aaee6ad78a05f52b69a99baa22b33418
# bad: [15b447361794271f4d03c04d82276a841fe06328] mm/lru: revise the comments
of lru_lock
git bisect bad 15b447361794271f4d03c04d82276a841fe06328
# good: [b10733527bfd864605c33ab2e9a886eec317ec39] Merge tag
'amd-drm-next-5.11-2020-12-09' of git://people.freedesktop.org/~agd5f/linux
into drm-next
git bisect good b10733527bfd864605c33ab2e9a886eec317ec39
# good: [2c075f38a708c578a752b738a45e8c26923eac2e] Merge branch 'radeon-fixes'
(Radeon and amdgpu fixes)
git bisect good 2c075f38a708c578a752b738a45e8c26923eac2e
# bad: [76d4acf22b4847f6c7b2f9042366fbdc3d20f578] Merge tag
'perf-kprobes-2020-12-14' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
git bisect bad 76d4acf22b4847f6c7b2f9042366fbdc3d20f578
# bad: [f9b4240b074730f41c1ef8e0d695d10fb5bb1e27] Merge tag 'fixes-v5.11' of
git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux
git bisect bad f9b4240b074730f41c1ef8e0d695d10fb5bb1e27
# good: [d889797530c66f699170233474eab3361471e808] Merge remote-tracking branch
'arm64/for-next/fixes' into for-next/core
git bisect good d889797530c66f699170233474eab3361471e808
# good: [2f6ea6fb88ab9d517644a098fc670b4d5dd1735e] s390/tape: remove
unsupported PM functions
git bisect good 2f6ea6fb88ab9d517644a098fc670b4d5dd1735e
# bad: [586592478b1fa8bb8cd6875a9191468e9b1a8b13] Merge tag 's390-5.11-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
git bisect bad 586592478b1fa8bb8cd6875a9191468e9b1a8b13
# good: [0b03beface02d519693edb8020f9811c67d5c88f] Merge tag
'm68k-for-v5.11-tag1' of
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k
git bisect good 0b03beface02d519693edb8020f9811c67d5c88f
# bad: [613775d62ec60202f98d2c5f520e6e9ba6dd4ac4] s390/kexec_file: fix diag308
subcode when loading crash kernel
git bisect bad 613775d62ec60202f98d2c5f520e6e9ba6dd4ac4
# good: [796cfabde5b23e1e506994fd11d2609ec2818e8d] s390/cio: remove pm support
from IO subchannel drivers
git bisect good 796cfabde5b23e1e506994fd11d2609ec2818e8d
# bad: [8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62] s390/cio: remove pm support
from ccw bus driver
git bisect bad 8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62
# good: [ef2eea78a6f363a58c909b7a0fd002df7cc52991] s390/cio: remove pm support
from css-bus driver
git bisect good ef2eea78a6f363a58c909b7a0fd002df7cc52991
# first bad commit: [8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62] s390/cio: remove
pm support from ccw bus driver
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves broken block devices around in Hirsute
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in udev package in Ubuntu:
New
Status in linux source package in Hirsute:
Confirmed
Status in systemd source package in Hirsute:
New
Status in udev source package in Hirsute:
New
Bug description:
Repro:
#1 Get a guest
$ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x
label=daily
$ uvt-kvm wait h release=hirsute arch=s390x label=daily
#2 Attach and Detach disk
$ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M
$ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
$ virsh detach-disk h vdc
From libvirts POV it is gone at this point
$ virsh domblklist h
Target Source
--
vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow
vdb
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
But it makes sense in regard to the broken use case and explains why we see it only on s390x. @sforshee - what should we do about it now that we know which commit it was - just revert it asap or are there bad dependencies to it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923358] Re: Other servers doesn't display server list (Software Updater)
great, it was probably the same as the mentioned issue, closing ** Changed in: software-properties (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1923358 Title: Other servers doesn't display server list (Software Updater) Status in software-properties package in Ubuntu: Fix Released Bug description: Using Settings and then trying to choose other server doesn't do anything. It should display the list of available other servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1923358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
Please, see below testing results. sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x78 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x003e // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x77 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0015 // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xf000 // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x3b sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x60d9 // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x33 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8580 // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1b sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0a6b // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1a sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8003 // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0f sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x02a2 // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0e sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x65c0 // bad sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7 // good, at this line sound works well and lines below are not necessary sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x06 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x6115 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1923358] Re: Other servers doesn't display server list (Software Updater)
Yes. Mirror list. But seems to be fixed now! thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1923358 Title: Other servers doesn't display server list (Software Updater) Status in software-properties package in Ubuntu: Incomplete Bug description: Using Settings and then trying to choose other server doesn't do anything. It should display the list of available other servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1923358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29457 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
The bug is actually in `kdb` package. Forcibly purging it using `sudo dpkg -P --force-all kbd` fixes the issue. But this package is useful. Please fix this bug. ** Bug watch added: github.com/legionus/kbd/issues #55 https://github.com/legionus/kbd/issues/55 ** Also affects: ubuntu-seeds via https://github.com/legionus/kbd/issues/55 Importance: Unknown Status: Unknown ** No longer affects: ubuntu-seeds ** Also affects: kbd-chooser via https://github.com/legionus/kbd/issues/55 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Unknown Status in kbd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
Running `sudo chmod a-x $(dpkg -L kbd | grep bin/)` also fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Unknown Status in kbd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
** Also affects: kbd (Ubuntu) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: shadow (Ubuntu) ** No longer affects: systemd (Ubuntu) ** No longer affects: console-setup (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707611] Re: Sound does not automatically switch to HDMI when connected
My laptop with Ubuntu 20.10 automatically switches to the HDMI output when I plug in my monitor (via a USB C cable connected to a dock station connected to the monitor via a HDMI cable). And then, a second later, it switches to the USB dock's audio output (which has nothing plugged in), but that's a different bug. Incidentally, module-switch-on-connect in PulseAudio 14 (and also Ubuntu 20.10's 13.99.2) has a blacklist of sink names that should not be switched to. The default value of this blacklist is a regexp matching "hdmi". The blacklist doesn't appear to work (which is also a different bug). If it does start to work at some point, you may have to edit /etc/pulse/default.pa and change load-module module-switch-on-connect to say load-module module-switch-on-connect blacklist="" if you want HDMI outputs to be switched to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707611 Title: Sound does not automatically switch to HDMI when connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: When connecting a HDMI cable or other audio device, the user must manually click on the "sound volume" in the top-right and switch to the newly connected device. Example: you connect a HDMI cable to the television, but then you must manually choose the HDMI sound option; it does not get selected automatically. Often times e.g. when the HDMI cable is disconnected, the user must then manually click on the "speakers" or "line out" setting - EVEN IF IT'S ALREADY SELECTED, it must be clicked on again for the sound to work through the computer's speakers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 778627] Re: bash completion now quotes shell variable references rather than expanding them
(corrected) Agreed, this is an annoying bug and has been around far too long (a decade?). ls $HOME/.ss should give: ls $HOME/.ssh/ "shopt -s direxpand" expands $HOME which is not wanted. "shopt -u complete_fullquote" should give me what I want but has no effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/778627 Title: bash completion now quotes shell variable references rather than expanding them Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Quantal: Fix Released Status in bash source package in Raring: Fix Released Status in bash package in Debian: Fix Released Status in bash package in Fedora: New Bug description: Binary package hint: bash NB! NB! NB! After applying the update to resolve this problem one _also_ must enable direxpand option by issuing: shopt -s direxpand If you do not do this, the variable expansion will not happen. NB! NB! NB! [Impact] Bash-4.2 tries to leave completed directory names as the user typed them, without expanding them to a full pathname. One effect of this is that shell variables used in pathnames being completed (e.g., $HOME) are left unchanged, but the `$' is quoted by readline because it is a special character to the shell. [Test Case] - [Current test case showing expected behavior] Items to address so far: - that $ is escaped less - that direxpand does not expand as expected - that direxpand option is available and if enabled, expands directories with variable names. zef:~/Projects/precise-amd64$ mkdir -p /tmp/testd/finger/toe zef:~/Projects/precise-amd64$ cd /tmp/testd/ zef:/tmp/testd$ td=`pwd` zef:/tmp/testd$ cd ../ zef:/tmp$ ls \$td/finger zef:/tmp$ shopt -s direxpand zef:/tmp$ ls $td/fing zef:/tmp$ ls /tmp/testd/finger/ toe - [Previous Test Case showing non-working bash installation] ~$ mkdir -p /tmp/testd/finger/toe /tmp$ cd /tmp/testd /tmp/testd$ td=`pwd` /tmp/testd$ cd ../ /tmp$ ls $td/fing Type a TAB character at this point, and bash completion makes the line: /tmp$ ls \$td/finger Note that while 'fing' has been expanded to 'finger ' (with a space at the end), the $td variable reference has had the $ character quoted with a backslash. This prevents further extension of the pathname, and in fact makes the command invalid; if I type a newline at this point, I get: ls: cannot access $td/finger: No such file or directory This is not useful behavior. I believe that in Ubuntu 10.10, the $td variable would have been expanded to '/tmp/testd', and subsequent completions starting from '/tmp/testd/finger' would have worked. [The version of /etc/bash_completion.d/acroread.sh that is installed starts with: # _filedir : to handle file and directories with spaces in their names. if ! type _filedir &> /dev/null ; then so I don't think that file is overriding /etc/bash_completion's _filedir ...] [Regression Potential] - (#32) low potential for regressions since this bug is related to the interactive command line and would not influence any scripts. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bash 4.2-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Fri May 6 09:48:29 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: bash UpgradeStatus: Upgraded to natty on 2011-04-30 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/778627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 778627] Re: bash completion now quotes shell variable references rather than expanding them
Agreed, this is an annoying bug and has been around far too long (a decade?). ls $top/.ss should give: ls $HOME/.ssh/ "shopt -s direxpand" expands $HOME which is not wanted. "shopt -u complete_fullquote" should give me what I want but has no effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/778627 Title: bash completion now quotes shell variable references rather than expanding them Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Quantal: Fix Released Status in bash source package in Raring: Fix Released Status in bash package in Debian: Fix Released Status in bash package in Fedora: New Bug description: Binary package hint: bash NB! NB! NB! After applying the update to resolve this problem one _also_ must enable direxpand option by issuing: shopt -s direxpand If you do not do this, the variable expansion will not happen. NB! NB! NB! [Impact] Bash-4.2 tries to leave completed directory names as the user typed them, without expanding them to a full pathname. One effect of this is that shell variables used in pathnames being completed (e.g., $HOME) are left unchanged, but the `$' is quoted by readline because it is a special character to the shell. [Test Case] - [Current test case showing expected behavior] Items to address so far: - that $ is escaped less - that direxpand does not expand as expected - that direxpand option is available and if enabled, expands directories with variable names. zef:~/Projects/precise-amd64$ mkdir -p /tmp/testd/finger/toe zef:~/Projects/precise-amd64$ cd /tmp/testd/ zef:/tmp/testd$ td=`pwd` zef:/tmp/testd$ cd ../ zef:/tmp$ ls \$td/finger zef:/tmp$ shopt -s direxpand zef:/tmp$ ls $td/fing zef:/tmp$ ls /tmp/testd/finger/ toe - [Previous Test Case showing non-working bash installation] ~$ mkdir -p /tmp/testd/finger/toe /tmp$ cd /tmp/testd /tmp/testd$ td=`pwd` /tmp/testd$ cd ../ /tmp$ ls $td/fing Type a TAB character at this point, and bash completion makes the line: /tmp$ ls \$td/finger Note that while 'fing' has been expanded to 'finger ' (with a space at the end), the $td variable reference has had the $ character quoted with a backslash. This prevents further extension of the pathname, and in fact makes the command invalid; if I type a newline at this point, I get: ls: cannot access $td/finger: No such file or directory This is not useful behavior. I believe that in Ubuntu 10.10, the $td variable would have been expanded to '/tmp/testd', and subsequent completions starting from '/tmp/testd/finger' would have worked. [The version of /etc/bash_completion.d/acroread.sh that is installed starts with: # _filedir : to handle file and directories with spaces in their names. if ! type _filedir &> /dev/null ; then so I don't think that file is overriding /etc/bash_completion's _filedir ...] [Regression Potential] - (#32) low potential for regressions since this bug is related to the interactive command line and would not influence any scripts. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bash 4.2-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Fri May 6 09:48:29 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: bash UpgradeStatus: Upgraded to natty on 2011-04-30 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/778627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1900068] Re: Upgrade to zeitgeist-1.0.3
As is GNOME Activity Journal ( https://packages.ubuntu.com/source/hirsute/gnome-activity-journal ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1900068 Title: Upgrade to zeitgeist-1.0.3 Status in zeitgeist package in Ubuntu: Fix Released Status in zeitgeist package in Debian: Fix Released Bug description: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity- journal-1-0/4521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
Ok build env set up and tested the starting points. >From that I also see: v5.10 - working v5.11 - failing So from here I think I can try a bisect -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1900068] Re: Upgrade to zeitgeist-1.0.3
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/1.0.3-4ubuntu1 Looks like the new version is in place in Hirsute now. ** Changed in: zeitgeist (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1900068 Title: Upgrade to zeitgeist-1.0.3 Status in zeitgeist package in Ubuntu: Fix Released Status in zeitgeist package in Debian: Fix Released Bug description: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity- journal-1-0/4521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923115] Re: Networkd vs udev nic renaming race condition
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923115 Title: Networkd vs udev nic renaming race condition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] systemd-networkd renames nic just after udev renamed it e.g kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0 kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192 systemd-networkd[511]: ens192: Interface name change detected, ens192 has been renamed to eth0. This cause netplan or the other network management pkg can't find proper nic sometimes. This happens on Bionic Below commit seems to solve this issue. https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b There are bunch of related commits but above one the customer tested it worked. [Test Plan] The customer has issue and they could help us to test this. Internally they already test this and it worked. Please refer to github issue's reproduction step as well. https://github.com/systemd/systemd/issues/7293#issue-272917058 where the test plan is described as: "Reboot a couple of times. Sometimes the interface is renamed correctly. Sometimes it is not." [Where problems could occur] systemd-networkd should be restarted for this patch. systemd-networkd nic renaming could have issue. renaming may not be happening unexpectedly. e.g doesn't rename it properly or rename it when it should do. [Others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923115] Re: Networkd vs udev nic renaming race condition
Customer has provided a positive feedback that the package in -proposed fixed this bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923115 Title: Networkd vs udev nic renaming race condition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] systemd-networkd renames nic just after udev renamed it e.g kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0 kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192 systemd-networkd[511]: ens192: Interface name change detected, ens192 has been renamed to eth0. This cause netplan or the other network management pkg can't find proper nic sometimes. This happens on Bionic Below commit seems to solve this issue. https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b There are bunch of related commits but above one the customer tested it worked. [Test Plan] The customer has issue and they could help us to test this. Internally they already test this and it worked. Please refer to github issue's reproduction step as well. https://github.com/systemd/systemd/issues/7293#issue-272917058 where the test plan is described as: "Reboot a couple of times. Sometimes the interface is renamed correctly. Sometimes it is not." [Where problems could occur] systemd-networkd should be restarted for this patch. systemd-networkd nic renaming could have issue. renaming may not be happening unexpectedly. e.g doesn't rename it properly or rename it when it should do. [Others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
I was trying mainline builds [1] to pinpoint the kernel change (if any). I had a few totally failing ones which stalled me a bit, but eventually I can show this helpful list: v5.8 - working v5.10 - working v5.10.31 - working v5.11 - failing v5.11.15 - failing v5.12-rc8 - failing So it isn't a >5.10 change that is backported into 5.10 stable. And it isn't something that was fixed in later master or 5.11 stable releases. If you want you could bisect the kernel for this, my env is great for testing but very bad for kernel builds. Do you want to throw kernels my way or should I try to build my own in another place? [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1925216] Re: confusing but harmless warning messages printed about syscalls
** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925216 Title: confusing but harmless warning messages printed about syscalls Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] systemd prints messages that complain about system calls such as: /lib/systemd/system/systemd-journald.service:33: Failed to parse system call, ignoring: pidfd_getfd [test case] boot bionic system with 4.15 kernel that does not support pidfd_getfd syscall [regression potential] any regression would prevent correct configuration of seccomp syscall filters, and/or failure to load/parse unit files that contain SystemCallFilter= directives [scope] this is needed only for b this is fixed upstream by commit 13d92c6300edbb1369f97c2e1bef4c4096de8ddb which was included in v238, so this is fixed in focal and later this is not needed for x as seccomp handling is completely different in that older release [other info] as the warning states, the invalid system call is ignored, which is the correct action, and the patch to fix this just changes the log to debug instead of warning (along with consolidation of several flag params into a single flag enum). Thus, no actual change in behavior should occur (other than logging the messages as debug instead of warning). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925216] [NEW] confusing but harmless warning messages printed about syscalls
Public bug reported: [impact] systemd prints messages that complain about system calls such as: /lib/systemd/system/systemd-journald.service:33: Failed to parse system call, ignoring: pidfd_getfd [test case] boot bionic system with 4.15 kernel that does not support pidfd_getfd syscall [regression potential] any regression would prevent correct configuration of seccomp syscall filters, and/or failure to load/parse unit files that contain SystemCallFilter= directives [scope] this is needed only for b this is fixed upstream by commit 13d92c6300edbb1369f97c2e1bef4c4096de8ddb which was included in v238, so this is fixed in focal and later this is not needed for x as seccomp handling is completely different in that older release [other info] as the warning states, the invalid system call is ignored, which is the correct action, and the patch to fix this just changes the log to debug instead of warning (along with consolidation of several flag params into a single flag enum). Thus, no actual change in behavior should occur (other than logging the messages as debug instead of warning). ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Bionic) Importance: Low Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925216 Title: confusing but harmless warning messages printed about syscalls Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Bug description: [impact] systemd prints messages that complain about system calls such as: /lib/systemd/system/systemd-journald.service:33: Failed to parse system call, ignoring: pidfd_getfd [test case] boot bionic system with 4.15 kernel that does not support pidfd_getfd syscall [regression potential] any regression would prevent correct configuration of seccomp syscall filters, and/or failure to load/parse unit files that contain SystemCallFilter= directives [scope] this is needed only for b this is fixed upstream by commit 13d92c6300edbb1369f97c2e1bef4c4096de8ddb which was included in v238, so this is fixed in focal and later this is not needed for x as seccomp handling is completely different in that older release [other info] as the warning states, the invalid system call is ignored, which is the correct action, and the patch to fix this just changes the log to debug instead of warning (along with consolidation of several flag params into a single flag enum). Thus, no actual change in behavior should occur (other than logging the messages as debug instead of warning). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
** Also affects: udev (Ubuntu Hirsute) Importance: Critical Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
FYI [15:43] cpaelzer, this may be related https://github.com/systemd/systemd/blob/4d484e14bb9864cef1d124885e625f33bf31e91c/NEWS#L5 And indeed it is an interesting read, but for now the question is why only with 5.11@s390x then? Maybe there is something small to get this back in line? No one is proposing to change "all rules" in the last minute :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924851] Re: intel display drivers not working
*** This bug is a duplicate of bug 1905466 *** https://bugs.launchpad.net/bugs/1905466 ** This bug is no longer a duplicate of bug 1924889 i915 graphics driver not loading for Rocket Lake i7-11700K [8086:4c8a] ** This bug has been marked a duplicate of bug 1905466 drm/i915: Drop force_probe requirement for Rocket Lake -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924851 Title: intel display drivers not working Status in xorg package in Ubuntu: New Bug description: Getting llvmpipe (LLVM 11.0.0, 256 bits) as display instead of intel drivers. Only available Resolution 1024X768 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 17 18:35:34 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.8.0-50-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2021-04-17 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. B560M DS3H AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=f0b245ca-169e-4fdc-80d3-14f66691147b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B560M DS3H AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF1:bd01/11/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560MDS3HAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560MDS3HAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B560 MB dmi.product.name: B560M DS3H AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
** Tags added: groovy hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in shadow package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
Hirsute - udevadm # attach KERNEL[319.020043] add /devices/css0/0.0.0005 (css) KERNEL[319.020088] add /devices/css0/0.0.0005/0.0.0005 (ccw) KERNEL[319.020103] bind /devices/css0/0.0.0005/0.0.0005 (ccw) UDEV [319.022297] add /devices/css0/0.0.0005 (css) UDEV [319.022802] add /devices/css0/0.0.0005/0.0.0005 (ccw) UDEV [319.023039] bind /devices/css0/0.0.0005/0.0.0005 (ccw) KERNEL[319.025073] add /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) UDEV [319.025527] add /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) KERNEL[319.027524] add /devices/virtual/bdi/252:32 (bdi) UDEV [319.028389] add /devices/virtual/bdi/252:32 (bdi) KERNEL[319.048685] add /devices/css0/0.0.0005/0.0.0005/virtio5/block/vdc (block) KERNEL[319.048743] bind /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) UDEV [319.072936] add /devices/css0/0.0.0005/0.0.0005/virtio5/block/vdc (block) UDEV [319.075862] bind /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) # detach Groovy - udevadm # attach KERNEL[719.986637] add /devices/css0/0.0.0005 (css) KERNEL[719.986669] add /devices/css0/0.0.0005/0.0.0005 (ccw) KERNEL[719.986685] bind /devices/css0/0.0.0005/0.0.0005 (ccw) UDEV [719.988667] add /devices/css0/0.0.0005 (css) KERNEL[719.992750] add /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) KERNEL[719.992757] add /devices/virtual/bdi/252:32 (bdi) UDEV [719.993298] add /devices/css0/0.0.0005/0.0.0005 (ccw) UDEV [719.993520] bind /devices/css0/0.0.0005/0.0.0005 (ccw) UDEV [719.994097] add /devices/virtual/bdi/252:32 (bdi) UDEV [719.995568] add /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) KERNEL[720.009523] add /devices/css0/0.0.0005/0.0.0005/virtio5/block/vdc (block) KERNEL[720.009544] bind /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) UDEV [720.058301] add /devices/css0/0.0.0005/0.0.0005/virtio5/block/vdc (block) UDEV [720.059128] bind /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) # detach KERNEL[780.673663] remove /devices/virtual/bdi/252:32 (bdi) KERNEL[780.673928] remove /devices/css0/0.0.0005/0.0.0005/virtio5/block/vdc (block) UDEV [780.676469] remove /devices/css0/0.0.0005/0.0.0005/virtio5/block/vdc (block) UDEV [780.678185] remove /devices/virtual/bdi/252:32 (bdi) KERNEL[780.708055] unbind /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) KERNEL[780.708078] remove /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) KERNEL[780.708088] unbind /devices/css0/0.0.0005/0.0.0005 (ccw) KERNEL[780.708101] remove /devices/css0/0.0.0005/0.0.0005 (ccw) KERNEL[780.708109] unbind /devices/css0/0.0.0005 (css) KERNEL[780.708117] remove /devices/css0/0.0.0005 (css) UDEV [780.708779] unbind /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) UDEV [780.709099] remove /devices/css0/0.0.0005/0.0.0005/virtio5 (virtio) UDEV [780.709397] unbind /devices/css0/0.0.0005/0.0.0005 (ccw) UDEV [780.709670] remove /devices/css0/0.0.0005/0.0.0005 (ccw) UDEV [780.709971] unbind /devices/css0/0.0.0005 (css) UDEV [780.710194] remove /devices/css0/0.0.0005 (css) The events on attach are exactly the same, but in slightly different order. On detach no events are fired at all - so I guess userspace isn't guilty of not doing anything if there is no event? As far as i am right now I'd point to the guest kernel, let me try a few other kernels ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc
[Touch-packages] [Bug 1925215] [NEW] System completely freezes and requires reboot
Public bug reported: The OS spontaneously froze whilst doing some work (firefox, VMs). I can't find anything suspect in the logs at this stage. I will keep an eye out for this issue but would like advise on what to check for, any tools I should install and commands to run when it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 20 14:28:46 2021 ExecutablePath: /usr/lib/systemd/systemd InstallationDate: Installed on 2021-04-16 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925215 Title: System completely freezes and requires reboot Status in systemd package in Ubuntu: New Bug description: The OS spontaneously froze whilst doing some work (firefox, VMs). I can't find anything suspect in the logs at this stage. I will keep an eye out for this issue but would like advise on what to check for, any tools I should install and commands to run when it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 20 14:28:46 2021 ExecutablePath: /usr/lib/systemd/systemd InstallationDate: Installed on 2021-04-16 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
Hirsute - dmesg # attach [ 264.065866] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 264.065906] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0 [ 264.099347] virtio_blk virtio5: [vdc] 385 512-byte logical blocks (197 kB/193 KiB) # detach [ 289.702243] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 289.702267] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0 Groovy - dmesg # attach [ 719.712747] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 719.712758] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0 [ 719.745538] virtio_blk virtio5: [vdc] 385 512-byte logical blocks (197 kB/193 KiB) [ 719.745542] vdc: detected capacity change from 0 to 197120 # detach [ 780.425222] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 780.425233] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0 There is a difference in hirsute missing the capacity change. The newer kernel might immediately do that instead of detecting as zero and then bumping it up. The sizes reported in the Hirsute guest are correct (e.g. 20M for a 20M zfs case). So this might be a red herring unless the missing message makes you very suspicious -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux
[Touch-packages] [Bug 1891953] Re: CVE-2019-8936
This bug was fixed in the package ntp - 1:4.2.8p12+dfsg-3ubuntu4.20.10.1 --- ntp (1:4.2.8p12+dfsg-3ubuntu4.20.10.1) groovy-security; urgency=medium * SECURITY UPDATE: Null dereference attack in mode 6 packet (LP: #1891953) - debian/patches/CVE-2019-8936.patch: Guard against operations on NULL pointer in ntpd/ntp_control.c. - CVE-2019-8936 * Fix FTBFS with GCC-10 - debian/rules: add -fcommon flag to CFLAGS -- Brian Morton Fri, 27 Nov 2020 16:10:51 -0500 ** Changed in: ntp (Ubuntu Groovy) Status: Confirmed => Fix Released ** Changed in: ntp (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1891953 Title: CVE-2019-8936 Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Bionic: Fix Released Status in ntp source package in Focal: Fix Released Status in ntp source package in Groovy: Fix Released Status in ntp package in Debian: Fix Released Bug description: It was discovered that the fix for CVE-2018-7182 introduced a NULL pointer dereference into NTP. An attacker could use this vulnerability to cause a denial of service (crash). https://people.canonical.com/~ubuntu- security/cve/2019/CVE-2019-8936.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891953] Re: CVE-2019-8936
This bug was fixed in the package ntp - 1:4.2.8p12+dfsg-3ubuntu4.20.04.1 --- ntp (1:4.2.8p12+dfsg-3ubuntu4.20.04.1) focal-security; urgency=medium * SECURITY UPDATE: Null dereference attack in mode 6 packet (LP: #1891953) - debian/patches/CVE-2019-8936.patch: Guard against operations on NULL pointer in ntpd/ntp_control.c. - CVE-2019-8936 -- Brian Morton Fri, 27 Nov 2020 16:10:51 -0500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1891953 Title: CVE-2019-8936 Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Bionic: Fix Released Status in ntp source package in Focal: Fix Released Status in ntp source package in Groovy: Fix Released Status in ntp package in Debian: Fix Released Bug description: It was discovered that the fix for CVE-2018-7182 introduced a NULL pointer dereference into NTP. An attacker could use this vulnerability to cause a denial of service (crash). https://people.canonical.com/~ubuntu- security/cve/2019/CVE-2019-8936.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490168/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490166/+files/SystemdDelta.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490167/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490165/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490164/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490163/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490162/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490161/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
This even happens with the most common image-file backed disks which further simplifies the repro: $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc ** Description changed: Repro: - # Prep a backing disk - $ sudo fallocate -l 100M /tmp/zfsbase1 - $ sudo fallocate -l 100M /tmp/zfsbase2 - $ sudo zpool create zfsmirrortest mirror /tmp/zfsbase1 /tmp/zfsbase2 - $ sudo zfs create -V 20M zfsmirrortest/vol1 - $ cat > disk-zfs.xml << EOF - - - - - - EOF - # Get a guest + #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily - # Attach and Detach disk - $ virsh attach-device h disk-zfs.xml - Device attached successfully - $ virsh detach-device h disk-zfs.xml - Device detached successfully + + #2 Attach and Detach disk + $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M + $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc + $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h - Target Source + Target Source -- - vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow - vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow - + vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow + vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk - ... - vdc252:32 0 20M 0 disk + ... + vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc - - The result above was originally found with hirsute-guest@hirsute-host on s390x + The result above was originally found with hirsute-guest@hirsute-host on + s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x - => Guest version dependent not Host/Hipervisor dependent + => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added - => not type dependent + => not type dependent I do NOT see the same on x86. - => Arch dependent ?? + => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! ** Tags added: apport-collected uec-images ** Description changed: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/
[Touch-packages] [Bug 1925211] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490160/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490159/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1925211/+attachment/5490158/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1925211 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: # Prep a backing disk $ sudo fallocate -l 100M /tmp/zfsbase1 $ sudo fallocate -l 100M /tmp/zfsbase2 $ sudo zpool create zfsmirrortest mirror /tmp/zfsbase1 /tmp/zfsbase2 $ sudo zfs create -V 20M zfsmirrortest/vol1 $ cat > disk-zfs.xml << EOF EOF # Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily # Attach and Detach disk $ virsh attach-device h disk-zfs.xml Device attached successfully $ virsh detach-device h disk-zfs.xml Device detached successfully From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] [NEW] Hot-unplug of disks leaves broken block devices around in Hirsute
Public bug reported: Repro: # Prep a backing disk $ sudo fallocate -l 100M /tmp/zfsbase1 $ sudo fallocate -l 100M /tmp/zfsbase2 $ sudo zpool create zfsmirrortest mirror /tmp/zfsbase1 /tmp/zfsbase2 $ sudo zfs create -V 20M zfsmirrortest/vol1 $ cat > disk-zfs.xml << EOF EOF # Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily # Attach and Detach disk $ virsh attach-device h disk-zfs.xml Device attached successfully $ virsh detach-device h disk-zfs.xml Device detached successfully >From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: udev (Ubuntu) Importance: Critical Status: New ** Tags: hirsute ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: udev (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: Repro: # Prep a backing disk $ sudo fallocate -l 100M /tmp/zfsbase1 $ sudo fallocate -l 100M /tmp/zfsbase2 $ sudo zpool create zfsmirrortest mirror /tmp/zfsbase1 /tmp/zfsbase2 $ sudo zfs create -V 20M zfsmirrortest/vol1 $ cat > disk-zfs.xml << EOF EOF # Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily # Attach and Detach disk $ virsh attach-device h disk-zfs.xml Device attached successfully $ virsh detach-device h disk-zfs.xml Device detached successfully From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I haven't got any pulseaudio updates on 21.04, to which version of ubuntu was the fix released to? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
When problem happens, please run each group of SET_COEF_INDEX and SET_PROC_COEF, then test if the audio changes normal or not: sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x78 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x003e // test if audio changes normal or not sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x77 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0015 // test if audio changes normal or not sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xf000 //... sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x3b sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x60d9 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x33 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8580 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1b sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0a6b sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1a sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8003 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0f sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x02a2 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0e sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x65c0 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x06 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x6115 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Tags removed: verification-done verification-done-bionic verification-done-focal verification-done-groovy ** Tags added: architecture-s39064 bugnameltc-192453 severity-high targetmilestone-inin2104 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E:
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
** Attachment added: "alsa-info-good.txt.yy9imLvHvj" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+attachment/5490137/+files/alsa-info-good.txt.yy9imLvHvj -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
** Attachment added: "alsa-info-bad.txt.k4EOeiWnvC" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+attachment/5490136/+files/alsa-info-bad.txt.k4EOeiWnvC -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
Please find the requested output attached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
Guest is Hirsute to have
libc6:s390x2.33-0ubuntu5 s390x
The following (not optimized for speed but readability) gives us a
simple environment-matrix for comparisons:
for r in xenial bionic focal groovy hirsute; do
uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=s390x label=daily release=${r};
uvt-kvm create --host-passthrough --password=ubuntu ${r}-test-nspawn
release=${r} arch=s390x label=daily;
uvt-kvm wait ${r}-test-nspawn
uvt-kvm ssh ${r}-test-nspawn "sudo apt update"
uvt-kvm ssh ${r}-test-nspawn "sudo apt upgrade -y"
uvt-kvm ssh ${r}-test-nspawn "wget
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-s390x-root.tar.xz;
uvt-kvm ssh ${r}-test-nspawn "mkdir h"
uvt-kvm ssh ${r}-test-nspawn "sudo tar -xzf
hirsute-server-cloudimg-s390x-root.tar.xz -C h";
uvt-kvm ssh ${r}-test-nspawn "sudo apt install -y systemd-container"
uvt-kvm ssh ${r}-test-nspawn "sudo reboot";
sleep 5s
uvt-kvm wait ${r}-test-nspawn
done
Test (as before) is:
$ cd h
$ sudo systemd-nspawn
$ bash -c 'test -x /usr/bin/gpg || echo Fail'
Out of that I can confirm (and further limit releases to just bionic) that on
s390x we have:
Xenial - 4.4.0-210/229-4ubuntu21.31 - works
Bionic - 4.15.0-142/237-3ubuntu10.46 - fails
Focal - 5.4.0-72/245.4-4ubuntu3.6 - works
Groovy - 5.8.0-50/246.6-1ubuntu1.3 - works
Hirsute - 5.11.0-16/247.3-3ubuntu3 - works
Next I split the Bionic case to for a few usual suspects (kernel/systemd/glibc):
Already on step #1 Kernel I found something:
Bionic - 4.15.0-142/237-3ubuntu10.46 - fails
Bionic - 5.4.0-72/237-3ubuntu10.46 - works
Ok so the new kernel fixes it (whatever it is) so what about things in proposed
already:
There is a new 4.15 kernel and a new systemd
Bionic - 4.15.0-143/237-3ubuntu10.47 - fails
So none of the builds in proposed has the fix, but something between
4.15 and 5.4 kernels fixes it. That might also be the reason why the
other releases are fine - the kernel levels are either >=5.4 (fixed) or
<4.15 (not having the issue).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1916485
Title:
test -x fails inside shell scripts in containers
Status in docker.io package in Ubuntu:
New
Status in glibc package in Ubuntu:
Opinion
Status in libseccomp package in Ubuntu:
Fix Committed
Status in runc package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in docker.io source package in Xenial:
New
Status in libseccomp source package in Xenial:
New
Status in runc source package in Xenial:
New
Status in systemd source package in Xenial:
Invalid
Status in docker.io source package in Bionic:
New
Status in libseccomp source package in Bionic:
New
Status in runc source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in docker.io source package in Focal:
New
Status in libseccomp source package in Focal:
New
Status in runc source package in Focal:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in docker.io source package in Groovy:
New
Status in libseccomp source package in Groovy:
New
Status in runc source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Status in docker.io source package in Hirsute:
New
Status in libseccomp source package in Hirsute:
Fix Committed
Status in runc source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
Status in systemd package in Debian:
Fix Released
Bug description:
(SRU template for systemd)
[impact]
bash (and some other shells) builtin test command -x operation fails
[test case]
on any affected host system, start nspawn container, e.g.:
$ sudo apt install systemd-container
$ wget
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
$ mkdir h
$ cd h
$ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
$ sudo systemd-nspawn
Then from a bash shell, verify if test -x works:
root@h:~# ls -l /usr/bin/gpg
-rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
root@h:~# test -x /usr/bin/gpg || echo "fail"
fail
[regression potential]
any regression would likely occur during a syscall, most likely
faccessat2(), or during other syscalls.
[scope]
this is needed for b/f
this is fixed upstream by commit
bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
this is fixed in h
this was pulled into Debian at version 246.2 in commit
e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g
in x, the entire systemd seccomp code is completely different and the
patch doesn't apply, nor does it appear to be needed, as the problem
doesn't reproduce in a h container under x.
[Touch-packages] [Bug 1923358] Re: Other servers doesn't display server list (Software Updater)
** Package changed: update-manager (Ubuntu) => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1923358 Title: Other servers doesn't display server list (Software Updater) Status in software-properties package in Ubuntu: Incomplete Bug description: Using Settings and then trying to choose other server doesn't do anything. It should display the list of available other servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1923358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923464] Re: ideally should boot rootfs from a matching hard drive
This proposal seems somewhat incompatible with our resilient boot specification. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923464 Title: ideally should boot rootfs from a matching hard drive Status in cloud-images: New Status in grub2 package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: New Bug description: Ideally we should strive to boot rootfs from a matching hard drive. I.e. if we are booting rootfs by UUID, we should try to find the one that came from the same drive as where ESP (UEFI) came from, or u-boot spl / u-boot got loaded from (loader1/loader2). Such that for example, when booted from external usb stick, rootfs from there is mounted. Or when booted from internal drive whilst a dd backup is attached over usb, rootfs is loaded from the internal drive not from the usb attached backup. This would need: * u-boot to export the drive it loaded extlinux.conf / bootscript from, and pass it on kernel command line * grub to export the device UUID it got loaded from (from the BootServices EFI table) and pass it on the kernel command line or via runtime EFI variable * sdboot already does that I believe, but not sure if initramfs-tools consumes the sdboot provided information * initramfs-tools to consume above and sort the discovered devices based on that, when deciding what to mount as rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923358] [NEW] Other servers doesn't display server list (Software Updater)
You have been subscribed to a public bug: Using Settings and then trying to choose other server doesn't do anything. It should display the list of available other servers. ** Affects: software-properties (Ubuntu) Importance: Low Status: Incomplete -- Other servers doesn't display server list (Software Updater) https://bugs.launchpad.net/bugs/1923358 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925025] Re: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Thanks for your bug report. Unfortunately, it lacks any actionable information, because we don't know why packagekit is in a very bad inconsistent state. If you figure out the cause for this, please let us know. Thanks! ** Changed in: packagekit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1925025 Title: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in packagekit package in Ubuntu: Incomplete Bug description: no further information ProblemType: Package DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 19 14:17:46 2021 DuplicateSignature: package:packagekit:1.1.13-2ubuntu1.1 Setting up libcurl4:amd64 (7.68.0-1ubuntu2.5) ... dpkg: error processing package packagekit (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-22 (209 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: packagekit Title: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1925025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925088] [NEW] Headphones don't work when speakers work
You have been subscribed to a public bug: Hi! I have problem with front panel audio output connector. Speakers still work after my headphones is connected. Everything correctly works on windows 10. I selected headphones in Settings -> Sound -> Output, but speakers were continuing working. PulseAudio Volume Control didn't help too. I've tried to change configuration and select headphones as output devices. When i disconnected speakers, headphones weren't still working. I've done all list from https://help.ubuntu.com/community/SoundTroubleshooting and haven't found any problems. pacmd - https://pastebin.com/Jkfqt4ft aplay - https://pastebin.com/NGq37fVb snd - https://pastebin.com/7bS0GKzc lspci - https://pastebin.com/Z6CYmRU2 alsa - http://alsa-project.org/db/?f=b5701e36e1510cb211fd3047c36598da27fef2d9 My hardware: CPU - Intel i9 10900k Mobo - Asus z590-e with the latest bios. GPU - Nvidia RTX 3070 If you need some additional information, I will provide it. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Headphones don't work when speakers work https://bugs.launchpad.net/bugs/1925088 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924184] Re: drive not showing
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924184 Title: drive not showing Status in xorg package in Ubuntu: Incomplete Bug description: i coudnt find graphic drive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 03:35:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0844] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:0844] InstallationDate: Installed on 2021-04-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 3578 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=7cf915de-bb29-49e2-a9cc-0079efc75ed1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 01Y7V4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd01/09/2020:br1.10:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3578 dmi.product.sku: 0844 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925088] Re: Headphones don't work when speakers work
** Package changed: ubuntu => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1925088 Title: Headphones don't work when speakers work Status in pulseaudio package in Ubuntu: New Bug description: Hi! I have problem with front panel audio output connector. Speakers still work after my headphones is connected. Everything correctly works on windows 10. I selected headphones in Settings -> Sound -> Output, but speakers were continuing working. PulseAudio Volume Control didn't help too. I've tried to change configuration and select headphones as output devices. When i disconnected speakers, headphones weren't still working. I've done all list from https://help.ubuntu.com/community/SoundTroubleshooting and haven't found any problems. pacmd - https://pastebin.com/Jkfqt4ft aplay - https://pastebin.com/NGq37fVb snd - https://pastebin.com/7bS0GKzc lspci - https://pastebin.com/Z6CYmRU2 alsa - http://alsa-project.org/db/?f=b5701e36e1510cb211fd3047c36598da27fef2d9 My hardware: CPU - Intel i9 10900k Mobo - Asus z590-e with the latest bios. GPU - Nvidia RTX 3070 If you need some additional information, I will provide it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-online-accounts (Ubuntu) Status: Confirmed => Triaged ** Also affects: gnome-online-accounts via https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/17 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925141] [NEW] There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
Public bug reported: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic focal xenial ** Also affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in shadow package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press key, enter some letters in capitals 5. Press key again, enter some letters in lowercase Actual results: * CapsLock key switches on CapsLock LED, the LED state indicates current CapsLock key function Expected results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
** Changed in: pulseaudio Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
We have also pushed out a new livecd-rootfs that manually adds ubuntu- raspi-settings as a dependency of the server images (temporary before we switch to using seeds). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Hirsute: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
