[Touch-packages] [Bug 1727811] Re: signon-ui crashes when trying to use KDE systemsettings to add a google account
** Changed in: signon-ui (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1727811 Title: signon-ui crashes when trying to use KDE systemsettings to add a google account Status in signon-ui package in Ubuntu: Fix Released Status in signon-ui source package in Artful: Won't Fix Status in signon-ui source package in Bionic: Fix Released Bug description: 0.17+17.10.20170606-0ubuntu1 in Artful & Bionic crash when trying to use KDE systemsettings to add a google account "There was an error while trying to process the request: userActionFinished error: 2" This results in no Google account be added. This appears to be the result of changes implemented for Unity. A WIP solution is discussed in the reported issue upstream: https://gitlab.com/accounts-sso/signon-ui/issues/1 However, that solution requires KDE upstream to adapt it's Kaccounts KCM. As KDE is now the only user of signon-ui (Unity dropping it's use) in Artful and abovea temporary solution is to revert to the last working version 0.17+17.04.20161109-0ubuntu1 This has been built here: https://launchpad.net/~rikmills/+archive/ubuntu/kio-grive and tested successfully, allowing the the addition of Google accounts, and the use of kio-gdrive to access google drive from Dolphin file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1727811/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error
** Changed in: kaccounts-providers (Ubuntu Wily) Status: Triaged => Won't Fix ** Changed in: ktp-accounts-kcm (Ubuntu Wily) Status: Triaged => Won't Fix ** Changed in: ktp-accounts-kcm (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in Telepathy KDE: Fix Released Status in kaccounts-integration package in Ubuntu: Fix Committed Status in kaccounts-providers package in Ubuntu: Fix Committed Status in ktp-accounts-kcm package in Ubuntu: Won't Fix Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Won't Fix Status in ktp-accounts-kcm source package in Wily: Won't Fix Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) SRU information === [Impact] It's not possible to install KDE and Unity in co-existence because of several file conflicts: many files under /usr/share/accounts/{providers,services}/ are provided by both the package "kaccounts-providers" and packages build from the "account- plugins" source package, for example 'account-plugin-facebook'. [Test case] Install both kaccounts-providers and account-plugin-facebook: you'll get file conflicts for /usr/share/accounts/services/facebook-im.service and /usr/share/accounts/providers/facebook.provider. You might get other conflicts as well, but those are due to bug 1565772 (also nominated for SRU). [Regression potential] Minimal: the changed packages belong to the default KDE installation, and have already landed in Yakkety. Things appear to be working fine there: account creation is still possible under KDE, even after changing the file paths as per this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
While date Do Read -t 60 x Done In another terminal, adjust the system clock by a few seconds Repeat hourly until the read hangs. Sometimes it hangs immediately after setting clock, Sometimes it runs for hours. I have seen hangs semi regularly for the last 5, maybe 10+ years. It often hangs with no apparent system clock changes, But more often when a cron job runs ntp No VM involved. Hangs on multiple AMD systems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Incomplete Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I have an issue. I can connect to the hotspot just fine, but the connected devices get disconnected almost immediately I tried all the wifi security options one by one, and there is the same behavior with each of them. from journalctrl output Nov 11 08:36:29 tortuga wpa_supplicant[19131]: wlo2: AP-STA-CONNECTED a6:81:e8:e3:73:66 Nov 11 08:36:29 tortuga wpa_supplicant[19131]: wlo2: EAPOL-4WAY-HS-COMPLETED a6:81:e8:e3:73:66 Nov 11 08:36:47 tortuga wpa_supplicant[19131]: wlo2: AP-STA-DISCONNECTED a6:81:e8:e3:73:66 How do I get this to work? The Ubuntu 22.04 machine gets internet from a wired connection to the home router, the router provided DHCP and DNS services -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1995137] Re: Add "sun4i-drm_dri.so" and fix compilation of libg1-mesa-dri on riscv64
** Summary changed: - "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64 + Add "sun4i-drm_dri.so" and fix compilation of libg1-mesa-dri on riscv64 ** Summary changed: - Add "sun4i-drm_dri.so" and fix compilation of libg1-mesa-dri on riscv64 + Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: New Bug description: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
This should be fixed in lunar by merging openssl from Debian -- 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/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Triaged Status in openssl source package in Jammy: Triaged Status in openssl source package in Kinetic: Triaged Bug description: https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
Thank you for describing the solution in this bug report. Could somebody come up with a patch/debdiff, so that any MOTU could test & sponsor the ifupdown fix into universe? ** Tags removed: foundations-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1981103 Title: System with DNS server in /etc/network/interfaces has bogus systemd- resolved config after upgrade to 22.04 Status in ifupdown package in Ubuntu: Triaged Bug description: Description:Ubuntu 22.04 LTS Release:22.04 ifupdown: Installed: 0.8.36+nmu1ubuntu3 Candidate: 0.8.36+nmu1ubuntu3 Version table: *** 0.8.36+nmu1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status After upgrading a server with classic ifupdown configuration after reboot the machine had no valid dns servers anymore. The problem is that the state file created by ifupdown using /etc/network/if-up.d/resolved looks like this: root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13 "DNS"="134.102.20.20 134.102.200.14" "DOMAINS"="marum.de" The script later sources this file and causes the following errors, easy to see when you execute this: root@pangaea-pm:~# ifdown ens13; ifup ens13 /etc/network/if-down.d/resolved: 12: mystatedir: not found /etc/network/if-up.d/resolved: 12: mystatedir: not found /etc/network/if-up.d/resolved: 71: DNS: not found /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: DNS=134.102.20.20 134.102.200.14: not found /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: DOMAINS=marum.de: not found Failed to parse DNS server address: DNS Failed to set DNS configuration: Invalid argument This happened to me on three different servers, so this is a serious bug and should be fixed before 22.04 upgrades are allowed for everybody. Most servers provided by data centers like Hetzner (Germany) are configure like that. After a do-release-upgrade you have no working DNS anymore, unless you disable systemd-resolved. I don't want to use netplan, so changing to this is no option. The fix is easy - remove the quotes in the script on the left side "$DNS" => $DNS; same for DOMAINS: if [ -n "$NEW_DNS" ]; then cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface" $DNS="$NEW_DNS" EOF if [ -n "$NEW_DOMAINS" ]; then cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface" $DOMAINS="$NEW_DOMAINS" EOF fi fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1892559] Re: [MIR] ccid opensc pcsc-lite
Desktop no longer has engineering goals to support smart cards. Foundations team might. Security Team is blocked until there is a mandate, an owning team, hardware funding, and possibly engineering support to resolve https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930530 Unassigning Security Team. ** Changed in: ccid (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: opensc (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: pcsc-lite (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl,
[Touch-packages] [Bug 1968109] Re: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources
I encourage flavours using Qt to fix this if they care about it. ** Tags removed: foundations-triage-discuss -- 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/1968109 Title: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources Status in software-properties package in Ubuntu: Triaged Bug description: I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box. What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect. I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE Date: Fri Mar 18 17:00:53 2022 LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all 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/1968109/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Tags removed: foundations-triage-discuss -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 1993037] Re: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course
Is this a clean installation of Ubuntu 22.04, or have you been upgrading your system from an older installation? I wonder if you have the `usrmerge` package installed correctly? ** Changed in: debianutils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course Status in debianutils package in Ubuntu: Incomplete Status in systemd-cron package in Ubuntu: New Bug description: (Found in Ubuntu 22.04 LTS) package debianutils keeps run-parts executable in /usr/bin/ while package systemd-cron tries to find it in /bin/ $ which run-parts /usr/bin/run-parts $ dpkg -S `which run-parts` debianutils: /usr/bin/run-parts $ grep =/bin/run /lib/systemd/system/cron* /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly Because of that, cron-daily.serice gets info "failed" state soon after system reboot. Please resolve the problem to make systemd-cron more usable. Thanks in advance for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+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 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64
The attached patch disables usage of LLVM JIT on riscv64, which was causing the error I reported in comment #3. I obtained this patch from the following Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004039 This patch, combined with the previous one, seems to work well on the Sipeed Lichee RV board. I have tested this with ubuntu-frame and a custom-built mesa-core20 snap containing the drivers built using these patches. ** Bug watch added: Debian Bug tracker #1004039 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004039 ** Patch added: "mesa-disable-llvm-riscv64.debdiff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+attachment/5630389/+files/mesa-disable-llvm-riscv64.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995137 Title: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64 Status in mesa package in Ubuntu: New Bug description: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56
Upstream merge request: https://github.com/canonical/apport/pull/24 ** Changed in: apport (Ubuntu) Status: Triaged => In Progress ** Changed in: apport Status: Triaged => In Progress -- 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/1996040 Title: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56 Status in Apport: In Progress Status in apport package in Ubuntu: In Progress Bug description: The latest GitKraken client (8.10.2 x64) is crashed every minute in cycle when you doing a rebase. When I try to inspect crash log to find the reason, the apport-unpack is not be able to process it: /var/lib/apport/coredump$ sudo apport-unpack core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891 unpack [sudo] пароль для mingun: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 59, in pr.load(f, binary=False) File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load key = key.decode('ASCII') UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: ordinal not in range(128) Unfortunately, crash file is too big (~9GB) and does not compress further To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1996040/+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 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
Seeing the comment now, I want to point out that /usr takes precedence over /, so if the command is available there is no overhead - only in the error case. -- 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/1792004 Title: built-in PATH seems to have sbin and bin out of order; and inconsistent Status in apt package in Ubuntu: Fix Released Status in bash package in Ubuntu: Fix Released Status in busybox package in Ubuntu: New Status in dash package in Ubuntu: New Status in dpkg package in Ubuntu: Won't Fix Status in pam package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bash source package in Xenial: Fix Released Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Bug description: [Impact] * For consistency reasons sbin should be ordered before bin in PATH. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' And check that matching pairs in PATH, have /sbin variant leading /bin variant. [Regression Potential] * Ubuntu does not ship duplicate binries, with different behaviour between /sbin and /bin, thus all binaries will continue to be found in all locations. Also PATH is normally already set in the environment, and this change only affects the fallback path when bash is executed without any environment, i.e. booting with 'init=/bin/bash' [Other Info] * Original bug report detailing inconsistent paths between various shells. --- $ env -u PATH /bin/sh -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/dash -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ systemd-run --unit test-env env # ... and check journal for PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. $ env -u PATH /bin/busybox sh -c 'echo $PATH' /sbin:/usr/sbin:/bin:/usr/bin $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/ initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin' initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} exported as PATH dracut-047+31/modules.d/99shutdown/shutdown.sh:export PATH=/usr/sbin:/usr/bin:/sbin:/bin $ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" apt & dpkg => should probably initiate /usr/local-less PATH Imho the rest should probably be harmonised to: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin === From a duplicate https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 : $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; done 12.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 12.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 14.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 16.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. I believe later releases of bash, do too include CWD in the built-in PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+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 1996177] [NEW] Cleaner environment for dpkg execution
Public bug reported: APT currently launches dpkg in the same environment as it is launched in leaking all sorts of environment variables to it, only overriding PATH with a sensible default. This is suboptimal, apt should clean the environment more thoroughly or populate a clean environment from scratch. Questions to answer: * Perhaps it can reuse systemd or sudo or pam mechanisms? * If not, what can we copy/pass-through? e.g. TERM needs to be kept the same. * What to do about hooks * umask(022) before executing dpkg (anything?), also need correct umask for lists for sure. ** Affects: apt (Ubuntu) Importance: Medium Status: Triaged ** Changed in: apt (Ubuntu) Importance: Undecided => Medium ** Changed in: apt (Ubuntu) Status: New => Triaged -- 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/1996177 Title: Cleaner environment for dpkg execution Status in apt package in Ubuntu: Triaged Bug description: APT currently launches dpkg in the same environment as it is launched in leaking all sorts of environment variables to it, only overriding PATH with a sensible default. This is suboptimal, apt should clean the environment more thoroughly or populate a clean environment from scratch. Questions to answer: * Perhaps it can reuse systemd or sudo or pam mechanisms? * If not, what can we copy/pass-through? e.g. TERM needs to be kept the same. * What to do about hooks * umask(022) before executing dpkg (anything?), also need correct umask for lists for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1996177/+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