[Touch-packages] [Bug 1915226] Re: network-manager continuous inappropriate site surveys
Kroger is conducting a customer satisfaction survey to learn about customers' actual experience during their Kroger store visit. As a token of appreciation from the company, the management is offering 50 fuel points for free to the customers who participated in the survey on the https://kroger-feedback.online/ official site. -- 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/1915226 Title: network-manager continuous inappropriate site surveys Status in network-manager package in Ubuntu: New Bug description: this message is flooding my kernel ring RTW: ERROR [RFK-CHK] RF-K not allowed due to ifaces under site-survey network details are as follows. ~$ ifconfig eno1: flags=4163 mtu 1500 inet 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::d323:619a:9114:8f78 prefixlen 64 scopeid 0x20 ether 48:0f:cf:5f:e6:12 txqueuelen 1000 (Ethernet) RX packets 49088 bytes 15509621 (15.5 MB) RX errors 0 dropped 0 overruns 0 frame RTL8811CU0 TX packets 36480 bytes 5212324 (5.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xd100-d102 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 204584 bytes 11022005 (11.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 204584 bytes 11022005 (11.0 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlx001325ad55e1: flags=4163 mtu 1500 inet 192.168.1.103 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::9a15:f995:c011:c29e prefixlen 64 scopeid 0x20 ether 00:13:25:ad:55:e1 txqueuelen 1000 (Ethernet) RX packets 62335 bytes 9276176 (9.2 MB) RX errors 0 dropped 2 overruns 0 frame 0 TX packets 4605 bytes 645037 (645.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1 is through motherboard wlx001325ad55e1 is though USB: Volans VL-UW60-FD using a RTL8811CU chip (see https://www.volans.com.au/product/vl-uw60-fd/) Both cable and wireless connections are working well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 12:06:18 2021 InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev eno1 proto dhcp metric 100 default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 metric 600 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1915226/+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 1869655] Re: Boot animations start too late to be useful
** Changed in: plymouth (Ubuntu) Status: Won't Fix => In Progress ** Changed in: plymouth (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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 1970069] Re: Annoying boot messages interfering with splash screen
Here's a fix for plymouth/noble. The source is in: https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest We skipped ubuntu5 because that technically existed in bug 2054769 for 10 days already. Also note this will cause some temporary initrd bloat while the initramfs-tools change is pending in comment #90. ** Patch added: "plymouth_24.004.60-1ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5756732/+files/plymouth_24.004.60-1ubuntu6.debdiff -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1869655] Re: Boot animations start too late to be useful
The patch proposed in https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/comments/91 will help here, but since it might not be the last plymouth change required for this issue, it doesn't mention bug 1869655. -- 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/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
Hi, Could you tell me when the fix will ready? And how we can get the fixed version? Our QA's test item is blocking on this issue, Will the fixed version be released in the next few days:)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2057996 Title: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme- stas,shim-signed Status in subiquity package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: verison:ubuntu 24.04 subiquity version OS:noble-live-server-amd64-0222.iso CPU:AMD EPYC 9634 84-Core Processor*1 MEMORY: M321R2GA3BB6-CQKVG*2 ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD UEFI MODE lsb_release -rd: Description:Untun Noble Numbat(development branch) Release: 24.04 What you expected to happen: Install os on nvme,expected to install succefully. What happened instead: Install os on nvme, install always failed. Before installation, we cleaned up all our nvme disk by dd if=/dev/zero of=/dev/sda bs=1M count=5 The error log: Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed', 'nvme-cli', 'nvme-stas', 'shim-signed'] Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages: FAIL: installing missing packages Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command curthooks Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback (most recent call last): Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py", line 202, in main Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret = args.func(args) Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py", line 1998, in curthooks Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: builtin_curthooks(cfg, target, state) Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py", line 1803, in builtin_curthooks Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: install_missing_packages(cfg, target, osfamily=osfamily) Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py", line 1362, in install_missing_packages Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: distro.install_packages(to_add, target=target, osfamily=osfamily) Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472, in install_packages Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return install_cmd('install', args=pkglist, opts=opts, target=target, Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254, in run_apt_command Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = apt_install(mode, args, opts=opts, env=env, target=target, Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302, in apt_install Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv = inchroot.subp(cmd + dl_opts + packages, env=env, Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791, in subp Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return subp(*args, **kwargs) Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283, in subp Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return _subp(*args, **kwargs) Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File "/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147, in _subp Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise ProcessExecutionError(stdout=out, stderr=err, Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: curtin.util.ProcessE
[Touch-packages] [Bug 2058017] Re: openssl is not LTO-safe
** Changed in: openssl (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2058017 Title: openssl is not LTO-safe Status in openssl package in Ubuntu: Fix Committed Bug description: tl;dr: since it's too much work to make openssl LTO-safe, upstream doesn't see it as a goal and doesn't test it, and there are probably no performance gains to LTO for this package. Openssl is an old project and the codebase wasn't written with aliasing rules in mind. There are several reports of issues related to LTO. The openssl technical commitee says "currently we're not going to fix all the strict aliasing and other LTO problems" and "Fixes raised in pull requests will be considered."; in other words: if you find a violation, we'll merge your fixes but we're not going to dedicate time to fixing them ourselves. We don't have specific reports on launchpad at the moment but there has been at least one issue experienced by the FIPS: the compiler decided a 0-filled array could be removed and proceeded to do so. In addition to that, compilers are only pushing this further and further. Issues are impossible to predict and even security updates could trigger issues. Gentoo prevents usage of LTO for openssl and has some links related to this at https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/openssl/openssl-3.2.1-r1.ebuild#n131 : - https://github.com/llvm/llvm-project/issues/55255 - https://github.com/openssl/openssl/issues/12247 - https://github.com/openssl/openssl/issues/18225 - https://github.com/openssl/openssl/issues/18663 - https://github.com/openssl/openssl/issues/18663#issuecomment-1181478057 Gentoo also prevents usage of -fstrict-aliasing and always set -fno- strict-aliasing. I don't plan to do the same at least at the moment and for Noble since I don't have time to investigate more changes. Performance shouldn't be impacted much if at all: - crypto algorithms are implemented in ASM (funnily, using C implementations can trigger issues because these got miscompiled) - the rest of the openssl codebase probably doesn't benefit from LTO because source files match codepaths quite well - at the moment, openssl performance for servers is bad due to algorithmic/architectural issues, not micro-optimizations and these wouldn't be noticed - if LTO-compliance was doable and thought to be useful by upstream, they would have certainly pushed that forward, especially in the wake of openssl 3.0's performance issues. Code size increases by a few percents except for libcrypto which gets 17% larger. The corresponding .deb file increases by 2.6% only. I ran "openssl speed" with a long benchmark time in order to get good results (there is a variation of several percents with the default times). I then scripted a diff which output is shown below; "." means the difference is within 2% which is the vast majority. Also note that some important ciphers are not present due to how openssl speed works; small aes-*-cbc are negatively impacted, up to -10% but that would -50% if you compared between "software" and "hardware" implementations, the results would be reversed at anything but the smallest data sizes, and the fact that you want to use hardware implementations as much as possible means that you also want to avoid places where LTO could have an effect. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes md5 . . . . .. sha1 . . . . .. rmd160. . . . .. sha256+2.3% . . . .. sha512. . . . .. hmac(md5) . . . . .. des-ede3 . . . . .. aes-128-cbc -10.0% . . . .. aes-192-cbc -7.6% . . . .. aes-256-cbc -5.2% . . . .. camellia-128-cbc . . . . .. camellia-192-cbc . . . . .. camellia-256-cbc . . . . .. ghash . . +21.2% -27.3% +30.5% +39.3% rand -2.8% -2.9% -2.9% -2.8% .. sign verify sign/s verify/s rsa 512 bits0.31s
[Touch-packages] [Bug 2056593] Re: [FFE] FIPS compatibility patches
** Changed in: openssl (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2056593 Title: [FFE] FIPS compatibility patches Status in openssl package in Ubuntu: Fix Committed Bug description: We have an open MR with a handful of FIPS compatibilty changes we wore hoping to get into 24.04. The main purpose of the changes is to detect whether the kernel is running in FIPS mode and adjust the behavior of the library accordingly by loading the correct provider backend and using defaults that are FIPS compliant (no md5, DES etc) instead trying to use non-compliant code paths and crashing. The proposed patches were taken from the OpenSSL version shipped in the FIPS archive at esm.ubuntu.com for 22.04. Having them in the regular archive will reduce the maintenance work significantly. None of the changes should have any impact on running OpenSSL in regular (non-fips) mode. Below is a detailed list of the changes: - d/p/fips/crypto-Add-kernel-FIPS-mode-detection.patch: This adds a new internal API to determine whether the kernel has been booted in FIPS mode. This can be overridden with the OPENSSL_FORCE_FIPS_MODE environment variable. OPENSSL_FIPS_MODE_SWITCH_PATH can be used to specify an alternative path for the fips_enabled file and is used in tests. The FIPS_MODULE switch can be used to enable build of the the FIPS provider module specific parts which are not needed in the OpenSSL library itself. - d/p/fips/crypto-Automatically-use-the-FIPS-provider-when-the-kerne.patch: This automatically configures all library contexts to use the FIPS provider when the kernel is booted in FIPS mode by: - Setting "fips=yes" as the default property for algorithm fetches - Loading and activating the FIPS provider as the fallback provider. If applications load providers via a configuration either because the default configuration is modified or they override the default configuration, this disables loading of the fallback providers. In this case, the configuration must load the FIPS provider when FIPS mode is enabled, else algorithm fetches will fail Applications can choose to use non-FIPS approved algorithms by specifying the "-fips" or "fips=no" property for algorithm fetches and loading the default provider. - d/p/fips/apps-speed-Omit-unavailable-algorithms-in-FIPS-mode.patch: Omit unavailable algorithms in FIPS mode - d/p/fips/apps-pass-propquery-arg-to-the-libctx-DRBG-fetches.patch The -propquery argument might be used to define a preference for which provider an algorithm is fetched from. Set the query properties for the library context DRBG fetches as well so that they are fetched with the same properties. - d/p/fips/test-Ensure-encoding-runs-with-the-correct-context-during.patch: This test uses 2 library contexts - one context for creating initial test keys, and then another context (or the default context) for running tests. There is an issue that during the encoding tests, the OSSL_ENCODER_CTX is created from the created EVP_PKEYs, which are associated with the library context used to create the keys. This means that encoding tests run with the wrong library context, which always uses the default provider. These changes are now included in a larger MR with other changes in the same package version: https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+merge/462486 The now-superseded MR is at https://code.launchpad.net/~tobhe/ubuntu/+source/openssl/+git/openssl/+merge/460953 Since OpenSSL just received another big update to 3.0.13 we had to rebase our changes and will have to rerun our install/upgrade tests. A test build is also available at https://launchpad.net/~tobhe/+archive/ubuntu/openssl-test/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2056593/+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 2058231] [NEW] Fallback to IPv4-LL when DHCP is failing
Public bug reported: The intention of the previous avahi-autoipd integration was that on a connection that does have dhcp configured, it will fall back to IPV4LL if dhcp is unavailable. This integration was recently dropped (and I think it never worked as intended in the first place): https://code.launchpad.net/~vorlon/ubuntu-seeds/+git/ubuntu/+merge/460785 We want to implement this functionality in Ubuntu/NetworkManager and there's some upstream work tracking this too: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/966 See FR-4142 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/2058231 Title: Fallback to IPv4-LL when DHCP is failing Status in network-manager package in Ubuntu: New Bug description: The intention of the previous avahi-autoipd integration was that on a connection that does have dhcp configured, it will fall back to IPV4LL if dhcp is unavailable. This integration was recently dropped (and I think it never worked as intended in the first place): https://code.launchpad.net/~vorlon/ubuntu-seeds/+git/ubuntu/+merge/460785 We want to implement this functionality in Ubuntu/NetworkManager and there's some upstream work tracking this too: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/966 See FR-4142 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2058231/+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 1970069] Re: Annoying boot messages interfering with splash screen
It seems unlikely my all-in-one kernel fix will be accepted upstream. While I could propose it as an Ubuntu patch, another alternative is to just let the linux task track bug 2049390 (Fix Committed). Then most people will only need the above Plymouth patch to get a complete fix. The remaining tasks beyond that are: initramfs-tools: Required to keep the initrd size under control after the Plymouth fix is released. systemd: Would still be nice to implement a redundant fix to suppress the "clean" message. That would fix bug 1914409 and when combined with loglevel=3, would also prevent this bug 1970069. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1869655] Re: Boot animations start too late to be useful
** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2058053] Re: Change sudo compile options from --with-all-insults to --with-pc-insults
Yep, we can close this, my mistake. I was thrown off but he fact that the brains one was previously gated by PC insults, but is included despite default to PC since https://www.sudo.ws/repos/sudo/rev/eb264d342601 . Nothing to see here, move along :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2058053 Title: Change sudo compile options from --with-all-insults to --with-pc- insults Status in sudo package in Ubuntu: New Bug description: Tame as they might be, I'd like to continue using "Defaults insults" without any risk of upsetting anyone (and without having to maintain our own package version.) Would the safe insults version at compile time "--with-pc-insults" be a sensible default for all? Current as of Jammy, but looks like it's still the default compile option across the board Version: 1.9.9-1ubuntu2 Current behaviour : Enabling includes the "not PC" insults Expected behaviour : Insults would default to "PC" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2058053/+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 2058241] [NEW] [X570 AORUS ELITE, Realtek ALCS1200A, Black Line Out, Rear] Pulseaudio fails to detect card
Public bug reported: Audio is very crackly, choppy, and when converting videos, the videos end up the same. The system has a Realtek audio built in, but the driver shows Generic. Tried nearly all online fixes, none work but it seems many people have the same issue. Can someone help? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-25.25.1-lowlatency 6.5.13 Uname: Linux 6.5.0-25-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 18 06:38:35 2024 InstallationDate: Installed on 2024-03-17 (1 days ago) InstallationMedia: Ubuntu-Studio 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HD-Audio Generic Symptom_Jack: Black Line Out, Rear Title: [X570 AORUS ELITE, Realtek ALCS1200A, Black Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F38e dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF38e:bd07/18/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2058241 Title: [X570 AORUS ELITE, Realtek ALCS1200A, Black Line Out, Rear] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: Audio is very crackly, choppy, and when converting videos, the videos end up the same. The system has a Realtek audio built in, but the driver shows Generic. Tried nearly all online fixes, none work but it seems many people have the same issue. Can someone help? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-25.25.1-lowlatency 6.5.13 Uname: Linux 6.5.0-25-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 18 06:38:35 2024 InstallationDate: Installed on 2024-03-17 (1 days ago) InstallationMedia: Ubuntu-Studio 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HD-Audio Generic Symptom_Jack: Black Line Out, Rear Title: [X570 AORUS ELITE, Realtek ALCS1200A, Black Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F38e dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF38e:bd07/18/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2058241/+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 2058053] Re: Change sudo compile options from --with-all-insults to --with-pc-insults
Actually, I think you're right, the brains one does seem to be included because while that upstream patch does do the following to plugins/sudoers/ins_classic.h, it didn't apply the same change to plugins/sudoers/ins_csops.h: -#ifdef PC_INSULTS +#ifndef OFFENSIVE_INSULTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2058053 Title: Change sudo compile options from --with-all-insults to --with-pc- insults Status in sudo package in Ubuntu: New Bug description: Tame as they might be, I'd like to continue using "Defaults insults" without any risk of upsetting anyone (and without having to maintain our own package version.) Would the safe insults version at compile time "--with-pc-insults" be a sensible default for all? Current as of Jammy, but looks like it's still the default compile option across the board Version: 1.9.9-1ubuntu2 Current behaviour : Enabling includes the "not PC" insults Expected behaviour : Insults would default to "PC" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2058053/+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 2058053] Re: Change sudo compile options from --with-all-insults to --with-pc-insults
Could you please file a bug upstream about the missing change, and let us know the bug number? https://bugzilla.sudo.ws/index.cgi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2058053 Title: Change sudo compile options from --with-all-insults to --with-pc- insults Status in sudo package in Ubuntu: New Bug description: Tame as they might be, I'd like to continue using "Defaults insults" without any risk of upsetting anyone (and without having to maintain our own package version.) Would the safe insults version at compile time "--with-pc-insults" be a sensible default for all? Current as of Jammy, but looks like it's still the default compile option across the board Version: 1.9.9-1ubuntu2 Current behaviour : Enabling includes the "not PC" insults Expected behaviour : Insults would default to "PC" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2058053/+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 2058053] Re: Change sudo compile options from --with-all-insults to --with-pc-insults
I'll fix this issue in noble. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2058053 Title: Change sudo compile options from --with-all-insults to --with-pc- insults Status in sudo package in Ubuntu: New Bug description: Tame as they might be, I'd like to continue using "Defaults insults" without any risk of upsetting anyone (and without having to maintain our own package version.) Would the safe insults version at compile time "--with-pc-insults" be a sensible default for all? Current as of Jammy, but looks like it's still the default compile option across the board Version: 1.9.9-1ubuntu2 Current behaviour : Enabling includes the "not PC" insults Expected behaviour : Insults would default to "PC" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2058053/+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 2058233] [NEW] Sound choppy watching video with bluetooth headset
You have been subscribed to a public bug: This is consistent across firefox, chrome and VLC. Checked all settings I could find in the GUI (still new to linux), and headphones seemed to be connected just fine. Sound test in the settings worked fine. Everything works well when using wired headphones. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: whistler 2494 F wireplumber /dev/snd/controlC1: whistler 2494 F wireplumber /dev/snd/seq:whistler 2478 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 11:51:27 2024 InstallationDate: Installed on 2024-02-23 (24 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2019 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: JDET69WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrJDET69WW(1.31):bd10/31/2019:br1.31:efr1.28:svnLENOVO:pn20DSS0U800:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20DS_BU_Think_FM_ThinkPadL450: dmi.product.family: ThinkPad L450 dmi.product.name: 20DSS0U800 dmi.product.sku: LENOVO_MT_20DS_BU_Think_FM_ThinkPad L450 dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- Sound choppy watching video with bluetooth headset https://bugs.launchpad.net/bugs/2058233 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 2058242] [NEW] Demote isc-dhcp to universe
Public bug reported: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc-dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2058242 Title: Demote isc-dhcp to universe Status in isc-dhcp package in Ubuntu: New Bug description: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc- dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2058242/+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 1970069] Re: Annoying boot messages interfering with splash screen
Looking at the remaining "add drm modules (only if MODULES=dep)" section: This logic should moved to hooks/framebuffer as well. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2058053] Re: Change sudo compile options from --with-all-insults to --with-pc-insults
I've filed the upstream bug and have linked it here, please ignore my comment #6. ** Bug watch added: bugzilla.sudo.ws/ #1068 http://bugzilla.sudo.ws/show_bug.cgi?id=1068 ** Also affects: sudo via http://bugzilla.sudo.ws/show_bug.cgi?id=1068 Importance: Unknown Status: Unknown ** Also affects: sudo (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu Focal) Status: New => Confirmed ** Changed in: sudo (Ubuntu Jammy) Status: New => Confirmed ** Changed in: sudo (Ubuntu Mantic) Status: New => Confirmed ** Changed in: sudo (Ubuntu Noble) Status: New => Confirmed ** Changed in: sudo (Ubuntu Noble) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2058053 Title: Change sudo compile options from --with-all-insults to --with-pc- insults Status in sudo: Unknown Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Focal: Confirmed Status in sudo source package in Jammy: Confirmed Status in sudo source package in Mantic: Confirmed Status in sudo source package in Noble: Confirmed Bug description: Tame as they might be, I'd like to continue using "Defaults insults" without any risk of upsetting anyone (and without having to maintain our own package version.) Would the safe insults version at compile time "--with-pc-insults" be a sensible default for all? Current as of Jammy, but looks like it's still the default compile option across the board Version: 1.9.9-1ubuntu2 Current behaviour : Enabling includes the "not PC" insults Expected behaviour : Insults would default to "PC" To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/2058053/+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 2058249] [NEW] US symlinks missing in /usr/share/zoneinfo
Public bug reported: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. ** 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/2058249 Title: US symlinks missing in /usr/share/zoneinfo Status in tzdata package in Ubuntu: New Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+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 2058253] [NEW] Notebook screen the look is "matte"
Public bug reported: Hi, feedback: In general, on the notebook screen, the look is "matte", smoke in the images, videos, games, on the desktop, etc., especially when the screen brightness increases. When compared to Ubuntu with gnome, windows 11, it has greater clarity, stronger colors, etc. In Kubuntu I didn't find the option to increase the sharpness, to improve etc., so I wanted to leave feedback here, to help with the project. 😄 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Mar 18 10:56:50 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f9c] InstallationDate: Installed on 2024-01-13 (64 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 82MD ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-26-generic root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2058253 Title: Notebook screen the look is "matte" Status in xorg package in Ubuntu: New Bug description: Hi, feedback: In general, on the notebook screen, the look is "matte", smoke in the images, videos, games, on the desktop, etc., especially when the screen brightness increases. When compared to Ubuntu with gnome, windows 11, it has greater clarity, stronger colors, etc. In Kubuntu I didn't find the option to increase the sharpness, to improve etc., so I wanted to leave feedback here, to help with the project. 😄 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Mar 18 10:56:50 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f9c] InstallationDate: Installed on 2024-01-13 (64 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 82MD ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-26-generic root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vend
[Touch-packages] [Bug 2058233] [NEW] Sound choppy watching video with bluetooth headset
You have been subscribed to a public bug: This is consistent across firefox, chrome and VLC. Checked all settings I could find in the GUI (still new to linux), and headphones seemed to be connected just fine. Sound test in the settings worked fine. Everything works well when using wired headphones. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: whistler 2494 F wireplumber /dev/snd/controlC1: whistler 2494 F wireplumber /dev/snd/seq:whistler 2478 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 11:51:27 2024 InstallationDate: Installed on 2024-02-23 (24 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2019 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: JDET69WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrJDET69WW(1.31):bd10/31/2019:br1.31:efr1.28:svnLENOVO:pn20DSS0U800:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20DS_BU_Think_FM_ThinkPadL450: dmi.product.family: ThinkPad L450 dmi.product.name: 20DSS0U800 dmi.product.sku: LENOVO_MT_20DS_BU_Think_FM_ThinkPad L450 dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- Sound choppy watching video with bluetooth headset https://bugs.launchpad.net/bugs/2058233 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 2045096] Re: Error in network definition: Invalid MAC address 'random'
This will be part of 1.0-1 ** Changed in: netplan.io (Ubuntu) Status: New => Fix Committed -- 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/2045096 Title: Error in network definition: Invalid MAC address 'random' Status in netplan: Fix Committed Status in netplan.io package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: New Bug description: netplan dose not understand the 'random' key word in 'Cloned MAC address' set by networkmanager. ``` /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC address 'random', must be XX:XX:XX:XX:XX:XX or XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX macaddress: "random" ^ ``` netplan Version 0.107-5ubuntu2 network-manager Version 1.44.2-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2045096/+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 2057768] Re: Unit and its Alias appear to be separate entities when enabling the unit by filepath
Fixed in upstream: https://github.com/systemd/systemd/pull/31816. I will plan on getting this patch in noble, but I am not sure about focal or jammy. ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged -- 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/2057768 Title: Unit and its Alias appear to be separate entities when enabling the unit by filepath Status in systemd package in Ubuntu: Triaged Bug description: ### systemd version the issue has been seen with 245 ### Used distribution Linux Mint 20.1 and Ubuntu 20.04 ### Linux kernel version used 5.4.0-135-generic ### CPU architectures issue was seen on None ### Component systemctl ### Expected behaviour you didn't see When including an alias in a unit file that is enabled by referring to its filepath, its alias should refer to the unit - the two should refer to the exact same service. This is the case when the unit file is enabled inside one of the systemd directories. I expect alias and unit to refer to one identical service also when enabling via filepath. In particular, the output of `systemctl status ...` should be identical for a Unit and its Alias. ### Unexpected behaviour you saw After passing a systemd unit including an alias to `systemctl enable PATH...` by path, systemctl treated the unit and its alias as separate units. Specifically, `systemctl status` reports different results (running/inactive, PID if applicable) for the unit name and its alias. When I start the unit by its original name, only the status of the unit is reported as running while the status of the alias remains inactive, and vice versa. After starting the Alias too, two services with different PIDs are running. (When copying the unit into /etc/systemd/system/ and running `systemctl enable UNIT...` this issue does not occur and alias and unit behave the same.) ### Steps to reproduce the problem ``` ~$ cat dummy.service [Service] ExecStart=tail -f /dev/null [Install] Alias=dumb.service ~$ sudo systemctl enable ~/dummy.service Created symlink /etc/systemd/system/dumb.service → /home/lukas/dummy.service. Created symlink /etc/systemd/system/dummy.service → /home/lukas/dummy.service. ~$ sudo systemctl start dummy ~$ systemctl status dummy ● dummy.service Loaded: loaded (/etc/systemd/system/dummy.service; enabled; vendor preset:> Active: active (running) since Tue 2024-03-12 15:36:58 CET; 8s ago Main PID: 159809 (tail) Tasks: 1 (limit: 76978) Memory: 160.0K CGroup: /system.slice/dummy.service └─159809 /usr/bin/tail -f /dev/null Mär 12 15:36:58 MyMachine systemd[1]: Started dummy.service. ~$ systemctl status dumb ● dumb.service Loaded: loaded (/etc/systemd/system/dumb.service; enabled; vendor preset: > Active: inactive (dead) Mär 12 15:30:53 MyMachine systemd[1]: Started dumb.service. Mär 12 15:31:16 MyMachine systemd[1]: Stopping dumb.service... Mär 12 15:31:16 MyMachine systemd[1]: dumb.service: Succeeded. Mär 12 15:31:16 MyMachine systemd[1]: Stopped dumb.service. ~$ ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057768/+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 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet
Thanks for the heads-up for Netplan! IIUC this will be fixed by a systemd SRU, so closing it as "Invalid" for Netplan. Please re-open if you feel there is something to do on our side. ** Changed in: netplan.io (Ubuntu) Status: New => Invalid -- 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/2055397 Title: netplan/systemd-networkd: route metric not applied to routes to the local subnet Status in cloud-init package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Bug description: Cloud-init introduced a feature to configure policy routing on AWS EC2 instances with multiple NICs in https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb targeting v24.1. Cloud-init generates the following netplan config: ``` $ cat /etc/netplan/50-cloud-init.yaml network: ethernets: ens5: dhcp4: true dhcp4-overrides: &id001 route-metric: 100 dhcp6: true dhcp6-overrides: *id001 match: macaddress: 0a:c8:ab:90:c2:fb set-name: ens5 ens6: dhcp4: true dhcp4-overrides: route-metric: 200 use-routes: true dhcp6: false match: macaddress: 0a:c6:55:a1:dc:3b routes: - table: 101 to: 0.0.0.0/0 via: 192.168.0.1 - table: 101 to: 192.168.0.0/20 routing-policy: - from: 192.168.10.212 table: 101 set-name: ens6 version: 2 ``` Which renders the following systemd-networkd config files: ``` $ cat 10-netplan-ens5.link [Match] MACAddress=0a:c8:ab:90:c2:fb [Link] Name=ens5 WakeOnLan=off $ cat 10-netplan-ens5.network [Match] MACAddress=0a:c8:ab:90:c2:fb Name=ens5 [Network] DHCP=yes LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true $ cat 10-netplan-ens6.link [Match] MACAddress=0a:c6:55:a1:dc:3b [Link] Name=ens6 WakeOnLan=off $ cat 10-netplan-ens6.network [Match] MACAddress=0a:c6:55:a1:dc:3b Name=ens6 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [Route] Destination=0.0.0.0/0 Gateway=192.168.0.1 Table=101 [Route] Destination=192.168.0.0/20 Scope=link Table=101 [RoutingPolicyRule] From=192.168.10.212 Table=101 [DHCP] RouteMetric=200 UseMTU=true ``` Which configures the instance with the following state in Ubuntu Focal: ``` $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5 valid_lft 2087sec preferred_lft 2087sec inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic noprefixroute valid_lft 440sec preferred_lft 130sec inet6 fe80::8c8:abff:fe90:c2fb/64 scope link valid_lft forever preferred_lft forever 3: ens6: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6 valid_lft 2083sec preferred_lft 2083sec inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link valid_lft forever preferred_lft forever $ ip route show default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.94 metric 100 default via 192.168.0.1 dev ens6 proto dhcp src 192.168.10.212 metric 200 192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.12.94 192.168.0.0/20 dev ens6 proto kernel scope link src 192.168.10.212 192.168.0.1 dev ens5 proto dhcp scope link src 192.168.12.94 metric 100 192.168.0.1 dev ens6 proto dhcp scope link src 192.168.10.212 metric 200 $ ip rule show 0: from all lookup local 0: from 192.168.10.212 lookup 101 32766: from all lookup main 32767: from all lookup default $ ip route show table 101 default via 192.168.0.1 dev ens6 proto static onlink 192.168.0.0/20 dev ens6 proto static scope link ``` The issue here is that the instance is not reachable from the same subnet via the private ipv4 of the primary NIC, packets are routed to egress via ens6 and dropped. The cause is that interface metrics are not applied to loca
[Touch-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
We should land a fix keeping the full string in networkmanager.passthrough and additionaly work on a proper upstream solution, as suggested by Danilo in comment #4, introducing new settings as a longer term solution. ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => High -- 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/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan Status in netplan: Triaged Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From: https://discourse.ubuntu.com/t/blog-netplan-developer- diaries/35932/11 Hi all, NetworkManager connections with an explicit DoT (DNS over TLS) configuration are not supported with Netplan, but NetworkManager does feed back the DoT DNS info with server address and Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+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 2058035] Re: [SRU] Create directories for apt configuration files if they are absent
I've included the bug reference to 0.96.20.13 and reuploaded (also force pushed the vcs so you might need to force pull over ubuntu/xenial) ** Changed in: software-properties (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058035 Title: [SRU] Create directories for apt configuration files if they are absent Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Xenial: Fix Committed Bug description: Impact -- The autopkgtest for 0.96.20.12, which introduces Ubuntu Pro in Xenial's software-properties, failed on Dbus tests[1]. The failure is because, at some point in time, the .keep file were removed from the otherwise empty tests/aptroot/etc/apt/apt.conf.d/. This caused the Git repository to drop tests/aptroot/etc/apt/apt.conf.d/ and also its parent, which also became empty, and the tests try to directly create files in those directories, raising the error. It seems that previous uploaders did not use the Git checkout, as the offending commit was introduced in Jun 2019 and there were subsequent uploads that did contain those empty directories. Test case - Trigger an autopkgtest against the proposed package version. It must succeed. Regression Potential Although the introduced change is idempotent, there could be other part of the code assuming the directories didn't exist and trying to create them with a "fail if already exists" approach, causing a runtime regression. [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- xenial/xenial/amd64/s/software- properties/20240301_100314_9e242@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058035/+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 2058233] Re: Sound choppy watching video with bluetooth headset
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2058233 Title: Sound choppy watching video with bluetooth headset Status in alsa-driver package in Ubuntu: New Bug description: This is consistent across firefox, chrome and VLC. Checked all settings I could find in the GUI (still new to linux), and headphones seemed to be connected just fine. Sound test in the settings worked fine. Everything works well when using wired headphones. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: whistler 2494 F wireplumber /dev/snd/controlC1: whistler 2494 F wireplumber /dev/snd/seq:whistler 2478 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 11:51:27 2024 InstallationDate: Installed on 2024-02-23 (24 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2019 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: JDET69WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrJDET69WW(1.31):bd10/31/2019:br1.31:efr1.28:svnLENOVO:pn20DSS0U800:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20DS_BU_Think_FM_ThinkPadL450: dmi.product.family: ThinkPad L450 dmi.product.name: 20DSS0U800 dmi.product.sku: LENOVO_MT_20DS_BU_Think_FM_ThinkPad L450 dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058233/+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 2058249] Re: US symlinks missing in /usr/share/zoneinfo
Yes, this is an intentional change. All backward compatibility symlinks were moved to the tzdata-legacy package. Please install this package for such use cases. ** Changed in: tzdata (Ubuntu) Status: New => Invalid ** Summary changed: - US symlinks missing in /usr/share/zoneinfo + US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy -- 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/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+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 2056187] Re: fails to configure BOOTIF when using iscsi
Attached the uploaded diff for jammy. Besides the few lines changed in scripts/functions I backported the improvements of the autopkgtest to increase the test coverage and to test on all architectures. See https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+ref/ubuntu/jammy for the individual commits for details. I tested the autopkgtest changes in my PPA. ** Description changed: + [ Impact ] + + * MAAS cannot PXE-boot a machine that has iSCSI disks + + * Focal is the default Ubuntu distribution deployed by MAAS, so we should +back-port this to ensure it works out-of-the-box. + + [ Test Plan ] + + * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager + in the original report), and a MAAS controller (3.4 or better) + + * the issue can be observed by simply enlisting the machine in MAAS. It will + fail to boot due to the missing BOOTIF configuration. + + [ Where problems could occur ] + + * the problematic code was an attempt to fix LP#2037202, so we should watch out + for regressions. + + [ Original report ] + we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: - for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do - if [ -e "$x" ]; then - IP=done - break - fi - done + for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do + if [ -e "$x" ]; then + IP=done + break + fi + done ** Patch added: "initramfs-tools_0.140ubuntu13.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5756863/+files/initramfs-tools_0.140ubuntu13.5.debdiff -- 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/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2058249] Re: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy
Thank you, that certainly resolves the missing files. While I understand the reason behind the switch, I can't find where the "intentional change" is communicated. There is no `apt changelog tzdata`, and nothing else I see gives me a hint that the package was split in that way. While it may not impact everybody like it did me, is there some way to formally communicate this, perhaps within the package description for `tzdata`? -- 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/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+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 2051181] Re: apt cannot upgrade phased updates if the current security version is same as updates
The regressions on mantic have cleared up and the tests of apt have passed so this is verified there. Still clearing out a regression from update-manager:i386 on jammy- ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2051181 Title: apt cannot upgrade phased updates if the current security version is same as updates Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Released Bug description: [Impact] A package that has the same version in -security and -updates, with the latter having a Phased-Update-Percentage set is subject to phasing which is not expected by the security team. [Test plan] An automatic test case has been added to apt's comprehensive integration test suite that simulates the problem. Passing of the autopkgtests is a successful test. [Where problems could occur] The fix in question changes the behavior, some people may have relied on that, but also this should not have happened server side (normally security updates do not receive a value but the real one in this case went a different route). Otherwise the fix is fairly contained, it removes a single OtherVer++ increment which made it go one version below the current version, so we do not expect any problems; setting aside the usual regression potential from bugs in the compiler and so on. [Original bug report] When I finished installation with Jammy 22.04.3, I noticed that nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-upgrade`. Below is the log of apt upgrade: ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run [2/1878] Reading package lists... Done Building dependency tree... Done Reading state information... Done Entering ResolveByKeep 10% Dependencies are not satisfied for nvidia-driver-535:amd64 < 535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib > Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 535.129.03-1) Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Keeping package linux-modules-nvidia-535-oem-22.04c:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Package linux-modules-nvidia-535-oem-22.04c:amd64 linux-modules-nvidia-535-oem-22.04c:amd64 Depends on linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27) Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN Ib > Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-objects-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package linux-objects-nvidia-535-6.1.0-1027-oem:amd64 due to Depends https://pastebin.canonical.com/p/7frwTKZG6D/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2051181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@
[Touch-packages] [Bug 1995790] Re: regression: ?garbage does not work correctly in install commands
The regressions on mantic have cleared up and the tests of apt have passed so this is verified there. Still clearing out a regression from update-manager:i386 on jammy- ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Released Bug description: [Impact] The '?garbage' pattern doesn't work with install/remove commands which is confusing, and the fix for it is trivial. [Test plan] Successful autopkgtest. The comprehensive test suite run as an autopkgtest has been updated in test/integration/test-apt-get-autoremove to test for the correct behavior of '?garbage' with install and remove. [Where problems could occur] You can see we had to tweak the test suite in a bunch of places because it relies on exact debug output format and because we now call "markandsweep" there's additional mark flags in the debug output. It's unlikely that this is a problem for others. We have not seen regressions in noble in the past 2 weeks or noble- proposed since 2023-11-23 (it was stuck for other reasons there), hence other places the code change may affect have been thoroughly exercised in the builders and autopkgtest runners. [Original bug report] The awesome apt has a some wonderful tips on their EXAMPLES section (printed below). The choice of name to "garbage" might not have been the best but the function is extremely useful. $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d' apt remove ?garbage Remove all packages that are automatically installed and no longer needed - same as apt autoremove apt purge ?config-files Purge all packages that only have configuration files left apt list '~i !~M (~slibs|~sperl|~spython)' List all manually-installed packages in sections matching libs, perl, or python. Lets mark a package as automatically installed, and use the examples. $ sudo apt-mark auto shotwell shotwell set to automatically installed. $ sudo apt remove ?garbage Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libraw20 shotwell shotwell-common Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libraw20 shotwell shotwell-common 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 9.806 kB disk space will be freed. Do you want to continue? [Y/n] N Abort. Apt-patterns works as it should everywhere else, as far as I can see, it works wonders with ie `apt list '~g|~c'` and many other applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I feel this is a regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.8 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 10:57:52 2022 SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2058276] [NEW] Improve ssh-gssapi DEP8 test
Public bug reported: The DEP8 test introduced in https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146 could still show s PASS even when the login didn't work. This is because it's relying on `set -e` to work inside functions, but that's not the case. For example, here I forced a failure by using an invalid user (I added "x" to the username): ``` ## ssh'ing into localhost using gssapi-keyex auth testuser229...@sshd-gssapi.example.fake: Permission denied (gssapi-keyex). ## checking that we got a service ticket for ssh (host/) 03/18/24 12:16:55 03/18/24 22:16:55 host/sshd-gssapi.example.fake@ Ticket server: host/sshd-gssapi.example.f...@example.fake ## Checking ssh logs to confirm gssapi-keyex auth was used Mar 18 12:16:55 sshd-gssapi.example.fake sshd[22994]: Failed gssapi-keyex for invalid user testuser22924x from 127.0.0.1 port 39550 ssh2: testuser22...@example.fake ## PASS test_gssapi_keyex_login ``` Furthermore, the --grep option used in journalctl is not specific enough, as can also be seen above. It's just looking for the authentication method name, not whether is succeeded or not. ** Affects: openssh (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2058276 Title: Improve ssh-gssapi DEP8 test Status in openssh package in Ubuntu: In Progress Bug description: The DEP8 test introduced in https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146 could still show s PASS even when the login didn't work. This is because it's relying on `set -e` to work inside functions, but that's not the case. For example, here I forced a failure by using an invalid user (I added "x" to the username): ``` ## ssh'ing into localhost using gssapi-keyex auth testuser229...@sshd-gssapi.example.fake: Permission denied (gssapi-keyex). ## checking that we got a service ticket for ssh (host/) 03/18/24 12:16:55 03/18/24 22:16:55 host/sshd-gssapi.example.fake@ Ticket server: host/sshd-gssapi.example.f...@example.fake ## Checking ssh logs to confirm gssapi-keyex auth was used Mar 18 12:16:55 sshd-gssapi.example.fake sshd[22994]: Failed gssapi-keyex for invalid user testuser22924x from 127.0.0.1 port 39550 ssh2: testuser22...@example.fake ## PASS test_gssapi_keyex_login ``` Furthermore, the --grep option used in journalctl is not specific enough, as can also be seen above. It's just looking for the authentication method name, not whether is succeeded or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2058276/+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 2057768] Re: Unit and its Alias appear to be separate entities when enabling the unit by filepath
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Focal) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu) Importance: Wishlist => Medium -- 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/2057768 Title: Unit and its Alias appear to be separate entities when enabling the unit by filepath Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: Confirmed Status in systemd source package in Jammy: Confirmed Status in systemd source package in Mantic: Won't Fix Bug description: ### systemd version the issue has been seen with 245 ### Used distribution Linux Mint 20.1 and Ubuntu 20.04 ### Linux kernel version used 5.4.0-135-generic ### CPU architectures issue was seen on None ### Component systemctl ### Expected behaviour you didn't see When including an alias in a unit file that is enabled by referring to its filepath, its alias should refer to the unit - the two should refer to the exact same service. This is the case when the unit file is enabled inside one of the systemd directories. I expect alias and unit to refer to one identical service also when enabling via filepath. In particular, the output of `systemctl status ...` should be identical for a Unit and its Alias. ### Unexpected behaviour you saw After passing a systemd unit including an alias to `systemctl enable PATH...` by path, systemctl treated the unit and its alias as separate units. Specifically, `systemctl status` reports different results (running/inactive, PID if applicable) for the unit name and its alias. When I start the unit by its original name, only the status of the unit is reported as running while the status of the alias remains inactive, and vice versa. After starting the Alias too, two services with different PIDs are running. (When copying the unit into /etc/systemd/system/ and running `systemctl enable UNIT...` this issue does not occur and alias and unit behave the same.) ### Steps to reproduce the problem ``` ~$ cat dummy.service [Service] ExecStart=tail -f /dev/null [Install] Alias=dumb.service ~$ sudo systemctl enable ~/dummy.service Created symlink /etc/systemd/system/dumb.service → /home/lukas/dummy.service. Created symlink /etc/systemd/system/dummy.service → /home/lukas/dummy.service. ~$ sudo systemctl start dummy ~$ systemctl status dummy ● dummy.service Loaded: loaded (/etc/systemd/system/dummy.service; enabled; vendor preset:> Active: active (running) since Tue 2024-03-12 15:36:58 CET; 8s ago Main PID: 159809 (tail) Tasks: 1 (limit: 76978) Memory: 160.0K CGroup: /system.slice/dummy.service └─159809 /usr/bin/tail -f /dev/null Mär 12 15:36:58 MyMachine systemd[1]: Started dummy.service. ~$ systemctl status dumb ● dumb.service Loaded: loaded (/etc/systemd/system/dumb.service; enabled; vendor preset: > Active: inactive (dead) Mär 12 15:30:53 MyMachine systemd[1]: Started dumb.service. Mär 12 15:31:16 MyMachine systemd[1]: Stopping dumb.service... Mär 12 15:31:16 MyMachine systemd[1]: dumb.service: Succeeded. Mär 12 15:31:16 MyMachine systemd[1]: Stopped dumb.service. ~$ ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057768/+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 2058249] Re: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy
In Ubuntu 24.04 (noble) we have /usr/share/doc/tzdata/NEWS.Debian.gz: tzdata (2023d-1) unstable; urgency=medium From 2023c-8 on the tzdata package ships only timezones that follow the current rules of geographical region (continent or ocean) and city name. All legacy timezone symlinks (old or merged timezones mentioned in the upstream backward file) were moved to tzdata-legacy. This includes the US/* timezones. Please install tzdata-legacy in case you need the legacy timezones or to restore the previous behavior. This might be needed in case the system provides timezone-aware data over the network (e. g. SQL databases). -- Benjamin Drung Tue, 02 Jan 2024 14:17:33 +0100 The debian changelog contains for 2023c-8: * Ship only timezones in tzdata that follow the current rules of geographical region (continent or ocean) and city name. Move all legacy timezone symlinks (that are upgraded during package update) to tzdata-legacy. This includes dropping the special handling for US/* timezones. (Closes: #1040997) Improvements to the documentation are welcome. -- 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/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+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 2058276] Re: Improve ssh-gssapi DEP8 test
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/openssh/+git/openssh/+merge/462619 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2058276 Title: Improve ssh-gssapi DEP8 test Status in openssh package in Ubuntu: In Progress Bug description: The DEP8 test introduced in https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146 could still show s PASS even when the login didn't work. This is because it's relying on `set -e` to work inside functions, but that's not the case. For example, here I forced a failure by using an invalid user (I added "x" to the username): ``` ## ssh'ing into localhost using gssapi-keyex auth testuser229...@sshd-gssapi.example.fake: Permission denied (gssapi-keyex). ## checking that we got a service ticket for ssh (host/) 03/18/24 12:16:55 03/18/24 22:16:55 host/sshd-gssapi.example.fake@ Ticket server: host/sshd-gssapi.example.f...@example.fake ## Checking ssh logs to confirm gssapi-keyex auth was used Mar 18 12:16:55 sshd-gssapi.example.fake sshd[22994]: Failed gssapi-keyex for invalid user testuser22924x from 127.0.0.1 port 39550 ssh2: testuser22...@example.fake ## PASS test_gssapi_keyex_login ``` Furthermore, the --grep option used in journalctl is not specific enough, as can also be seen above. It's just looking for the authentication method name, not whether is succeeded or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2058276/+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 2056802] Re: crypttab does not honor `x-initrd.attach` option
AFAIK, we don't use systemd-cryptsetup in Ubuntu's initrd, and you are trying to use an option specific to systemd's crypttab implementation. So I am not surprised by: cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach What are you trying to do here exactly? ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Jammy) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Mantic) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Noble) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2056802 Title: crypttab does not honor `x-initrd.attach` option Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Incomplete Status in systemd source package in Jammy: Incomplete Status in systemd source package in Mantic: Incomplete Status in systemd source package in Noble: Incomplete Bug description: From systemd version 245+ an option was added x-initrd.attach - Setup this encrypted block device in the initrd, similarly to systemd.mount(5) units marked with x-initrd.mount. Although it's not necessary to mark the mount entry for the root file system with x-initrd.mount, x-initrd.attach is still recommended with the encrypted block device containing the root file system as otherwise systemd will attempt to detach the device during the regular system shutdown while it's still in use. With this option the device will still be detached but later after the root file system is unmounted. All other encrypted block devices that contain file systems mounted in the initrd should use this option. Added in version 245. [0] - release: noble systemd version: 253.5-1ubuntu6 Install noble to a vm with virt-manager and encrypt the lvm during subiquity install. After successful install, Modify /etc/crypttab to include the parameter in the 4th column example: sda6_crypt UUID=099aae4a-b11b-49a6-a6c4-62939eddf7a0 none luks,x-initrd.attach update-initramfs -u -k all During boot or shutdown the logs show cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach There are two separate problems 1. crypttab doesn't recognize x-initrd.attach option in /etc/crypttab file. cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach 2. this error happens on shutdown/restart [systemd-cryptsetup]: Device dm-crypt-0 is still in use. [systemd-cryptsetup]: Failed to deactivate: Device or resource busy. The vm does eventually shutdown after throwing the above warnings. [0] https://www.freedesktop.org/software/systemd/man/latest/crypttab.html#x-initrd.attach These patches look like they could fix the issue, The last one might not be needed. git format-patch -1 8ce02b87cece09797c1030c778db4180e1e2ce2e https://github.com/systemd/systemd/commit/8ce02b87cece09797c1030c778db4180e1e2ce2e git format-patch -1 1dc85eff1d0dff18aaeaae530c91bf53f34b726e https://github.com/systemd/systemd/commit/1dc85eff1d0dff18aaeaae530c91bf53f34b726e git format-patch -1 bf1484c70a24cf04c145a9509c8124ffd7fb0879 https://github.com/systemd/systemd/commit/bf1484c70a24cf04c145a9509c8124ffd7fb0879 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056802/+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 2058249] Re: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy
I see it now within `/usr/share/doc/tzdata/changelog.Debian.gz`, that's a file I did not check. Thank you! -- 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/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+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 2054977] Re: systemd-networkd fails to renew DHCP v4 lease when renew attempt times out
I think this would be better suited as an upstream issue, because AFAICT this case is still not handled in the latest version. If you do open an upstream bug (https://github.com/systemd/systemd/issues), they will want to see this reproduced on at least systemd v254. Please comment back here if you open a bug upstream. ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2054977 Title: systemd-networkd fails to renew DHCP v4 lease when renew attempt times out Status in systemd package in Ubuntu: Incomplete Bug description: I'm seeing exactly what this gist describes: https://gist.github.com/raggi/1f8d0b9f45c5b62e7131b03e6e2ffe68 Summary: 1. Configure a machine with a DHCPv4 lease on a network with a DHCPv4 server. 2. Place machine under unusual load sufficient to cause a timeout on netlink requests. 3. Observe the interface failing with the following logs: systemd-networkd[139370]: eth0: Could not set DHCPv4 address: Connection timed out systemd-networkd[139370]: eth0: Failed The error seems to come from here: https://github.com/systemd/systemd/blob/v245.4/src/network/networkd-dhcp4.c#L781 Expected behavior The DHCPv4 client should retry the lease refresh when the issue is a timeout, eventually succeeding in these scenarios. Actual behavior Permanent loss of connectivity on the affected interface. Additional info: $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.23 Candidate: 245.4-4ubuntu3.23 Version table: *** 245.4-4ubuntu3.23 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.20 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2054977/+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 2056187] Re: fails to configure BOOTIF when using iscsi
** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Focal) Importance: Undecided Status: New -- 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/2056187 Title: fails to configure BOOTIF when using iscsi Status in initramfs-tools package in Ubuntu: Fix Committed Status in open-iscsi package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: New Status in open-iscsi source package in Focal: New Status in initramfs-tools source package in Jammy: New Status in open-iscsi source package in Jammy: New Bug description: [ Impact ] * MAAS cannot PXE-boot a machine that has iSCSI disks * Focal is the default Ubuntu distribution deployed by MAAS, so we should back-port this to ensure it works out-of-the-box. [ Test Plan ] * reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager in the original report), and a MAAS controller (3.4 or better) * the issue can be observed by simply enlisting the machine in MAAS. It will fail to boot due to the missing BOOTIF configuration. [ Where problems could occur ] * the problematic code was an attempt to fix LP#2037202, so we should watch out for regressions. [ Original report ] we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured. when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface. The existence of this file makes configure_networking() skip configuring the BOOTIF later due to this code in `scripts/functions`: for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do if [ -e "$x" ]; then IP=done break fi done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056153] Re: Removing the systemd-resolved package breaks DNSSEC validation
Yeah, this looks like a bug. The systemd-resolved.postrm is copying /run/systemd/resolve/resolv.conf to /etc/resolv.conf, rather then copying /run/systemd/resolve/stub-resolv.conf (which is where /etc/resolv.conf is symlinked to prior to removal). ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation Status in systemd package in Ubuntu: Confirmed Bug description: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+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 2056153] Re: Removing the systemd-resolved package breaks DNSSEC validation
Or, actually, not exactly. We don't want the stub-resolv.conf since systemd-resolved is leaving, but we probably do want the options. -- 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/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation Status in systemd package in Ubuntu: Confirmed Bug description: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I have just tried running firefox from the firefox-nightly download and all runs well using that version 125.0a1 (2024-03-17) (64-bit). I assume the beta3 you speak of is the new version of apparmor; is that the same version as the current apparmor-proposed version? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@ajg-charlbury: no apparmor beta3 has not landed in proposed yet, we are working on the upload now. firefox separately have added a bug fix that will detect when the user namespace/capabilities are denied and fallback without crashing but it disables the full sandbox. the apparmor-beta3 fix should enable firefox to function with the full sandbox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure
** Changed in: gobject-introspection Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/2056753 Title: pygobject FTBFS on armhf: time_t build test failure Status in GObject Introspection: Fix Released Status in gobject-introspection package in Ubuntu: Fix Committed Status in gobject-introspection package in Debian: New Bug description: pygobject fails to build on armhf, the only Ubuntu 32-bit architecture that has done the time_t transition. test_gi.py runs a time_t test that I believe is using functions in glib2.0 Test log excerpt tests/test_gi.py ... [ 21%] . --- stderr --- Fatal Python error: Aborted Current thread 0xf785e020 (most recent call first): File "/<>/tests/test_gi.py", line 579 in test_time_t_in File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod File "/usr/lib/python3.12/unittest/case.py", line 634 in run File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__ File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in pytest_runtest_call File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in call_runtest_hook File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in call_and_report File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in runtestprotocol File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in pytest_runtest_protocol File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in pytest_runtestloop File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in wrap_session File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in pytest_cmdline_main File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in _multicall File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in _hookexec File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__ File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 in main File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 in console_main File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in File "", line 88 in _run_code File "", line 198 in _run_module_as_main Full build log == https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2058310] [NEW] Dummy output with Celeron Silver audio
Public bug reported: Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there is no sound. I believe the CPU sound unit is essx-8336. Many people have reported similar problems, with the system sound being "dummy output". My bluetooth ear buds do work. Endeavour-OS and Fedora 39 live images do work with this machine, as does the Win 11 dual boot, so the hardware works. Will this problem be fixed in version 24.04? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 21:29:33 2024 InstallationDate: Installed on 2024-03-11 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2023 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GM118C_V33.1180.01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 140.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2058310 Title: Dummy output with Celeron Silver audio Status in alsa-driver package in Ubuntu: New Bug description: Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there is no sound. I believe the CPU sound unit is essx-8336. Many people have reported similar problems, with the system sound being "dummy output". My bluetooth ear buds do work. Endeavour-OS and Fedora 39 live images do work with this machine, as does the Win 11 dual boot, so the hardware works. Will this problem be fixed in version 24.04? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 21:29:33 2024 InstallationDate: Installed on 2024-03-11 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2023 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GM118C_V33.1180.01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 140.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packa
[Touch-packages] [Bug 2058253] Re: Notebook screen the look is "matte" in KDE
If it looks correct in GNOME then please briefly log into GNOME and run: xrandr --verbose > gnome-xrandr.txt and attach the resulting text file here. Also if KDE has any monitor colour profile settings then try toggling those. ** Summary changed: - Notebook screen the look is "matte" + Notebook screen the look is "matte" in KDE ** Package changed: xorg (Ubuntu) => kwin (Ubuntu) ** Changed in: kwin (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2058253 Title: Notebook screen the look is "matte" in KDE Status in kwin package in Ubuntu: Incomplete Bug description: Hi, feedback: In general, on the notebook screen, the look is "matte", smoke in the images, videos, games, on the desktop, etc., especially when the screen brightness increases. When compared to Ubuntu with gnome, windows 11, it has greater clarity, stronger colors, etc. In Kubuntu I didn't find the option to increase the sharpness, to improve etc., so I wanted to leave feedback here, to help with the project. 😄 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Mar 18 10:56:50 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f9c] InstallationDate: Installed on 2024-01-13 (64 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 82MD ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-26-generic root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 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/kwin/+bug/2058253/+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 2058313] [NEW] whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 → main → collect_info → process_report → add_gdb_info → gdb_command
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.28.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/def1584660098f405d12c36422a9561aa02aa911 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: jammy noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2058313 Title: whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload- all@220 → main → collect_info → process_report → add_gdb_info → gdb_command Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.28.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/def1584660098f405d12c36422a9561aa02aa911 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2058313/+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 2058313] Re: whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 → main → collect_info → process_report → add_gdb_info → gdb_command
** Summary changed: - /usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@220:main:collect_info:process_report:add_gdb_info:gdb_command + whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 → main → collect_info → process_report → add_gdb_info → gdb_command -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2058313 Title: whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload- all@220 → main → collect_info → process_report → add_gdb_info → gdb_command Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.28.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/def1584660098f405d12c36422a9561aa02aa911 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2058313/+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 2058314] Re: software-properties-gtk (ValueError) /usr/bin/software-properties-gtk@100 → __init__ → __init__ → backup_sourceslist → __init__
*** This bug is a duplicate of bug 2053228 *** https://bugs.launchpad.net/bugs/2053228 ** Summary changed: - /usr/bin/software-properties-gtk:ValueError:/usr/bin/software-properties-gtk@100:__init__:__init__:backup_sourceslist:__init__ + software-properties-gtk (ValueError) /usr/bin/software-properties-gtk@100 → __init__ → __init__ → backup_sourceslist → __init__ ** This bug has been marked a duplicate of bug 2053228 software-properties-gtk does not start -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058314 Title: software-properties-gtk (ValueError) /usr/bin/software-properties- gtk@100 → __init__ → __init__ → backup_sourceslist → __init__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.42, the problem page at https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058314/+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 2053228] Re: software-properties-gtk does not start
Also tracking in: https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2053228 Title: software-properties-gtk does not start Status in software-properties package in Ubuntu: Triaged Bug description: On a new install with the new format sources.list software-properties-gtk does not start: corrado@corrado-n4-nn-0215:~$ software-properties-gtk Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) ^^^ File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 163, in __init__ SoftwareProperties.__init__(self, options=options, datadir=datadir, File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 109, in __init__ self.backup_sourceslist() File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 437, in backup_sourceslist source_bkp = SourceEntry(line=source.line,file=source.file) ^^ File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in __init__ raise ValueError("Classic SourceEntry cannot be written to .sources file") ValueError: Classic SourceEntry cannot be written to .sources file corrado@corrado-n4-nn-0215:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.42 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 10:07:43 2024 InstallationDate: Installed on 2024-02-15 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2058314] [NEW] software-properties-gtk (ValueError) /usr/bin/software-properties-gtk@100 → __init__ → __init__ → backup_sourceslist → __init__
*** This bug is a duplicate of bug 2053228 *** https://bugs.launchpad.net/bugs/2053228 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.42, the problem page at https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: jammy noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058314 Title: software-properties-gtk (ValueError) /usr/bin/software-properties- gtk@100 → __init__ → __init__ → backup_sourceslist → __init__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.42, the problem page at https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058314/+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 2014677] Re: libgdk-pixbuf2.0-common is required by libgdk-pixbuf-2.0-0 but is empty.
** Changed in: gdk-pixbuf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2014677 Title: libgdk-pixbuf2.0-common is required by libgdk-pixbuf-2.0-0 but is empty. Status in gdk-pixbuf package in Ubuntu: Incomplete Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libgdk-pixbuf2.0-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2014677/+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 2014597] Re: libsecret-common is required by libsecret-1-0 but is empty.
** Changed in: libsecret (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/2014597 Title: libsecret-common is required by libsecret-1-0 but is empty. Status in libsecret package in Ubuntu: Incomplete Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libsecret-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/2014597/+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 2014549] Re: libjson-glib-1.0-common is required by libjson-glib-1.0-0 but is empty.
** Changed in: json-glib (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/2014549 Title: libjson-glib-1.0-common is required by libjson-glib-1.0-0 but is empty. Status in json-glib package in Ubuntu: Incomplete Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libjson-glib-1.0-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/2014549/+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 1876917] Re: libu2f-udev has been rendered unnecessary by systemd v244
** Tags removed: lunar ** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1876917 Title: libu2f-udev has been rendered unnecessary by systemd v244 Status in libu2f-host package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: New Bug description: Since systemd v244, specifically this commit (https://github.com/systemd/systemd/issues/11996), systemd detects U2F devices based on their declared usage (page) and automatically generates the relevant udev rules. Manually maintaining device- specific rules is therefore no longer necessary and libu2f-udev can be removed from libu2f-host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libu2f-host/+bug/1876917/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Hints removed, closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Released Bug description: [ Impact ] * The device_add_remove_test test fails on the affected series (e.g. Bionic). * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] * Run the affected test on an affected series (e.g. Bionic). * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 1970069] Re: Annoying boot messages interfering with splash screen
That change is in plymouth, but hooks/framebuffer is in initramfs-tools. If you're suggesting moving the code from plymouth into initramfs-tools then I kind of understand, but it's not directly related to fixing this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
If you are suggesting moving the logic from plymouth into initramfs- tools then please start by duplicating the code you'd like moved into initramfs-tools. That would be efficient since you have commit access to initramfs-tools, and would mean I only have to deal with plymouth here. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Hello René, or anyone else affected, Accepted coreutils into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/coreutils/8.32-4.1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: coreutils (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Committed Status in coreutils package in Fedora: Fix Released Bug description: [Impact] Issuing a 'ls -l' or a 'stat' on an autofs share when you have set --ghost in the auto.master file, or browse_mode=yes in autofs.conf will lead to the shares being mounted, when they didn't previously. Disks / shares may not be present and the mounts may fail, leading to errors in your output. This is a behaviour change in autofs 8.32, which occurred in the transition to using statx() instead of stat()/lstat() in previous releases. There doesn't seem to be any workarounds, apart from not running a 'ls -l' in your autofs share directory. [Testcase] Start two Jammy VMs. One will be a NFS server, the other, the client. NFS server: Server VM: $ sudo hostnamectl set-hostname jammy-nfs-server $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-kernel-server $ sudo mkdir /export $ sudo mkdir /export/users $ sudo vi /etc/exports # add the following lines: /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) $ sudo systemctl restart nfs-server.service AutoFS Client: $ sudo apt update $ sudo apt install autofs $ sudo vim /etc/autofs.conf browse_mode = yes $ sudo mkdir /mnt2 $ sudo vim /etc/auto.master /mnt2 /etc/auto.indirect $ sudo vim /etc/auto.indirect export 192.168.122.18:/export export-missing 192.168.122.18:/export-missing $ sudo reboot $ cd /mnt2 $ ls -l ls: cannot access 'export-missing': No such file or directory total 4 drwxr-xr-x 3 root root 4096 Feb 12 21:48 export d? ? ?? ?? export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561) 192.168.122.18:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18) We see the mount for export occurred, and export-missing was attempted, but it was either bogus or the disk was not present, leading to a "No such file or directory" error. There are test packages available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test If you install them, this is what should occur: $ ls -l total 0 drwxr-xr-x 2 root root 0 Feb 12 22:01 export drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346) No mounts happen, and no errors either. [Where problems could occur] We are changing the behaviour of core utilities, ls and stat, such that they no longer attempt to mount autofs shares when --ghost option is present or browse_mode is enabled. This is the intended behaviour in the first place, and has been this way for at least a decade prior, and was changed to return to this behaviour shortly after the r
[Touch-packages] [Bug 2058329] [NEW] Update apparmor to 4.0.0-beta3 in noble
Public bug reported: Latest upstream release https://gitlab.com/apparmor/apparmor/-/releases/v4.0.0-beta3 Contains only bug fixes since 4.0.0-beta2 which is currently in noble- proposed thus does not require a FFe. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058329 Title: Update apparmor to 4.0.0-beta3 in noble Status in apparmor package in Ubuntu: New Bug description: Latest upstream release https://gitlab.com/apparmor/apparmor/-/releases/v4.0.0-beta3 Contains only bug fixes since 4.0.0-beta2 which is currently in noble- proposed thus does not require a FFe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058329/+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