[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status
I have the same problem in 22.04. Is it so difficult to fix it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1980991 Title: /usr/sbin/on_ac_power incorrectly reporting ac power status Status in powermgmt-base package in Ubuntu: Triaged Status in powermgmt-base source package in Kinetic: Won't Fix Status in powermgmt-base source package in Lunar: Won't Fix Bug description: Good afternoon, folks. I believe I discovered a bug in the /usr/sbin/on_ac_power script. I have a Dell OptiPlex 5090 host that has an entry in /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe this is the USB-C power delivery port on the front of the chassis. The issue I'm encountering is that /usr/sbin/on_ac_power is exiting with code 1 which states: (1 (false) if not on AC power) when that isn't the case. This looks to be because of the ucsi-source-psy-USBC000:001 entry reporting the "online" status as 0, presumably because nothing is currently connected to that USB-C port. This causes /usr/sbin/on_ac_power to incorrectly report that the machine isn't connected to AC power and causes other utilities like unattended-upgrades to quit when using the default configuration since it believes the machine isn't connected to AC power. There is a workaround with unattended-upgrades where you can specify it to run regardless of if AC power is connected, but as more and more chassis implement power-delivery USB-C ports I foresee this becoming more of an issue. I'm not sure if it's anything to look into, but I figured I would share my findings. Please let me know if you have any questions or if I can provide any additional information, troubleshooting, or testing. Thanks! -Kevin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I tried kernel 5.3.0-43 from proposed but my notebook does not wake up from S3 suspend anymore (Lenovo Carbon X1 7th gen). I'm returning to kernel 5.3.0-40 where this is working... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1853115] [NEW] localauthority.conf - AdminIdentities: unix-group is ignored
Public bug reported: Allowed users and groups as admins for pkexec are defined in: /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin As you can see, I added unix-group:localadmin My user is localadmin-user1 who is in the local group localadmin. It does not matter if I create a new configuration file /etc/polkit-1/localauthority.conf.d/99-myadmins.conf or expand the original 51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin If I add the user himself instead of his group localadmin the user is listed the allowed list for pkexec. [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-user:localadmin-user1 How to reproduce: - create local user and group (here: localadmin) - add unix-group:localadmin to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user in group localadmin is not listed - add unix-user:localadmin-user1 to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user localadmin-user1 is listed Kubuntu 19.10 policykit-10.105-26ubuntu1 SSSD for system authorization including domain ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1853115 Title: localauthority.conf - AdminIdentities: unix-group is ignored Status in policykit-1 package in Ubuntu: New Bug description: Allowed users and groups as admins for pkexec are defined in: /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin As you can see, I added unix-group:localadmin My user is localadmin-user1 who is in the local group localadmin. It does not matter if I create a new configuration file /etc/polkit-1/localauthority.conf.d/99-myadmins.conf or expand the original 51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin If I add the user himself instead of his group localadmin the user is listed the allowed list for pkexec. [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-user:localadmin-user1 How to reproduce: - create local user and group (here: localadmin) - add unix-group:localadmin to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user in group localadmin is not listed - add unix-user:localadmin-user1 to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user localadmin-user1 is listed Kubuntu 19.10 policykit-10.105-26ubuntu1 SSSD for system authorization including domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1853115/+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 1746527] Re: Systemd User Service Cannot Start with ECryptFS Due to PAM Misconfiguration
*** This bug is a duplicate of bug 1734290 *** https://bugs.launchpad.net/bugs/1734290 ** This bug has been marked a duplicate of bug 1734290 ecryptfs decrypts home AFTER systemd user daemon is loaded. trouble ensues… -- 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/1746527 Title: Systemd User Service Cannot Start with ECryptFS Due to PAM Misconfiguration Status in systemd package in Ubuntu: Confirmed Bug description: If a user encrypts their home directory using the standard Ubuntu installer GUI, which uses ecryptfs, then the users home directory is encrypted while systemd is trying to start their user services so they cant be read. After consulting with the systemd developers, the problem is remarkably simple to fix Ubuntu releases /etc/pam.d/common-session with the follow entries: session optionalpam_systemd.so session optionalpam_ecryptfs.so unwrap they need to be swapped to session optionalpam_ecryptfs.so unwrap session optionalpam_systemd.so so that decryption happens before systemd user services are started. Check the thread on the systemd developers mailing list at https://lists.freedesktop.org/archives/systemd- devel/2018-January/040301.html for further information ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 Uname: Linux 4.14.4-acso x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 09:25:10 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (87 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.4-acso root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_iommu=on pci=noaer pcie_acs_override=downstream vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1746527/+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 1792930] Re: split does not break on error when reading from standard input
Ok, now I use the bash option set -o pipefail and let split fail with the error code of tar. ** Changed in: coreutils (Ubuntu) Status: New => Invalid -- 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/1792930 Title: split does not break on error when reading from standard input Status in coreutils package in Ubuntu: Invalid Bug description: Hi all, I found a bug in "split". I want to tar some files but some of them have wrong permissions. tar puts out an exit code 2 "Cannot open: Permission denied". That is good because in my script I can catch this error and react to this. $ tar -c -f /tmp/test.tar -C /media/testpath testfile ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 2 Unfortunately my tar directory is too big to save it in one file on my filesystem that I have to split the archive. But doing this "split" does not get the error code 2 from standard input (tar) and does not break as it should: $ tar -c -f - -C /media/testpath testfile | split - ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 0 In the end I got a tar file without files that have no permissions and my script does not break because of error code 0. Ubuntu 18.04.1 tar 1.29b coreutils 8.28 Best regards, Alexander To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1792930/+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 1792930] [NEW] split does not break on error when reading from standard input
Public bug reported: Hi all, I found a bug in "split". I want to tar some files but some of them have wrong permissions. tar puts out an exit code 2 "Cannot open: Permission denied". That is good because in my script I can catch this error and react to this. $ tar -c -f /tmp/test.tar -C /media/testpath testfile ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 2 Unfortunately my tar directory is too big to save it in one file on my filesystem that I have to split the archive. But doing this "split" does not get the error code 2 from standard input (tar) and does not break as it should: $ tar -c -f - -C /media/testpath testfile | split - ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 0 In the end I got a tar file without files that have no permissions and my script does not break because of error code 0. Ubuntu 18.04.1 tar 1.29b coreutils 8.28 Best regards, Alexander ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- 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/1792930 Title: split does not break on error when reading from standard input Status in coreutils package in Ubuntu: New Bug description: Hi all, I found a bug in "split". I want to tar some files but some of them have wrong permissions. tar puts out an exit code 2 "Cannot open: Permission denied". That is good because in my script I can catch this error and react to this. $ tar -c -f /tmp/test.tar -C /media/testpath testfile ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 2 Unfortunately my tar directory is too big to save it in one file on my filesystem that I have to split the archive. But doing this "split" does not get the error code 2 from standard input (tar) and does not break as it should: $ tar -c -f - -C /media/testpath testfile | split - ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 0 In the end I got a tar file without files that have no permissions and my script does not break because of error code 0. Ubuntu 18.04.1 tar 1.29b coreutils 8.28 Best regards, Alexander To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1792930/+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