[Touch-packages] [Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: avahi (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Focal: Confirmed Status in avahi source package in Jammy: Confirmed Status in avahi source package in Kinetic: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: avahi (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Focal: Confirmed Status in avahi source package in Jammy: Confirmed Status in avahi source package in Kinetic: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Confirmed affecting Samsung Galaxy Book2 (i7-1255U, Intel Iris Xe Graphics, 16GB LPDDR4x / NP750XED-KC4SE). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package, then test grubx64.efi is under “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case: `/var/cache/pbuilder/build/276481/bui
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Hey Lindsay, don't worry, this is just meant to keep information out there. :) So, although disabling the patches didn't make an effect for a typical "Ubuntu on Xorg" (as in GDM's cog option), if I use a more minimal environment, such as if I log in a console and just `startx /bin/dwm`, the bug doesn't show up, either with patched or not patched GTK. Another difference is that upon closing Evolution the following warning is logged in stderr: Your application did not unregister from D-Bus before destruction. Consider using g_application_run(). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files Status in evolution package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Bug description: Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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 1955084] Re: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown
As requested, here's what I managed to dig up on possible alternatives to running unattended-upgrades-shutdown persistently: There appear to be several methods by which systemd can be told to run something at or near shutdown, but one has to be exceptionally careful in the selection to cover all edge cases. Some possibilities can be trivially discarded. For instance, the systemd-shutdown (8) logic runs too late, potentially after the root file-system has been remounted read-only. Other possibilities have extremely subtle side-effects. For example, one tempting possibility is to reverse the current logic of the unattended-upgrades.service, which currently looks like this: [Service] ExecStart=/usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal KillMode=process TimeoutStopSec=1800 And instead use a "fake" service that systemd pretends is running, then activate the shutdown script when systemd goes to stop the service, like so: [Service] ExecStart=/bin/true RemainAfterExit=yes ExecStop=/usr/share/unattended-upgrades/unattended-upgrade-shutdown KillMode=process TimeoutStopSec=1800 Note the lack of --wait-for-signal (because we want the script to run immediately when systemd goes to "stop" the fake service). However, tempting though this possibility is, LP: #1778219 (and associated commits, particularly [4]) describes why this doesn't work in practice. If a package upgrade is occurring during shutdown, and that package attempts to start or restart a systemd service, the attempt will hang. This is particularly an issue with the "InstallOnShutdown" behaviour (not the default) which expects to fully complete the upgrade before shutdown (as opposed to the default behaviour which attempts to stop the upgrade after the next transaction completes). Side note: The KillMode setting appears to be an attempt to prevent systemd from killing a subordinate apt process in the event it deems unattended-upgrades to have timed out. This seems … risky to me. The timeout duration is, so far as I can tell, picked fairly arbitrarily and what happens in the event that unattended-upgrades times out, but leaves subordinate apt/dpkg processes lying around is unclear (does systemd wait for them indefinitely, does it kill them after another timeout, does it shutdown/reset the machine with them still running?). There's some more context in LP: #1690980 regard this. Ultimately, the solution appears to have been having a persistent process (u-u-shutdown) watch for the logind PrepareForShutdown event which occurs well before systemd actually starts the shutdown. Unfortunately (as far as I've been able to tell?) this requires an active process to watch for it. The following bugs contain a great deal of detail and further context to this issue: * LP: #1778219 -- u-u hanging on shutdown * LP: #1654600 -- u-u hanging when /var is separate file-system * LP: #1618900 -- u-u failing to upgrade kernels due to missing mount (+others) * LP: #1690980 -- context regarding u-u's shutdown inhibit, and killmode There are also some useful test cases found in these bugs that should be used in ensuring certain scenarios aren't broken. The following PRs and GitHub issues are also well worth a read, especially #148: [1]: https://github.com/mvo5/unattended-upgrades/pull/64 [2]: https://github.com/mvo5/unattended-upgrades/pull/148 [3]: https://github.com/mvo5/unattended-upgrades/issues/176 [4]: https://github.com/mvo5/unattended-upgrades/commit/3734e06d03c5146dc307b3996ea11c8b398a55c1 Balint's comment ([5]) in LP: #1778219 also offered an intriguing (partial?) solution: maintscripts should not be calling systemctl themselves, but deb-systemd-invoke (lintian already checks for this), and deb-systemd-invoke should be enhanced to detect when it is operating during shutdown, and refuse to start/restart services (only stopping them). It appears there was an intention to fix this but it got lost somewhere along the way. [5]: https://bugs.launchpad.net/ubuntu/+source/unattended- upgrades/+bug/1778219/comments/6 ** Bug watch added: github.com/mvo5/unattended-upgrades/issues #176 https://github.com/mvo5/unattended-upgrades/issues/176 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1955084 Title: systemd unit leaves a process running for the system lifetime but it only does anything at shutdown Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Jammy: New Bug description: The /lib/systemd/system/unattended-upgrades.service unit leaves a process, /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal, running from system start until shutdown. This increases the minimum memory footprint of every host, VM, or container where unattended-upgrades is installed. The motivation for having
[Touch-packages] [Bug 1986936] [NEW] No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages
You have been subscribed to a public bug: While trying to link against corresponding libraries to get i386 executable like that: > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ... I get the following errors: > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so > when searching for -lQt5Widgets > > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory > > > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so > when searching for -lQt5Widgets > > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so > when searching for -lQt5Gui > > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory > > > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so > when searching for -lQt5Gui > > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so > when searching for -lQt5Core > > /usr/bin/ld: cannot find -lQt5Core: No such file or directory > > > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so > when searching for -lQt5Core despite corresponging packages are installed (libqt5gui5:i386 and same for widgets and core). Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no symlinks named exactly libQt5Core.so (and same for two other libs). Adding those symlinks by hand completely solves the problem. I believe however that those symlinks must be installed by corresponding .debs. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment i386 qt5 -- No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages https://bugs.launchpad.net/bugs/1986936 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages
** Package changed: ubuntu => qtbase-opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1986936 Title: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages Status in qtbase-opensource-src package in Ubuntu: New Bug description: While trying to link against corresponding libraries to get i386 executable like that: > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ... I get the following errors: > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core > /usr/bin/ld: cannot find -lQt5Core: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core despite corresponging packages are installed (libqt5gui5:i386 and same for widgets and core). Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no symlinks named exactly libQt5Core.so (and same for two other libs). Adding those symlinks by hand completely solves the problem. I believe however that those symlinks must be installed by corresponding .debs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages
You probably need to install qtbase5-dev:i386, not just libqt5*:i386. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1986936 Title: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages Status in qtbase-opensource-src package in Ubuntu: New Bug description: While trying to link against corresponding libraries to get i386 executable like that: > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ... I get the following errors: > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core > /usr/bin/ld: cannot find -lQt5Core: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core despite corresponging packages are installed (libqt5gui5:i386 and same for widgets and core). Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no symlinks named exactly libQt5Core.so (and same for two other libs). Adding those symlinks by hand completely solves the problem. I believe however that those symlinks must be installed by corresponding .debs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt
** Changed in: bolt (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1945321 Title: umockdev 0.16.3-1 breaks autopkgtest of bolt Status in bolt package in Ubuntu: Fix Released Status in umockdev package in Ubuntu: Invalid Status in umockdev package in Debian: Fix Released Bug description: The test of bolt fails with the new version due to a crash: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz ... Trace/breakpoint trap (core dumped) The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and python3-dbusmock and the new version causes this. Retrying autopkgtest locally with no, all and just umockdev from proposed and it seems reproducible. - impish-release - works - impish-all-proposed - crashes - impish-release + umockdev+libc6 from proposed - crashes Repro: $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power FYI: Downgrading to umockdev 0.16.2-1 in the same environment does not eliminate the issue. So it might happen at the bolt test-build time. Debian has the same issue in: https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz The new mockdev fails to create /sys/bus which is requested by the test. From there the error path is what crashes, but the root cause is why we enter the error-path in the first place. One should be aware, this fail is "normal" if the environment is not mocked. Even in the good case the different calls with/without umockdev lead to exactly the same crash. # good $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power # same crash as the new version has with umockdev-wrapper $ gdb /usr/libexec/installed-tests/bolt/test-power This is based on ldpreload. $ cat /usr/bin/umockdev-wrapper #!/bin/sh # Wrapper program to preload the libumockdev library, so that test programs can # set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed. exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@" Gut feeling: it seems the mocking no more happens, and due to that it runs into the non-mocked crash Debugging with that: $ pull-lp-source bolt $ cd bolt-0.9.1/tests $ gdb /usr/libexec/installed-tests/bolt/test-power (gdb) set environment LD_PRELOAD libumockdev-preload.so.0 (gdb) b mock_sysfs_init (gdb) run With that we can see that while the crash is somewhere inside g_warning the reason is in the g_mkdir failing with the new umockdev. Good-case Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165 165 { (gdb) n 171 ms->bed = umockdev_testbed_new (); (gdb) [New Thread 0x76e65640 (LWP 11444)] # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created # DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1 172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal, (gdb) [New Thread 0x76664640 (LWP 11445)] 175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal); (gdb) 180 sys = umockdev_testbed_get_sys_dir (ms->bed); (gdb) 182 bus = g_build_filename (sys, "bus", NULL); (gdb) p sys $1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys" (gdb) n 183 r = g_mkdir (bus, 0744); (gdb) p bus $2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus" (gdb) n 185 if (r < 0) (gdb) p r $3 = 0 (gdb) n 188 cls = g_build_filename (sys, "class", NULL); Bad-Case Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165 165 { (gdb) n 171 ms->bed = umockdev_testbed_new (); (gdb) [New Thread 0x76e65640 (LWP 17082)] # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created # DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1 172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal, (gdb) [New Thread 0x76664640 (LWP 17083)] 175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal); (gdb) 180 sys = umockdev_testbed_get_sys_dir (ms->bed); (gdb) 182 bus = g_build_filename (sys, "bus", NULL); (gdb) p sys $1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys" (gdb) n 183 r = g_mkdir (bus, 0744); (gdb) p bus $2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus" (gdb) n 185 if (r < 0) (gdb) p r $3 = -1 (gdb) n 186 g_warning ("could not create %s", bus); (gdb) n ** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **: 15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap. I'll tag this update-excuse and FYI-subscribe Martin who has
[Touch-packages] [Bug 1984327] Re: Component mismatch: new lerc support requires universe package
Yes, will do today -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1984327 Title: Component mismatch: new lerc support requires universe package Status in tiff package in Ubuntu: Fix Released Bug description: tiff is in sync with debian, and version tiff 4.4.0-1[1] enabled lerc support. Unfortunately lerc[2] is in ubuntu universe, and tiff is in main, so we either MIR lerc, or disable it in tiff. For now, let's disable lerc support. 1. https://launchpad.net/ubuntu/+source/tiff/4.4.0-1 2. https://launchpad.net/ubuntu/+source/lerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1984327/+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 1984327] Re: Component mismatch: new lerc support requires universe package
Uploaded: Uploading tiff_4.4.0-4ubuntu2.dsc Uploading tiff_4.4.0-4ubuntu2.debian.tar.xz Uploading tiff_4.4.0-4ubuntu2_source.buildinfo Uploading tiff_4.4.0-4ubuntu2_source.changes I decided to retain the ubuntu suffix (see discussion at [1]), and will sync the package the next time there is a debian upload. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2022-May/042099.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1984327 Title: Component mismatch: new lerc support requires universe package Status in tiff package in Ubuntu: Fix Released Bug description: tiff is in sync with debian, and version tiff 4.4.0-1[1] enabled lerc support. Unfortunately lerc[2] is in ubuntu universe, and tiff is in main, so we either MIR lerc, or disable it in tiff. For now, let's disable lerc support. 1. https://launchpad.net/ubuntu/+source/tiff/4.4.0-1 2. https://launchpad.net/ubuntu/+source/lerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1984327/+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 1983359] Re: hwrng drivers missing in initrd.img
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1983359 Title: hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Confirmed Bug description: The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 1983359] Re: hwrng drivers missing in initrd.img
Sponsored for kinetic. ** Also affects: initramfs-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1983359 Title: hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Jammy: New Bug description: The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 1341598] Re: Typo in "app-install-data-ubuntu"
Reviewing 100 Papercuts issues I see that this bug report refers to a package that is no longer included in any currently supported release of Ubuntu. Closing as "Invalid" but probably should be "Won't Fix". ** Changed in: hundredpapercuts Status: Fix Committed => Invalid ** Changed in: unity-webapps-qml (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1341598 Title: Typo in "app-install-data-ubuntu" Status in One Hundred Papercuts: Invalid Status in unity-webapps-qml package in Ubuntu: Invalid Bug description: Hi, In string #5167: "Unity WebApp QML Comonent - Example of WebApps Applications Model" "Comonent" should be replaced by "Component". Link: https://translations.launchpad.net/ubuntu/utopic/+source/app- install-data-ubuntu/+pots/app-install-data/fr/5167/+translate To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1341598/+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 1940715] Re: systemd-resolved restricts edns0 advertised max size to 512
** Changed in: systemd (Ubuntu Hirsute) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Focal) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Bionic) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Focal) Status: In Progress => New ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => 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/1940715 Title: systemd-resolved restricts edns0 advertised max size to 512 Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Bug description: [impact] when talking to upstream nameservers, systemd-resolved limits its advertised max packet size as 512 in its edns0 opt. However, one of the primary benefits of edns0 is to allow using packet sizes larger than 512, which is the pre-edns0 max packet size. this results in systemd-resolved failing to handle responses larger than 512 with udp/edns0, and having to fall back to tcp. This is not optimal (since tcp dns imposes significantly higher overhead) and may even cause failures, if a firewall allows udp dns but blocks tcp dns traffic. [test case] enable debug logging in systemd-resolved, with 'sudo systemctl edit systemd-resolved' and then add: [Service] Environment=SYSTEMD_LOG_LEVEL=debug then save that file and restart systemd-resolved (or reboot). Make sure to flush the cache and reset server features before reproducing: $ sudo resolvectl flush-caches $ sudo resolvectl reset-server-features Lookup 'toomany.ddstreet.org' and check systemd-resolved logs to see if it used TCP fallback or not: ... Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Reply truncated, retrying via TCP. ... Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Verified we get a response at feature level TCP from DNS server 10.202.51.1. Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Added positive unauthenticated cache entry for toomany.ddstreet.org IN A 1799s on eth0/INET/10.202.51.1 A correct lookup using larger EDNS0 response size looks like: ... Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using feature level UDP+EDNS0 for transaction 43808. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using DNS server 10.202.51.1 for transaction 43808. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Announcing packet size 1472 in egress EDNS(0) packet. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Emitting UDP, link MTU is 1500, socket MTU is 0, minimal MTU is 40 Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Sending query packet with id 43808 of size 49. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing query... Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Received dns UDP packet of size 689, ifindex=131, ttl=0, fragsize=0 Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing incoming packet of size 689 on transaction 43808 (rcode=SUCCESS). Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Added positive unauthenticated non-confidential cache entry for toomany.ddstreet.org IN A 1175s on eth0/INET/10.202.51.1 ... [regression potential] failure to correctly look up dns records, or other problems while performing dns lookups with systemd-resolved [scope] this is needed in impish and earlier this is fixed in jammy at commit 22545a74c3a24395bc6e894fe6a681deb66d434c this is fixed upstream by commit 526fce97afe130f71dba3bd4646196bbb1188b82 which in included in v250, so this is fixed in kinetic and later the upstream PR is: https://github.com/systemd/systemd/pull/20528 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1940715/+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 1983359] Re: hwrng drivers missing in initrd.img
The attachment "initramfs-tools-0.140ubuntu14..0.140ubuntu15.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1983359 Title: hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Jammy: New Bug description: The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 1986984] [NEW] Availability of tzdata 2022c for Ubuntu 20.04
Public bug reported: tzdata 2022b and 2022c were just released that includes some timezone changes for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a change to the start of their daylight savings and pushed it from Sept 4th to the 11th, so we really need our servers updated before the 4th. Thanks Jason ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1986984 Title: Availability of tzdata 2022c for Ubuntu 20.04 Status in tzdata package in Ubuntu: New Bug description: tzdata 2022b and 2022c were just released that includes some timezone changes for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a change to the start of their daylight savings and pushed it from Sept 4th to the 11th, so we really need our servers updated before the 4th. Thanks Jason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+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 1970081] Re: The background image of the login window cannot be changed
Here's the supposedly final solution: (sudo) apt-get install lightdm-settings slick-greeter and then killall -HUP mate-panel "Login Window" will automagically appear in the "Administration" section of "Control Center". Thanks @ubucolors for confirming it was a matter of something no more available. ** Attachment added: "The Control Center as expected" https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+attachment/5609683/+files/Screenshot%20at%202022-08-18%2018-39-14.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
*** This bug is a duplicate of bug 1842320 *** https://bugs.launchpad.net/bugs/1842320 I guess the problem hasn't been fixed in ubuntu-22.04.1. I'm having the same exact issue when trying to install ubuntu-22.04.1 from USB on a computer with large memory (32GB of RAM). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1970081] Re: The background image of the login window cannot be changed
I was hasty, I didn't realize I just found a way to add the missing setup in the "Control Center". I'm stuck at the default image as well, though the setup actually writes the image I've chosen in a file in /etc. I'm working on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Deleting the certificate also worked for me. To do this user needs admin privileges. I guess this breaks basic printing functionality for regular users. This is my printer: HP_Smart_Tank_530_series_21D133 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Confirmed affecting GIGABYTE Z690 AORUS ELITE DDR4 (LGA1700, USB 3.2, PCIe 5.0) after installing nvidia-driver-515 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package, then test grubx64.efi is under “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case: `/var/cache/pbuilder/build/276
[Touch-packages] [Bug 1839598] Re: tcp_wrappers does not whitelisting of domains, vs IPs
** Changed in: tcp-wrappers (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tcp-wrappers in Ubuntu. https://bugs.launchpad.net/bugs/1839598 Title: tcp_wrappers does not whitelisting of domains, vs IPs Status in tcp-wrappers package in Ubuntu: Won't Fix Bug description: TCP Wrappers (also known as tcp_wrappers) is a host-based networking ACL system, used to filter network access to Internet Protocol servers. It allows host or subnetwork IP addresses, names and/or ident query replies, to be used as tokens on which to filter for access control purposes. The original code was written by Wietse Venema in 1990 He maintained it until 1995, and on June 1, 2001, released it under its own BSD-style license. The tarball includes a library named Libwrap that implements the actual functionality. I had an email conversation with him that lead to nowhere. He does not agree with my request for a redesign. Very concisely, there is no way as of now to whitelist a domain, vs an IP address. You need to know the IP address to which the domain resolves to beforehand, which makes domain updates impossible to process. This causes tremendous operational problems when the person you need to give access to has an IP address that changes often. But I need to digress. Every foreign worker is a potential hacker, for there is no way to perform a security check on her/him. Many companies use them nevertheless because of the low cost. I know a company that hires North Korean engineers working out of mainland China. They log in for legitimate purposes to American corporate servers. They actually live in North Korea and are forced to back home every 3 weeks. They only have access to dynamic IP addresses, where a PTR record does not exist, thus, no reverse-hostname is possible. As a fact: no dynamic IP address has a corresponding PTR record. The question is how to whitelist a remote worker’s IP automatically. This issue cannot be easily solved since commercial VPNs do not guarantee that the same IP will be offered on the next connection. Many small companies that hire foreign workers end up creating fence servers, but that is exponentially more insecure since now you have a potential hacker sitting comfortably inside your firewall, behind your line of defense. Your network may have access to other companies networks, all the way up to a power station or a government facility, maybe a nuclear facility. A very somber scenario. Since Libwrap is the ultimate defense to keep hackers from controlling your servers, it should ONLY verify if an incoming connection resolves to a domain listed in /etc/hosts.allow. It does not. Prior, it performs a hostname check that invariably fails unless the pair IP address/ domain exists in /etc/hosts, but of course that information changes sometimes hourly. As a result of this problem, you cannot use it as a gatekeeper for remote access from dynamic IP addresses, increasing your level of insecurity. As I said, I explained all these ideas to the author, Wietse, without success. He insisted that using a public key was how you protect servers. I disagree. Without Libwrap, which means IP whitelisting, a simple public key mechanism is suicidal. It is very easy to see why. In a first step, a hacker steals the pair public-private key from a box which has legitimate access to your network. Then he uses the pair in another box located in his country, from which he will access your network as if he were the legitimate client or worker. It happened to me already. Libwrap applied to a domain plus public key will perform infinitely better than a public key alone. In fact, public key alone should not be used at all. This is obvious since by using it, you are delegating your security to the box you are allowing to connect, so your entire network is now as secure as your client or worker’s home network, which you don’t control. You just opened the doors of your company wide-open. What I suggest is to modify Libwrap so a domain listed in /etc/hosts.allow would work for real, just performing a simple DNS lookup to will match the IP address to the domain. Right now, this is impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcp-wrappers/+bug/1839598/+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 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
I think there are multiple bugs in play here. My system-connections dir is a symlink within the same filesystem, and whenever I try to save a new connection I get the "settings plugin does not support adding connections" message. Aug 18 17:11:08 workhorse4 NetworkManager[4092654]: [1660857068.1365] audit: op="connection-add" pid=4124192 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" The symlink target dir has the same ownership/permissions as the original system-connections dir - 0755, root:root. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1913979 Title: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink Status in network-manager package in Ubuntu: Confirmed Bug description: If the /etc/NetworkManager/system-connections directory is a cross- filesystem symlink, activating connections will fail with the unrelated messages: * "failed to create file ...: Read-only file system" (TRACE level) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above) * no error message (Gnome UI) I suspect moving the systems-connections directory onto a separate filesystem is not supported because network manager tries to atomically move a connection temp file into place and fails, but this is really hard to figure out since the error messages are completely unrelated. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: sudo mv /etc/NetworkManager/system-connections /some/other/mountpoint/system-connections sudo ln -s /some/other/mountpoint/system-connections /etc/NetworkManager/system-connections Then: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * "failed to create file ...: Read-only file system" (TRACE level, journalctl) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above, journalctl and nmtui/nmcli output) * no error message (Gnome UI) Relevant sample logs: Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4038] active-connection[0x56274f6f0a60]: creating Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] active-connection[0x56274f6f0a60]: set device "wlp61s0" [0x56274f883f00] Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] device[d62304f9da70d783] (wlp61s0): add_pending_action (1): 'activation-5' Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] active-connection[0x56274f6f0a60]: constructed (NMActRequest, version-id 5, type managed) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] auth: call[37]: CheckAuthorization(org.freedesktop.NetworkManager.network-control), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[37]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[38]: CheckAuthorization(org.freedesktop.NetworkManager.settings.modify.system), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] auth: call[38]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': settings plugin does not support adding connections Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4061] keyfile: commit: a4e6f563-eb2a-41ff-bc23-986ee3438ed9 (mywifi_2G) failed to add: error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] active-connection[0x56274f6f0a60]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] active-connection[0x56274f6f0a60]: set state deactivated (was unknown) Feb 01 20:56:04 la
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
A couple of days ago I upgraded my 21.10 system to 22.04 and got this "out of memory" issue (Dell XPS 15 9550 with 3840x2160 display). The fix in comment #41 worked (changing the compression to 19), and the sequence of commands in #44 helped. However, just noting that there are several typos in #44 that had me stumped for a while (it's the first time I've used chroot to update grub). So here are (I think!) the corrected commands to update grub: $ sudo su - # mkdir root # mkdir boot # mkdir efi # cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt # mount /dev/mapper/vgubuntu-root ./root # mount /dev/nvme0n1p1 ./efi # was "nvme01p1" # mount /dev/nvme0n1p2 ./boot # was "nvme01p2" # mount -B ./boot ./root/boot # mount -B ./efi ./root/boot/efi # mount -B /dev ./root/dev # was: mount -B ./dev ./root/boot/dev # mount -B /dev/pts ./root/dev/pts # was: mount -B ./dev/pts ./root/boot/dev/pts # mount -B /proc ./root/proc # was: mount -B ./proc ./root/proc # mount -B /sys ./root/sys # was: mount -B ./sys ./root/sys # chroot ./root # ### Now edit line 196 of /usr/sbin/mkinitramfs to to use -19 instead of -1 # update-initramfs -u -k all # update-grub # exit # reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__
[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'
This bug was fixed in the package netplan.io - 0.105-0ubuntu1 --- netplan.io (0.105-0ubuntu1) kinetic; urgency=medium * New upstream release: 0.105 - Add support for VXLAN tunnels (#288), LP: #1764716 - Add support for VRF devices (#285), LP: #1773522 - Add support for InfiniBand (IPoIB) (#283), LP: #1848471 - Allow key configuration for GRE tunnels (#274), LP: #1966476 - Allow setting the regulatory domain (#281), LP: #1951586 - Documentation improvements & restructuring (#287) - Add meson build system (#268) - Add abigail ABI compatibility checker (#269) - Update of Fedora RPM spec (#264) - CI improvements (#265, #282) - Netplan `set` uses the consolidated libnetplan YAML parser (#254) - Refactor ConfigManager to use the libnetplan YAML parser (#255) - New `netplan_netdef_get_filepath` API (#275) - Improve NetworkManager device management logic (#276), LP: #1951653 Bug fixes: - Fix `apply` netdev rename/create race condition (#260), LP: #1962095 - Fix `try` timeout (#271), LP: #1967084 - Fix infinite timeouts in ovs-vsctl (#266), Closes: #1000137 - Fix offload options using tristate setting (#270), LP: #1956264 - Fix rendering of NetworkManager passthrough WPA (#279), LP: #1972800 - Fix CLI crash on LibNetplanException (#286) - Fix NetworkManager internal DHCP client lease lookup (#284), LP: #1979674 * Update symbols file for 0.105 * d/patches/: Drop patches, applied upstream * d/p/autopkgtest-fixes.patch: Refresh * d/control: bump Standards-Version, no changes needed * d/control, d/tests/control: suggest/add iw for setting a regulatory domain * d/control: merge with Debian, dropping deprecated versioned depends * d/control: Update Vcs-* tags for Ubuntu * d/watch: sync with Debian * d/u/metadata: sync with Debian * d/tests: partially merge with Debian -- Lukas Märdian Thu, 18 Aug 2022 14:53:33 +0200 ** Changed in: netplan.io (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951653 Title: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: I have tried to tell netplan to let my ethernet device be managed by NetworkManager, so that I can then configure a pppoe connection on top of this device. This fails with: # nmcli c up netplan-wan Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged). # I don't know why it mentions 'lo' in that message, but the wan interface is unmanaged (as are all devices on the system, but this one is supposed to be managed): # nmcli d status | grep wan wan ethernet unmanaged -- # After much searching, I've figured out that this comes from /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf: keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Even though I've told netplan to use the NM renderer for this device, the configuration emitted by netplan is insufficient to override this. Using the workaround from https://askubuntu.com/questions/71159/network-manager-says-device-not- managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf) doesn't work, but if I set NetworkManager as the toplevel renderer in /etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-devices.conf is emitted, which evidently DOES work. But I only have one device that I want rendered by NM, so I shouldn't have to declare NM at the top level of the yaml with a lot of duplication in order to get this result. I would argue that the 10-globally-managed-devices.conf should not be there at all. But if it is going to be, then netplan needs to consistently override it whenever there is any use of the NetworkManager backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+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 1951586] Re: Need option to specify wifi regulatory domain
This bug was fixed in the package netplan.io - 0.105-0ubuntu1 --- netplan.io (0.105-0ubuntu1) kinetic; urgency=medium * New upstream release: 0.105 - Add support for VXLAN tunnels (#288), LP: #1764716 - Add support for VRF devices (#285), LP: #1773522 - Add support for InfiniBand (IPoIB) (#283), LP: #1848471 - Allow key configuration for GRE tunnels (#274), LP: #1966476 - Allow setting the regulatory domain (#281), LP: #1951586 - Documentation improvements & restructuring (#287) - Add meson build system (#268) - Add abigail ABI compatibility checker (#269) - Update of Fedora RPM spec (#264) - CI improvements (#265, #282) - Netplan `set` uses the consolidated libnetplan YAML parser (#254) - Refactor ConfigManager to use the libnetplan YAML parser (#255) - New `netplan_netdef_get_filepath` API (#275) - Improve NetworkManager device management logic (#276), LP: #1951653 Bug fixes: - Fix `apply` netdev rename/create race condition (#260), LP: #1962095 - Fix `try` timeout (#271), LP: #1967084 - Fix infinite timeouts in ovs-vsctl (#266), Closes: #1000137 - Fix offload options using tristate setting (#270), LP: #1956264 - Fix rendering of NetworkManager passthrough WPA (#279), LP: #1972800 - Fix CLI crash on LibNetplanException (#286) - Fix NetworkManager internal DHCP client lease lookup (#284), LP: #1979674 * Update symbols file for 0.105 * d/patches/: Drop patches, applied upstream * d/p/autopkgtest-fixes.patch: Refresh * d/control: bump Standards-Version, no changes needed * d/control, d/tests/control: suggest/add iw for setting a regulatory domain * d/control: merge with Debian, dropping deprecated versioned depends * d/control: Update Vcs-* tags for Ubuntu * d/watch: sync with Debian * d/u/metadata: sync with Debian * d/tests: partially merge with Debian -- Lukas Märdian Thu, 18 Aug 2022 14:53:33 +0200 ** Changed in: netplan.io (Ubuntu Kinetic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Committed Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1987004] [NEW] Touchpad stops functioning after wakeup
You have been subscribed to a public bug: Although it happens randomly. The touchpad stops working where the cursor freezes after the system wakes up from suspension mode. The mouse, though, does work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Aug 18 15:15:02 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu wayland-session -- Touchpad stops functioning after wakeup https://bugs.launchpad.net/bugs/1987004 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987004] Re: Touchpad stops functioning after wakeup
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1987004 Title: Touchpad stops functioning after wakeup Status in xorg package in Ubuntu: New Bug description: Although it happens randomly. The touchpad stops working where the cursor freezes after the system wakes up from suspension mode. The mouse, though, does work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Aug 18 15:15:02 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1987004/+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 1987004] Re: [Dell Inspiron 3180] Touchpad stops functioning after wakeup
*** This bug is a duplicate of bug 1899235 *** https://bugs.launchpad.net/bugs/1899235 ** Summary changed: - Touchpad stops functioning after wakeup + [Dell Inspiron 3180] Touchpad stops functioning after wakeup ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1899235 [Dell Inspiron 3180] Touchpad freeze after overnight sleep -- 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/1987004 Title: [Dell Inspiron 3180] Touchpad stops functioning after wakeup Status in linux package in Ubuntu: New Bug description: Although it happens randomly. The touchpad stops working where the cursor freezes after the system wakes up from suspension mode. The mouse, though, does work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Aug 18 15:15:02 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987004/+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 1987026] [NEW] Account Online crash in wayland session
Public bug reported: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987026 Title: Account Online crash in wayland session Status in gnome-online-accounts package in Ubuntu: New Bug description: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1987026/+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 1987026] Re: Account Online crash in wayland session Ubuntu 22.04.1
** Summary changed: - Account Online crash in wayland session + Account Online crash in wayland session Ubuntu 22.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987026 Title: Account Online crash in wayland session Ubuntu 22.04.1 Status in gnome-online-accounts package in Ubuntu: New Bug description: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1987026/+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 1987033] [NEW] Ubuntu Software every time proposes ThinkPad P50 ME update
Public bug reported: Ubuntu Software propose every time to perform ThinkPad P50 ME firmware Update After performing the update at next boot ME firmware is correctly updated. Ubuntu software proposed again at next update. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Attachment added: "Schermata del 2022-08-19 07-16-47.png" https://bugs.launchpad.net/bugs/1987033/+attachment/5609795/+files/Schermata%20del%202022-08-19%2007-16-47.png ** Package changed: gnome-online-accounts (Ubuntu) => software-center (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987033 Title: Ubuntu Software every time proposes ThinkPad P50 ME update Status in software-center package in Ubuntu: New Bug description: Ubuntu Software propose every time to perform ThinkPad P50 ME firmware Update After performing the update at next boot ME firmware is correctly updated. Ubuntu software proposed again at next update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1987033/+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 1987026] Re: Account Online crash in wayland session Ubuntu 22.04.1
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1987026 Title: Account Online crash in wayland session Ubuntu 22.04.1 Status in gnome-online-accounts package in Ubuntu: New Bug description: I am trying to add my google account but dialog box closes immediately and then give me error Ubuntu 22.04.1 has experienced and internal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1987026/+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 1986619] Re: Fail to install base-passwd
** Description changed: /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb (Reading database ... 236425 files and directories currently installed.) Preparing to unpack base-passwd_3.5.52build1_amd64.deb ... Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ... Setting up base-passwd (3.5.52build1) ... Changing home-directory of irc from /var/run/ircd to /run/ircd 1 changes have been made, rewriting files Writing passwd-file to /etc/passwd Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission denied dpkg: error processing package base-passwd (--install): - installed base-passwd package post-installation script subprocess returned error exit status 4 + installed base-passwd package post-installation script subprocess returned error exit status 4 Errors were encountered while processing: - base-passwd - root@CNQDSX-160396:/home/frank/Downloads# + base-passwd + root@CNQDSX:/home/frank/Downloads# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1986619 Title: Fail to install base-passwd Status in base-passwd package in Ubuntu: New Bug description: /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb (Reading database ... 236425 files and directories currently installed.) Preparing to unpack base-passwd_3.5.52build1_amd64.deb ... Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ... Setting up base-passwd (3.5.52build1) ... Changing home-directory of irc from /var/run/ircd to /run/ircd 1 changes have been made, rewriting files Writing passwd-file to /etc/passwd Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission denied dpkg: error processing package base-passwd (--install): installed base-passwd package post-installation script subprocess returned error exit status 4 Errors were encountered while processing: base-passwd root@CNQDSX:/home/frank/Downloads# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1986619/+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 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
** Summary changed: - My machine as Wi-Fi Hotspot broken after upgrade to 22.04 + My machine has Wi-Fi Hotspot broken after upgrade to 22.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1969709] Re: libreoffice font selection unusably slow
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in fontconfig package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 1969709] Re: libreoffice font selection unusably slow
This font delay problem in libreoffice-writer 7.3/7.4 seems to be a combination of libreoffice-gtk3 and Nvidia proprietary driver. The problem appears with default desktop enviroment and with gnome classic. Problem appears in wayland and xorg. Ubuntu 22.04 GPU Nvidia 750ti (Nvidia Driver 515) Libre Office 7.3/7.4 Extreme Font Menu Delay when: Nvidia driver - Installed AND libreofffice-gtk3 Installed No Font Menu delay when: Nvidia driver Installed AND libreofffice-gtk3 Not Installed Nvidia driver Not Installed AND libreofffice-gtk3 Installed Nvidia driver Not Installed AND libreofffice-gtk3 Not Installed I can confirm David White. No problem in Mint 21. BUT As soon as i install gnome and log into a gnome session with Mint 21, then the extreme font delay will appear in libre office. When i log back into a mate session then the font menu behaves as it should. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in fontconfig package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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