[Touch-packages] [Bug 1833833] Re: avro does not work
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1833833 Title: avro does not work Status in ibus package in Ubuntu: Expired Bug description: I am using Avro to pin Bangla after I started using Ubuntu 18.04 LTS but some days later it won,t work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 23 07:23:19 2019 InstallationDate: Installed on 2019-04-27 (56 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1833833/+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 1844031] Re: package whoopsie 0.2.52.5ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for whoopsie (Ubuntu) because there has been no activity for 60 days.] ** Changed in: whoopsie (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1844031 Title: package whoopsie 0.2.52.5ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in whoopsie package in Ubuntu: Expired Bug description: Sub-process /usr/bin/dpkg returned an error code ProblemType: Package DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: libwhoopsie0: Install libwhoopsie0: Configure whoopsie: Configure NULL: ConfigurePending Architecture: amd64 CrashReports: 600:0:117:82082:2019-09-15 08:49:33.570032835 +0400:2019-09-15 08:49:34.570032835 +0400:/var/crash/whoopsie.0.crash Date: Sun Sep 15 08:49:34 2019 DpkgHistoryLog: Start-Date: 2019-09-15 08:49:22 Commandline: apt --fix-broken install Requested-By: cvit (1000) Upgrade: libwhoopsie0:amd64 (0.2.52.5, 0.2.52.5ubuntu0.1) DuplicateSignature: package:whoopsie:0.2.52.5ubuntu0.1 Setting up libwhoopsie0:amd64 (0.2.52.5ubuntu0.1) ... dpkg: error processing package whoopsie (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-02-20 (206 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.52.5ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1844031/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: New Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1844867] Re: nautilus window "open file" cannot be maximized
the report seems to be rather with the gtk fileselector ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - nautilus window "open file" cannot be maximized + gtkfileselector window "open file" cannot be maximized -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1844867 Title: gtkfileselector window "open file" cannot be maximized Status in gtk+3.0 package in Ubuntu: New Bug description: When I do "Open file" from within any application, the nautilus window appears but it doesn't have the "maximize" button and also the double-click on its titlebar does nothing. I must resize it manually by dragging each border... In the previous versions of nautilus this action were possible and much useful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 14:20:27 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'890x545+428+170'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-09-07 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1844867/+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 1844867] [NEW] nautilus window "open file" cannot be maximized
You have been subscribed to a public bug: When I do "Open file" from within any application, the nautilus window appears but it doesn't have the "maximize" button and also the double-click on its titlebar does nothing. I must resize it manually by dragging each border... In the previous versions of nautilus this action were possible and much useful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 14:20:27 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'890x545+428+170'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-09-07 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- nautilus window "open file" cannot be maximized https://bugs.launchpad.net/bugs/1844867 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1835622] Re: Cannot start desktop session with compositor enabled
with newest Mesa version 19.0.8-0ubuntu0~18.04.3 from oficial (non-ppa) bionic-updates repository is problem gone -- 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/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Invalid Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1850977] Re: Snap installs software without user having sudo access
Maciej, that looks like javascript polkit and I believe we're staying on
the pre-javascript version of polkit.
Thanks
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
Invalid
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1796501] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Bug description: [impact] an NXDOMAIN response from a dns server when systemd-resolved is configured as DNSSEC=yes breaks dns resolution as it downgrades from DNSSEC. [test case] see comment 9 [regression potential] as with the original patch that introduced this problem, this has the potential to break dns resolution. [other info] original description: I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the following steps: 1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size. 2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit. 3. Ask upstream for SOA of test.asdf. with EDNS0. 4. Ask upstream for SOA of test.asdf. without EDNS0. 5. Repeat 1-4 for DS of test.asdf. 6. Repeat 1-5 for asdf. 7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size. 8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size. The upstream returns an unfragmented NXDOMAIN response for steps 1-6, an unfragmented NOERROR response for step 7 and a fragmented NOERROR response for step 8 which is the correct behaviour. DNSSEC records are included in the response if the DO-bit in the request was set. systemd-resolved should take the response from step 1 and start with validation instead of starting useless retries with reduced feture set. Step 3 and 4 are completely useless and probably lead to the SERVFAIL because I have configured it with DNSSEC=yes to prevent downgrade attacks. This regression seems to be caused by the patch resolved-Mitigate- DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic should only be executed if it is configured as DNSSEC=allow-downgrade or DNSSEC=no. See also https://github.com/systemd/systemd/pull/8608#issuecomment-396927885. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1843381] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Invalid Bug description: [impact] On Dell system with BIOS-based "MAC passthrough", there can be multiple USB nics with identical MAC addresses. Since the udev rules in Debian and Ubuntu assign interface names for USB nics by mac address (because that is the only consistent identifier for USB nics; their path can change based on which USB port they are connected to), it's impossible to name two interfaces with the same name. As Ubuntu also carries a patch to retry renaming of any interface when the first renaming fails, this causes a 90 second delay before being able to the "MAC passthrough" nic after connecting it. [test case] On a system with this "MAC passthrough" enabled and required devices, boot the system and then connect to the dock or connect the second USB nic with identical MAC. It will not be usable for 90 seconds as its renames takes that long to timeout. [regression potential] the change here is very limited to only Dell systems with the specific USB vendor/product ID affected by this, and additionally the change only sets a ENV flag in the udev rule, which is later used by udevd to skip the rename-retries for 90 seconds. So, the regression potential for anyone else without a system affected by this "MAC passthrough" should be very low, and any regression potential for those with this "MAC passthrough" should still be low, as this only skips the rename- retry that we know will never succeed. However, the regression potential is likely limited to failure to properly name a USB nic, or other bugs during the udev processing of new USB nics. [other info] original description: --- This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019
[Touch-packages] [Bug 1783994] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1783994 Title: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] on systems with mmc device installed, systemd-gpt-auto-generator fails. [test case] on a system with mmc device installed, run systemd-gpt-auto-generator and check log for: systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error [regression potential] as this is related to boot, regressions might occur at boot, or while modifying or configuring a boot loader. [other info] original description: --- If a device has an mmc installed, systemd-gpt-auto-generator will fail because of "special partition" (rpmb, boot) and record a log message: systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error This issue was discussed here: https://github.com/systemd/systemd/issues/5806 and a fix is proposed for new systemd versions. Please include in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1783994/+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 1849658] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1849658 Title: resolved fallback to TCP fails for truncated UDP replies Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] for DNS UDP replies larger than 512 bytes, fallback to TCP is used. For example 'host toomany.ddstreet.org'. Due to a bug in resolved in refcounting DNS stream types, the refcount underflows for type 0 streams (which resolved uses to talk to upstream nameservers), resulting in resolved being unable to fallback to TCP to handle truncated UDP replies. [test case] ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2683 ;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;toomany.ddstreet.org.IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Thu Oct 24 11:40:29 UTC 2019 ;; MSG SIZE rcvd: 678 ubuntu@sf247344-upstream:~$ sudo resolvectl flush-caches ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; connection timed out; no servers could be reached [regression potential] very low, as this only properly sets the stream type in the DnsStream object; any regression would be a failure to be able to use TCP for DNS requests or replies. [other info] https://github.com/systemd/systemd/pull/13838 The commit adding stream types is not present in x/b, so this is needed only for disco and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849658/+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 1832672] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1832672 Title: systemd-resolve not ignoring comments in /etc/hosts Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] resolved does not ignore comments properly in /etc/hosts [test case] see original description below [regression potential] as this modifies resolved parsing of /etc/hosts, regressions would likely be in hostname lookups from hosts in /etc/hosts, or failure(s) to parse /etc/hosts correctly. [other info] original description: --- $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ LANG=C apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 Candidate: 237-3ubuntu10.22 Version table: *** 237-3ubuntu10.22 500 500 http://ch.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.19 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://mirrors.kernel.org/ubuntu bionic/main amd64 Packages $ head -1 /etc/hosts 127.0.2.1 foo # bar $ /usr/bin/systemd-resolve -4 bar expected -- bar: resolve call failed: 'bar' not found What happened instead - bar: 127.0.2.1 HOSTS(5) > Text from a "#" character until the end of the line is a comment, and is ignored. This is fixed in upstream: https://github.com/systemd/systemd/issues/10779 https://github.com/systemd/systemd/commit/bd0052777981044cf54a1e9d6e3acb1c3d813656 Please backport to current LTS version. I accidentally connected to wrong systems because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832672/+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 1805183] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [other info] this fix was included in the initial release of systemd for eoan, but the fix required the additional change in bug 1849608. Both the original patch plus that change (to avoid using bash-specific &>) are included in the b/d patch for this bug. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Touch-packages] [Bug 1840640] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el)
linux/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1840640
Title:
sync_file_range fails in nspawn containers on arm, ppc
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Disco:
Fix Committed
Bug description:
[impact]
calling the glibc function sync_file_range() on a armhf nspawn
container fails.
[test case]
see sample C program from original description below. compile and run
that inside a nspawn container on armhf and it will fail.
nspawn instructions:
sudo apt install debootstrap systemd-container
sudo -i
debootstrap --arch=armhf bionic ~/bionic-tree/
systemd-nspawn -D ~/bionic-tree/
[regression potential]
this only adjusts nspawn to allow the sync_file_range2 syscall which
is used on armhf, so the regression potential is very low. any
possible regressions would likely be when calling sync_file_range().
[other info]
original description:
---
ARM has two sync_file_range syscalls, sync_file_range and
sync_file_range2. The former is apparently not used, and glibc calls
the latter whenever a userspace program calls sync_file_range. I'm
guessing systemd-nspawn doesn't know this, because the follow code
consistently fails in an nspawn container on ARM:
#define _GNU_SOURCE
#include
#include
#include
#include
void main()
{
int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
int r=sync_file_range(f, 0, 0, 0);
if (r)
perror("sync_file_range");
close(f);
}
This seems to be causing problems specifically for borg(backup) and
postgres:
https://github.com/borgbackup/borg/issues/4710
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93
The solution should be to cherrypick
https://github.com/systemd/systemd/pull/13352, I am currently waiting
for systemd to rebuild on a slow ARM box. Any chance of an SRU?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu10.24
Uname: Linux 4.14.66+ armv7l
NonfreeKernelModules: extcon_usb_gpio
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: armhf
Date: Mon Aug 19 11:10:48 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+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 1849733] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1849733 Title: resolved incorrectly limits TCP reply to edns0 payload Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] glibc's getaddrinfo() uses EDNS0 to talk to resolved, and it sets its payload limit to 1200. When the response is larger than 1200, resolved will limit the response and set the truncate flag. This causes getaddrinfo() to switch to TCP and request again, but glibc incorrectly keeps the EDNS0 RR opt, with the same 1200 payload limit. Most dns nameservers ignore EDNS0 payload limit for TCP, since per RFC it applies only to UDP, but resolved does not and again marks the response as truncated. This prevents getaddrinfo() from being able to resolve any records with a response over 1200 bytes. [test case] use ping or telnet, which use getaddrinfo(), to lookup an A record with a lot of results, like toomany100.ddstreet.org $ telnet toomany100.ddstreet.org telnet: could not resolve toomany100.ddstreet.org/telnet: Temporary failure in name resolution [regression potential] any regression would likely result in failure to correctly lookup a hostname or to provide the correct response to a local client. [other info] note that on Bionic, this also requires backporting TCP pipelining support in the stub resolver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849733/+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 1850704] Autopkgtest regression report (systemd/237-3ubuntu10.32)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el) linux/unknown (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1850704 Title: networkd doesn't set MTUBytes if interface is already up Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] if a networkd .network file specifies a [Link] section with MTUBytes=XXX set, networkd will only apply that mtu if the interface is down when networkd starts; if the interface is already up, the mtu won't be applied. [test case] on a bionic system, create a .network file like: [Match] Name=ens8 [Link] MTUBytes= then, reboot. The interface should be set correctly with that mtu: $ ip l show ens8 3: ens8: mtu qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff now, manually change the interface back to 1500 mtu, and restart networkd, then recheck the mtu: $ ip l show ens8 3: ens8: mtu qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff $ sudo ip l set mtu 1500 dev ens8 $ ip l show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff $ sudo systemctl restart systemd-networkd $ ip l show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff [regression potential] low, but any regression would likely involve failure to correctly set the configured mtu. this is needed only in bionic, it's fixed in disco and later already. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1850704/+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 1852018] Re: Audio Stops Playing Briefly When Emptying Trash
can you try with? $ aplay /usr/share/sounds/freedesktop/stereo/service-login.oga -- 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/1852018 Title: Audio Stops Playing Briefly When Emptying Trash Status in pulseaudio package in Ubuntu: Incomplete Bug description: I am running Ubuntu 19.10 and encountered this issue. I had a podcast playing in the background on Firefox v. 70.0.1 and I was deleting some files. I then proceeded to empty the trash and saw that the audio stops briefly till the "Empty all items from Trash?" prompt shows up. I was able to duplicate this many times and it even occurred with audio on Chrome. The expected way for things to work would be the audio keeps on playing, if I just empty the trash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1852018/+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 1852018] Re: Audio Stops Playing Briefly When Emptying Trash
tried that and the sound ends too quickly for me to delete the file and test -- 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/1852018 Title: Audio Stops Playing Briefly When Emptying Trash Status in pulseaudio package in Ubuntu: Incomplete Bug description: I am running Ubuntu 19.10 and encountered this issue. I had a podcast playing in the background on Firefox v. 70.0.1 and I was deleting some files. I then proceeded to empty the trash and saw that the audio stops briefly till the "Empty all items from Trash?" prompt shows up. I was able to duplicate this many times and it even occurred with audio on Chrome. The expected way for things to work would be the audio keeps on playing, if I just empty the trash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1852018/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
Installing ncsd worked well for me 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF 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:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664/+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 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
Verified in bionic with 237-3ubuntu10.32 Dnssec and not are now consistent, tested general functionality with dnssec=yes and not set as well. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Bug description: [impact] an NXDOMAIN response from a dns server when systemd-resolved is configured as DNSSEC=yes breaks dns resolution as it downgrades from DNSSEC. [test case] see comment 9 [regression potential] as with the original patch that introduced this problem, this has the potential to break dns resolution. [other info] original description: I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the following steps: 1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size. 2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit. 3. Ask upstream for SOA of test.asdf. with EDNS0. 4. Ask upstream for SOA of test.asdf. without EDNS0. 5. Repeat 1-4 for DS of test.asdf. 6. Repeat 1-5 for asdf. 7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size. 8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size. The upstream returns an unfragmented NXDOMAIN response for steps 1-6, an unfragmented NOERROR response for step 7 and a fragmented NOERROR response for step 8 which is the correct behaviour. DNSSEC records are included in the response if the DO-bit in the request was set. systemd-resolved should take the response from step 1 and start with validation instead of starting useless retries with reduced feture set. Step 3 and 4 are completely useless and probably lead to the SERVFAIL because I have configured it with DNSSEC=yes to prevent downgrade attacks. This regression seems to be caused by the patch resolved-Mitigate- DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic should only be executed if it is configured as DNSSEC=allow-downgrade or DNSSEC=no. See also https://github.com/systemd/systemd/pull/8608#issuecomment-396927885. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1850977] Re: Snap installs software without user having sudo access
Unfortunately it isn't that easy in my case. I need to have every action
attempted logged. That will still give it to me, but modifying what's
happening by changing what's being requested.
So, if a normal user attempts something, the best case is for it to ask
for the users password and fail when they don't have permission to do
the action, or the password entered is wrong.
Second best, is to fall back to asking for the root password. I can deal
with the logging inaccuracy.
But not always ask for the root password in every case which is what
that override will do.
I'm going to be needing to implement some custom polkit/apparmour stuff
eventually anyway (now that I've seen this), but this came about as I am
not a Debian/Ubuntu person. So I hit something that _shouldn't_ have
been happening in my mind (hey, no sudoers access, no way to run as
root) ... It threw me that it was happening.
But thanks to everyone for digging into this with me.
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
Invalid
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
In /etc/systemd/system/systemd-logind.service comment out IPAddressDeny=Any this work around has been working for us for about a 10 months now -- 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF 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:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664/+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 1850977] Re: Snap installs software without user having sudo access
Not sure whether removing files that came with distro packages is the
best idea long term. I think a better option would be to drop in a
custom rule that runs before the default ones. As usual ArchWiki has
some examples:
https://wiki.archlinux.org/index.php/Polkit#Administrator_identities
Specifically, if I'm reading this right, putting the following rule in
/etc/polkit-1/rules.d/00-override.rules should be enough:
/* Always authenticate Admins by prompting for the root
* password, similar to the rootpw option in sudo
*/
polkit.addAdminRule(function(action, subject) {
return ["unix-user:root"];
});
Having this it's easy to build a package that can be later distributed
to other workstations.
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
Invalid
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1847527] Re: Backport systemd-journal-remote fix PR #11953
> I'm currently traveling for work, but will verify the fix this evening hopefully. Thanks - I did a quick verification but it would be good if you could verify it works for you 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in openstack-ansible: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does not specify Content-Length. [test case] setup 2 systems, A and B. Install systemd-journal-remote on both. On A: $ sudo systemctl edit systemd-journal-remote.service in the editor, add: [Service] ExecStart= ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/ Then enable/start the socket: $ sudo systemctl enable systemd-journal-remote.socket $ sudo systemctl start systemd-journal-remote.socket Optionally, start the service and verify it is running (not required, since the socket will start the service): $ sudo systemctl start systemd-journal-remote.service $ sudo systemctl status systemd-journal-remote.service | grep Active Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago On B: Edit the file /etc/systemd/journal-upload.conf: [Upload] URL=http://192.168.122.184:19532 Replacing the IP address with the actual ip addr of node A. Then enable/start the service: $ sudo systemctl enable systemd-journal-upload.service $ sudo systemctl start systemd-journal-upload.service Check for failure: ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. -- Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service. Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to http://192.168.122.184:19532/upload failed with code 411: gth Required Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=1/FAILURE Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'. [regression potential] this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there. Any regression would likely result in the failure to upload a remote journal. [other info] the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco. original description: -- I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 1847527] Re: Backport systemd-journal-remote fix PR #11953
with testcase setup from description, system A is -remote and system B is -d ubuntu@lp1847527-remote:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.7 amd64system and service manager ubuntu@lp1847527-d:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.7 amd64system and service manager ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. -- Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service. Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to http://192.168.122.184:19532/upload failed with code 411: gth Required Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=1/FAILURE Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'. Fix must be applied to system A (where systemd-journal-remote.serivce is running): ubuntu@lp1847527-remote:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.8 amd64system and service manager ubuntu@lp1847527-d:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.7 amd64system and service manager ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:34:28 UTC. -- Nov 14 20:33:33 lp1847527-d systemd[1]: Started Journal Remote Upload Service. and upgrading system B, it still works correctly (as long as system A has been upgraded): ubuntu@lp1847527-d:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.8 amd64system and service manager ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:38:38 UTC. -- Nov 14 20:38:35 lp1847527-d systemd[1]: Started Journal Remote Upload Service. ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in openstack-ansible: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does not specify Content-Length. [test case] setup 2 systems, A and B. Install systemd-journal-remote on both. On A: $ sudo systemctl edit systemd-journal-remote.service in the editor, add: [Service] ExecStart= ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/ Then enable/start the socket: $ sudo systemctl enable systemd-journal-remote.socket $ sudo systemctl start systemd-journal-remote.socket Optionally, start the service and verify it is running (not required, since the socket will start the service): $ sudo systemctl start systemd-journal-remote.service $ sudo systemctl status systemd-journal-remote.service | grep Active Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago On B: Edit the file /etc/systemd/journal-upload.conf: [Upload] URL=http://192.168.122.184:19532 Replacing the IP address with the actual ip addr of node A. Then enable/start the service: $ sudo systemctl enable systemd-journal-upload.service $ sudo systemctl start systemd-journal-upload.service Check for failure: ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. -- Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service. Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to http://192.168.122.184:19532/upload failed with code 411: gth Required Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=1/FAILURE Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'. [regression potential] this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there. Any regression would likely result in the failure to upload a remote journal.
[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
And this also helps here? https://github.com/systemd/systemd/issues/9431#issuecomment-412195708 -- 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF 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:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664/+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 1850977] Re: Snap installs software without user having sudo access
As an addition... If I remove the 51-ubuntu-admin.conf file, when I run
`snap install blender --classic`, it pops up a dialog box asking for the
"Administrator" password.
Entering roots password will install it.
This is the behaviour wanted. Not install it with only the users
authentication.
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
Invalid
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1774417] Re: systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted
Does this workaround help here as well? https://github.com/systemd/systemd/issues/9431#issuecomment-412195708 Essentially, replace IPAddressDeny=any with just "IPAddressDeny=" ** Bug watch added: github.com/systemd/systemd/issues #9431 https://github.com/systemd/systemd/issues/9431 -- 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/1774417 Title: systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Confirmed Bug description: See upstream bug report 7074 (systemd-logind's IP sandbox breaks nss- nis and suchlike) [1]. Logging in takes a long time. May 30 13:26:25 ubuntu1804 systemd-logind[2993]: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted May 30 13:26:50 ubuntu1804 sshd[3446]: pam_systemd(sshd:session): Failed to create session: Connection timed out Conclusion: > Please ask your downstream distribution to either: > > 1. include a systemd-logind.service.d/ snippet in your nss-nis package that turns off the IP firewalling logic for logind > 2. or patching systemd-logind.service for everybody to disable it distro-wide (which I'd really not recommend though, compromising the security for everybody just because for compat of a nowadays pretty niche nss module that does some very questionnable things doesn't sound like the best way out to me) [1] https://github.com/systemd/systemd/issues/7074 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1774417/+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
Re: [Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953
I'm currently traveling for work, but will verify the fix this evening hopefully. Thanks On Thu, Nov 14, 2019, 10:41 Dan Streetman wrote: > @drdabbles can you please verify the fix in systemd in proposed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1847527 > > Title: > Backport systemd-journal-remote fix PR #11953 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+subscriptions > -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in openstack-ansible: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does not specify Content-Length. [test case] setup 2 systems, A and B. Install systemd-journal-remote on both. On A: $ sudo systemctl edit systemd-journal-remote.service in the editor, add: [Service] ExecStart= ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/ Then enable/start the socket: $ sudo systemctl enable systemd-journal-remote.socket $ sudo systemctl start systemd-journal-remote.socket Optionally, start the service and verify it is running (not required, since the socket will start the service): $ sudo systemctl start systemd-journal-remote.service $ sudo systemctl status systemd-journal-remote.service | grep Active Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago On B: Edit the file /etc/systemd/journal-upload.conf: [Upload] URL=http://192.168.122.184:19532 Replacing the IP address with the actual ip addr of node A. Then enable/start the service: $ sudo systemctl enable systemd-journal-upload.service $ sudo systemctl start systemd-journal-upload.service Check for failure: ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. -- Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service. Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to http://192.168.122.184:19532/upload failed with code 411: gth Required Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=1/FAILURE Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'. [regression potential] this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there. Any regression would likely result in the failure to upload a remote journal. [other info] the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco. original description: -- I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 1852566] Re: [OptiPlex 3050, Intel ID 280b, Digital Out, HDMI] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852566 Title: [OptiPlex 3050, Intel ID 280b, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound is coming ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 14 16:43:36 2019 InstallationDate: Installed on 2018-05-12 (550 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: subhrashree 1845 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [OptiPlex 3050, Intel ID 280b, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852566/+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 1847527] Re: Backport systemd-journal-remote fix PR #11953
** Description changed: [impact] upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does not specify Content-Length. [test case] - see comment 5 + setup 2 systems, A and B. Install systemd-journal-remote on both. + + On A: + + $ sudo systemctl edit systemd-journal-remote.service + + in the editor, add: + + [Service] + ExecStart= + ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/ + + + Then enable/start the socket: + + $ sudo systemctl enable systemd-journal-remote.socket + $ sudo systemctl start systemd-journal-remote.socket + + Optionally, start the service and verify it is running (not required, + since the socket will start the service): + + $ sudo systemctl start systemd-journal-remote.service + $ sudo systemctl status systemd-journal-remote.service | grep Active +Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago + + + On B: + + Edit the file /etc/systemd/journal-upload.conf: + + [Upload] + URL=http://192.168.122.184:19532 + + + Replacing the IP address with the actual ip addr of node A. Then enable/start the service: + + $ sudo systemctl enable systemd-journal-upload.service + $ sudo systemctl start systemd-journal-upload.service + + Check for failure: + + ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service + -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. -- + Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service. + Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to http://192.168.122.184:19532/upload failed with code 411: gth Required + Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=1/FAILURE + Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'. + [regression potential] this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there. Any regression would likely result in the failure to upload a remote journal. [other info] the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco. original description: -- I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in openstack-ansible: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does not specify Content-Length. [test case] setup 2 systems, A and B. Install systemd-journal-remote on both. On A: $ sudo systemctl edit systemd-journal-remote.service in the editor, add: [Service] ExecStart= ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/ Then enable/start the socket: $ sudo systemctl enable systemd-journal-remote.socket $ sudo systemctl start systemd-journal-remote.socket Optionally, start the service and verify it is running (not required, since the socket will start the service): $ sudo systemctl start systemd-journal-remote.service $ sudo systemctl status systemd-journal-remote.service | grep Active Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago On B: Edit the file /etc/systemd/journal-upload.conf: [Upload] URL=http://192.168.122.184:19532 Replacing the IP address with the actual ip addr of node A. Then enable/start the service: $ sudo systemctl enable systemd-journal-upload.service $ sudo systemctl start systemd-journal-upload.service Check for failure: ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. -- Nov 14
[Touch-packages] [Bug 1850977] Re: Snap installs software without user having sudo access
That's what I want though. I want control through sudoers, not polkit.
The file: /etc/polkit-1/localauthority.conf.d/50-localauthority.conf ... still
contains:
```
[Configuration]
AdminIdentities=unix-user:0
```
I don't know why you need to say root is an admin, but whatever it's
there... And that *should* be the only admin. No other user should have
administrative privileges on their own, without using sudo or becoming
root. Full stop.
This isn't for a single desktop home system, but a corporate controlled
system. A user that can install software just because they want to isn't
going to fly (or pass Government regulations we need to). And not all
admins are created equal.
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
Invalid
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1850977] Re: Snap installs software without user having sudo access
Having no group listed by default would means admin users wouldn't be
able to use polkit which is not what we want.
https://gitlab.freedesktop.org/polkit/polkit/issues/24 discusses a bit
the group checking logic
** Changed in: gnome-software (Ubuntu)
Status: New => Invalid
** Bug watch added: gitlab.freedesktop.org/polkit/polkit/issues #24
https://gitlab.freedesktop.org/polkit/polkit/issues/24
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
Invalid
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
Verified in disco with, ii systemd 240-6ubuntu5.8 Dnssec and not are now consistent, tested general functionality with dnssec=yes and not set as well. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Bug description: [impact] an NXDOMAIN response from a dns server when systemd-resolved is configured as DNSSEC=yes breaks dns resolution as it downgrades from DNSSEC. [test case] see comment 9 [regression potential] as with the original patch that introduced this problem, this has the potential to break dns resolution. [other info] original description: I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the following steps: 1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size. 2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit. 3. Ask upstream for SOA of test.asdf. with EDNS0. 4. Ask upstream for SOA of test.asdf. without EDNS0. 5. Repeat 1-4 for DS of test.asdf. 6. Repeat 1-5 for asdf. 7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size. 8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size. The upstream returns an unfragmented NXDOMAIN response for steps 1-6, an unfragmented NOERROR response for step 7 and a fragmented NOERROR response for step 8 which is the correct behaviour. DNSSEC records are included in the response if the DO-bit in the request was set. systemd-resolved should take the response from step 1 and start with validation instead of starting useless retries with reduced feture set. Step 3 and 4 are completely useless and probably lead to the SERVFAIL because I have configured it with DNSSEC=yes to prevent downgrade attacks. This regression seems to be caused by the patch resolved-Mitigate- DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic should only be executed if it is configured as DNSSEC=allow-downgrade or DNSSEC=no. See also https://github.com/systemd/systemd/pull/8608#issuecomment-396927885. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1851695] Re: DEP8 failure/regression in nspr on arm64 and armhf
According to that commit, it's not yet enough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/1851695 Title: DEP8 failure/regression in nspr on arm64 and armhf Status in notary package in Ubuntu: New Status in nspr package in Ubuntu: Invalid Status in notary package in Debian: Confirmed Bug description: nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf: autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest autopkgtest [09:46:25]: test command1: [--- [info] Testing github.com/theupdateframework/notary... [info] Source code installed by binary package, overriding dh_auto_configure... [info] Disabling existing override_dh_auto_configure... dh build --builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build \ --buildsystem=golang \ --with=golang dh_update_autotools_config -O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build -O--buildsystem=golang dh_autoreconf -O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build -O--buildsystem=golang debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' mkdir -p "_build" cp -a /usr/share/gocode/src "_build" make[1]: Leaving directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' debian/rules override_dh_auto_build make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' dh_auto_build -- -tags "pkcs11" cd _build && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -v -p 1 -tags pkcs11 github.com/theupdateframework/notary github.com/theupdateframework/notary/client github.com/theupdateframework/notary/client/changelist github.com/theupdateframework/notary/cmd/escrow github.com/theupdateframework/notary/cmd/notary github.com/theupdateframework/notary/cmd/notary-server github.com/theupdateframework/notary/cmd/notary-signer github.com/theupdateframework/notary/cryptoservice github.com/theupdateframework/notary/passphrase github.com/theupdateframework/notary/proto github.com/theupdateframework/notary/server github.com/theupdateframework/notary/server/errors github.com/theupdateframework/notary/server/handlers github.com/theupdateframework/notary/server/snapshot github.com/theupdateframework/notary/server/storage github.com/theupdateframework/notary/server/timestamp github.com/theupdateframework/notary/signer github.com/theupdateframework/notary/signer/api github.com/theupdateframework/notary/signer/client github.com/theupdateframework/notary/signer/keydbstore github.com/theupdateframework/notary/storage github.com/theupdateframework/notary/storage/rethinkdb github.com/theupdateframework/notary/trustmanager github.com/theupdateframework/notary/trustmanager/remoteks github.com/theupdateframework/notary/trustmanager/yubikey github.com/theupdateframework/notary/trustpinning github.com/theupdateframework/notary/tuf github.com/theupdateframework/notary/tuf/data github.com/theupdateframework/notary/tuf/signed github.com/theupdateframework/notary/tuf/testutils github.com/theupdateframework/notary/tuf/testutils/interfaces github.com/theupdateframework/notary/tuf/testutils/keys github.com/theupdateframework/notary/tuf/utils github.com/theupdateframework/notary/tuf/validation github.com/theupdateframework/notary/utils github.com/theupdateframework/notary/version src/github.com/docker/distribution/digestset/set.go:9:2: cannot find package "github.com/opencontainers/go-digest" in any of: /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/go-digest (vendor tree) /usr/lib/go-1.12/src/github.com/opencontainers/go-digest (from $GOROOT) /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/go-digest (from $GOPATH) src/github.com/docker/distribution/blobs.go:13:2: cannot find package "github.com/opencontainers/image-spec/specs-go/v1" in any of: /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/image-spec/specs-go/v1 (vendor tree) /usr/lib/go-1.12/src/github.com/opencontainers/image-spec/specs-go/v1 (from $GOROOT) /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/image-spec/specs-go/v1 (from $GOPATH) dh_auto_build: cd _build && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -v -p 1 -tags pkcs11 github.com/theupdateframework/notary github.com/theupdateframework/notary/client github.com/theupdateframework/notary/client/changelist
[Touch-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.99-1ubuntu1~18.04.1 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: libdrm (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- 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/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.99-1ubuntu1~18.04.1 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: libdrm (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-9 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1850977] Re: Snap installs software without user having sudo access
Thank You!!!
Can you set it like:
```
[Configuration]
AdminIdentities=
```
So *nothing* is considered an Admin?
That file has `unix-group:sudo;unix-group:admin` ... by default from
what I can tell. But at least that I know this thing exists and hey, you
can elevate privileges without being in sudoers (Ugh... another thing to
restrict for regulations).
Does that deal only with the *name* of the group, or what it sees as the
GID?
I mean, I can make another user named `bob` with a UID of 0 ... so I'm
still effectively root even if I'm logged in as bob. Does this work that
way with GID's? Or is it looking explicitly at the name only even if the
name is irrelevant is actual system usage?
Meaning, I can have groups named: Admin, AdminA, AdminB, AdminC
with different members but the same GID. In this way anything on the
filesystem owned by the `Admin` group, can be accessed by any of the
Admin groups since it's the GID that matters.
Does PolicyKit take GIDs into account, or just the name?
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
New
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-9 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-9/1:9-2~ubuntu18.04.1 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: llvm-toolchain-9 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: In Progress Status in llvm-toolchain-9 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1850977] Re: Snap installs software without user having sudo access
The polkit definition of the admin group is in
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
Did you update that file to reflect that your admin group has a
different naming?
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
New
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1850977] Re: Snap installs software without user having sudo access
The above still stands... but that isn't it for `snap` ... I changed all
the `isIngroup("sudo")` to use `sudoA` since that's the actually group
that's in sudoers...
And snap is still letting me install the blender snap in `--classic`
mode. So How do you find out what polkit rules are running at any
given time?
The `io.snapcraft.snapd.manage' action has:
```
auth_admin
```
But where is what `auth_admin` does defined? It *looks* like it's seeing
it as a local login and just allowing it. If I log in through SSH and
try the same command I get:
$ snap install blender --classic
error: access denied (try with sudo)
Being a locally logged in user does not mean you should have the ability to
install software. Again, that's an incorrect assumption being made :/
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
New
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
llvm-toolchain-9, libdrm uploaded to the queue ** Description changed: - PLACEHOLDER + [Impact] + + These are needed for 18.04.4 images. + + [Test case] + + Boot a daily image, see that it still has the necessary stack installed + and working. + + Check upgrade from stock bionic. + + [Regression potential] + + libdrm: very minimal chance for regressions + + llvm-9: a new package, no regression potential on it's own + + libclc: more or less just adds support for new llvm + + mesa: a new major release, but we'll pull the final stable release of + 19.2.x series, so there shouldn't be any regressions left at that point + + xserver: a new git snapshot (or maybe a point-release) + + xorg drivers: modest updates, mainly just new ati/amdgpu + + [Other info] ** Changed in: llvm-toolchain-9 (Ubuntu Bionic) Status: New => In Progress ** Changed in: libdrm (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: In Progress Status in llvm-toolchain-9 source package in Bionic: In Progress Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1850977] Re: Snap installs software without user having sudo access
the requirement for policykit (and dropping of gksu/gksudo) came with
the switch to gnome upstream, its a hard requirement for the desktop
nowadays.
while the default here might be wrong (and should be reviewed by someone
from the desktop team), this is definitely not a snapd related bug. i
added a gnome-software task and will close the snapd one ...
** Changed in: snapd (Ubuntu)
Status: Incomplete => Invalid
** Also affects: gnome-software (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/1850977
Title:
Snap installs software without user having sudo access
Status in gnome-software package in Ubuntu:
New
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Invalid
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
LGTM on bionic ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii ii systemd237-3ubuntu10.32 i386 system and service manager ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution. Nov 14 17:05:44 srv-ywz63 systemd[1]: Started Network Name Resolution. ubuntu@srv-ywz63:~$ sudo dhclient eth0 RTNETLINK answers: File exists ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution. Nov 14 17:05:44 srv-ywz63 systemd[1]: Started Network Name Resolution. ubuntu@srv-ywz63:~$ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [other info] this fix was included in the initial release of systemd for eoan, but the fix required the additional change in bug 1849608. Both the original patch plus that change (to avoid using bash-specific &>) are included in the b/d patch for this bug. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018
[Touch-packages] [Bug 1723390] Re: lxd containers have become degraded
That particular issue is gone, but there are others now # systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● sys-kernel-config.mount loaded failed failed Kernel Configuration File System ● systemd-modules-load.service loaded failed failed Load Kernel Modules -- 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/1723390 Title: lxd containers have become degraded Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Eoan: Fix Released Bug description: 20170920 container boots degraded with Oct 13 10:09:28 test20170920 systemd[256]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied 20170919 container boots non-degraded. Package list changes are insignificant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723390/+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 1851349] Re: Xorg freeze
I don't have any specific hint for what to look at in the journal no, just hints of what the problems could be. You can switch drivers in software-properties-gtk ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- 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/1851349 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor now and then. Problem with multitasking. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 10:29:50 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2019-10-18 (17 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851349/+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 1850977] Re: Snap installs software without user having sudo access
I think I may have found it It looks like policykit has some rules
with entries like:
```
subject.isInGroup("sudo")
```
That's ... broken. Just being in the `sudo` group should *NOT* let me
install software or elevate my priviledges, *ESPECIALLY* if the user
isn't actually in the sudoers. It's a broken assumption.
I changed the /etc/sudoers file so the `sudo` group does *NOT* have
permissions explicitly for this reason.
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Incomplete
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1850977/+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 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
with dnsmasq server setup to provide dhcp with 1m lease timeout, just run dhclient on test system: ubuntu@lp1805183-d:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.7 amd64system and service manager ubuntu@lp1805183-d:~$ journalctl -b -u systemd-resolved | grep Started Nov 14 16:02:12 lp1805183-d systemd[1]: Started Network Name Resolution. ubuntu@lp1805183-d:~$ sudo dhclient ens8 ubuntu@lp1805183-d:~$ journalctl -b -u systemd-resolved | grep Started Nov 14 16:02:12 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:04:32 lp1805183-d systemd[1]: Started Network Name Resolution. ubuntu@lp1805183-d:~$ sleep 900 ; journalctl -b -u systemd-resolved | grep Started Nov 14 16:02:12 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:04:32 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:05:22 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:06:11 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:06:57 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:07:52 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:08:41 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:09:25 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:10:17 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:11:03 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:11:51 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:12:33 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:13:24 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:14:16 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:15:11 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:16:03 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:16:46 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:17:34 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:18:23 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:19:16 lp1805183-d systemd[1]: Started Network Name Resolution. ubuntu@lp1805183-d:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.8 amd64system and service manager ubuntu@lp1805183-d:~$ journalctl -b -u systemd-resolved | grep Started Nov 14 16:21:20 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:29:41 lp1805183-d systemd[1]: Started Network Name Resolution. ubuntu@lp1805183-d:~$ sudo dhclient ens8 cmp: EOF on /tmp/tmp.qY6fTBCaSb which is empty ubuntu@lp1805183-d:~$ sleep 900 ; journalctl -b -u systemd-resolved | grep Started Nov 14 16:21:20 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:29:41 lp1805183-d systemd[1]: Started Network Name Resolution. Nov 14 16:30:51 lp1805183-d systemd[1]: Started Network Name Resolution. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it
[Touch-packages] [Bug 1850977] Re: Snap installs software without user having sudo access
Oliver,
> if you are marked as admin in the policyKit setup
Where do you find this? Where is the definition for what `auth_admin`
does located? From the freedesktop site it *seems* that it's an
"Administrative user," which to me is sudoers. As the system admin I'm
not defining an admin user anywhere else but sudoers. If it's just by
group that's broken all to hell...
The freedesktop.org site states[1]:
> If the system is configured without a root account it may prompt for a
specific user designated as the administrative user:
Where do you designate a user as the administrative user outside of
putting them in sudoers?
I need to implement government regulations. Some users need to be in
the admin group from LDAP, but cannot install software on workstations.
sudoers *should* control this. The init system has nothing to do with
account elevation... unless they're taking that over as well.
This was a straight up install from Ubuntu. Nothing in my Salt
configurations touch polkit settings.
Since I'm doing LDAP login, there's /etc/pam.d entries in files for
LDAP auth that polkit uses. Would this be interfering?
-J
[1] -
https://www.freedesktop.org/software/polkit/docs/latest/polkit.8.html
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Incomplete
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1850977/+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 1851806] Re: 'module' object has no attribute 'O_PATH'
** Tags added: regression-update
** Changed in: apport (Ubuntu)
Status: Incomplete => New
--
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/1851806
Title:
'module' object has no attribute 'O_PATH'
Status in apport package in Ubuntu:
New
Bug description:
I encountered the following exception in python-apport while
encountering an exception `bup` which uses `python-apport`. I'm sure
that the exception lies in the responsibility of `python-apport` (the
`AttributeError` stacktrace is relevant):
```
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
AttributeError: 'module' object has no attribute 'O_PATH'
Original exception was:
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
```
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: python-apport 2.20.11-0ubuntu8.2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 8 10:43:02 2019
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851806/+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 1850977] Re: Snap installs software without user having sudo access
I looked at the policy used by PackageKit. I believe gnome-software uses
it as a backend, so can you try installing something that is
specifically not a snap?
At this point, all snapd does is ask PolicyKit whether given the policy,
the user can install a package. PolicyKit responds with yes, therefore
the installation can proceed. There's not much we can do inside the
declared policy, as the defaults are fine IMO.
>From my perspective, this should likely be investigated by someone more
familiar with PolicyKit to find out why it's treating your user as
admin.
** Also 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/1850977
Title:
Snap installs software without user having sudo access
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Incomplete
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1850977/+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 1851806] Re: 'module' object has no attribute 'O_PATH'
Here's a reproduction of the error:
bcurtiss@bcurtiss-laptop:~$ ipython
Python 2.7.12 (default, Oct 8 2019, 14:14:10)
Type "copyright", "credits" or "license" for more information.
IPython 2.4.1 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object', use 'object??' for extra details.
In [1]: import apport_python_hook;
apport_python_hook.apport_excepthook(Exception, Exception(), None)
Exception
---
AttributeErrorTraceback (most recent call last)
in ()
> 1 import apport_python_hook;
apport_python_hook.apport_excepthook(Exception, Exception(), None)
/usr/lib/python2.7/dist-packages/apport_python_hook.pyc in
apport_excepthook(exc_type, exc_obj, exc_tb)
107 traceback.print_exception(exc_type, exc_obj, exc_tb,
file=tb_file)
108 pr['Traceback'] = tb_file.getvalue().strip()
--> 109 pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
110 pr.add_user_info()
111 # override the ExecutablePath with the script that was actually
running
/usr/lib/python2.7/dist-packages/apport/report.pyc in add_proc_info(self, pid,
proc_pid_fd, extraenv)
517 self.pid = int(pid)
518 pid = str(pid)
--> 519 proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY |
os.O_PATH | os.O_DIRECTORY)
520
521 try:
AttributeError: 'module' object has no attribute 'O_PATH'
In [2]: exit
bcurtiss@bcurtiss-laptop:~$ ipython3
Python 3.5.2 (default, Oct 8 2019, 13:06:37)
Type "copyright", "credits" or "license" for more information.
IPython 2.4.1 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object', use 'object??' for extra details.
In [1]: import apport_python_hook;
apport_python_hook.apport_excepthook(Exception, Exception(), None)
Exception
In [2]: exit
bcurtiss@bcurtiss-laptop:~$
--
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/1851806
Title:
'module' object has no attribute 'O_PATH'
Status in apport package in Ubuntu:
Incomplete
Bug description:
I encountered the following exception in python-apport while
encountering an exception `bup` which uses `python-apport`. I'm sure
that the exception lies in the responsibility of `python-apport` (the
`AttributeError` stacktrace is relevant):
```
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
AttributeError: 'module' object has no attribute 'O_PATH'
Original exception was:
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
```
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: python-apport 2.20.11-0ubuntu8.2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 8 10:43:02 2019
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851806/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help
[Touch-packages] [Bug 1850977] Re: Snap installs software without user having sudo access
policyKit does not involve sudo in any way, it uses systemd-logind from
the session to elevate privileges. if you are marked as admin in the
policyKit setup you will indeed be able to do admin things no matter
what is written in sudoers ;)
--
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/1850977
Title:
Snap installs software without user having sudo access
Status in policykit-1 package in Ubuntu:
New
Status in snapd package in Ubuntu:
Incomplete
Bug description:
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
3.28.1-0ubuntu4.18.04.12 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
*** 3.28.1-0ubuntu4.18.04.8 100
100 /var/lib/dpkg/status
3.28.1-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64
What I expect to happen:
Software is not installed for a user without sudo access.
What does happen:
I'm logging in with an LDAP user. This user does not have sudo access.
When I select software from gnome-software ("Ubuntu Software"), it
pops up and asks for my users password. I enter this in, and the
software then installs (tested with blender, libreoffice, opencl
driver).
My user does *not* have sudo access on the system.
$ sudo su -
[sudo] password for jason:
jason is not in the sudoers file. This incident will be reported.
It appears these *may* be being installed with Snaps ... which still:
How, without having root access, can an unprivileged user install
something onto the system?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.8
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 1 13:53:03 2019
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1850977/+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 1851806] Re: 'module' object has no attribute 'O_PATH'
I'm not exactly sure how to reproduce this bug, but I did encounter the
same issue. It looks like the bug was recently introduced in this
commit:
https://git.launchpad.net/ubuntu/+source/apport/commit/?h=applied/ubuntu
/xenial-security=ecd7418b02911c6649b69a592cca74cfbac8813d
```
@@ -510,22 +510,24 @@ class Report(problem_report.ProblemReport):
- _LogindSession: logind cgroup path, if present (Used for filtering
out crashes that happened in a session that is not running any more)
'''
-if not pid:
-pid = self.pid or os.getpid()
-if not self.pid:
-self.pid = int(pid)
-pid = str(pid)
+if not proc_pid_fd:
+if not pid:
+pid = self.pid or os.getpid()
+if not self.pid:
+self.pid = int(pid)
+pid = str(pid)
+proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
try:
-self['ProcCwd'] = os.readlink('/proc/' + pid + '/cwd')
+self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
except OSError:
pass
self.add_proc_environ(pid, extraenv)
-self['ProcStatus'] = _read_file('/proc/' + pid + '/status')
-self['ProcCmdline'] = _read_file('/proc/' + pid +
'/cmdline').rstrip('\0')
-self['ProcMaps'] = _read_maps(int(pid))
+self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
+self['ProcCmdline'] = _read_file('cmdline',
dir_fd=proc_pid_fd).rstrip('\0')
+self['ProcMaps'] = _read_maps(proc_pid_fd)
try:
-self['ExecutablePath'] = os.readlink('/proc/' + pid + '/exe')
+self['ExecutablePath'] = os.readlink('exe', dir_fd=proc_pid_fd)
except OSError as e:
if e.errno == errno.ENOENT:
raise ValueError('invalid process')
```
The problem is that os.O_PATH does not exist in python2, and only exists
in python3. However, python-apport is a python2 package.
```
bcurtiss@bcurtiss-laptop:~$ python3 -c 'import os; print(os.O_PATH)'
2097152
bcurtiss@bcurtiss-laptop:~$ python -c 'import os; print(os.O_PATH)'
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'module' object has no attribute 'O_PATH'
bcurtiss@bcurtiss-laptop:~$
```
--
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/1851806
Title:
'module' object has no attribute 'O_PATH'
Status in apport package in Ubuntu:
Incomplete
Bug description:
I encountered the following exception in python-apport while
encountering an exception `bup` which uses `python-apport`. I'm sure
that the exception lies in the responsibility of `python-apport` (the
`AttributeError` stacktrace is relevant):
```
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
AttributeError: 'module' object has no attribute 'O_PATH'
Original exception was:
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
```
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: python-apport 2.20.11-0ubuntu8.2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 8 10:43:02 2019
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851806/+subscriptions
--
Mailing list:
[Touch-packages] [Bug 1847815] Re: storage autopkgtest is flaky
the 'storage' autopkgtest passes on all archs now. other systemd autopkgtests still fail on ppc64el, but systemd tests have always failed on disco ppc64el so those failures can be ignored. ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- 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/1847815 Title: storage autopkgtest is flaky Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] the systemd autopkgtest 'storage' is flaky. [test case] look at the autopkgtest test log and see some of them are failures due to failing 'storage' test; on re-running the test is passes. [regression potential] only an autopkgtest fix; very low if any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847815/+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 1847527] Re: Backport systemd-journal-remote fix PR #11953
@drdabbles can you please verify the fix in systemd in proposed -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in openstack-ansible: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does not specify Content-Length. [test case] see comment 5 [regression potential] this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there. Any regression would likely result in the failure to upload a remote journal. [other info] the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco. original description: -- I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 1849733] Re: resolved incorrectly limits TCP reply to edns0 payload
ubuntu@lp1849733-d:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.7 amd64system and service manager ubuntu@lp1849733-d:~$ telnet toomany100.ddstreet.org telnet: could not resolve toomany100.ddstreet.org/telnet: Temporary failure in name resolution ubuntu@lp1849733-d:/etc/systemd/network$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.8 amd64system and service manager ubuntu@lp1849733-d:/etc/systemd/network$ telnet toomany100.ddstreet.org Trying 10.254.201.100... ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1849733 Title: resolved incorrectly limits TCP reply to edns0 payload Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] glibc's getaddrinfo() uses EDNS0 to talk to resolved, and it sets its payload limit to 1200. When the response is larger than 1200, resolved will limit the response and set the truncate flag. This causes getaddrinfo() to switch to TCP and request again, but glibc incorrectly keeps the EDNS0 RR opt, with the same 1200 payload limit. Most dns nameservers ignore EDNS0 payload limit for TCP, since per RFC it applies only to UDP, but resolved does not and again marks the response as truncated. This prevents getaddrinfo() from being able to resolve any records with a response over 1200 bytes. [test case] use ping or telnet, which use getaddrinfo(), to lookup an A record with a lot of results, like toomany100.ddstreet.org $ telnet toomany100.ddstreet.org telnet: could not resolve toomany100.ddstreet.org/telnet: Temporary failure in name resolution [regression potential] any regression would likely result in failure to correctly lookup a hostname or to provide the correct response to a local client. [other info] note that on Bionic, this also requires backporting TCP pipelining support in the stub resolver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849733/+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 1849658] Re: resolved fallback to TCP fails for truncated UDP replies
ubuntu@lp1849733-d:~$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.7 amd64system and service manager ubuntu@lp1849733-d:~$ dig +noanswer +noedns toomany.ddstreet.org ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.11.5-P1-1ubuntu2.5-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57225 ;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;toomany.ddstreet.org. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Thu Nov 14 15:15:13 UTC 2019 ;; MSG SIZE rcvd: 678 ubuntu@lp1849733-d:~$ sudo resolvectl flush-caches ubuntu@lp1849733-d:~$ dig +noanswer +noedns toomany.ddstreet.org ; <<>> DiG 9.11.5-P1-1ubuntu2.5-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; connection timed out; no servers could be reached ubuntu@lp1849733-d:/etc/systemd/network$ dpkg -l systemd|grep ii ii systemd240-6ubuntu5.8 amd64system and service manager ubuntu@lp1849733-d:/etc/systemd/network$ dig +noanswer +noedns toomany.ddstreet.org ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.11.5-P1-1ubuntu2.5-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26936 ;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;toomany.ddstreet.org. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Thu Nov 14 15:21:10 UTC 2019 ;; MSG SIZE rcvd: 678 ubuntu@lp1849733-d:/etc/systemd/network$ sudo resolvectl flush-caches ubuntu@lp1849733-d:/etc/systemd/network$ dig +noanswer +noedns toomany.ddstreet.org ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.11.5-P1-1ubuntu2.5-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57527 ;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;toomany.ddstreet.org. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Thu Nov 14 15:21:14 UTC 2019 ;; MSG SIZE rcvd: 678 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1849658 Title: resolved fallback to TCP fails for truncated UDP replies Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] for DNS UDP replies larger than 512 bytes, fallback to TCP is used. For example 'host toomany.ddstreet.org'. Due to a bug in resolved in refcounting DNS stream types, the refcount underflows for type 0 streams (which resolved uses to talk to upstream nameservers), resulting in resolved being unable to fallback to TCP to handle truncated UDP replies. [test case] ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2683 ;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;toomany.ddstreet.org.IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Thu Oct 24 11:40:29 UTC 2019 ;; MSG SIZE rcvd: 678 ubuntu@sf247344-upstream:~$ sudo resolvectl flush-caches ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; connection timed out; no servers could be reached [regression potential] very low, as this only properly sets the stream type in the DnsStream object; any regression would be a failure to be able to use TCP for DNS requests or replies. [other info] https://github.com/systemd/systemd/pull/13838 The commit adding stream types is not present in x/b, so this is needed only for disco and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849658/+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 1843381] Re: Dell system takes a long time to connect network with external dock
Hello Che, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Invalid Bug description: [impact] On Dell system with BIOS-based "MAC passthrough", there can be multiple USB nics with identical MAC addresses. Since the udev rules in Debian and Ubuntu assign interface names for USB nics by mac address (because that is the only consistent identifier for USB nics; their path can change based on which USB port they are connected to), it's impossible to name two interfaces with the same name. As Ubuntu also carries a patch to retry renaming of any interface when the first renaming fails, this causes a 90 second delay before being able to the "MAC passthrough" nic after connecting it. [test case] On a system with this "MAC passthrough" enabled and required devices, boot the system and then connect to the dock or connect the second USB nic with identical MAC. It will not be usable for 90 seconds as its renames takes that long to timeout. [regression potential] the change here is very limited to only Dell systems with the specific USB vendor/product ID affected by this, and additionally the change only sets a ENV flag in the udev rule, which is later used by udevd to skip the rename-retries for 90 seconds. So, the regression potential for anyone else without a system affected by this "MAC passthrough" should be very low, and any regression potential for those with this "MAC passthrough" should still be low, as this only skips the rename- retry that we know will never succeed. However, the regression potential is likely limited to failure to properly name a USB nic, or other bugs during the udev processing of new USB nics. [other info] original description: --- This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This
[Touch-packages] [Bug 1783994] Re: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc
Hello Marc, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1783994 Title: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] on systems with mmc device installed, systemd-gpt-auto-generator fails. [test case] on a system with mmc device installed, run systemd-gpt-auto-generator and check log for: systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error [regression potential] as this is related to boot, regressions might occur at boot, or while modifying or configuring a boot loader. [other info] original description: --- If a device has an mmc installed, systemd-gpt-auto-generator will fail because of "special partition" (rpmb, boot) and record a log message: systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error This issue was discussed here: https://github.com/systemd/systemd/issues/5806 and a fix is proposed for new systemd versions. Please include in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1783994/+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 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc
Hello Steve, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
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/1840640
Title:
sync_file_range fails in nspawn containers on arm, ppc
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Disco:
Fix Committed
Bug description:
[impact]
calling the glibc function sync_file_range() on a armhf nspawn
container fails.
[test case]
see sample C program from original description below. compile and run
that inside a nspawn container on armhf and it will fail.
nspawn instructions:
sudo apt install debootstrap systemd-container
sudo -i
debootstrap --arch=armhf bionic ~/bionic-tree/
systemd-nspawn -D ~/bionic-tree/
[regression potential]
this only adjusts nspawn to allow the sync_file_range2 syscall which
is used on armhf, so the regression potential is very low. any
possible regressions would likely be when calling sync_file_range().
[other info]
original description:
---
ARM has two sync_file_range syscalls, sync_file_range and
sync_file_range2. The former is apparently not used, and glibc calls
the latter whenever a userspace program calls sync_file_range. I'm
guessing systemd-nspawn doesn't know this, because the follow code
consistently fails in an nspawn container on ARM:
#define _GNU_SOURCE
#include
#include
#include
#include
void main()
{
int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
int r=sync_file_range(f, 0, 0, 0);
if (r)
perror("sync_file_range");
close(f);
}
This seems to be causing problems specifically for borg(backup) and
postgres:
https://github.com/borgbackup/borg/issues/4710
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93
The solution should be to cherrypick
https://github.com/systemd/systemd/pull/13352, I am currently waiting
for systemd to rebuild on a slow ARM box. Any chance of an SRU?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu10.24
Uname: Linux 4.14.66+ armv7l
NonfreeKernelModules: extcon_usb_gpio
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: armhf
Date: Mon Aug 19 11:10:48 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+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 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
Hello jrb0001, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Bug description: [impact] an NXDOMAIN response from a dns server when systemd-resolved is configured as DNSSEC=yes breaks dns resolution as it downgrades from DNSSEC. [test case] see comment 9 [regression potential] as with the original patch that introduced this problem, this has the potential to break dns resolution. [other info] original description: I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the following steps: 1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size. 2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit. 3. Ask upstream for SOA of test.asdf. with EDNS0. 4. Ask upstream for SOA of test.asdf. without EDNS0. 5. Repeat 1-4 for DS of test.asdf. 6. Repeat 1-5 for asdf. 7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size. 8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size. The upstream returns an unfragmented NXDOMAIN response for steps 1-6, an unfragmented NOERROR response for step 7 and a fragmented NOERROR response for step 8 which is the correct behaviour. DNSSEC records are included in the response if the DO-bit in the request was set. systemd-resolved should take the response from step 1 and start with validation instead of starting useless retries with reduced feture set. Step 3 and 4 are completely useless and probably lead to the SERVFAIL because I have configured it with DNSSEC=yes to prevent downgrade attacks. This regression seems to be caused by the patch resolved-Mitigate- DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic should only be executed if it is configured as DNSSEC=allow-downgrade or DNSSEC=no. See also https://github.com/systemd/systemd/pull/8608#issuecomment-396927885. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
Hello Neil, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [other info] this fix was included in the initial release of systemd for eoan, but the fix required the additional change in bug 1849608. Both the original patch plus that change (to avoid using bash-specific &>) are included in the b/d patch for this bug. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name
[Touch-packages] [Bug 1832672] Re: systemd-resolve not ignoring comments in /etc/hosts
Hello Bruno, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1832672 Title: systemd-resolve not ignoring comments in /etc/hosts Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] resolved does not ignore comments properly in /etc/hosts [test case] see original description below [regression potential] as this modifies resolved parsing of /etc/hosts, regressions would likely be in hostname lookups from hosts in /etc/hosts, or failure(s) to parse /etc/hosts correctly. [other info] original description: --- $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ LANG=C apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 Candidate: 237-3ubuntu10.22 Version table: *** 237-3ubuntu10.22 500 500 http://ch.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.19 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://mirrors.kernel.org/ubuntu bionic/main amd64 Packages $ head -1 /etc/hosts 127.0.2.1 foo # bar $ /usr/bin/systemd-resolve -4 bar expected -- bar: resolve call failed: 'bar' not found What happened instead - bar: 127.0.2.1 HOSTS(5) > Text from a "#" character until the end of the line is a comment, and is ignored. This is fixed in upstream: https://github.com/systemd/systemd/issues/10779 https://github.com/systemd/systemd/commit/bd0052777981044cf54a1e9d6e3acb1c3d813656 Please backport to current LTS version. I accidentally connected to wrong systems because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832672/+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 1849733] Re: resolved incorrectly limits TCP reply to edns0 payload
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1849733 Title: resolved incorrectly limits TCP reply to edns0 payload Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] glibc's getaddrinfo() uses EDNS0 to talk to resolved, and it sets its payload limit to 1200. When the response is larger than 1200, resolved will limit the response and set the truncate flag. This causes getaddrinfo() to switch to TCP and request again, but glibc incorrectly keeps the EDNS0 RR opt, with the same 1200 payload limit. Most dns nameservers ignore EDNS0 payload limit for TCP, since per RFC it applies only to UDP, but resolved does not and again marks the response as truncated. This prevents getaddrinfo() from being able to resolve any records with a response over 1200 bytes. [test case] use ping or telnet, which use getaddrinfo(), to lookup an A record with a lot of results, like toomany100.ddstreet.org $ telnet toomany100.ddstreet.org telnet: could not resolve toomany100.ddstreet.org/telnet: Temporary failure in name resolution [regression potential] any regression would likely result in failure to correctly lookup a hostname or to provide the correct response to a local client. [other info] note that on Bionic, this also requires backporting TCP pipelining support in the stub resolver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849733/+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 1850704] Re: networkd doesn't set MTUBytes if interface is already up
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1850704 Title: networkd doesn't set MTUBytes if interface is already up Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] if a networkd .network file specifies a [Link] section with MTUBytes=XXX set, networkd will only apply that mtu if the interface is down when networkd starts; if the interface is already up, the mtu won't be applied. [test case] on a bionic system, create a .network file like: [Match] Name=ens8 [Link] MTUBytes= then, reboot. The interface should be set correctly with that mtu: $ ip l show ens8 3: ens8: mtu qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff now, manually change the interface back to 1500 mtu, and restart networkd, then recheck the mtu: $ ip l show ens8 3: ens8: mtu qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff $ sudo ip l set mtu 1500 dev ens8 $ ip l show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff $ sudo systemctl restart systemd-networkd $ ip l show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff [regression potential] low, but any regression would likely involve failure to correctly set the configured mtu. this is needed only in bionic, it's fixed in disco and later already. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1850704/+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 1849658] Re: resolved fallback to TCP fails for truncated UDP replies
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- 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/1849658 Title: resolved fallback to TCP fails for truncated UDP replies Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] for DNS UDP replies larger than 512 bytes, fallback to TCP is used. For example 'host toomany.ddstreet.org'. Due to a bug in resolved in refcounting DNS stream types, the refcount underflows for type 0 streams (which resolved uses to talk to upstream nameservers), resulting in resolved being unable to fallback to TCP to handle truncated UDP replies. [test case] ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2683 ;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;toomany.ddstreet.org.IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Thu Oct 24 11:40:29 UTC 2019 ;; MSG SIZE rcvd: 678 ubuntu@sf247344-upstream:~$ sudo resolvectl flush-caches ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns toomany.ddstreet.org ;; global options: +cmd ;; connection timed out; no servers could be reached [regression potential] very low, as this only properly sets the stream type in the DnsStream object; any regression would be a failure to be able to use TCP for DNS requests or replies. [other info] https://github.com/systemd/systemd/pull/13838 The commit adding stream types is not present in x/b, so this is needed only for disco and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849658/+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 1852591] [NEW] typo in debian/patches/lp1668771-resolved-switch-cache-option-to-a-tri-state-option-s.patch
Public bug reported: [impact] the patch contains a typo, or mis-backport, including both the function definition line as well as a function definition macro, i.e.: int config_parse_resolve_support(const char *unit, const char *filename, unsigned line, const char *section, unsigned section_line, const char *lvalue, int ltype, const char *rvalue, void *data, void *userdata); int config_parse_dnssec_mode(const char *unit, const char *filename, unsigned line, const char *section, unsigned section_line, const char *lvalue, int ltype, const char *rvalue, void *data, void *userdata); +int config_parse_dns_cache_mode(const char *unit, const char *filename, unsigned line, const char *section, unsigned section_line, const char *lvalue, int ltype, const char *rvalue, void *data, void *userdata); + +CONFIG_PARSER_PROTOTYPE(config_parse_resolve_support); +CONFIG_PARSER_PROTOTYPE(config_parse_dnssec_mode); +CONFIG_PARSER_PROTOTYPE(config_parse_dns_cache_mode); The macro isn't defined until later versions of systemd, so including the macro here just results in a build-time warning: In file included from ../src/shared/resolve-util.c:22:0: ../src/shared/resolve-util.h:68:1: warning: data definition has no type or storage class CONFIG_PARSER_PROTOTYPE(config_parse_resolve_support); ^~~ ../src/shared/resolve-util.h:68:1: warning: type defaults to ‘int’ in declaration of ‘CONFIG_PARSER_PROTOTYPE’ [-Wimplicit-int] ../src/shared/resolve-util.h:68:1: warning: parameter names (without types) in function declaration ../src/shared/resolve-util.h:69:1: warning: data definition has no type or storage class CONFIG_PARSER_PROTOTYPE(config_parse_dnssec_mode); ^~~ ../src/shared/resolve-util.h:69:1: warning: type defaults to ‘int’ in declaration of ‘CONFIG_PARSER_PROTOTYPE’ [-Wimplicit-int] ../src/shared/resolve-util.h:69:1: warning: parameter names (without types) in function declaration ../src/shared/resolve-util.h:69:1: warning: redundant redeclaration of ‘CONFIG_PARSER_PROTOTYPE’ [-Wredundant-decls] ../src/shared/resolve-util.h:68:1: note: previous declaration of ‘CONFIG_PARSER_PROTOTYPE’ was here CONFIG_PARSER_PROTOTYPE(config_parse_resolve_support); ^~~ ../src/shared/resolve-util.h:70:1: warning: data definition has no type or storage class CONFIG_PARSER_PROTOTYPE(config_parse_dns_cache_mode); ^~~ ../src/shared/resolve-util.h:70:1: warning: type defaults to ‘int’ in declaration of ‘CONFIG_PARSER_PROTOTYPE’ [-Wimplicit-int] ../src/shared/resolve-util.h:70:1: warning: parameter names (without types) in function declaration ../src/shared/resolve-util.h:70:1: warning: redundant redeclaration of ‘CONFIG_PARSER_PROTOTYPE’ [-Wredundant-decls] ../src/shared/resolve-util.h:69:1: note: previous declaration of ‘CONFIG_PARSER_PROTOTYPE’ was here CONFIG_PARSER_PROTOTYPE(config_parse_dnssec_mode); ^~~ [test case] look at build logs, e.g.: https://launchpadlibrarian.net/444833135/buildlog_ubuntu-bionic-amd64.systemd_237-3ubuntu10.31_BUILDING.txt.gz [regression potential] any regression would likely cause the build to fail. it's unlikely this would cause any runtime regression. [other info] typo introduced in the patch for bug 1668771 ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Bionic) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1852591 Title: typo in debian/patches/lp1668771-resolved-switch-cache-option-to-a -tri-state-option-s.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] the patch contains a typo, or mis-backport, including both the function definition line as well as a function definition macro, i.e.: int config_parse_resolve_support(const char *unit, const char *filename, unsigned line, const char *section, unsigned section_line, const char *lvalue, int ltype, const char *rvalue, void *data, void *userdata); int config_parse_dnssec_mode(const char *unit, const char *filename, unsigned line, const char *section, unsigned section_line, const char *lvalue, int ltype, const char *rvalue, void *data, void *userdata); +int config_parse_dns_cache_mode(const char *unit, const char *filename, unsigned line, const
[Touch-packages] [Bug 1850161] Re: Suggestion: Configure apport (?) to write coredumps for custom applications in working directory
** Package changed: xubuntu-default-settings (Ubuntu) => apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1850161 Title: Suggestion: Configure apport (?) to write coredumps for custom applications in working directory Status in apport package in Ubuntu: New Bug description: - Regarding XUbuntu 19.04 - apport version: 2.20.10-0ubuntu27.1 Current behaviour: == Core dumps of custom software (e.g. self-created software) are not created by default. (It says "core dumped", but actually nothing was created. This is a bug, but not of matter now) To create coredumps within `/var/crash/`, one has to - Create `~/.config/apport/settings` with the following content: [main] unpackaged=true - set ulimit -c unlimited Suggested behaviour: Setup apport (? or whatever package is in charge) to - create core dumps of custom software - inside the current working directory - by default Alternative Suggested behaviour: Setup apport (? or whatever package is in charge) to - create core dumps of custom software - inside the current working directory - after setting `ulimit -c unlimited` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850161/+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 1850161] [NEW] Suggestion: Configure apport (?) to write coredumps for custom applications in working directory
You have been subscribed to a public bug: - Regarding XUbuntu 19.04 - apport version: 2.20.10-0ubuntu27.1 Current behaviour: == Core dumps of custom software (e.g. self-created software) are not created by default. (It says "core dumped", but actually nothing was created. This is a bug, but not of matter now) To create coredumps within `/var/crash/`, one has to - Create `~/.config/apport/settings` with the following content: [main] unpackaged=true - set ulimit -c unlimited Suggested behaviour: Setup apport (? or whatever package is in charge) to - create core dumps of custom software - inside the current working directory - by default Alternative Suggested behaviour: Setup apport (? or whatever package is in charge) to - create core dumps of custom software - inside the current working directory - after setting `ulimit -c unlimited` ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- Suggestion: Configure apport (?) to write coredumps for custom applications in working directory https://bugs.launchpad.net/bugs/1850161 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport 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 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
I can possibly try 19.10 later, however at the moment I only have my LTS laptop to test with. Just to ensure we've covered any variations, here is a redacted version of my connection file, in case I have missed anything. [connection] id=Vxxx uuid=---- type=vpn permissions=user::; timestamp=1572967683 [vpn] auth=SHA512 ca=/home//.cert/nm-openvpn/xxx-ca.pem cert=/home//.cert/nm-openvpn/xxx-cert.pem cert-pass-flags=0 cipher=AES-256-CBC comp-lzo=adaptive connection-type=password-tls dev=tun key=/home//.cert/nm-openvpn/xxx-key.pem password-flags=2 remote=1.vpn..xxx remote-cert-tls=server reneg-seconds=604800 ta=/home//.cert/nm-openvpn/xxx-tls-auth.pem ta-dir=1 username=xx service-type=org.freedesktop.NetworkManager.openvpn [ipv4] dns-priority=50 dns-search= method=auto never-default=true [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto -- 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/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1852578] [NEW] package dictionaries-common 1.26.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13
Public bug reported: Description:Ubuntu 16.04.6 LTS Release:16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dictionaries-common 1.26.3 ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Tue Nov 12 11:54:17 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 ErrorMessage: subprocess installed post-installation script returned error exit status 13 InstallationDate: Installed on 2018-11-15 (364 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: dictionaries-common Title: package dictionaries-common 1.26.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial ** Attachment added: "bugreport.png" https://bugs.launchpad.net/bugs/1852578/+attachment/5305364/+files/bugreport.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1852578 Title: package dictionaries-common 1.26.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 Status in dictionaries-common package in Ubuntu: New Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dictionaries-common 1.26.3 ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Tue Nov 12 11:54:17 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 ErrorMessage: subprocess installed post-installation script returned error exit status 13 InstallationDate: Installed on 2018-11-15 (364 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: dictionaries-common Title: package dictionaries-common 1.26.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1852578/+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 1852578] Re: package dictionaries-common 1.26.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1852578 Title: package dictionaries-common 1.26.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 Status in dictionaries-common package in Ubuntu: New Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dictionaries-common 1.26.3 ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Tue Nov 12 11:54:17 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 ErrorMessage: subprocess installed post-installation script returned error exit status 13 InstallationDate: Installed on 2018-11-15 (364 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: dictionaries-common Title: package dictionaries-common 1.26.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1852578/+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 1831423] Re: Bogus warning message in Net::Ping in Bionic
Thanks for the patch, I tried it and suggest the following instead
(removing the "_" and everything beyond in the Version string) so that
it actually keeps its behaviour for versions prior to 1.94 and in
addition to that I encountered a third location where $Socket::VERSION
is being used inside that file:
--- Ping.pm.orig2016-10-27 14:12:58.0 +0200
+++ Ping.pm 2019-11-14 13:45:56.886072962 +0100
@@ -1798,7 +1798,9 @@
# address check
# new way
- if ($Socket::VERSION >= 1.94) {
+ my $socketVersion = $Socket::VERSION;
+ $socketVersion = $1 if $socketVersion =~ /(\d\.\d+)_\d+/;
+ if ($socketVersion >= 1.94) {
my %hints = (
family => $AF_UNSPEC,
protocol => IPPROTO_TCP,
@@ -1831,7 +1833,7 @@
# resolve
# new way
- if ($Socket::VERSION >= 1.94) {
+ if ($socketVersion >= 1.94) {
my %hints = (
family => $family,
protocol => IPPROTO_TCP
@@ -1908,7 +1910,9 @@
) = @_;
my $ret;
- if ($Socket::VERSION >= 1.94) {
+ my $socketVersion = $Socket::VERSION;
+ $socketVersion = $1 if $socketVersion =~ /(\d\.\d+)_\d+/;
+ if ($socketVersion >= 1.94) {
my ($err, $address) = Socket::getnameinfo($addr, $NI_NUMERICHOST);
if (defined($address)) {
$ret = $address;
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1831423
Title:
Bogus warning message in Net::Ping in Bionic
Status in perl package in Ubuntu:
New
Bug description:
In Ubuntu Bionic's Ping.pm a test of the used socket's version is done
numerically although the Socket.pm's version contains a special
character ("_") which causes this warning message:
Argument "2.020_03" isn't numeric in numeric ge (>=) at
/usr/share/perl/5.26/Net/Ping.pm line 1801, line 755.
Since Socket.pm is part of the same package, the test is not really useful
anymore. I suggest removing it quick'n dirty via the attached patch to get rid
of the warning while conserving the "old way".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1831423/+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 1609700] Re: username is not saved in openconnect connection dialog
Also happening on OpenSUSE Tumbleweed 20191101 -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1851349] Re: Xorg freeze
Seems to be an issue with the graphics drivers. Is it easy to uninstall 100% and go back to default drivers if wanted? Like to have as clean installation as possible but if this helps I might give it a try. https://askubuntu.com/questions/1185491/ubuntu-19-10-freezes-and-lags- reguarly -- 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/1851349 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor now and then. Problem with multitasking. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 10:29:50 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2019-10-18 (17 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851349/+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 1850184] Update Released
The verification of the Stable Release Update for klibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Eoan: Fix Released Status in klibc source package in Focal: Fix Released Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
This bug was fixed in the package klibc - 2.0.6-1ubuntu3 --- klibc (2.0.6-1ubuntu3) eoan; urgency=medium * Pull upstream fixes for losetup issues raised with gcc-9 (LP: #1850184): - loop-header.patch: Switch to using the kernel's UAPI exported loop.h - loop-fixes.patch: Fix some type mismatch warnings from above change. - loop-fixes-2.patch: Fix last type mismatch in code dropped upstream. -- Adam Conrad Wed, 06 Nov 2019 23:15:53 -0700 ** Changed in: klibc (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Eoan: Fix Released Status in klibc source package in Focal: Fix Released Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1851349] Re: Xorg freeze
Problem is still present. Happened when running ClamAV, that took up a lot of memory so that's one thing to change but I had the same setup in 19.04. Can also appear in FireFox (70.0.1, used a lot) when using Twitter. Perhaps a js running away? Will take a closer look in the console next time. I also had VSCode open (runs js right?). I'm not an expert but something around memory and multitasking is wrong in 19.10 that wasn't there in 19.04. Instead of posting all of journalctl what should I look for? Thanks. -- 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/1851349 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor now and then. Problem with multitasking. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 10:29:50 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2019-10-18 (17 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851349/+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
