[Touch-packages] [Bug 1921664] Re: Recent update broke qemu-system-riscv64
Before going into any rebuild-mania I wanted to further reduce how much builds I'll need I've changed "qemu-system-misc" but kept the others like "qemu-block-extra" and "qemu-system-common" - that mostly means /usr/bin/qemu-system-riscv64 is replaced but all the roms and modules (can't load then). Reminder: all these are the same effective source I've done this two ways: All good pkg (1:5.2+dfsg-9ubuntu1) + emu bad (1:5.2+dfsg-9ubuntu2~hirsuteppa3): All bad pkg (1:5.2+dfsg-9ubuntu2~hirsuteppa3) + emu good (1:5.2+dfsg-9ubuntu1): 3/3 fails That made me wonder and I also got: All good pkg (1:5.2+dfsg-9ubuntu1): 5/5 fails (formerly this was known good) Sadly - the formerly seen non-distinct results continued. For example I did at one point end up with all packages of version "1:5.2+dfsg- 9ubuntu1" (that is known good) failing in 5/5 tests repeatedly. So I'm not sure how much the results are worth anymore :-/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Coroutines are racy for risc64 emu on arm64 - crash on Assertion Status in QEMU: New Status in qemu package in Ubuntu: Confirmed Bug description: Note: this could as well be "riscv64 on arm64" for being slow@slow and affect other architectures as well. The following case triggers on a Raspberry Pi4 running with arm64 on Ubuntu 21.04 [1][2]. It might trigger on other environments as well, but that is what we have seen it so far. $ wget https://github.com/carlosedp/riscv-bringup/releases/download/v1.0/UbuntuFocal-riscv64-QemuVM.tar.gz $ tar xzf UbuntuFocal-riscv64-QemuVM.tar.gz $ ./run_riscvVM.sh (wait ~2 minutes) [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting udev Kernel Device Manager... qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. This is often, but not 100% reproducible and the cases differ slightly we see either of: - qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. - qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. Rebuilding working cases has shown to make them fail, as well as rebulding (or even reinstalling) bad cases has made them work. Also the same builds on different arm64 CPUs behave differently. TL;DR: The full list of conditions influencing good/bad case here are not yet known. [1]: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#1-overview [2]: http://cdimage.ubuntu.com/daily-preinstalled/pending/hirsute-preinstalled-desktop-arm64+raspi.img.xz --- --- original report --- --- I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days ago broke it. Now when I launch it, it hits an assertion: OpenSBI v0.6 _ _ / __ \ / | _ \_ _| | | | |_ __ ___ _ __ | (___ | |_) || | | | | | '_ \ / _ \ '_ \ \___ \| _ < | | | |__| | |_) | __/ | | |) | |_) || |_ \/| .__/ \___|_| |_|_/|/_| | | |_| ... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 618 bytes read in 2 ms (301.8 KiB/s) RISC-V Qemu Boot Options 1: Linux kernel-5.5.0-dirty 2: Linux kernel-5.5.0-dirty (recovery mode) Enter choice: 1:Linux kernel-5.5.0-dirty Retrieving file: /boot/initrd.img-5.5.0-dirty qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. ./run.sh: line 31: 1604 Aborted (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin -device virtio-blk-devi ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04 (fully updated). Think you have everything already, but just in case: $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ uname -a Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux (note this is a VM running on macOS/M1) $ apt-cache policy qemu qemu: Installed: 1:5.2+dfsg-9ubuntu1 Candidate: 1:5.2+dfsg-9ubuntu1 Version table: *** 1:5.2+dfsg-9ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 Packages 100 /var/lib/dpkg/status ProblemType: Bug Distr
[Touch-packages] [Bug 1921664] Re: Recent update broke qemu-system-riscv64
I've continued on one of the former approaches and started a full Ubuntu style package build of the full source on arm64 in Groovy and Hirsute. But it fell apart going out of space and I'm slowly getting hesitant to spend more HW and time on this without a) at least asking upstream if it is any known issue b) not seeing it on a less edge case than risc emulation @ arm64 But I think by now we can drop the formerly "usual suspects" again as I have had plenty of fails with the former good builds. It is just racy and a yet unknown amount of conditions seems to influence this race. If we are later on finding some evidence we can add them back ... ** No longer affects: glibc (Ubuntu) ** No longer affects: binutils (Ubuntu) ** No longer affects: gcc-10 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Coroutines are racy for risc64 emu on arm64 - crash on Assertion Status in QEMU: New Status in qemu package in Ubuntu: Confirmed Bug description: Note: this could as well be "riscv64 on arm64" for being slow@slow and affect other architectures as well. The following case triggers on a Raspberry Pi4 running with arm64 on Ubuntu 21.04 [1][2]. It might trigger on other environments as well, but that is what we have seen it so far. $ wget https://github.com/carlosedp/riscv-bringup/releases/download/v1.0/UbuntuFocal-riscv64-QemuVM.tar.gz $ tar xzf UbuntuFocal-riscv64-QemuVM.tar.gz $ ./run_riscvVM.sh (wait ~2 minutes) [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting udev Kernel Device Manager... qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. This is often, but not 100% reproducible and the cases differ slightly we see either of: - qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. - qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. Rebuilding working cases has shown to make them fail, as well as rebulding (or even reinstalling) bad cases has made them work. Also the same builds on different arm64 CPUs behave differently. TL;DR: The full list of conditions influencing good/bad case here are not yet known. [1]: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#1-overview [2]: http://cdimage.ubuntu.com/daily-preinstalled/pending/hirsute-preinstalled-desktop-arm64+raspi.img.xz --- --- original report --- --- I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days ago broke it. Now when I launch it, it hits an assertion: OpenSBI v0.6 _ _ / __ \ / | _ \_ _| | | | |_ __ ___ _ __ | (___ | |_) || | | | | | '_ \ / _ \ '_ \ \___ \| _ < | | | |__| | |_) | __/ | | |) | |_) || |_ \/| .__/ \___|_| |_|_/|/_| | | |_| ... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 618 bytes read in 2 ms (301.8 KiB/s) RISC-V Qemu Boot Options 1: Linux kernel-5.5.0-dirty 2: Linux kernel-5.5.0-dirty (recovery mode) Enter choice: 1:Linux kernel-5.5.0-dirty Retrieving file: /boot/initrd.img-5.5.0-dirty qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. ./run.sh: line 31: 1604 Aborted (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin -device virtio-blk-devi ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04 (fully updated). Think you have everything already, but just in case: $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ uname -a Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux (note this is a VM running on macOS/M1) $ apt-cache policy qemu qemu: Installed: 1:5.2+dfsg-9ubuntu1 Candidate: 1:5.2+dfsg-9ubuntu1 Version table: *** 1:5.2+dfsg-9ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: qemu 1:5.2+dfsg-9ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic aarc
[Touch-packages] [Bug 1921664] Re: Recent update broke qemu-system-riscv64
Furthermore I've built (again the very same source) in groovy as 5.2+dfsg-9ubuntu2~groovyppa1 in the same PPA. This build works as well in my tries. So I have the same code as in "1:5.2+dfsg-9ubuntu1" three times now: 1. [1] => built 2021-03-23 in Hirsute => works 2. [2] => built 2021-04-12 in Hirsute => fails 3. [3] => built 2021-04-13 in Groovy => works [1]: https://launchpad.net/ubuntu/+source/qemu/1:5.2+dfsg-9ubuntu1/+build/21196422 [2]: https://launchpad.net/~paelzer/+archive/ubuntu/lp-1921664-testbuilds-rebuildold/+build/21392458 [3]: https://launchpad.net/~paelzer/+archive/ubuntu/lp-1921664-testbuilds-rebuildold/+build/21394457 With the two results above, I expected as next step could spin up a (git based) Groovy and a Hirsute build environment. I'd do a build from git (and optimize a bit for build speed). If these builds confirm the above results of [2] and [3] then I should be able to upgrade the components in the Groovy build environment one by one to Hirsute To identify which one is causing the breakage... But unfortunately I have to start to challenge the reproducibility and that is breaking the camels back here. Without that I can't go on well, and as sad (it is a real issue) as it is it is riscv64 emulation on an arm64 host really isn't the most common use case. So I'm unsure how much time I can spend on this. Maybe I have looked at this from the wrong angle, let me try something else before I give up ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Coroutines are racy for risc64 emu on arm64 - crash on Assertion Status in QEMU: New Status in qemu package in Ubuntu: Confirmed Bug description: Note: this could as well be "riscv64 on arm64" for being slow@slow and affect other architectures as well. The following case triggers on a Raspberry Pi4 running with arm64 on Ubuntu 21.04 [1][2]. It might trigger on other environments as well, but that is what we have seen it so far. $ wget https://github.com/carlosedp/riscv-bringup/releases/download/v1.0/UbuntuFocal-riscv64-QemuVM.tar.gz $ tar xzf UbuntuFocal-riscv64-QemuVM.tar.gz $ ./run_riscvVM.sh (wait ~2 minutes) [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting udev Kernel Device Manager... qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. This is often, but not 100% reproducible and the cases differ slightly we see either of: - qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. - qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. Rebuilding working cases has shown to make them fail, as well as rebulding (or even reinstalling) bad cases has made them work. Also the same builds on different arm64 CPUs behave differently. TL;DR: The full list of conditions influencing good/bad case here are not yet known. [1]: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#1-overview [2]: http://cdimage.ubuntu.com/daily-preinstalled/pending/hirsute-preinstalled-desktop-arm64+raspi.img.xz --- --- original report --- --- I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days ago broke it. Now when I launch it, it hits an assertion: OpenSBI v0.6 _ _ / __ \ / | _ \_ _| | | | |_ __ ___ _ __ | (___ | |_) || | | | | | '_ \ / _ \ '_ \ \___ \| _ < | | | |__| | |_) | __/ | | |) | |_) || |_ \/| .__/ \___|_| |_|_/|/_| | | |_| ... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 618 bytes read in 2 ms (301.8 KiB/s) RISC-V Qemu Boot Options 1: Linux kernel-5.5.0-dirty 2: Linux kernel-5.5.0-dirty (recovery mode) Enter choice: 1:Linux kernel-5.5.0-dirty Retrieving file: /boot/initrd.img-5.5.0-dirty qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. ./run.sh: line 31: 1604 Aborted (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin -device virtio-blk-devi ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04 (fully updated). Think you have everything already, but just in case: $ lsb_release -rd Description:Ubuntu Hir
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275#note_796719:
```
if (ret < 0) {
#ifdef DEBUG
const bool color = INTEL_DEBUG & DEBUG_COLOR;
fprintf(stderr, "%siris: Failed to submit batchbuffer: %-80s%s\n",
color ? "\e[1;41m" : "", strerror(-ret), color ? "\e[0m" : "");
#endif
abort();
}
```
which means `submit_batch` failed, which means `DRM_IOCTL_I915_GEM_EXECBUFFER2`
failed.
(keep a note here)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4275
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
New
Status in mesa package in Ubuntu:
New
Bug description:
I run checkbox job
com.canonical.certification::memory/memory_stress_ng on focal, and the
xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers
This bug was fixed in the package libseccomp - 2.5.1-1ubuntu1~16.04.1 --- libseccomp (2.5.1-1ubuntu1~16.04.1) xenial; urgency=medium * Updated to new upstream 2.5.1 version for updated syscalls support (LP: #1891810) - Removed the following patches that are now included in the new version: + d/p/fix-aarch64-syscalls.patch + d/p/db-consolidate-some-of-the-code-which-adds-rules.patch + d/p/db-add-shadow-transactions.patch - Deleted the patch to add a local copy of architecture specific header files from linux-libc-dev/focal as this is not needed anymore + d/p/add-5.4-local-syscall-headers.patch - debian/control: Added gperf to Build-Depends as this is now required by upstream - debian/libseccomp2.symbols: Added new symbols * Add system call headers for powerpc required for backport to xenial - d/p/add-5.8-powerpc-syscall-headers.patch -- Alex Murray Mon, 01 Mar 2021 13:50:00 +1030 ** Changed in: libseccomp (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in libseccomp source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in libseccomp source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1923686] Re: Ubuntu 20.10 Network Issue
It's not clear what exactly you are trying to do, or what is changing that you don't like. maybe you should provide both 'good' and 'bad' data for comparison, like the output of 'ip a' and 'ip r' ** 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/1923686 Title: Ubuntu 20.10 Network Issue Status in systemd package in Ubuntu: Incomplete Bug description: I have a server running Ubuntu 20.10 running VMware Workstation 16 which loses its default route. I keep setting it manually but every 30 minutes or so, it reverts to the incorrect route. This server has 5 (4 used) GigE ports on different VLANs. Each of the 4 ports is connected to a Cisco switch which applies the proper tag for that VLAN so that traffic can be routed correctly. I have tried disabling netplan and setting up interfaces in /etc/network/interfaces with the proper default route. But vmnetbrdige resets them every 30 minutes or so, adding routes for each interface which results in the incorrect default route. I have read of similar problems in Ubuntu 16.04 and 20.04 with a fix which claims to have corrected related problems, but not my issue. I had this server on CentOS 6 before and everything was work as expected. Below are the details. Contents of /etc/network/interfaces: iface eth1 inet static address 10.0.1.6 netmask 255.255.255.0 gateway 10.0.1.1 dns-nameservers 8.8.8.8, 75.75.76.76 dns-search mydomain.local up route add -net 0.0.0.0 netmask 0.0.0.0 gw 10.0.1.1 dev eth0 iface eth2 inet static address 10.0.20.60 netmask 255.255.255.0 gateway 10.0.20.1 iface eth3 inet static address 10.0.4.60 netmask 255.255.255.0 gateway 10.0.4.1 iface eth4 inet static address 192.168.3.60 netmask 255.255.255.0 gateway 192.168.3.1 Output of ifconfig -a: eth1: flags=4163 mtu 1500 inet 10.0.1.60 netmask 255.255.255.0 broadcast 10.0.1.255 inet6 fe80::264b:feff:fe5a:3622 prefixlen 64 scopeid 0x20 ether 24:4b:fe:5a:36:22 txqueuelen 1000 (Ethernet) RX packets 17216 bytes 14604772 (14.6 MB) RX errors 0 dropped 1283 overruns 0 frame 0 TX packets 14670 bytes 1719546 (1.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfc60-fc61 eth2: flags=4163 mtu 1500 inet 10.0.20.60 netmask 255.255.255.0 broadcast 10.0.20.255 inet6 fe80::226:55ff:fed7:d054 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:54 txqueuelen 1000 (Ethernet) RX packets 3159 bytes 212180 (212.1 KB) RX errors 0 dropped 1426 overruns 0 frame 0 TX packets 1691 bytes 122628 (122.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 106 memory 0xfca0-fca2 eth3: flags=4163 mtu 1500 inet 10.0.4.60 netmask 255.255.255.0 broadcast 10.0.4.255 inet6 fe80::226:55ff:fed7:d057 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:57 txqueuelen 1000 (Ethernet) RX packets 3835 bytes 249203 (249.2 KB) RX errors 0 dropped 1408 overruns 0 frame 0 TX packets 370 bytes 31235 (31.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 115 memory 0xfc82-fc84 eth4: flags=4163 mtu 1500 inet 192.168.3.60 netmask 255.255.255.0 broadcast 192.168.3.255 inet6 fe80::226:55ff:fed7:d056 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:56 txqueuelen 1000 (Ethernet) RX packets 2973 bytes 211765 (211.7 KB) RX errors 0 dropped 1433 overruns 0 frame 0 TX packets 238 bytes 29345 (29.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 117 memory 0xfc80-fc82 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 119 bytes 17075 (17.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 119 bytes 17075 (17.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923686/+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 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers
This bug was fixed in the package libseccomp - 2.5.1-1ubuntu1~18.04.1 --- libseccomp (2.5.1-1ubuntu1~18.04.1) bionic; urgency=medium * Updated to new upstream 2.5.1 version for updated syscalls support (LP: #1891810) - Removed the following patches that are now included in the new version: + d/p/fix-aarch64-syscalls.patch + d/p/db-consolidate-some-of-the-code-which-adds-rules.patch + d/p/db-add-shadow-transactions.patch - Deleted the patch to add a local copy of architecture specific header files from linux-libc-dev/focal as this is not needed anymore + d/p/add-5.4-local-syscall-headers.patch - debian/control: Added gperf to Build-Depends as this is now required by upstream - debian/libseccomp2.symbols: Added new symbols * Add system call headers for powerpc required for backport to xenial - d/p/add-5.8-powerpc-syscall-headers.patch -- Alex Murray Mon, 01 Mar 2021 13:49:23 +1030 ** Changed in: libseccomp (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1891810 Title: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in systemd source package in Xenial: Invalid Status in libseccomp source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in libseccomp source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in libseccomp source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in libseccomp source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1923632] Re: Screen flickering
Is the problem tearing or flickering? In which apps? Only when full screen? Please attach a video or photo of the problem so we can understand better. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Confirmed => 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/1923632 Title: Screen flickering Status in xorg-server package in Ubuntu: Incomplete Bug description: ubuntu whole screen flickering. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-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: Tue Apr 13 20:36:04 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core Processor Family Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2021-04-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=03a76041-a4c2-4e9f-a936-29041654a888 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V6.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-server/+bug/1923632/+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 1923657] Re: the information was send by the system
Please explain what kind of problem you have. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923657 Title: the information was send by the system Status in Ubuntu: Incomplete Bug description: the information was send by the system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Apr 13 16:15:07 2021 DistUpgraded: 2020-10-14 17:02:19,103 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0782] Subsystem: Dell GM108M [GeForce 940MX] [1028:0782] InstallationDate: Installed on 2018-05-07 (1072 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 7560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-14 (180 days ago) dmi.bios.date: 07/19/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.6 dmi.board.name: 09WC1G dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7560 dmi.product.sku: 0782 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.2.6-0ubuntu0.20.04.1 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 1:2.10.6-1 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 xserver.bootTime: Mon Jan 28 09:06:38 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1716 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923657/+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 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1896171 Title: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in Mutter: Unknown Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Committed Bug description: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+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 1923686] [NEW] Ubuntu 20.10 Network Issue
Public bug reported: I have a server running Ubuntu 20.10 running VMware Workstation 16 which loses its default route. I keep setting it manually but every 30 minutes or so, it reverts to the incorrect route. This server has 5 (4 used) GigE ports on different VLANs. Each of the 4 ports is connected to a Cisco switch which applies the proper tag for that VLAN so that traffic can be routed correctly. I have tried disabling netplan and setting up interfaces in /etc/network/interfaces with the proper default route. But vmnetbrdige resets them every 30 minutes or so, adding routes for each interface which results in the incorrect default route. I have read of similar problems in Ubuntu 16.04 and 20.04 with a fix which claims to have corrected related problems, but not my issue. I had this server on CentOS 6 before and everything was work as expected. Below are the details. Contents of /etc/network/interfaces: iface eth1 inet static address 10.0.1.6 netmask 255.255.255.0 gateway 10.0.1.1 dns-nameservers 8.8.8.8, 75.75.76.76 dns-search mydomain.local up route add -net 0.0.0.0 netmask 0.0.0.0 gw 10.0.1.1 dev eth0 iface eth2 inet static address 10.0.20.60 netmask 255.255.255.0 gateway 10.0.20.1 iface eth3 inet static address 10.0.4.60 netmask 255.255.255.0 gateway 10.0.4.1 iface eth4 inet static address 192.168.3.60 netmask 255.255.255.0 gateway 192.168.3.1 Output of ifconfig -a: eth1: flags=4163 mtu 1500 inet 10.0.1.60 netmask 255.255.255.0 broadcast 10.0.1.255 inet6 fe80::264b:feff:fe5a:3622 prefixlen 64 scopeid 0x20 ether 24:4b:fe:5a:36:22 txqueuelen 1000 (Ethernet) RX packets 17216 bytes 14604772 (14.6 MB) RX errors 0 dropped 1283 overruns 0 frame 0 TX packets 14670 bytes 1719546 (1.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfc60-fc61 eth2: flags=4163 mtu 1500 inet 10.0.20.60 netmask 255.255.255.0 broadcast 10.0.20.255 inet6 fe80::226:55ff:fed7:d054 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:54 txqueuelen 1000 (Ethernet) RX packets 3159 bytes 212180 (212.1 KB) RX errors 0 dropped 1426 overruns 0 frame 0 TX packets 1691 bytes 122628 (122.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 106 memory 0xfca0-fca2 eth3: flags=4163 mtu 1500 inet 10.0.4.60 netmask 255.255.255.0 broadcast 10.0.4.255 inet6 fe80::226:55ff:fed7:d057 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:57 txqueuelen 1000 (Ethernet) RX packets 3835 bytes 249203 (249.2 KB) RX errors 0 dropped 1408 overruns 0 frame 0 TX packets 370 bytes 31235 (31.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 115 memory 0xfc82-fc84 eth4: flags=4163 mtu 1500 inet 192.168.3.60 netmask 255.255.255.0 broadcast 192.168.3.255 inet6 fe80::226:55ff:fed7:d056 prefixlen 64 scopeid 0x20 ether 00:26:55:d7:d0:56 txqueuelen 1000 (Ethernet) RX packets 2973 bytes 211765 (211.7 KB) RX errors 0 dropped 1433 overruns 0 frame 0 TX packets 238 bytes 29345 (29.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 117 memory 0xfc80-fc82 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 119 bytes 17075 (17.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 119 bytes 17075 (17.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ** Affects: systemd (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/1923686 Title: Ubuntu 20.10 Network Issue Status in systemd package in Ubuntu: New Bug description: I have a server running Ubuntu 20.10 running VMware Workstation 16 which loses its default route. I keep setting it manually but every 30 minutes or so, it reverts to the incorrect route. This server has 5 (4 used) GigE ports on different VLANs. Each of the 4 ports is connected to a Cisco switch which applies the proper tag for that VLAN so that traffic can be routed correctly. I have tried disabling netplan and setting up interfaces in /etc/network/interfaces with the proper default route. But vmnetbrdige resets them every 30 minutes or so, adding routes for each interface which results in the incorrect default route. I have read of similar problems in Ubuntu 16.04 and 20.04 with a fix which claims to have correcte
[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
Seeds have now been updated: https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400932 https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400933 And the meta package has been updated to incorporate these changes in 1.467 ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-settings (Ubuntu) Milestone: None => ubuntu-21.04 -- 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: New 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
[Touch-packages] [Bug 1923672] [NEW] [FFe] Provide access to GPIO to default user
Public bug reported: At present, access to the GPIO pins is provided to the dialout group by the udev rules from the rpi.gpio-common package. However, rpi.gpio is a single GPIO library, and the device(s) it provides access to are not specific to it. Moreover, the interface used is deprecated and the /dev/gpiochip* interface is now the favoured mechanism for controlling the GPIO pins. The choice of the dialout group appears reasonable (historically it's used to provide access to the serial ports, and indeed the serial ports are part of the GPIO header on Raspberry Pi devices), but the rules should be extended to cover the modern /dev/gpiochip* devices, the related /dev/spidev* and /dev/i2c-* devices, and should be placed in a central location (i.e. ubuntu-raspi-settings) rather than in a specific GPIO library (like rpi.gpio). Related to this is LP: #1923363 which seeks to ensure equal access across images (the default user is currently granted "dialout" group membership on the pi server images, but not the desktop ones). ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Provide access to GPIO to default user + [FFe] Provide access to GPIO to default user -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923672 Title: [FFe] Provide access to GPIO to default user Status in ubuntu-settings package in Ubuntu: New Bug description: At present, access to the GPIO pins is provided to the dialout group by the udev rules from the rpi.gpio-common package. However, rpi.gpio is a single GPIO library, and the device(s) it provides access to are not specific to it. Moreover, the interface used is deprecated and the /dev/gpiochip* interface is now the favoured mechanism for controlling the GPIO pins. The choice of the dialout group appears reasonable (historically it's used to provide access to the serial ports, and indeed the serial ports are part of the GPIO header on Raspberry Pi devices), but the rules should be extended to cover the modern /dev/gpiochip* devices, the related /dev/spidev* and /dev/i2c-* devices, and should be placed in a central location (i.e. ubuntu-raspi-settings) rather than in a specific GPIO library (like rpi.gpio). Related to this is LP: #1923363 which seeks to ensure equal access across images (the default user is currently granted "dialout" group membership on the pi server images, but not the desktop ones). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1923672/+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 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
@callegar It would be nice to see the full resolvectl status. Because depending on which things you have configured it might be expected to have DNSSEC validation working, and the request is routed to multiple interfaces, and none of them return results or the results fail to validate. Also note that strict DNSSEC is off by default did you turn it on in the first place? -- 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/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 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 CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-root 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/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1920781/+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 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
Happened again today. How do you disable dnssec completely in systemd-resolved? resolvectl does not seem to have an option for that. Is editing resolved.conf and restarting resolved the only way? In any case I could not try, I was too much on a hurry and reconfiguring network manager to use google dns for the connection was quicker. Still: why should one need to disable dnssec globally when there is a per connection setting? -- 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/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 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 CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-root 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/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1920781/+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 1923657] [NEW] the information was send by the system
Public bug reported: the information was send by the system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Apr 13 16:15:07 2021 DistUpgraded: 2020-10-14 17:02:19,103 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0782] Subsystem: Dell GM108M [GeForce 940MX] [1028:0782] InstallationDate: Installed on 2018-05-07 (1072 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 7560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-14 (180 days ago) dmi.bios.date: 07/19/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.6 dmi.board.name: 09WC1G dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7560 dmi.product.sku: 0782 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.2.6-0ubuntu0.20.04.1 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 1:2.10.6-1 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 xserver.bootTime: Mon Jan 28 09:06:38 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1716 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923657 Title: the information was send by the system Status in xorg package in Ubuntu: New Bug description: the information was send by the system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Apr 13 16:15:07 2021 DistUpgraded: 2020-10-14 17:02:19,103 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0782] Subsystem: Dell GM108M [GeForce 940MX] [1028:0782] InstallationDate: Installed on 2018-05-07 (1072 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 7560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-14 (180 days ago) dmi.bios.date: 07/19/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.6 dmi.board.name: 09WC1G dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7560 dmi.product.sku: 0782 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.0
[Touch-packages] [Bug 1923632] Re: Screen flickering
Hello, I was affected by the same bug as you following the Linux 5.8.0-49-generic kernel update (everything is ok with the 5.8.0-48-generic kernel) However, the problem has been solved with the X.org update which has been available for a few hours. Can you look for new updates available and test after updating the X.org server and restarting the PC? My PC : - Dell Inc. Inspiron 3847/088DT1, BIOS A11 05/07/2019 - EFI v2.31 by American Megatrends - Secure boot disable - CPU : Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz - GPU : Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller (rev 06) - A single screen connected via HDMI. Resolution: 1920x1080 - RAM : 16 GB DDR3 My Ubuntu 20.10 : - Linux 5.8.0-49-generic #55-Ubuntu SMP Wed Mar 24 14:45:45 UTC 2021 - X11 - GNOME 3.38.2 - French language -- 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/1923632 Title: Screen flickering Status in xorg package in Ubuntu: Confirmed Bug description: ubuntu whole screen flickering. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-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: Tue Apr 13 20:36:04 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core Processor Family Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2021-04-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=03a76041-a4c2-4e9f-a936-29041654a888 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V6.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1923632/+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 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
Thanks! -- 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/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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 1923632] Re: Screen flickering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1923632 Title: Screen flickering Status in xorg package in Ubuntu: Confirmed Bug description: ubuntu whole screen flickering. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-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: Tue Apr 13 20:36:04 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core Processor Family Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2021-04-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=03a76041-a4c2-4e9f-a936-29041654a888 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V6.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1923632/+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 1920047] Re: sanlock global lock creation fail
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1920047 Title: sanlock global lock creation fail Status in lvm2 package in Ubuntu: New Bug description: Hello, Running Ubuntu server 20.04, I cannot create a shared VG using sanlock : # vgcreate --shared foo /dev/mapper/vol Enabling sanlock global lock Skipping global lock: lockspace not found or started Logical volume "lvmlock" created. VG foo init failed: -28 Failed to initialize lock args for lock type sanlock Volume group "foo" successfully removed Messages in /var/log/syslog lvmlockd[446807]: 1616089866 WARNING: mixed block sizes physical 4096 logical 512 (using 4096) for /dev/mapper/foo-lvmlock lvmlockd[446807]: 1616089866 S lvm_foo init_vg_san write_resource gl error -28 /dev/mapper/foo-lvmlock # lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 # dpkg -l | grep lvm ii liblvm2cmd2.03:amd64 2.03.07-1ubuntu1 amd64LVM2 command library ii lvm2 2.03.07-1ubuntu1 amd64Linux Logical Volume Manager ii lvm2-lockd 2.03.07-1ubuntu1 amd64LVM locking daemon A similar bug report from RHEL8 : https://bugzilla.redhat.com/show_bug.cgi?id=1833837 Bug has been fixed upstream : https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87 It seems to be included in version 2.03.10 : https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/tags/v2_03_10 How can we get this patch included in Ubuntu 20.04 ? King Regards, Charles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1920047/+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 1921626] Re: size mismatch error if request of unknown size is larger than others
** Changed in: apt (Ubuntu Hirsute) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1921626 Title: size mismatch error if request of unknown size is larger than others Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: New Status in apt source package in Focal: New Status in apt source package in Groovy: New Status in apt source package in Hirsute: Fix Committed Bug description: 1) Ubuntu 18.04.5 LTS 2) apt 1.6.12ubuntu0.2 3) What you expected to happen I set a custom set of repositories in /etc/apt/sources.list and then I run "apt install ". I expect the command to download and install the packages. 4) What happened instead "apt install ..." fails during the download phase with "File has unexpected size " 5) What I've established trying to debug the issue: - Disabling http pipelining resolves the issue: "apt -oAcquire::http::Pipeline-Depth=0 install ..." - All the packages, and repo metadata in the referenced repositories is correct - The issue is easily reproducible in my setup with different repositories - tcpdump shows that requests and responses are in the correct order, and contain the correct data More details about the issue: https://projects.theforeman.org/issues/32178 With all the above in mind, it appears that this must be a bug in apt's http pipeline handling. It seem that apt is trying to match a request to do wrong response, and size doesn't match. I've attached an example log, where the error pops up for multiple packages, and they all appear to be compared to one size (86464 bytes). That size is correct for one of the package being downloaded, but somehow apt is trying to match to multiple other packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+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 1923564] Re: BlueZ 5.58 release
** Tags added: upgrade-software-version -- 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/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: New Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1923632] [NEW] Screen flickering
Public bug reported: ubuntu whole screen flickering. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-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: Tue Apr 13 20:36:04 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core Processor Family Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2021-04-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=03a76041-a4c2-4e9f-a936-29041654a888 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V6.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923632 Title: Screen flickering Status in xorg package in Ubuntu: New Bug description: ubuntu whole screen flickering. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-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: Tue Apr 13 20:36:04 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core Processor Family Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2021-04-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=03a76041-a4c2-4e9f-a936-29041654a888 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V6.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Touch-packages] [Bug 1923541] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
** Branch linked: lp:~ubuntu-core-dev/ubuntu/hirsute/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1923541 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: In Progress Status in apport source package in Hirsute: In Progress Bug description: Currently running 21.04, apport version is 2.20.11-0ubuntu62 . When I try to fill a bug, I see: $ ubuntu-bug network-manager ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in attach_casper_md5check del report['CasperMD5json'] File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__ del self.data[key] KeyError: 'CasperMD5json' It's not crashing the bug reporting itself, but it looks wrong to have a stacktrace on the command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1923541/+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 1923541] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
** Also affects: apport (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Hirsute) Status: New => In Progress ** Changed in: apport (Ubuntu Hirsute) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1923541 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: In Progress Status in apport source package in Hirsute: In Progress Bug description: Currently running 21.04, apport version is 2.20.11-0ubuntu62 . When I try to fill a bug, I see: $ ubuntu-bug network-manager ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in attach_casper_md5check del report['CasperMD5json'] File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__ del self.data[key] KeyError: 'CasperMD5json' It's not crashing the bug reporting itself, but it looks wrong to have a stacktrace on the command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1923541/+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
** Also affects: systemd (Ubuntu Groovy) 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/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: New Status in systemd source package in Groovy: New 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] [NEW] upgrading systemd on groovy terminates sessions
Public bug reported: 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. ** Affects: systemd (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/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: New 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 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
You can prevent lvm2 from scanning the card reader by using the global filter. Instead of using drive letters for the filter, like 'sde' which is liable to change, use the id of the device(s). E.g.: # ls -l /dev/disk/by-id/ | grep sd[e-h] lrwxrwxrwx 1 root root9 Apr 13 11:06 usb-Generic_USB_CF_Reader_058F312D81B-0:1 -> ../../sdf lrwxrwxrwx 1 root root9 Apr 13 11:06 usb-Generic_USB_MS_Reader_058F312D81B-0:3 -> ../../sdh lrwxrwxrwx 1 root root9 Apr 13 11:06 usb-Generic_USB_SD_Reader_058F312D81B-0:0 -> ../../sde lrwxrwxrwx 1 root root9 Apr 13 11:06 usb-Generic_USB_SM_Reader_058F312D81B-0:2 -> ../../sdg Since all card reader slot device ids contain the unique 'Reader_058F312D81B', you can use the following global filter in lvm.conf. "r|/dev/disk/by-id/.*Reader_058F312D81B.*" # filter out card reader slots Good luck! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Confirmed Bug description: sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 3.7T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 3.7T 0 part └─sda3_crypt 253:00 3.7T 0 crypt ├─kubuntu--vg-swap_1 253:10 976M 0 lvm [SWAP] └─kubuntu--vg-root 253:20 3.7T 0 lvm / sdb8:16 0 3.7T 0 disk └─sdb1 8:17 0 3.7T 0 part sdg8:96 0 7.3T 0 disk └─sdg1 8:97 0 7.3T 0 part /media/scott/8TB Ext Drive sr0 11:01 15.7G 0 rom -- cat /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on" GRUB_CMDLINE_LINUX="" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2-common 2.02+dfsg1-12ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: ubiquity (Ubuntu Hirsute) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Invalid Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1923564] [NEW] BlueZ 5.58 release
Public bug reported: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Description changed: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... + http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ -- 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/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: New Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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
